I'm ready to help you with this, but somebody needs to take ownership of these build jobs. Does anybody from the Rampart team have access to Hudson?
Andreas [1] maintain the configuration, investigate build issues, subscribe to [email protected] to watch for issues caused by the jobs, etc. On Tue, Jun 22, 2010 at 03:51, Nandana Mihindukulasooriya <[email protected]> wrote: > +1 > > Best Regards, > Nandana > > On Tue, Jun 22, 2010 at 2:07 AM, Andreas Veithen > <[email protected]>wrote: > >> I think it becomes urgent to add Rampart (and Sandesha as well) to >> Hudson so that we can detect this kind of integration issues in a >> timelier way. It also appears that the latest snapshots are almost 4 >> months old [1], so this would be a good thing anyway. >> >> Andreas >> >> [1] >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/rampart/rampart-core/SNAPSHOT/ >> >> On Sun, Jun 20, 2010 at 17:41, Thilina Mahesh Buddhika >> <[email protected]> wrote: >> > Hi Devs, >> > >> > With the latest changes in the transport trunk, there are some test >> failures >> > and compilation failures in rampart-integration module. >> > >> > Due to the modifications done in org.apache.axis2.transport.tcp.TCPServer >> > class in transport trunk, >> > >> rampart-integration/src/main/java/org/apache/axis2/integration/UtilsTCPServer.java >> > class fails to get compiled. Actually this class is not used inside >> Rampart, >> > so we can get rid of this class. >> > >> > Also, there are some test failures due to these changes in transport >> trunk. >> > Until we fix these compilation failures and test failures, shall we >> switch >> > back to transport 1.0.0 released version ? >> > >> > WDYT ? >> > >> > Thanks, >> > Thilina >> > >> > >> > Thilina Mahesh Buddhika >> > http://blog.thilinamb.com >> > >> >
