[ http://jira.codehaus.org/browse/MNGECLIPSE-103?page=all ]
Eugene Kuleshov closed MNGECLIPSE-103.
--------------------------------------
Resolution: Fixed
Fix Version/s: 0.0.10
With changes in a trunk from MNGECLIPSE-59, this doesn't seem to be an issue
anymore. Scott, please reopen if you think there is something else need to be
done with this. Thanks.
> Multiple projects launch configuration name collision
> ------------------------------------------------------
>
> Key: MNGECLIPSE-103
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-103
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.5
> Environment: eclipse 3.2M5a
> Reporter: Scott Cytacki
> Priority: Minor
> Fix For: 0.0.10
>
> 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
