search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Cannot generate eclipse project files from maven-alfresco-amp-archetype #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Calling mvn eclipse:eclipse generates an empty .project file and no
.classpath file.

Original issue reported on code.google.com by damonr...@gmail.com on 14 Jul 2008 at 3:09

GoogleCodeExporter commented 9 years ago

Original comment by colum...@gmail.com on 5 Aug 2008 at 3:05

GoogleCodeExporter commented 9 years ago 
How about this bug? Is it going to be under consideration? thanks in advance.

Original comment by ealbi...@gmail.com on 24 Nov 2008 at 11:29

GoogleCodeExporter commented 9 years ago 
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 ? :)

Original comment by colum...@gmail.com on 24 Nov 2008 at 11:35

GoogleCodeExporter commented 9 years ago 
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.

Original comment by pmo...@gmail.com on 28 Oct 2009 at 6:53

GoogleCodeExporter commented 9 years ago 
Is this still an issue

Original comment by colum...@gmail.com on 2 Dec 2009 at 12:43

GoogleCodeExporter commented 9 years ago 
This is still an issue. Could this be a bug/feature in the Maven Eclipse plugin?

Original comment by bille...@gmail.com on 10 Feb 2010 at 11:55

GoogleCodeExporter commented 9 years ago 
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

Original comment by bille...@gmail.com on 10 Feb 2010 at 12:02

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

Original comment by bille...@gmail.com on 4 Mar 2010 at 8:09