Ok, here is the plan for the standalone remoting build: 1. Implement the export/import funcationality described above. 2. Add remoting's thirdparty deps to cruisecontrol.jboss.com/repository 3. Create a standalone remoting cvs alias which includes remoting and tools (for jbossbuild) 4. Create a release.xml in the jboss-remoting module which describes the release structure of remoting.
This will allow Tom to create a standalone release of remoting. I think all of this will take about a week. This doesn't address the issue of integrating the remoting jar back into head. As far as I can tell, this will have to wait until the new build is complete in head and is downloading dependencies. This looks like the beginning of May to me (milestone-3). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872913#3872913 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872913 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
