[jboss-dev] Mavenizing Thirdparty

[Scott Stark]

One difference is that the source artifacts are not being downloaded any 
longer. We should be able to define which sources are downloaded by 
default in the mapping section via an includeSources or some such element:

            <dependency>
              <groupId>org.jboss.cl</groupId>
              <artifactId>jboss-classloader</artifactId>
              <mapping>
                <componentId>jboss.jboss-cl</componentId>
                <includeSources>true</includeSources>
              </mapping>
            </dependency>

Would that be easy to add?

I can run mvn dependency:sources from thirdparty to pull all of the 
source dependencies into my local maven tree, but this does not update 
thirdparty.

Paul Gier wrote:
> The mavenized thirdparty builds have been running ok (similar 
> testsuite results to non-maven build) on hudson for a few days and 
> I've heard from other people that have successfully run the build 
> locally.
>
> So I'm planning to switch to the mavenized thirdparty build at the end 
> of the day today.  Please try it out if you haven't already (ant -f 
> build-maven.xml), and bring up any issues.
>
> There are still some issues that we are working out regarding managing 
> the dependencies (see build forum for more info), but these issues 
> don't prevent building and testing, and I believe they can be resolved 
> as development continues.
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development