You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Scott Cytacki (JIRA)" <ji...@codehaus.org> on 2006/05/19 20:14:41 UTC
[jira] Updated: (MNGECLIPSE-103) Multiple projects launch
configuration name collision
[ http://jira.codehaus.org/browse/MNGECLIPSE-103?page=all ]
Scott Cytacki updated MNGECLIPSE-103:
-------------------------------------
Attachment: maven-plugin-launch-bug.zip
> Multiple projects launch configuration name collision
> ------------------------------------------------------
>
> Key: MNGECLIPSE-103
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-103
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Versions: 0.0.5
> Environment: eclipse 3.2M5a
> Reporter: Scott Cytacki
> Assignee: Eugene Kuleshov
> Priority: Minor
> Attachments: maven-plugin-launch-bug.zip
>
>
> Context:
> I have three eclipse projects with depencencies: A -> B -> C
> Each project depends on several jars declared in a pom.xml.
> Using the maven2 plugin there is a "Maven2 Dependencies" library in each project.
> From the poms, I've removed the B depency from A, and the C dependency from B. And I've added these dependencies in the eclipse project.
> Problem:
> When I try to run a class in project A from eclipse it is very difficult to construct the runtime classpath. This is setup in the "Classpath" tab of the Run dialog.
> If the "Maven2 Dependencies" is exported from projects B and C. Then adding those projects to this classpath should also add the Maven2 Dependencies library. What actually happens is that only one Maven2 library is added.
> I was able to make this work by saving the a launch configuration I was configuring and modifying the launcit by hand. The launch file can be saved though the "shared file" option in the common tab.
> My guess is that Run Classpath dialog requires the name of libraries to be unique.
> One solution:
> It seems that if the the name of the Maven2 Depedencies library had the name of the project appended or prepended then creating launch configurations would be possible through the gui instead of editing the launch configuration file directly.
--
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