[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_47130 ]
Brett Porter commented on MNG-699: ---------------------------------- I trust your ability to review the patch, I'll just complain later if I see anything I don't like ;) Why would you want to delegate application.xml generation? That would only be something in the EAR, right? Actually the relationship should be: - plexus-archiver has everything possible shared (so EarArchiver might deal with application.xml?) - maven-archiver is a layer on that that can translate MavenProject to plexus-archiver and has shared stuff amongst mojos - mojo is configuration -> maven-archiver bridge. > 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]
