[
http://jira.codehaus.org/browse/MECLIPSE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108938
]
Frank Cornelis commented on MECLIPSE-94:
----------------------------------------
As Vincent commented, generating a .project file for POM projects that do not
have leaf projects is indeed quite useful.
I have several POM leaf project:
- documentation projects, i.e., they only contain sites.
- assembly projects, i.e. they package things into ZIP files via the
maven-assembly-plugin
The boring thing is that these projects are not visible from within Eclipse
right now.
For my documentation projects the simple workaround is to change the artifact
type to JAR. This makes the project to generate an empty JAR but at least it's
visible/editable from within Eclipse.
As for the assembly projects, there is no easy way around here... so I cannot
access these easily from within Eclipse.
> Allow eclipse:eclipse to work on pom (and other) projects
> ---------------------------------------------------------
>
> Key: MECLIPSE-94
> URL: http://jira.codehaus.org/browse/MECLIPSE-94
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Felipe Leme
>
> I'm creating a Java EE project based on the m2book (which I was reviewing;
> it's not available yet...) and one of the projects is a pom-packaging project
> used for integration tests. According to Vincent, currently this project must
> be a pom (in fact, I tried to set it as jar, but then the test phase would be
> run anyway, which would cause the tests to fail), as it doesn't produces a
> jar. But as it has java files (on the src/main/it/java directory), I tried to
> call eclipse:eclipse but it fails, saying that "Not running eclipse plugin
> goal for pom project".
> For these scenarios, I think a propery would be enough. At first I thought
> something about a 'force' or 'forceGeneration' property, would enough, which
> the code change being from:
> if ( "pom".equals( packaging ) && eclipseProjectDir == null )
> to:
> if ( "pom".equals( packaging ) && eclipseProjectDir == null &&
> !forceGeneration )
> Then I realized there is other place where the pom nature is checked:
> if ( "pom".equals( packaging ) && eclipseProjectDir == null &&
> !forceGeneration )
> So, I think a better name for the property would be 'javaProject' and the
> change would be:
> final boolean isJavaProjectProperty = // read property; defaults to false...
> if ( "pom".equals( packaging ) && eclipseProjectDir == null &&
> !isJavaProjectProperty )
> isJavaProject = isJavaProjectProperty || !"ear".equals( packaging ) &&
> !"pom".equals( packaging );
> If nobody objects and someone is willing to apply the changes, I can provide
> such patch (with the proper test cases).
> -- Felipe
> PS: I'm assigning it to Vincent for now, as he 'dreamed' that such features
> already existed :-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
