Hi Graham,
"Upgraded" to 2.4-SNAPSHOT solved the missing .classpath issue :-)
Besides the .classpath issue, the eclipse:eclipse also does some bad
changes to the OSGI manifest file. It tries to "guess" the right bundle
name from the maven artifactId and version, but it gets it wrong (labels
are not accepted in OSGI bundle versions).
I think that maven-eclipse-plugin is a small issue...
The big one is pde-maven-plugin. I have managed to make it build my
empty eclipse feature and plugins, but now when I need to add
dependencies to these plugins it does not add those dependencies to the
compile classpath. Any suggestions?
Thanks,
Adrian.
Graham Leggett wrote:
On Mon, June 11, 2007 5:45 pm, Adrian Herscu wrote:
I have a similar problem...
Added a dependency to my PDE project run mvn eclipse:clean
eclipse:eclipse and only the .project file is generated (without those
linkedResources!). The .classpath file is not generated at all!!!
Moreover, running mvn install on the project fails because the
dependency is not in the classpath :-(
This is a separate problem, fixed in
http://jira.codehaus.org/browse/MECLIPSE-279.
I am trying to get the maven-eclipse-plugin to a state where it a) works
and is b) documented, but this is turning out to be a bit of a nightmare.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
