Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.5
    • Component/s: core
    • Labels:
      None

      Description

      Lets build a jboss compatible war file that's integrated into the build process, shouldn't be too hard

        Activity

        Hide
        kurtstam Kurt T Stam added a comment -

        Done. I used maven profile; I'm trying to stay with one build tool . See the readme in the juddiv3.war module

        Show
        kurtstam Kurt T Stam added a comment - Done. I used maven profile; I'm trying to stay with one build tool . See the readme in the juddiv3.war module
        Hide
        spyhunter99 Alex O'Ree added a comment -

        Sounds similar to the way Jboss Web services is shipped. An Ant script that selectively copies or deletes file based on the deployment target. That would do it

        Show
        spyhunter99 Alex O'Ree added a comment - Sounds similar to the way Jboss Web services is shipped. An Ant script that selectively copies or deletes file based on the deployment target. That would do it
        Hide
        kurtstam Kurt T Stam added a comment -

        My plan is to collapse the juddiv3-war and the juddi-cxf modules back to one juddiv3.war module, the by default select the openjpa-cxf profile (which will be pushed to the maven repos), but then add the sources of this module to the distro so that users can build different configurations as mentioned above. If anyone has any better ideas then please let me know.

        Show
        kurtstam Kurt T Stam added a comment - My plan is to collapse the juddiv3-war and the juddi-cxf modules back to one juddiv3.war module, the by default select the openjpa-cxf profile (which will be pushed to the maven repos), but then add the sources of this module to the distro so that users can build different configurations as mentioned above. If anyone has any better ideas then please let me know.
        Hide
        kurtstam Kurt T Stam added a comment -

        I think that rather then building wars for each target platform, we should provide a maven based script to 'package' a war for a certain platform (and JAXWS and JPA implementation) using profiles. This way we limit what we have as release artifacts. The user would download our distro and run the correct target. I will create profiles some initial profiles (appserver: JBoss5/6/7, JAXWS: JBossWSNative/CXF, JPA: Hibernate). By default we keep shipping deployment on Tomcat, with CXF and OpenJPA.

        Show
        kurtstam Kurt T Stam added a comment - I think that rather then building wars for each target platform, we should provide a maven based script to 'package' a war for a certain platform (and JAXWS and JPA implementation) using profiles. This way we limit what we have as release artifacts. The user would download our distro and run the correct target. I will create profiles some initial profiles (appserver: JBoss5/6/7, JAXWS: JBossWSNative/CXF, JPA: Hibernate). By default we keep shipping deployment on Tomcat, with CXF and OpenJPA.

          People

          • Assignee:
            kstam Kurt T Stam
            Reporter:
            spyhunter99 Alex O'Ree
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development