Hi,
Ricardo Argüello:
> Maybe we should give Maven a try then...
Ewww. Maven is at least as complex as the current buildmagic.
And the behaviour of first fetching Megabytes of stuff before
bringing the first error report is in my eyes not desirable
(yes, I know there is an offline mode).
On th
I remember that someone successfully built JBoss using Maven. I can't
remember who it was, or where was that documented.
Here:
http://marc.theaimsgroup.com/?l=jboss-development&m=105734564109596&w=2
Build files:
http://www.monkeymachine.ltd.uk/jbossmaven.zip
Maven site:
http://monkeymachine.ath.cx
Maybe we should give Maven a try then...
I remember that someone successfully built JBoss using Maven. I can't
remember who it was, or where was that documented.
I'm not a Maven fan, but with jars not being part of the repository
anymore, we could host different sub-projects in a hierarchical w
The problem is that we do alternate release builds off the different
slices of the cvs modules, nukes, jmx, jmx-remoting, jms, etc. I'm
all for cleaning up the build, but there really is not one monolithic
release. What is your suggestion for a reorg that allows for obtaining
a jmx build that does
>From Ricardo Argüello:
> I'd like to have everything under ONE module ("jboss"), and
> BRANCHes for every major release (3.0, 3.2, 4.0 or HEAD).
+1 :-)
Heiko
--
Heiko W. Rupp EMail: [EMAIL PROTECTED]
Senior Consultant Telefon: +49 711 222 992 - 900
Cellent AG
Adrian Brock wrote:
The big problem (which probably hit Bill) is that a cvs update
doesn't pull down new jars in thirdparty.
Are we going to keep everything separated in CVS modules, with
CVSROOT/modules hacks and thirdparty "magic"? Or isn't it time for us to
reconsider the repository organizat
On Sun, 2003-11-23 at 14:09, Bill Burke wrote:
> I think buildmagic files were moved around. One shapshot I had recently
> wouldn't build, but I got latest, and it worked.
I am very conservative when it comes to checking for changes.
If build/build.xml, module/build.xml, tools or thirdparty chan
; Subject: Re: [JBoss-dev] Build in 3.2
>
> On Sun, 2003-11-23 at 14:09, Bill Burke wrote:
> > I think buildmagic files were moved around. One shapshot I had
> > recently wouldn't build, but I got latest, and it worked.
>
> I am very conservative when it comes to
The two most recent changes were to consistently use the module/library
entity definitions:
and to move the xdoclet.task.classpath definition to
tools/etc/buildmagic/buildmagic.ent
I don't see anything that should have changed the build-bypass-check logic.
--
Scott
I think buildmagic files were moved around. One shapshot I had recently
wouldn't build, but I got latest, and it worked.
Sacha Labourey wrote:
Has anything changed recently? Adrian had optimized the build process a few
months ago so that rebuilding JBoss (build after build) was taking MUCH less
Has anything changed recently? Adrian had optimized the build process a few
months ago so that rebuilding JBoss (build after build) was taking MUCH less
time and it seems this doesn't work anymore.
---
This SF.net email is sponsored by: SF.net
11 matches
Mail list logo
