Jane,
I agree with those steps except #3. Can we have this *slf4j-all* module
outside of slf4j/1.5.9.RC1. e.g., v3/glassfish/packager/external or
something like that, so that
a) We don't have to create it every time we add new version of slf4j in
our scm.
b) We don't mix an artifact with groupId org.glassfish with that of the
external project.
I also think org.glassfish.external is *not* an appropriate groupId.
org.glassfish is more appropriate. Any additional qualifier should be
part of artifactId; the group name should remain same for all artifacts
produced by this team.
Thanks,
Sahoo
Jane Young wrote:
> Hi Ed,
>
> I'm fine with this approach in creating one bundle containing all the
> slf4j artifacts.
>
> So, this is what's going to happen:
>
> 1. Mirror slf4j sources version 1.5.9.RC1 in our SCM [1]
> 2. Use the same steps from JBoss' in building the artifacts producing
> the same maven coordinates in the local Maven repository
> 3. Create a pom.xml in [1]/slf4j/1.5.9.RC1/slf4j-all that references
> the artifacts from step 2 to create one slf4j-all bundle. Name this
> artifact slf4j-all with the version 1.5.9.RC1 and the groupId:
> org.glassfish.external
> 4. We will publish the one slf4j bundle to our maven repository
> 5. Provide a README describing the build. This should include steps
> like checking out a particular version from external repo, setting env
> and then issuing some commands.
>
> Jerome/Sahoo, let us know if you're okay with this approach.
>
> Ed, so BV will have a dependency on slf4j artifact and downloaded to
> v3 workspace from hk2? Does Snjezana need to add this artifact in the
> packager module or will this be added via transitive dependency?
>
> Thanks,
> Jane
>
>