[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich reopened MEV-177: -------------------------------------
It looks like all of them got updated except for the 1.0.2 version It's timestamp changed like all the rest but the change is not in it. That's the one that actually effects me. > older jstl jars in old location need relocation tag added > --------------------------------------------------------- > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: MEV-177-jstl.jstl.patch, jstl-1.0.1.pom, jstl-1.0.2.pom, > jstl-1.0.3.pom, jstl-1.0.4.pom, jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, > jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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]
