OK, that's done. I updated the .bat and .sh, but not the xml. On a related note, how should changes in plugins or contrib modules be tagged? I just back-ported a 3.0 fix to the 2.4 branch and tagged the jetty module and the main jboss module (2.4 branch) is that sufficient, and should I also Rel tag for the script changes?
thanks, danch Scott M Stark wrote: > I don't use the build scripts in 2.4 to do builds. I only use Ant > 1.4 and the build.xml files. If you want to update the build > scripts make them compatible with this and do not change > the build.xml files to work with an earlier version of Ant. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "danch" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, February 22, 2002 8:04 AM > Subject: [JBoss-dev] Build problem with contrib/jetty in Branch_2_4 > > > >>I ran into a couple of build issues with the 2.4 branch of the jetty >>plugin. I had to change the build.bat/build.sh scripts to set the >>properties that build.xml was expecting (jboss.dist, etc.) rather than >>what the scripts were doing (jboss.home, etc.). >> >>If noone squawks before ~2:00 PM (GMT-6) I'll check that in. >> >>There was also an incompatibility in the build script with the version >>of ant that was being used. The jetty plugin in 2.4 seams to borrow ant >>from the tomcat plugin, and used a FixCRLF attribute that wasn't >>available in that version of ant. I changed this to use the older style >>and it worked, but I'm leary of checking that one in. Comments? >> >>danch >> > > > > _______________________________________________ > 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
