Thanks, Stuart! That (mostly) fixed my problem. I still need to cd into
each individual project's directory. It won't compile from the "pax"
directory.

It's better than the fix Efy suggested (upgrade to maven 2.0.6).


But wow! I didn't realize 2.0.4 was so buggy!! Guess I'll have to add
that to my "todo" list.


Cheers,
Dave




On Thu, 2007-06-21 at 11:30 +0800, Stuart McCulloch wrote:
> On 21/06/07, Edward Yakop <[EMAIL PROTECTED]> wrote:
> > The weird part is. It builds on my system and I have no clue why is
> > not building on some machines.
> >
> > I did
> > rm -Rf ~/.m2/repository
> > I'm using the same jdk version as the server
> > only checked out wicket and build from there
> >
> > It build on my machine. But it doesn't build on the server.
> > This is very peculiar.
> 
> see recent note - build server still uses maven-2.0.4...
> 
> >
> > Regards,
> > Edward Yakop
> >
> >
> >
> > On 6/21/07, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> > > On 21/06/07, David Leangen <[EMAIL PROTECTED]> wrote:
> > > > > afaik it's not a problem with the infrastructure, it's whether the 
> > > > > person
> > > > > who put in the change that broke the build notices the bamboo failure
> > > > > and acts on it...
> > > >
> > > > Ok... so the next question should be: how do we get (force?) committers
> > > > to notice whether or not the build passes on bamboo?
> > > >
> > > > I think this is a fundamental quality problem that needs to be
> > > > addressed... Should be fairly easy to fix. :-)
> > > >
> > >
> > > indeed - the pax-wicket build was broken by edward's recent changes:
> > >
> > >    http://ci.ops4j.org/bamboo/browse/PAXWICKET-DEFAULT-15
> > >
> > > which somehow dropped the required junit / mock test dependencies
> > >
> > > >
> > > > Cheers,
> > > > Dave
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > general mailing list
> > > > general@lists.ops4j.org
> > > > http://lists.ops4j.org/mailman/listinfo/general
> > > >
> > >
> > >
> > > --
> > > Cheers, Stuart
> > >
> > > _______________________________________________
> > > general mailing list
> > > general@lists.ops4j.org
> > > http://lists.ops4j.org/mailman/listinfo/general
> > >
> >
> > _______________________________________________
> > general mailing list
> > general@lists.ops4j.org
> > http://lists.ops4j.org/mailman/listinfo/general
> >
> 
> 


_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to