[ http://jira.codehaus.org/browse/MNG-871?page=comments#action_46628 ]
Brett Porter commented on MNG-871: ---------------------------------- the lack of clarity I meant was that you couldn't tell what the dependency was by looking at it. If type is missing now, it is a JAR. Otherwise, if type is missing, you have to look it up. Is there an outstanding issue with the ear plugin to resolve here, or can I close this req? Thanks! > propagate the type attribute of a pom up to the dependency when dependency > doesn't specify it > --------------------------------------------------------------------------------------------- > > Key: MNG-871 > URL: http://jira.codehaus.org/browse/MNG-871 > Project: Maven 2 > Type: Bug > Components: maven-core > Reporter: Adam Hardy > > > Using maven-ear-plugin, I have two dependencies in my project and I left out > the types when I declared the dependencies. > maven-ear-plugin generated an application.xml descriptor for the EAR file, > but left out the module declarations which it should have generated for the > EJB dependencies, because the dependency types defaulted to JAR. > The dependencies are not updated to reflect the type of the pom associated > with it, and hence type has to be specified, yet it is possible to leave it > out. > However, since the type information is available in the pom, it would be very > convenient if m2 just propagated that back to the dependency. -- 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]
