From colum...@gmail.com on August 05, 2008 08:05:40

Labels: -Priority-Medium Priority-Low Milestone-Release1.1 Component-Amp-Archetype

From ealbi...@gmail.com on November 24, 2008 03:29:44

How about this bug? Is it going to be under consideration? thanks in advance.

From colum...@gmail.com on November 24, 2008 03:35:26

I'd like to release soon a 3.0 ready version of archetypes and plugin with this
fixed, but I'm short handed right now.

Maybe you wanna give a hand ? :)

From pmo...@gmail.com on October 28, 2009 11:53:42

One workaround is to temporarily change the packaging to "jar", then run mvn
eclipse:eclipse, then revert the packaging back to "amp". It's a bit of a hassle,
but not as much of a hassle as having to build your Eclipse project definitions from
scratch.

From colum...@gmail.com on December 02, 2009 04:43:12

Is this still an issue

Status: WontFix

From bille...@gmail.com on February 10, 2010 03:55:02

This is still an issue. Could this be a bug/feature in the Maven Eclipse plugin?

From bille...@gmail.com on February 10, 2010 04:02:59

Have done some investigation and found the following issue in the JIRA of Maven
Eclipse: http://jira.codehaus.org/browse/MECLIPSE-90 "version 2.2 will generate a classpath file only for java-capable projects (checking
artifactHandler.getLanguage() ). If you pom specify a custom packaging a classpath
file (and related natures/builders in .project) will not be added"

My guess is that the "amp-packaging" is not considered to be a "java-capable"
project. Maybe we could ask them kindly to accept amp as an accepted packaging type
in future versions?

/Erik

From bille...@gmail.com on March 04, 2010 00:09:14

Posted an issue a while ago http://jira.codehaus.org/browse/MECLIPSE-639