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,
Hi,
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
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,
On 6/11/07, Graham Leggett [EMAIL PROTECTED] 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
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
Tom Huybrechts wrote:
Generating PDE projects is much different from ordinary projects. PDE
handles the classpath and interproject dependencies itself. Maven
should never generate these, and certainly not try to link to a jar in
the local repository. For external dependencies, you should think
