[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_49729 ]
Stephane Nicoll commented on MNG-699: ------------------------------------- Nothing, I just need to make sure that trygvis has committed the new lifecycle in maven-core for par and ejb3. The plugins are in the sandbox, ready to be moved to the main plugins directory. That said, I must say that the plugins in MOJO-98 / MOJO-99 seems more complete to me that what we have in the sandbox. If we had to choose between those too, I would take the ones on the MOJO-side. Is there any rule regarding plugin's locations? That would be good if all J2EE stuff would be on one location, wouldn't it? Let me know and I'll finish this. > Add EJB3 support in a plugin > ---------------------------- > > Key: MNG-699 > URL: http://jira.codehaus.org/browse/MNG-699 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Piotr Bzdyl > Assignee: Stephane Nicoll > Priority: Minor > Attachments: JarMojo.java-patch, maven2-ejb3-support.zip > > > Please, provide possibility to generate artifact with extension other than > 'jar' only. It is not possible to set the project (artifactId = example) > artifact type i.e. to 'par' (persistance archive) or 'ejb3' and get > example.par or example.ejb3 - jar plugin will always generate *.jar files. > There is no way to change this behaviour via plugin properties - jar > extension is hardcoded in the plugin source code. > IMHO it would be better to generate default file extension based on the > project artifact ID or let it to specify via plugin properties. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
