[jboss-dev] WARNING: Mavenizing Thirdparty (2nd try)

[Paul Gier]

The change I'm making is only to replace build-thirdparty.xml (downloading from 
the buildmagic repository).  The app server will still be using ant for the builds.

You can use "mvn deploy:deploy-file" to deploy individual jars to the 
repository.  There is also some information on the wiki here: 
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseRepository

I will be adding more docs soon.

Clebert Suconic wrote:
> I'm considering to move JBossMessaging configuration files to thirdparty.
> This will require some sort of script to place the files in place after 
> the build.
> 
> Like doing this for several files:
> Copy ./thirdparty/jbm/resources/som-file.xml into its proper place
> 
> 
> How the creationg of /default and /all is being done with Maven?
> 
> Paul Gier wrote:
>> Hi Everyone,
>>
>> I'd like to make a second attempt at replacing build-thirdparty.xml 
>> with maven.      I'm going to add a new file called build-maven.xml to 
>> the build directory.  This will allow anyone who is interested to try 
>> it out before the actual switch.  I'm planning to do some additional 
>> testing and dependency checking this afternoon (I still need to make 
>> some updates to jbossws dependencies), and then make the change to 
>> build.xml at the end of the day today.
>>
>> I will leave the build-thirdparty.xml file in the build directory for 
>> testing this week, and then if everything is working fine, it can be 
>> removed next week.
>>
>> If this conflicts with any changes you had planned, or you have 
>> concerns about this please let me know.
>>
>> Thanks!
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development