[JBoss JIRA] Created: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[JBoss JIRA] Created: (JBAS-8090)...

[JBoss JIRA] Created: (JBAS-8676)...

Richard Opalka (JIRA)

Wednesday, 24 March 2010 Wed, 24 Mar '10

8:18 a.m.

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: Richard Opalka 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

Show replies by date

Richard Opalka (JIRA)

Wednesday, 24 March Wed, 24 Mar

9:01 a.m.

New subject: [JBoss JIRA] Resolved: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka resolved JBAS-7857. ---------------------------------- Resolution: Done

...

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: Richard Opalka 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

Richard Opalka (JIRA)

9:43 a.m.

New subject: [JBoss JIRA] Reopened: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka reopened JBAS-7857: ---------------------------------- Assignee: Fernando Nasser (was: Richard Opalka) Reassigning to fernando.

...

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.

Fernando Nasser (JIRA)

9:47 a.m.

New subject: [JBoss JIRA] Resolved: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] 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.

Fernando Nasser (JIRA)

9:59 a.m.

New subject: [JBoss JIRA] Assigned: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Fernando Nasser reassigned JBAS-7857: ------------------------------------- Assignee: Paul Gier (was: Fernando Nasser) assigning to Paul for comments.

...

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: Paul Gier 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.

Fernando Nasser (JIRA)

9:59 a.m.

New subject: [JBoss JIRA] Commented: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Fernando Nasser commented on JBAS-7857: --------------------------------------- Richard, maven2-brew has nothing to do with the community AS, specially the trunk. So don't expect coordinates to match. Also, if the AS 6 needs a xalan-j fix, it needs to switch to a Xalan release that contains this fix. Please contact Paul Gier by e-mail or irc for clarifications. This is important for the Maven reorganization that is going on.

...

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.

Richard Opalka (JIRA)

10:01 a.m.

New subject: [JBoss JIRA] Reopened: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka reopened JBAS-7857: ----------------------------------

...

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: Paul Gier 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.

Richard Opalka (JIRA)

10:01 a.m.

New subject: [JBoss JIRA] Assigned: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka reassigned JBAS-7857: ------------------------------------ Assignee: Richard Opalka (was: Paul Gier)

...

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: Richard Opalka 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.

Richard Opalka (JIRA)

10:03 a.m.

New subject: [JBoss JIRA] Resolved: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka resolved JBAS-7857. ---------------------------------- Fix Version/s: (was: JBossAS-6.0.0.M3) Resolution: Rejected

...

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: Richard Opalka 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.

Richard Opalka (JIRA)

10:03 a.m.

New subject: [JBoss JIRA] Reopened: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://jira.jboss.org/jira/browse/JBAS-7857?page=com.atlassian.jira.plug... ] Richard Opalka reopened JBAS-7857: ---------------------------------- Assignee: Paul Gier (was: Richard Opalka) Aha, just noticed the Fernando comments. Paul, could you comment on this issue?

...

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: Paul Gier 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.

Paul Gier (JIRA)

Friday, 17 December Fri, 17 Dec

2:09 p.m.

New subject: [JBoss JIRA] Commented: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

[ https://issues.jboss.org/browse/JBAS-7857?page=com.atlassian.jira.plugin.... ] Paul Gier commented on JBAS-7857: --------------------------------- Sorry for not getting back earlier on this. Does this upgrade still need to happen for AS6? I see both apache-xalan:xalan and xalan:xalan included in the AS6 dep tree, so probably the "apache-xalan" deps should be excluded. And the new patched version should be uploaded to the thirdparty-releases community repo.

...

Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03 --------------------------------------------------------------------- Key: JBAS-7857 URL: https://issues.jboss.org/browse/JBAS-7857 Project: JBoss Application Server Issue Type: Thirdparty Change Security Level: Public(Everyone can see) Components: XML services Reporter: Richard Opalka Assignee: Paul Gier 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

5707

days inactive

5975

days old

jboss-jira@lists.jboss.org

Manage subscription

10 comments

3 participants

tags (0)

participants (3)

Fernando Nasser (JIRA)
Paul Gier (JIRA)
Richard Opalka (JIRA)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03