Now, the axis2-war tests has been enabled. however there are two majors parts failed as following:
1. rampart security tests failed.. I was trying to upgrade the rampart to 1.5, as we now use axis2-1.5.1, the compatible should be rampart 1.5, but I haven't managed to make it work yet. current buildr one is still using rampart 1.4.1 version, so it would be better that someone know axis2 better can jump in and fix it? ;), also I am thinking that should we had all of these tests in ODE codebase? as these are from rampart, would it be better that we can have some typical samples to verify the security feature, but not all. thoughts? 2. right now the InstanceManagementTest and DeploymentTest failed.. Next, I will try to work on my local jpa refactoring work, against current maven build, and then try to put it in our trunk.. Would it be any problems if I can make a commit with current maven build or do you prefer to have me committed to some branch firstly?? Regards Jeff On Thu, Jul 29, 2010 at 6:52 PM, Jeff Yu <jeff.yuch...@gmail.com> wrote: > Hi all, > > Was running successfully with following combinations by using buildr. > > buildr 1.3.5 + jruby 1.4.0 + sun's jdk 1.6. > > However, I found that in the buildr's config file, we are still using the > 1.4.1 version for things like addressing-1.4.1.mar, mex-1.41.mar etc. while > in the maven build, we've already used the 1.5.1.mar version... > > can someone tell me which one is the way to go? 1.4.1 or 1.5.1? > > Thanks > Jeff > > On Tue, Jul 20, 2010 at 6:31 PM, Rafal Rusin <ra...@intalio.com> wrote: > >> Hello, >> >> recently I did update to security tests. >> This is latest build from buildr, which is known to pass all tests: >> >> Revision: 965628 >> Changes >> >> 1. ODE-874: Server should log the error for the fault and also >> point the position of fault (instance details) Fix thanks to Veresh >> Jain (detail) >> >> >> On Tue, Jul 20, 2010 at 7:49 AM, Aaron Anderson <aaronander...@acm.org> >> wrote: >> > Hi Jeff, >> > >> > If there is anything I can do to help please let me know. Overall I >> didn't need >> > to tweak much to get the tests to work in the experimental trunk. The >> most >> > challenging part was getting the Axis security tests to pass which >> required a >> > slight tweak to the base test class to allow for overriding the Axis >> module >> > directory at runtime and a few lines of groovy to move files around to >> the right >> > places. >> > >> > Cheers, >> > >> > Aaron >> > >> > >> > >> > >> > ________________________________ >> > From: Jeff Yu <jef...@apache.org> >> > To: dev@ode.apache.org >> > Sent: Mon, July 19, 2010 3:12:35 AM >> > Subject: maven build for axis2-war testing discussion >> > >> > Hi all, >> > >> > Instead of following up the 'ode trunk build' thread, I'd like to start >> a >> > new thread of enabling maven build for axis2-war module. >> > >> > I think we can start work on it by importing Aaron's work from ode 2.x >> > experiment, >> > >> http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_2.X-experimental/axis2-war/pom.xml >> > >> > >> > I am importing this work, but currently had some problems which I am >> looking >> > into it. >> > >> > @waruna, any problems on that we start from here? As I've run >> successfully >> > axis2-war module in the ode-2.x experiment branch. >> > >> > Regards >> > Jeff >> > >> > -- >> > Cheers, >> > Jeff Yu >> > >> > ---------------- >> > blog: http://jeff.familyyu.net >> > >> >> >> >> -- >> Regards, >> Rafał Rusin >> http://rrusin.blogspot.com >> > > > > -- > Cheers, > Jeff Yu > > ---------------- > blog: http://jeff.familyyu.net > > -- Cheers, Jeff Yu ---------------- blog: http://jeff.familyyu.net
