[jira] Created: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

JIRA jira@codehaus.org
Workspace dependencies not added to classpath container for WST dynamic web projects
------------------------------------------------------------------------------------

                 Key: MNGECLIPSE-438
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Dependency Resolver
    Affects Versions: 0.0.12
         Environment: eclipse europa jee fall (3.3.1), windows xp
            Reporter: Mark Hewett
         Attachments: m2eclipse-bug.zip

If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.

I'm attaching a set of projects to demonstrate the problem:

ProjOne - a Java/JAR project
ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up

If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.

Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.

                <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
                <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>


--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

JIRA jira@codehaus.org

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

Olivier LE MERDY commented on MNGECLIPSE-438:
---------------------------------------------

h4. Further consideration

I got the very same issue reported here, on both Linux and Windows platforms. I played a bit further with project properties and created different types of WTP projects:
* Utility module with Maven artifact package set to "jar"
* EJB module with Maven artifact package set to "ejb"
* Application module with Maven artifact package set to "jar"
* Web module with Maven artifact package set to "war"

All these projects have exactly the same .project files (but, of course, project name) with the same builders. Interestingly enough, the only project that cannot resolve artifacts corresponding to open projects is the web module one.

Playing with installed facets (for example removing Web facet and adding Utility one) does not change anything to the problem. However changing the owning artifact package does the trick! If you simply switch package type from "war" to "jar" in the Web module pom.xml (even if it does not make sens ;)), the artifact is automagically resolve from the project.

h4. Test case

So here is the test case:
* Create a Java project "ProjectJar" with a maven packaging of "jar"
* Create a Dynamic Web Project "ProjectWar" with a maven packaging of "war"
* Add "ProjectJar" to "ProjectWar" maven dependencies and check it is not resolved at all (neither from repository nor workspace)
* Close "ProjectJar" and check it is resolved from repository (assuming you mvn-installed ProjectJar)
* Re-open the project and switch ProjectWar packaging from "war" to "jar" in its pom.xml
* Check the dependency resolves from workspace!

There is obviously an issue with handling of "war" projects combined with facets...

h4. Criticity

As of me, this bug is a really serious one. Working on a Web project using multiple artifacts/Eclipse project makes me opening, closing and installing artifacts all the time in order to make the web-app project compile with latest changes from depending modules. A bug fix would be truly appreciated :) . Please ask if further test is needed.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Eugene Kuleshov commented on MNGECLIPSE-438:
--------------------------------------------

Oliver, can you please attach your test projects to this issue. Thanks.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Updated: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Olivier LE MERDY updated MNGECLIPSE-438:
----------------------------------------

    Attachment: m2eclipse-test-packaging.zip

This file contains two Eclipse projects:
- TestJar (packaged as "jar")
- TestWar (packaged as "war") depending on the first

Import these trwo projects into your workspace. TestWar should not compile and TestJar should not be included in its Maven depencies.
Mvn-install the two projects thanks to the parent pom and then close TestJar. TestWar should now resolve TestJar from repository and compile.
Reopen TestJar and change packaging from "war" to "jar" in TestWar pom.xml. TestWar should now resolve TestJar from workspace!

This last fact signifies you can work almost normally by changing the Web modules from "war" to another type of packaging but this workaround is really dangerous as you could put an incorrectly typed pom.xml in your control version system and generate bad applications.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Issue Comment Edited: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

olemerdy edited comment on MNGECLIPSE-438 at 1/8/08 1:32 PM:
---------------------------------------------------------------------

