jUDDI
  1. jUDDI
  2. JUDDI-314

Create a juddi-client-bundle-3.0.0 with jar, source and javadocs for juddi-client and uddi-ws

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.0, 3.0.1
    • Fix Version/s: 3.2
    • Component/s: juddi-client
    • Labels:
      None
    • Environment:
      All

      Description

      Would be helpful to juddi-client users to provide a juddi-client-bundle-3.0.0 that contains bytecode, javadoc and source code for the juddi-client and uddi-ws modules.

        Issue Links

          Activity

          Hide
          Kurt T Stam added a comment -

          I opened a separate jira for this (which is linked)

          Show
          Kurt T Stam added a comment - I opened a separate jira for this (which is linked)
          Hide
          Alex O'Ree added a comment -

          The jar file "uddi-tck" doesn't actually contain any classes. I think by default, the test classes aren't included within a jar.

          Show
          Alex O'Ree added a comment - The jar file "uddi-tck" doesn't actually contain any classes. I think by default, the test classes aren't included within a jar.
          Hide
          Kurt T Stam added a comment -

          done, however it will work much better once we productize the TCK and add client docs.

          Show
          Kurt T Stam added a comment - done, however it will work much better once we productize the TCK and add client docs.
          Hide
          Kurt T Stam added a comment -

          Yes we already run this in the -Papache-release profile, which is how the javadoc ends up in the juddi distro. So really all we need to do is create the maven assembly. In fact, since we have the nice distro now, the client distro is just a scaled down version of it. Should be easy to make now.

          Show
          Kurt T Stam added a comment - Yes we already run this in the -Papache-release profile, which is how the javadoc ends up in the juddi distro. So really all we need to do is create the maven assembly. In fact, since we have the nice distro now, the client distro is just a scaled down version of it. Should be easy to make now.
          Hide
          Alex O'Ree added a comment -

          Kurt, could we use this to include javadoc in the distribution jars?

          http://maven.apache.org/plugins/maven-javadoc-plugin/jar-mojo.html

          Show
          Alex O'Ree added a comment - Kurt, could we use this to include javadoc in the distribution jars? http://maven.apache.org/plugins/maven-javadoc-plugin/jar-mojo.html
          Hide
          Alex O'Ree added a comment -

          From 3.1.5, there's a boat ton of API documentation brought in from the uddi spec which should greatly aid new users to uddi. Steve, I feel you you're pain. Many of the jUDDI specific components are not API documented. Since joining the team, I've been documenting stuff (that I can understand) as I go through the code. Some of the more internal functions of juddi-core are still a bit of a mystery to me though.

          Show
          Alex O'Ree added a comment - From 3.1.5, there's a boat ton of API documentation brought in from the uddi spec which should greatly aid new users to uddi. Steve, I feel you you're pain. Many of the jUDDI specific components are not API documented. Since joining the team, I've been documenting stuff (that I can understand) as I go through the code. Some of the more internal functions of juddi-core are still a bit of a mystery to me though.
          Hide
          Kurt T Stam added a comment -

          Hi Steve, I like the idea of having a 'client' package, but I guess the question is how are people going to use this. If it is just to build on top of then adding a <depends>juddi-client</depends> to their pom would bring all that stuff in. Maybe we just need add documentation to the juddi-client chapter in the user guide in that case. However if the use case if more 'standalone' then I can see the bundle being useful.

          Show
          Kurt T Stam added a comment - Hi Steve, I like the idea of having a 'client' package, but I guess the question is how are people going to use this. If it is just to build on top of then adding a <depends>juddi-client</depends> to their pom would bring all that stuff in. Maybe we just need add documentation to the juddi-client chapter in the user guide in that case. However if the use case if more 'standalone' then I can see the bundle being useful.
          Hide
          Steve Viens added a comment -

          Perhaps this could include Apache log4j lib and the Apache commons products that the jUDDI client depends on as well (collections, configuration, lang, logging).

          Show
          Steve Viens added a comment - Perhaps this could include Apache log4j lib and the Apache commons products that the jUDDI client depends on as well (collections, configuration, lang, logging).

            People

            • Assignee:
              Kurt T Stam
              Reporter:
              Steve Viens
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development