maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyons, Roy" <>
Subject Re: Eclipse plugin and project references
Date Mon, 25 Feb 2013 19:22:17 GMT
>From my experience to date, it has proven far better to use the m2eclipse
plugin and import the maven project directly.  It will then perform the
build using maven...

When people come to me with issues such as yours, I generally tell them to
delete the project and re-import using m2eclipse (and never use mvn
eclipse:eclipse again) -- and then everything works wonderfully for them.


Roy Lyons

On 2/25/13 11:03 AM, "Stiffler82" <> wrote:

>I have a problem and can not find any support for it, also not in google.
>created my own lib called "core.jar" and when I try to refer it as a
>dependency in from my POM all works fine:
>	<dependency>
>	   <groupId>com.innosquared</groupId>
>	   <artifactId>core</artifactId>
>	   <version>1.1.10</version>
>	</dependency>
>But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
>.project files. It resolves my jar as a java project instead of a jar
>library. The following entry will be created in my classpath:
>  <classpathentry kind="src" path="/core"/>
>In my .projects file there is now:
> <projects>
>    <project>core</project>
>  </projects>
>I do not define anything in my Build-Cycle in POM, so I don't understand
>this strange behaviour. What can I do to prevent Maven from resolving my
>as a java project and resolving it as a normal dependency instead?
>View this message in context:
>Sent from the Maven - Users mailing list archive at
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message