Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-927

Upgrade JBossWS to 2.0.1.SP2_CP04

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 4.3.0.GA_CP03
    • None
    • Web Services
    • None
    • Release Notes

        • This release will also require a SPI and Framework release (Primarily for JBPAPP-982) **
        • The container integration project also needs to be released. **
        • Add Common to the release list **

      Dependency List

      SPI ->

      { no JBossWS dependencies }

      Common -> SPI
      Framework -> SPI, Common
      Container -> SPI, Common, Framework
      Native -> SPI, Common, Framework, Container

      Also do not forget the svn:externals on stack-native/src

      The 'ant release' targets should be used for each of the projects, these should use the component-info.xml from the project.

      Looking at the existing CP releases a number of the releases have a long list of compatible versions - this should not be the case as unless tested compatibility is not guaranteed and in some cases this would cause dependent bug fixes to be missing.

      For each component being released the thirdparty versions should be checked to be in alignment with the versions used by EAP, this will cause the ant release targets to create correct component-info.xml descriptors reducing the need to add additional compatible versions by hand.

      Also ensure that javac debug info is left on.

            fnasser Fernando Nasser
            darran.lofthouse@redhat.com Darran Lofthouse
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: