Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.2.0-alpha-1
    • Component/s: None
    • Labels:
      None

      Description

      We should separate out the JBoss-specific descriptors into their own modules such that we don't leak them out along with the spec ones.

      Dependency chain:

      api-jboss > api-javaee > api (to be renamed from what is now api-base)

        Gliffy Diagrams

          Activity

          Hide
          rbattenfeld Ralf Battenfeld added a comment -

          To have different output folders than the javaee packages, it is required to separate the jboss descriptors into an own xslt transformation step, e.b. schemaJboss5 and metadataJBoss5. What we can do here, is to set the output folders in the pom section of the xml plugin and overwriting the hard coded path. This is should be supported by the plugin

          Show
          rbattenfeld Ralf Battenfeld added a comment - To have different output folders than the javaee packages, it is required to separate the jboss descriptors into an own xslt transformation step, e.b. schemaJboss5 and metadataJBoss5. What we can do here, is to set the output folders in the pom section of the xml plugin and overwriting the hard coded path. This is should be supported by the plugin
          Hide
          rbattenfeld Ralf Battenfeld added a comment -

          I realized that there little more required. JBoss descriptors need imports from javaee namespaces. That means, the transformation has to add javaee import statements but should not generate the classes, they are already generated in other sub modules (api-gen, impl-gen). I think, a flag in schemaXXX-xml per schema can suppress class generation and will trigger correct imports for the jboss classes.

          Show
          rbattenfeld Ralf Battenfeld added a comment - I realized that there little more required. JBoss descriptors need imports from javaee namespaces. That means, the transformation has to add javaee import statements but should not generate the classes, they are already generated in other sub modules (api-gen, impl-gen). I think, a flag in schemaXXX-xml per schema can suppress class generation and will trigger correct imports for the jboss classes.
          Show
          alrubinger Andrew Rubinger added a comment - Upstream commit was: https://github.com/shrinkwrap/descriptors/commit/c18ff1c2eba0f59276cc4ec6bb13f8230e8c8dbe

            People

            • Assignee:
              rbattenfeld Ralf Battenfeld
              Reporter:
              alrubinger Andrew Rubinger
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development