You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Ryan Sonnek (JIRA)" <ji...@codehaus.org> on 2006/01/24 05:47:06 UTC

[jira] Created: (MEV-313) publish seperate spring POM's for seperate dependencies

publish seperate spring POM's for seperate dependencies
-------------------------------------------------------

         Key: MEV-313
         URL: http://jira.codehaus.org/browse/MEV-313
     Project: Maven Evangelism
        Type: Improvement

  Components: Dependencies  
    Reporter: Ryan Sonnek


instead of one massive POM that forces developers to use <excludes> like crazy, there should be seperate POM's for seperate dependencies.  Ideally, there would be no need for the whole "exclude" concept.

For starters, spring-orm-hibernate should be fairly easy to extract from the current POM.

http://jroller.com/page/wireframe/?anchor=seperate_artifacts_for_seperate_dependencies

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