[jira] Commented: (MNG-871) propagate the type attribute of a pom up to the dependency when dependency doesn't specify it

["Brett Porter (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-871?page=comments#action_46476 ] 

Brett Porter commented on MNG-871:
----------------------------------

I'm inclined to mark WON'T FIX.

Yes, it will work - but issues I see:
1) lack of clarity
2) won't work with a legacy repository
3) we currently have an issue where packaging != type in some circumstances.

How much inconvenience do you believe this causes?

> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org