[ http://jira.codehaus.org/browse/MNGECLIPSE-196?page=all ]
Tuomas Kiviaho updated MNGECLIPSE-196:
--------------------------------------
Attachment: DudeWhereIsMyCar.pom
Car.pom
Attached two pom.xml that represent Eclipse workspace projects. When type ejb
is removed from the depencency the dependent project starts appearing in the
classpath container.
> Dependency with ejb type doesn't appead in classpath container at all when
> dependent project is located at Eclipse workspace
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-196
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-196
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.0.10
> Reporter: Tuomas Kiviaho
> Attachments: Car.pom, DudeWhereIsMyCar.pom
>
>
> The user experience with typed dependencies differs from previous releases
> that didn't include workspace resolving. I've only verified that type ejb
> behaves as described below but I could imagine that other types and propably
> classified dependencies as well will behave similarly.
> Console contains following line:
> <artifact>:pom:<version>: resolved to Eclipse workspace - found at
> <workspace>\<project>\pom.xml
> This leads to "The import <class> cannot be resolved" error on every single
> class reference pointing to dependent workspace project and these classes do
> not compile. The whole dependent project is missing from the classpath
> container. The previous version of the plugin did resolve the dependency from
> repository without any problems whatsoever.
> When type specification is removed the result is:
> <artifact>:jar:<version>: resolved to Eclipse workspace - found at
> <workspace>\<project>\pom.xml
> Now references appear to be ok, but the pom.xml is of course not correct
> anymore. Claspath container contains the dependent project, but since the
> workspace projects do not fold open as the repository dependencies I can't
> tell wether or not the hack is really working 100%. It would be great if
> there is a way to make workspace project dependencies to fold open at least
> as far as seeing the source folders as we do under Debug As... and on
> Sources panel.
--
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
