Also fixed/commited.. -peter ----- Original Message ----- From: "Marius" <[EMAIL PROTECTED]> To: "Peter Braswell" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, April 10, 2002 4:24 AM Subject: Re: [JBoss-dev] RE: AW: Patches to jboss.net
> Peter Braswell wrote: > > > > All, > > I'm not sure if this is the *approved* way of doing things, but here's the sequence that seems to work for me: > > > > 1. Do a CVS update, rebuild jboss from jboss-all\build\build.sh or build.bat depending on your poison. > > > > 2. Goto jboss.net and build. Make sure .sar file makes it into the jboss deploy directory. This is a manual process for me. If this is a fresh "get" from CVS, sometimes the required .jars/config files don't make it to the right jboss directory in which case you have to do it manually. I can provide details here if this is what you are having problems with. > > > > 3. Start jboss, make sure jboss-net.sar deploys okay. > > > > 4. Goto jboss.net\testsuite and do a build tests-standard-unit > Do you use windows? This step gived me many syntax-errors, for example: > > "[javac] > /home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/src/main/org/jboss/t est/net/jmx/JmxUnitTestCase.java:72: > cannot resolve symbol > [javac] symbol : class RemoteAdaptor > [javac] location: class org.jboss.test.net.jmx.JmxUnitTestCase > [javac] RemoteAdaptor handler=createRemoteAdaptor(new > URL(JMX_END_POINT)); > [javac] ^ > [javac] 36 errors > " > > > > > > 5. Watch in utter amazement the miracle to which you are witness to. Okay, maybe not that dramatic, but you get the idea... :-) > > > > All and all I know how frustrating this can be (BELEIVE ME!). Christoph and I will be working on docs/process/hints to make the whole thing easier... promise!! > > > > hope this helps, > > peter > > > > On Tue, 9 Apr 2002 15:24:44 -0700 [EMAIL PROTECTED] wrote: > > > Hi Marius, > > > > > > I used "./build.sh -Dmodules=jboss.net/testsuite modules-tests" which > > > seems to just run the JBoss.net testsuite. This worked this morning > > > but when I reapply my testsuite patch (capitalisation error removing > > > the emption address book impl class, obviously hasn't made it into > > > cvs yet), I still get a whole bunch of "cannot resolve symbols" when > > > building the testsuites. > > > > > > I will try to find out what's causing this tomorrow morning. > > > > > > Cheers, > > > > > > Martin > > > > > > >---- Original Message ---- > > > >From: [EMAIL PROTECTED] > > > >To: [EMAIL PROTECTED] > > > >Subject: Re: [JBoss-dev] RE: AW: Patches to jboss.net > > > >Date: Tue, 09 Apr 2002 14:36:13 +0200 > > > > > > > >>Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain > > > >on > > > >>anything, but I can't see any .ear or wsr-files generated. Is this > > > >>right? I though it would create hello.wsr. > > > >> > > > >>Martin Maisey wrote: > > > >>> > > > >>> Hi Christoph > > > >>> > > > >>> > Thanks for having such a deep look into jboss.net and fixing > > > >these > > > >>> > open issues. > > > >>> > > > >>> No problem + it wasn't a particularly deep look! > > > >>> > > > >>> > Some of them were cause by my stupidity (the techtrader-lib > > > >>> > copy operation, I did not commit, simply forgot it), > > > >>> > > > >>> Thought it was probably something like that - I've done the same > > > >>> thing myself many times... > > > >>> > > > >>> > some of them are those frequent changes in the jboss-core which > > > >I > > > >>> > cannot immediately adopt because of restricted time ... We > > > >really > > > >>> > should have a separation of core and modules such as Peter > > > >>> > Braswell suggested ... > > > >>> > > > >>> If you need a 'second pair of hands' to try to keep on top of this > > > >>> type of thing and test updates, I'm happy to do it as I would like > > > >to > > > >>> get a better knowledge of JBoss and web services and have (a small > > > >>> amount of ;-)) spare time. I noticed that some of the project web > > > >>> page seems a bit out of date - only one of the build commands > > > >worked > > > >>> for me and the command to start the test suite needs tweaking. > > > >What's > > > >>> the process to update it? > > > >>> > > > >>> I could also take a look at the failing JMX endpoint unit test if > > > >it > > > >>> would help, although this is likely to take a bit longer as I will > > > >>> probably have to wrap my head around much more of Axis and JBoss > > > >JMX > > > >>> ;-) > > > >>> > > > >>> Cheers, > > > >>> > > > >>> Martin > > > >>> > > > >>> _______________________________________________ > > > >>> Jboss-development mailing list > > > >>> [EMAIL PROTECTED] > > > >>> https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > Peter Braswell > > Utopian Software > > [EMAIL PROTECTED] > > 757.560.8867 > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
