RE: [JBoss-dev] requirements for build
Hi, I thought the idea was to permit the use of external ANT_HOME. idea: JBoss build stops if it does not find build-magic.jar in ANT_HOME/lib Also stops if ANT is not 1.4 version Maybe other... (with a 3 pages explanation if necessary)µ Vincent -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Jason Dillon Envoyé : samedi 1 septembre 2001 8:51 À : Dan - Blue Lotus Software Cc : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] requirements for build I will add that to my list of things todo. Thanks, --jason On Sat, 1 Sep 2001, Dan - Blue Lotus Software wrote: Like I said, simply unsetting the environment variable ANT_HOME in the build script should take care of this. I use Ant on many other non-JBoss related projects. I need ANT_HOME to be set for these other projects. I assume others will have the same problem. Because I was not aware JBoss included a fully functional Ant in the distribution, I was thrown off by this. Simply unsetting ANT_HOME in build.bat (and I suspect build.sh, as this is probably a problem for both sides) would have fixed this. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 11:49 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Perhaps we should ignore any user set ANT_HOME, or warn the user if it is set. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ 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 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Trying to support everyone's different environment is really not possible. There are currently 15 non-standard libraries used by some part of the build system, which means that every user who wants to use their own ANT_HOME, would have to have the exact same version for complete compatiblity. It is not just about the buildmagic stuff, there are required xslt jars for the testsuite manual, junit to actually run the tests and so on. It might be possible with future versions of ant to support this, but for now there are better things to work on. Right now using the build.sh build.bat scripts (or the ant scripts from tools/bin) are the only methods for building the system which are directly supported. If you would like to build from something else, I can probably help you set it up. There is a better way to deal with all of these support jars, I just haven't figure out what it is yet. --jason On Sat, 1 Sep 2001, Vincent Harcq wrote: Hi, I thought the idea was to permit the use of external ANT_HOME. idea: JBoss build stops if it does not find build-magic.jar in ANT_HOME/lib Also stops if ANT is not 1.4 version Maybe other... (with a 3 pages explanation if necessary)µ Vincent -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Jason Dillon Envoyé : samedi 1 septembre 2001 8:51 À : Dan - Blue Lotus Software Cc : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] requirements for build I will add that to my list of things todo. Thanks, --jason On Sat, 1 Sep 2001, Dan - Blue Lotus Software wrote: Like I said, simply unsetting the environment variable ANT_HOME in the build script should take care of this. I use Ant on many other non-JBoss related projects. I need ANT_HOME to be set for these other projects. I assume others will have the same problem. Because I was not aware JBoss included a fully functional Ant in the distribution, I was thrown off by this. Simply unsetting ANT_HOME in build.bat (and I suspect build.sh, as this is probably a problem for both sides) would have fixed this. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 11:49 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Perhaps we should ignore any user set ANT_HOME, or warn the user if it is set. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net
Re: [JBoss-dev] requirements for build
For what it's worth, a novice jboss builder's impression: I allocated half a day to work through the usual incompatibilities, fired off the build, found and fixed the ANT_HOME problem in 1 minute, reran and...it worked! Amazing. Congrats to whoever set it up. I did what I'm sure others encountering the problem will do--changed build.bat to unset ANT_HOME. It would be convenient for others if this was always done, as suggested. I suppose it would be handy to do a dependency check like Red Hat rpm or provide a way to selectively override the build jars, but I doubt that it's worth the bother. - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Dan - Blue Lotus Software [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, September 01, 2001 4:06 AM Subject: RE: [JBoss-dev] requirements for build Trying to support everyone's different environment is really not possible. There are currently 15 non-standard libraries used by some part of the build system, which means that every user who wants to use their own ANT_HOME, would have to have the exact same version for complete compatiblity. It is not just about the buildmagic stuff, there are required xslt jars for the testsuite manual, junit to actually run the tests and so on. It might be possible with future versions of ant to support this, but for now there are better things to work on. Right now using the build.sh build.bat scripts (or the ant scripts from tools/bin) are the only methods for building the system which are directly supported. If you would like to build from something else, I can probably help you set it up. There is a better way to deal with all of these support jars, I just haven't figure out what it is yet. --jason On Sat, 1 Sep 2001, Vincent Harcq wrote: Hi, I thought the idea was to permit the use of external ANT_HOME. idea: JBoss build stops if it does not find build-magic.jar in ANT_HOME/lib Also stops if ANT is not 1.4 version Maybe other... (with a 3 pages explanation if necessary)µ Vincent -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Jason Dillon Envoyé : samedi 1 septembre 2001 8:51 À : Dan - Blue Lotus Software Cc : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] requirements for build I will add that to my list of things todo. Thanks, --jason On Sat, 1 Sep 2001, Dan - Blue Lotus Software wrote: Like I said, simply unsetting the environment variable ANT_HOME in the build script should take care of this. I use Ant on many other non-JBoss related projects. I need ANT_HOME to be set for these other projects. I assume others will have the same problem. Because I was not aware JBoss included a fully functional Ant in the distribution, I was thrown off by this. Simply unsetting ANT_HOME in build.bat (and I suspect build.sh, as this is probably a problem for both sides) would have fixed this. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 11:49 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Perhaps we should ignore any user set ANT_HOME, or warn the user if it is set. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond
Re: [JBoss-dev] requirements for build
For what it's worth, a novice jboss builder's impression: I allocated half a day to work through the usual incompatibilities, fired off the build, found and fixed the ANT_HOME problem in 1 minute, reran and...it worked! Amazing. Congrats to whoever set it up. Great. I did what I'm sure others encountering the problem will do--changed build.bat to unset ANT_HOME. It would be convenient for others if this was always done, as suggested. I think this has been resolved, or at least will be shortly. Thanks for the feedback. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. I didn't need to install anything... worked fine for me. -- Juha ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
Dan - Blue Lotus Software wrote: -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. It should work OK out of the box. I was in the same position last night - I hadn't done a build since 2.* and I spent ages messing about doing all sorts of unnecessary stuff trying to get it working - installing ant, hacking about with scripts, modifying paths in cygwin etc. etc. However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. I reckon the build.bat file will still have to work though, to avoid lots of user queries. Seems pretty impressive so far Luke. -- Luke Taylor. PGP Key ID: 0x57E9523C ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
I didn't need to install anything... worked fine for me. As it should be. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
on 1-08-31 22.35, Jason Dillon at [EMAIL PROTECTED] wrote: I didn't need to install anything... worked fine for me As it should be. Yes - on my post of success tagged True Build and Rabbit Magic was on 7.1 red Hat distro, BlackDown.com JVM. cvs get jboss-all ... and it just works ... sorry for being sloppy on the details there ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Win2k jboss-all One thing. I first tried it with Ant v1.3. It crashed and burned quickly, due to a missing buildmagic class. So I copied the Jar file into the lib directory of Ant. This got me past the classpath problem, but exposed the record problem. So when I installed Ant v1.4beta2, I dropped the buildmagic jar file into its lib directory, too. That may not have been necessary. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 9:35 PM To: JBoss Dev Subject: Re: [JBoss-dev] requirements for build What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. ;) I reckon the build.bat file will still have to work though, to avoid lots of user queries. build.bat will always have issues, since we can not give it all of the features that build.sh has (like chaning the JAXP impl and such). I highly recommended that every windows user install cygwin. It will be worth the effort, believe me. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|build.bat will always have issues, since we can not give it all of the |features that build.sh has (like chaning the JAXP impl and such). | |I highly recommended that every windows user install cygwin. It will be |worth the effort, believe me. no, we have been down this road before and the result is not pretty. 95% will NOT install cygwin and will NOT be able to build. |--jason Jason I am serious now, I am working on linux these days so I don't notice these thing but if your stuff is dependent in any way on cygwin stuff it goes right out the door. The build wars of early EJBoss still send shivers down my spine and I won't let *anyone* monkey with this. ANT brought us Linux/windows tools acgnosticism, anything that touches that is a regression. You must have SIMILAR builds on both. Kill features that break this. I am dead serious jason, tell me it is not the case. marcf | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Did you try the build.bat script? It should use the correct version of Ant with all of the correct support jars. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Win2k jboss-all One thing. I first tried it with Ant v1.3. It crashed and burned quickly, due to a missing buildmagic class. So I copied the Jar file into the lib directory of Ant. This got me past the classpath problem, but exposed the record problem. So when I installed Ant v1.4beta2, I dropped the buildmagic jar file into its lib directory, too. That may not have been necessary. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 9:35 PM To: JBoss Dev Subject: Re: [JBoss-dev] requirements for build What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
You should not need ANT_HOME set at all. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: This makes sense. I have the ANT_HOME environment variable set to a separate install of Ant. It probably just used that instead of the one included with jboss-all. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Luke Taylor Sent: Friday, August 31, 2001 8:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] requirements for build Dan - Blue Lotus Software wrote: -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. It should work OK out of the box. I was in the same position last night - I hadn't done a build since 2.* and I spent ages messing about doing all sorts of unnecessary stuff trying to get it working - installing ant, hacking about with scripts, modifying paths in cygwin etc. etc. However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. I reckon the build.bat file will still have to work though, to avoid lots of user queries. Seems pretty impressive so far Luke. -- Luke Taylor. PGP Key ID: 0x57E9523C ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Perhaps we should ignore any user set ANT_HOME, or warn the user if it is set. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|I highly recommended that every windows user install cygwin. It will be |worth the effort, believe me. no, we have been down this road before and the result is not pretty. 95% will NOT install cygwin and will NOT be able to build. Notice I said recommend. Jason I am serious now, I am working on linux these days so I don't notice these thing but if your stuff is dependent in any way on cygwin stuff it goes right out the door. No worries, nothing is dependent on cygwin. But I don't have the patience to deal with maintaining a batch script. I would rather write it in basic than have to deal with the frustrations of the different versions of batch. The build wars of early EJBoss still send shivers down my spine and I won't let *anyone* monkey with this. ANT brought us Linux/windows tools acgnosticism, anything that touches that is a regression. You must have SIMILAR builds on both. Kill features that break this. There are not features that break this, short of letting users run any old version of ant that they have installed, that is what breaks things. The scripts probably need to be tuned a little more to complain when the running env is not correct, but other wise everything is compatible with all java enabled os's. I am dead serious jason, tell me it is not the case. It is not the case. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|No worries, nothing is dependent on cygwin. But I don't have the patience |to deal with maintaining a batch script. I have agreed to this experiment with the understanding that it would not break portability. If it does because you don't maintain it and you put the windows developers (80% of our developers) through pain then this is a failed experiment. you work up that fucking patience or it is me that is going to run out of it with you marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|No worries, nothing is dependent on cygwin. But I don't have the patience |to deal with maintaining a batch script. I have agreed to this experiment with the understanding that it would not break portability. If it does because you don't maintain it and you put the windows developers (80% of our developers) through pain then this is a failed experiment. I do not wish to break portability, I just need some help to make the batch stuff as good as the /bin/sh bits. That is all I meant. you work up that fucking patience or it is me that is going to run out of it with you Chill. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
