Quantcast

[jira] Created: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Created: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
Maven dependencies are ignored when maven enabled project is included
---------------------------------------------------------------------

                 Key: MNGECLIPSE-341
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Dependency Resolver
    Affects Versions: 0.0.9
         Environment: linux, eclipse 3.2.2 M20070212-1330
            Reporter: Achim Abeling
            Priority: Minor
         Attachments: eclipsemavenbug.tar.gz

I have two maven enabled projects: A and B.

A has a dependency to e.g. commons-lang.
B has a dependency to e.g. commons-logging.

A has project B as a required project.

When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.

This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
It shows (in my testcase):
/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin

My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97345 ]

Achim Abeling commented on MNGECLIPSE-341:
------------------------------------------

Same problem with 0.0.10.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97347 ]

Stefan Seidel commented on MNGECLIPSE-341:
------------------------------------------

WFM:
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}
Version 0.0.11

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Issue Comment Edited: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97347 ]

Stefan Seidel edited comment on MNGECLIPSE-341 at 5/29/07 5:10 AM:
-------------------------------------------------------------------

WFM:
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}
Version 0.0.11
But it looks like your sample projects are not as you described them - neither does depend on the other.


 was:
WFM:
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}
Version 0.0.11

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Issue Comment Edited: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97347 ]

Stefan Seidel edited comment on MNGECLIPSE-341 at 5/29/07 5:14 AM:
-------------------------------------------------------------------

WFM:
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}
Version 0.0.11
But it looks like your sample projects are not as you described them - neither does depend on the other.
When adding
{code}
    <dependency>
      <groupId>de.freenet</groupId>
      <artifactId>eclipsemavenbug2</artifactId>
      <version>0.0.1</version>
    </dependency>
{code}
to project 1 I get
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/srv1/stefan/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/srv1/stefan/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/srv1/stefan/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/srv1/stefan/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}


 was:
WFM:
{code}
/home/stefan/workspace/eclipsemavenbug1/target/classes:/home/srv1/stefan/.m2/repository/commons-lang/commons-lang/1.0/commons-lang-1.0.jar:/home/srv1/stefan/.m2/repository/junit/junit/3.7/junit-3.7.jar
{code}
Version 0.0.11
But it looks like your sample projects are not as you described them - neither does depend on the other.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97351 ]

Achim Abeling commented on MNGECLIPSE-341:
------------------------------------------

The dependency of eclipsemavenbug2 to eclipsemavenbug1 is not defined in the pom.xml but only in Eclipse via the "Projects" tab in the "Java Build Path" configuration.

I know that is not the way maven should be used but I currently have no other choice.

You can see the dependency in eclipsemavenbug1/.class. There is an entry
<classpathentry combineaccessrules="false" kind="src" path="/eclipsemavenbug2"/>



> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Achim Abeling updated MNGECLIPSE-341:
-------------------------------------

    Attachment: eclipsemavenbug.tar.gz

The test class in eclipsemavenbug1 now tries to load a class of eclipsemavenbug2.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97355 ]

Achim Abeling commented on MNGECLIPSE-341:
------------------------------------------

Still does not work for me with 0.0.11.20070304-1200.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97357 ]

Stefan Seidel commented on MNGECLIPSE-341:
------------------------------------------

I still don't see the problem. I import the projects. Run Maven -> Update source folders on both. Add eclipsemavenbug2 to the required project list of eclipsemavenbug1. Clean all projects, build, run, works, class is found and classpath is ok.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97360 ]

Achim Abeling commented on MNGECLIPSE-341:
------------------------------------------

Did you change the class path order such that
eclipsemavenbug2 is before the maven dependencies of eclipsemavenbug1?

The .classpath file of eclipsemavenbug1 should look like
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
        <classpathentry kind="src" path="src/main/java"/>
        <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
        <classpathentry combineaccessrules="false" kind="src" path="/eclipsemavenbug2"/>
        <classpathentry kind="output" path="bin"/>
</classpath>

If eclipsemavenbug2 is after the maven dependencies everything is fine, yes.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Issue Comment Edited: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97360 ]

Achim Abeling edited comment on MNGECLIPSE-341 at 5/29/07 6:23 AM:
-------------------------------------------------------------------

Did you change the class path order such that
eclipsemavenbug2 is before the maven dependencies of eclipsemavenbug1?

The .classpath file of eclipsemavenbug1 should look like
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
        <classpathentry kind="src" path="src/main/java"/>
        <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        <classpathentry combineaccessrules="false" kind="src" path="/eclipsemavenbug2"/>
        <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
        <classpathentry kind="output" path="bin"/>
</classpath>

If eclipsemavenbug2 is after the maven dependencies everything is fine, yes.


 was:
Did you change the class path order such that
eclipsemavenbug2 is before the maven dependencies of eclipsemavenbug1?

