Hi all,
I have been having an interesting time trying to get some eclipse plugin
code built with maven, and I would like to check whether a number of
assumptions made by maven-eclipse-plugin are still valid against modern
copies of Eclipse.
When maven-eclipse-plugin creates the .project file, entries such as the
following are created to refer to jar dependencies:
<linkedResources>
<link>
<name>abbot-0.13.0.jar</name>
<type>1</type>
<location>C:/[path]/.m2/repository/abbot/abbot/0.13.0/abbot-0.13.0.jar</location>
</link>
...
When an attempt is made to build code using the eclipse IDE, the classpath
is picked up correctly, and code that depends on these linked dependencies
builds and runs correctly.
However: As soon as an attempt is made to export the plugin using the
Eclipse export plugin wizard, these linked dependencies are ignored.
The linked dependencies do not show up in the final plugin build, the log
of the plugin export process is full of java compile errors about missing
packages caused by these missing jars.
So, the question is: Does the "link" method as shown above still work in
Eclipse v3.2.x, and is maven-eclipse-plugin producing a bogus .project
file?
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
