[jboss-dev] Mavenizing Thirdparty
Scott Stark
sstark at redhat.com
Sat Apr 12 09:53:08 EDT 2008
Looks good in my usage so far.
Paul Gier wrote:
> I just wanted to follow up on this issue of including the source jars.
> Yesterday I added a profile to the maven thirdparty build that will
> download source jars (using the maven dependency plugin) to the local
> maven repo. The maven plugin will then look for the source jars in
> the local maven repository and copy them to the correct location in
> the thirdparty folder.
>
> Currently this is off by default because checking for the sources can
> be time consuming, and they only need to be downloaded on the first
> build.
>
> I also added the ability to pass maven options to the thirdparty build
> through build.sh or build.xml. So for example to call the profile for
> downloading sources, the command looks like this:
>
> ./build.sh -Dthirdparty.maven.opts="-Pdownload-sources"
>
> This causes the following command to be run against the
> thirdparty/pom.xml
>
> mvn -Pdownload-sources package
>
> So any maven options that you want to pass to the mavenized thirdparty
> can be passed through that property.
More information about the jboss-development
mailing list