[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03
Fernando Nasser (JIRA)
jira-events at lists.jboss.org
Wed Mar 24 10:47:38 EDT 2010
[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fernando Nasser resolved JBAS-7857.
-----------------------------------
Resolution: Done
We don't do this for the community builds, which should just use the latest release from the upstream community if it wants any fixes. This was just discussed in Westford a couple of weeks ago.
> Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03
> ---------------------------------------------------------------------
>
> Key: JBAS-7857
> URL: https://jira.jboss.org/jira/browse/JBAS-7857
> Project: JBoss Application Server
> Issue Type: Thirdparty Change
> Security Level: Public(Everyone can see)
> Components: XML services
> Reporter: Richard Opalka
> Assignee: Fernando Nasser
> Fix For: JBossAS-6.0.0.M3
>
>
> There's a naming conflict between
> http://repository.jboss.org/maven2/apache-xalan/xalan/2.7.1.patch01-brew/
> and
> http://repository.jboss.org/maven2-brew/apache-xalan/xalan/2.7.1.patch02/
> We need to create another patched xalan release (that will be identical with 2.7.1.patch01-brew) to ensure
> naming convention will represent upgrade of the component in EAP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list