3 Replies Latest reply on Feb 21, 2011 10:46 AM by dward

    maven artifactIds and resulting jars

    dward

      I propose that we change our various project artifactIds to all have a "switchyard-" prefix.  Here is my reasoning:

       

      Right now, we have a mix of generated jars ("V" = version):

       

      switchyard-application-V.jar

      component-bean-V.jar

      component-soap-V.jar

      core-api-V.jar

      core-runtime-V.jar

      deploy-cdi-V.jar

      registry-V.jar

      switchyard-config-V.jar

      switchyard-plugin-V.jar

       

      I believe we all didn't really care about the names of the jars with regard to maven, because they are all associated with the org.switchyard groupId.  However, consider people who will one day download switchyard who don't use maven, but more importantly people who deploy switchyard in integration/qa/production environments (where maven isn't applicable).  At that point these jars become standalone jars somewhere in their CLASSPATH.  Let's say all our jars, plus some 3rd party jars, plus the user's jars - are all dumped into the same directory (which is quite possible).  By looking in that directory, the only jars that will stand out as being switchyard jars are the ones with the "switchyard-" prefix.  Things like core-api-V.jar, core-runtime-V.jar and the others? API of what? Runtime of what?

       

      Other projects prefix their jars with the project name, and I believe we should too.  Thoughts?

        • 1. maven artifactIds and resulting jars
          kcbabo

          I agree that the jars should be prefixed with switchyard, so we should definitely do that.  In terms of the artifactId, I'm kind of on the fence.  On the one hand, the generated jar can be anything we want in maven - it doesn't have to be the artifactId alone.  On the other hand, having a strong affinity between jar name and module name makes it easier to track down the module for a given jar.  I guess I tilt more towards changing artifactId as well.  Let's see what other people have to say and make a decision before we close out M1.

          • 2. Re: maven artifactIds and resulting jars
            tcunning

            It may be redundant (having switchyard in the groupId and artifactId), but changing the artifactId is more straightforward than using finalName everywhere to fix everything up.

            • 3. maven artifactIds and resulting jars
              dward

              We're going to move forward with this change.  I will do it as part of: https://issues.jboss.org/browse/SWITCHYARD-104