Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7857

Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          incorporates

          Component Upgrade Subtask - A subtask tracking an update to a bundled component JBAS-7772 Upgrade xalan and serializer to 2.7.1.patch01-brew

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBPAPP-3976 Upgrade xalan to 2.7.1.patch03

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pgier@redhat.com Paul Gier (Inactive)
              ropalka Richard Opalka
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: