You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/20 19:17:06 UTC

[jira] Created: (MNG-1631) FAQ: why there are no dependency properties in Maven 2

FAQ: why there are no dependency properties in Maven 2
------------------------------------------------------

         Key: MNG-1631
         URL: http://jira.codehaus.org/browse/MNG-1631
     Project: Maven 2
        Type: Task
  Components: documentation - faqs  
    Reporter: Brett Porter


They were removed because they aren't reliable in a transitive
environment. It implies that the dependency knows something about the
environment of the dependee, which is back to front. In most cases,
granted, the value for war bundle will be the same for a particular
dependency - but that relies on the dependency specifying it.

In the end, we give control to the actual POM doing the building,
trying to use sensible defaults that minimise what needs to be
specified, and allowing the use of artifact filters in the
configuration of plugins.

-- 
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