[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=comments#action_79318
]
Daniel Schulz commented on MNGECLIPSE-30:
-----------------------------------------
i found the reason for the "${pom.version} is 2.4.1" problem (for more details
and a fix see MNGECLIPSE-20). there is a system property of name "version" set
to "2.4.1" in your eclipse jvm (see [Eclipse]->Help->About Eclipse
Platform->Configuration Details).
> Maven plugin keeps looking for non-existent apacheds-*-2.4.1 dependency
> -----------------------------------------------------------------------
>
> Key: MNGECLIPSE-30
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-30
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.3
> Environment: Mac OS X, Eclipse 3.1.1, Plugin v0.0.3
> Reporter: Federico Sauter
> Assigned To: Eugene Kuleshov
> Fix For: 0.0.10
>
> Attachments: MNGECLIPSE-30.launcher.log, mvn_test-output.txt,
> plugin-test.zip, pom.xml
>
>
> When using the plugin in the mentioned environment it is impossible to build
> the project. The error message states that there was a dependency the plugin
> was not able to find in any repository, namely apacheds-shared or
> apacheds-core, version 2.4.1. Of course there is no such library in the
> respository and there is no pom file referencing it.
> Having read http://jira.codehaus.org/browse/MNGECLIPSE-20 I tried to
> eliminate all version references from ${pom.version} to an actual versino
> number, but the error persisted. I am posting this as a bug, since I do not
> understand what is going wrong and where the plugin got that version number
> (2.4.1).
--
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