[This file|http://jira.codehaus.org/secure/attachment/31717/m2eclipse-test-packaging.zip] contains two Eclipse projects:
- TestJar (packaged as "jar")
- TestWar (packaged as "war") depending on the first

Import these trwo projects into your workspace. TestWar should not compile and TestJar should not be included in its Maven depencies.
Mvn-install the two projects thanks to the parent pom and then close TestJar. TestWar should now resolve TestJar from repository and compile.
Reopen TestJar and change packaging from "war" to "jar" in TestWar pom.xml. TestWar should now resolve TestJar from workspace!

This last fact signifies you can work almost normally by changing the Web modules from "war" to another type of packaging but this workaround is really dangerous as you could put an incorrectly typed pom.xml in your control version system and generate bad applications.

      was (Author: olemerdy):
    This file contains two Eclipse projects:
- TestJar (packaged as "jar")
- TestWar (packaged as "war") depending on the first

Import these trwo projects into your workspace. TestWar should not compile and TestJar should not be included in its Maven depencies.
Mvn-install the two projects thanks to the parent pom and then close TestJar. TestWar should now resolve TestJar from repository and compile.
Reopen TestJar and change packaging from "war" to "jar" in TestWar pom.xml. TestWar should now resolve TestJar from workspace!

This last fact signifies you can work almost normally by changing the Web modules from "war" to another type of packaging but this workaround is really dangerous as you could put an incorrectly typed pom.xml in your control version system and generate bad applications.
 

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Issue Comment Edited: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

olemerdy edited comment on MNGECLIPSE-438 at 1/8/08 1:35 PM:
---------------------------------------------------------------------

h4. Versions used
Eclipse 3.3.1 for both Linux and Windows.
m2eclipse 0.0.12
WST 2.0.1

h4. Further consideration

I got the very same issue reported here, on both Linux and Windows platforms. I played a bit further with project properties and created different types of WTP projects:
* Utility module with Maven artifact package set to "jar"
* EJB module with Maven artifact package set to "ejb"
* Application module with Maven artifact package set to "jar"
* Web module with Maven artifact package set to "war"

All these projects have exactly the same .project files (but, of course, project name) with the same builders. Interestingly enough, the only project that cannot resolve artifacts corresponding to open projects is the web module one.

Playing with installed facets (for example removing Web facet and adding Utility one) does not change anything to the problem. However changing the owning artifact package does the trick! If you simply switch package type from "war" to "jar" in the Web module pom.xml (even if it does not make sens ;)), the artifact is automagically resolve from the project.

h4. Test case

So here is the test case:
* Create a Java project "ProjectJar" with a maven packaging of "jar"
* Create a Dynamic Web Project "ProjectWar" with a maven packaging of "war"
* Add "ProjectJar" to "ProjectWar" maven dependencies and check it is not resolved at all (neither from repository nor workspace)
* Close "ProjectJar" and check it is resolved from repository (assuming you mvn-installed ProjectJar)
* Re-open the project and switch ProjectWar packaging from "war" to "jar" in its pom.xml
* Check the dependency resolves from workspace!

There is obviously an issue with handling of "war" projects combined with facets...

h4. Criticity

As of me, this bug is a really serious one. Working on a Web project using multiple artifacts/Eclipse project makes me opening, closing and installing artifacts all the time in order to make the web-app project compile with latest changes from depending modules. A bug fix would be truly appreciated :) . Please ask if further test is needed.

      was (Author: olemerdy):
    h4. Further consideration

I got the very same issue reported here, on both Linux and Windows platforms. I played a bit further with project properties and created different types of WTP projects:
* Utility module with Maven artifact package set to "jar"
* EJB module with Maven artifact package set to "ejb"
* Application module with Maven artifact package set to "jar"
* Web module with Maven artifact package set to "war"

All these projects have exactly the same .project files (but, of course, project name) with the same builders. Interestingly enough, the only project that cannot resolve artifacts corresponding to open projects is the web module one.

Playing with installed facets (for example removing Web facet and adding Utility one) does not change anything to the problem. However changing the owning artifact package does the trick! If you simply switch package type from "war" to "jar" in the Web module pom.xml (even if it does not make sens ;)), the artifact is automagically resolve from the project.

h4. Test case