The .classpath file of eclipsemavenbug1 should look like
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
        <classpathentry kind="src" path="src/main/java"/>
        <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
        <classpathentry combineaccessrules="false" kind="src" path="/eclipsemavenbug2"/>
        <classpathentry kind="output" path="bin"/>
</classpath>

If eclipsemavenbug2 is after the maven dependencies everything is fine, yes.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97361 ]

Stefan Seidel commented on MNGECLIPSE-341:
------------------------------------------

My classpath in mavenbug1 is
{code}
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
        <classpathentry combineaccessrules="false" kind="src" path="/eclipsemavenbug2"/>
        <classpathentry kind="src" path="src/main/java"/>
        <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
        <classpathentry kind="output" path="bin"/>
</classpath>
{code}
Anyway, I don't think this is an issue of the plugin. The Maven2ClasspathContainer is still fine even with the classpathentry item order like in your example. Just use maven dependencies and everything will be fine.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97365 ]

Achim Abeling commented on MNGECLIPSE-341:
------------------------------------------

And you can't reproduce the problem with these classpath settings?

Ok, my problem description is misleading. The Maven2ClasspathContainer in eclipsemavenbug1 is fine.
But when the test application is executed from within eclipse the maven dependencies of mavenbug1 are obviously missing.

Using maven dependencies does not solve the problem in my situation.
Suppose that eclipsemavenbug2 is already a maven dependency in eclipsemavenbug1.
But eclipsemavenbug2 has changes in subversion which I want to test. These changes are not released yet.
So I have to use my working copy of eclipsemavenbug2 and change the class path order such that the working copy comes before
the release jar.
My workaround at the moment is to comment the dependency in eclipsemavenbug1 and have
eclipsemavenbug2 as a required project coming behind the maven dependencies in the class path order.




> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97367 ]

Stefan Seidel commented on MNGECLIPSE-341:
------------------------------------------

In 0.0.11, this behaviour has changed. Dependencies are now always resolved from workspace if they are present there, no matter if there is another version in the repository.

This here seems more like a real eclipse bug unless there is some rule about ordering of classpathentries that I don't know.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100080 ]

M. Rohrmoser commented on MNGECLIPSE-341:
-----------------------------------------

I have the same issue here. Eclipse resolves a dependency to a fellow-project and I can't have it refer to the jar (from the m2 repo).

How can I control this behaviour?

Greetings,
    M

P.S.: I don't consider this to be irrelevant but a real and serious bug.


> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100086 ]

Eugene Kuleshov commented on MNGECLIPSE-341:
--------------------------------------------

M, out of curiosity, why would you want to use something from repository if there is a project in the workspace?

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100130 ]

M. Rohrmoser commented on MNGECLIPSE-341:
-----------------------------------------

Hm, yes - to develop project B against a dedicated, stable version of project A.

Aside of this it's a little bit annoying to not have this kind of control over the dependencies. Even if project A is closed and/or maven disabled or deleted project B still wants to use the project dependency (after Refresh/Clean/Close-Open/Eclipse-Restart/Update-Sources/Maven-disable-enable etc.).

:-(

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100161 ]

Eugene Kuleshov commented on MNGECLIPSE-341:
--------------------------------------------

> Hm, yes - to develop project B against a dedicated, stable version of project A.

Project dependency resolution is picking up exact version. So, all you need is to make sure that dependency in workspace is not the same version.

> Aside of this it's a little bit annoying to not have this kind of control over the dependencies.

I just convinced that such control could be dangerous, and the next thing you'll complain about is that you couldn't step trough the source code for the jar from repository, which is not an issue if dependency is picked up from the workspace.
Anyways, there is a separate issue that is requesting manual control how dependencies are resolved.

> Even if project A is closed and/or maven disabled or deleted project B still wants to use the
> project dependency (after Refresh/Clean/Close-Open/Eclipse-Restart/Update-Sources/Maven-disable-enable etc.).

Sounds like a bug. Please open a separate bug report for that and provide complete test projects and other information (i.e. Eclipse version) that would be sufficient to reproduce this issue. Thing is that it does work for me in builds after 0.0.10

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100178 ]

M. Rohrmoser commented on MNGECLIPSE-341:
-----------------------------------------

Hi Eugene,
I agree on the dangers (fiddling with dependencies almost never is a good idea) and will check the "Project closed" behaviour (>0.0.10) and open a new bug in case.

Thanks a lot & greetings,
    M

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Closed: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kuleshov closed MNGECLIPSE-341.
--------------------------------------

    Resolution: Fixed

It doesn't seem anything left here. please feel free to reopen if I missed something.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-341
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>         Environment: linux, eclipse 3.2.2 M20070212-1330
>            Reporter: Achim Abeling
>            Priority: Minor
>         Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Loading...