I don't know what to do about this. One issue is that we are using xml entity bits to pull in standard configuration. This helped shrink the size and complexity of these files a lot.
The other is that we use custom tasks which are expected on the pri* classloader. If we revert to the previous style of hard-coded paths, then we have to add that configuration maddness again (plus we can't use the res:// protocol handler to import with. I will try to get this resolved. I may be switching to NetBeans, as I am having too many stupid issues with XEmacs at the moment. --jason On Tue, 2002-02-12 at 18:50, Scott M Stark wrote: > > Not since 3.0 and the move to buildmagic. At some point I want to > address not being able to run directly from the build.xml files in > environments that support Ant. > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: "Sacha Labourey" <[EMAIL PROTECTED]> > Cc: "Dain Sundstrom" <[EMAIL PROTECTED]>; "JBoss-dev" > <[EMAIL PROTECTED]> > Sent: Tuesday, February 12, 2002 3:25 PM > Subject: RE: [JBoss-dev] JBoss Code Style Guide > > > > Off topic, but were you able to get NetBeans to build JBoss using its > > ant fluff? > > > > --jason > > > > > > > > _______________________________________________ > 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
