[
https://jira.codehaus.org/browse/MJS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292303#comment-292303
]
Christopher Hunt commented on MJS-45:
-------------------------------------
Sorry for the delay.
There is a general issue with m2e support. We've tried to resolve things with
the m2e committers, but it seems like there's no intrinsic support for what we
want to do.
The detail is that we hook into an early lifecycle event of Maven (which is
public), and m2e does not support it. More info:
http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00866.html
http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00867.html
I'm still not quite sure what to do about m2e going forward.
> Eclipse build fails
> -------------------
>
> Key: MJS-45
> URL: https://jira.codehaus.org/browse/MJS-45
> Project: Maven Javascript Tools
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Mac OS, Eclipse Indigo SR1, with m2e 1.0.100
> Reporter: Nigel
> Assignee: Christopher Hunt
>
> Creating an archetype using :
> mvn archetype:generate -DarchetypeGroupId=org.codehaus.mojo
> -DarchetypeArtifactId=javascript-ria-archetype
> -DarchetypeCatalog=https://nexus.codehaus.org/content/repositories/snapshots/archetype-catalog.xml
> Version (2.0.0-SNAPSHOT)
> Running mvn test from command line results in tests passing.
> However, when imported into Eclipse as an existing maven project, the project
> fails to compile.
> To fix, missing dependencies junit and jstestrunner-junit must be added.
> Not sure why, dependencies aren't resolved within IDE.
> Nigel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