So here is the test case:
* Create a Java project "ProjectJar" with a maven packaging of "jar"
* Create a Dynamic Web Project "ProjectWar" with a maven packaging of "war"
* Add "ProjectJar" to "ProjectWar" maven dependencies and check it is not resolved at all (neither from repository nor workspace)
* Close "ProjectJar" and check it is resolved from repository (assuming you mvn-installed ProjectJar)
* Re-open the project and switch ProjectWar packaging from "war" to "jar" in its pom.xml
* Check the dependency resolves from workspace!

There is obviously an issue with handling of "war" projects combined with facets...

h4. Criticity

As of me, this bug is a really serious one. Working on a Web project using multiple artifacts/Eclipse project makes me opening, closing and installing artifacts all the time in order to make the web-app project compile with latest changes from depending modules. A bug fix would be truly appreciated :) . Please ask if further test is needed.
 

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Holger Brands commented on MNGECLIPSE-438:
------------------------------------------

We've also run into this issue, now.
We want to integrate a maven project with packaging war with Eclipse dynamic web project.
As the last comment states, when you change packaging in the pom.xml from war to jar, the dependencies are resolved from workspace.
(with packaging war *not*).

But, we also want to use the "Run on Server" feature of  WTP, so we'd like to publish the project via WTP to the configured tomcat instance.
But even if the dependencies are resolved from workspace by changing war to jar packaging, these dependencies are not published by WTP
to the server.
I have to close all dependent projects such that the dependencies are resolved as jar files. Only in this case, the dependency jars are deployed by WTP.



> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Matthew Lieder commented on MNGECLIPSE-438:
-------------------------------------------

Holger, we also have run across that issue. Until m2eclipse fixes it, our current work-around is to create source links (Project Properties -> Java Build Path -> Source -> Link Source) to the dependency projects. That does the trick pretty nicely.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Mark Hewett commented on MNGECLIPSE-438:
----------------------------------------

The WTP integration article on the Wiki (http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+WTP) shows what may be the best solution at the moment - adding a J2EE Module Dependency entry for the missing projects.  This should get WTP to deploy the dependent projects.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Matthew Lieder commented on MNGECLIPSE-438:
-------------------------------------------

Unfortunately my dependency projects don't show on that list, and there's no "Add Project" button :/

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Updated: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

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

Eugene Kuleshov updated MNGECLIPSE-438:
---------------------------------------

    Component/s:     (was: Dependency Resolver)
                 WTP integration

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: WTP integration
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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
|

[jira] Commented: (MNGECLIPSE-438) Workspace dependencies not added to classpath container for WST dynamic web projects

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

    [ http://jira.codehaus.org/browse/MNGECLIPSE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130946#action_130946 ]

Michael Reardon commented on MNGECLIPSE-438:
--------------------------------------------

Also the J2EE Module Dependencies workaround from the Wiki, does not work for Eclipse features that do not use WTP. For example, launching JUnits.

> Workspace dependencies not added to classpath container for WST dynamic web projects
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-438
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-438
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: WTP integration
>    Affects Versions: 0.0.12
>         Environment: eclipse europa jee fall (3.3.1), windows xp
>            Reporter: Mark Hewett
>         Attachments: m2eclipse-bug.zip, m2eclipse-test-packaging.zip
>
>
> If a project dependency for a dynamic web project is also an open workspace project, then the dependency is not added to the maven classpath container.
> I'm attaching a set of projects to demonstrate the problem:
> ProjOne - a Java/JAR project
> ProjTwo - a Java/JAR project that depends on ProjOne - the dependency shows up OK
> ProjThree - a dynamic web project/WAR that depends on ProjOne - the dependency does not show up
> If ProjOne is installed in the local repository, and then closed, ProTwo and ProjThree will both correctly resolve the dependency to the JAR from the repository.
> Also, if the following lines are removed from the ProjThree's .project file, and the project is cleaned (with ProjOne open), the dependency will resolve correctly to the workspace project.
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>

--
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