You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (JIRA)" <ji...@apache.org> on 2013/05/10 17:45:16 UTC

[jira] [Resolved] (SLING-2861) Include Apache Commons Lang in Dependency Management

     [ https://issues.apache.org/jira/browse/SLING-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Klco resolved SLING-2861.
-----------------------------

    Resolution: Won't Fix

Agreed, the cost of having to release a new parent to update this dependency is too large, closing as won't fix.
                
> Include Apache Commons Lang in Dependency Management
> ----------------------------------------------------
>
>                 Key: SLING-2861
>                 URL: https://issues.apache.org/jira/browse/SLING-2861
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Dan Klco
>            Priority: Minor
>
> Right now, Apache Commons Lang is referenced in 8 locations and two different versions (2.4 and 2.5), given this it would seem much cleaner to move Apache Commons Lang into the dependency management of the root pom and remove the versions from the references.
> trunk
> 	bundles
> 		auth
> 			form
> 				pom.xml
> 					152: <artifactId>commons-lang</artifactId>  
> 	extensions
> 		adapter
> 			pom.xml
> 				152: <artifactId>commons-lang</artifactId>  
> 	servlets
> 		get
> 			pom.xml
> 				133: <artifactId>commons-lang</artifactId>  
> 	resolver
> 		pom.xml
> 			104: <artifactId>commons-lang</artifactId>  
> 	contrib
> 		extensions
> 			rewriter
> 				pom.xml
> 					96: <artifactId>commons-lang</artifactId>  
> 	scripting
> 		script-console
> 			pom.xml
> 				97: <artifactId>commons-lang</artifactId> 
> 	velocity
> 		pom.xml
> 			135: <artifactId>commons-lang</artifactId>  
> 	samples
> 		urlfilter
> 			pom.xml
> 				95: <artifactId>commons-lang</artifactId> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira