You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Archimedes Trajano (JIRA)" <ji...@codehaus.org> on 2006/03/23 23:06:11 UTC
[jira] Commented: (MECLIPSE-83) ear projects should not be java
projects
[ http://jira.codehaus.org/browse/MECLIPSE-83?page=comments#action_61813 ]
Archimedes Trajano commented on MECLIPSE-83:
--------------------------------------------
The following code block should not be present in the .project file
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments/>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
The only reason I would see is if you want to put JUnit test cases for integration testing on the EAR, but I am not sure if that's the right place to do such a thing. It might be better to have a separate project for integration testing? Or at least detect that the user would want integration testing code in the EAR project.
> ear projects should not be java projects
> ----------------------------------------
>
> Key: MECLIPSE-83
> URL: http://jira.codehaus.org/browse/MECLIPSE-83
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.1
> Environment: Eclipse 3.1.2
> Reporter: Archimedes Trajano
>
>
> Given a POM with
> <packaging>ear</packaging>
> It should create an Enterprise Application project rather than a standard java project.
--
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