Re: [tag] Re: The good ol' JUnit problem

2005-11-14 Thread Peter Reilly
Not quite, one can use the "classloader" task as implemented in bugzilla 28228. http://enitsys.sourceforge.net/ant-classloadertask/ Please note that this uses protected methods on the java classes and thus may not be future compible. However, I do think that optional ant tasks should not require t

RE: [tag] Re: The good ol' JUnit problem

2005-11-14 Thread Jon Skeet
> i didn't quite catch the resolution to this. is there a > solution to using a stock ant distribution , without > modifying your target environment (ANT_HOME/lib, ~/.ant/lib, > etc), and using the optional tasks such as junit, scp, ftp, > etc? if so, can someone give an example of how to do t

Re: The good ol' JUnit problem

2005-11-12 Thread Mark Lybarger
i didn't quite catch the resolution to this. is there a solution to using a stock ant distribution , without modifying your target environment (ANT_HOME/lib, ~/.ant/lib, etc), and using the optional tasks such as junit, scp, ftp, etc? if so, can someone give an example of how to do this? On 11/9

RE: The good ol' JUnit problem

2005-11-09 Thread Jon Skeet
> --- Jon Skeet <[EMAIL PROTECTED]> wrote: > [SNIP] > > I've made the change (as well as fixing up some HTML > > problems) and > > mailed the file to Steve for check-in. It looks like I > don't have SVN > > access after all - either that, or I've got a different username or > > password to befor

Re: The good ol' JUnit problem

2005-11-08 Thread Stefan Bodewig
Hi Jon, long time no see. On Tue, 8 Nov 2005, Jon Skeet <[EMAIL PROTECTED]> wrote: > Assuming I actually *do* still have write-access, shall I add these > two properties to the manual in SVN? No, you don't. This is the current list of people with write access to Ant's svn. ant=rubys,conor,bod

RE: The good ol' JUnit problem

2005-11-08 Thread Matt Benson
--- Jon Skeet <[EMAIL PROTECTED]> wrote: [SNIP] > I've made the change (as well as fixing up some HTML > problems) and > mailed the file to Steve for check-in. It looks like > I don't have SVN > access after all - either that, or I've got a > different username or > password to before. > To commi

RE: The good ol' JUnit problem

2005-11-08 Thread Jon Skeet
> FYI ${ant.home} is documented on > using.html#built-in-props > > ${ant.library.dir} should probably be documented alongside it > and share its caveat. Yup - I noticed that when I dived into SVN. (It's not in the online manual, which is what I was looking at before.) I've made the change (

Re: The good ol' JUnit problem

2005-11-08 Thread Matt Benson
--- Steve Loughran <[EMAIL PROTECTED]> wrote: > Jon Skeet wrote: > > Steve wrote: > > > >>${ant.home}/lib > >>${user.home}/.ant/lib > > > > > > Having just checked the source, it's even easier > than that (for the > > first one): ${ant.library.dir} > > > > Both ant.home and ant.library.dir w

RE: The good ol' JUnit problem

2005-11-08 Thread Jon Skeet
Steve wrote (replying to me): > > I think if Ant provided a property for its "home" location > ${ant.home}/lib > ${user.home}/.ant/lib You star. Could I suggest that ant.home should be added to the manual? (I did look on the website first, honest!) I suppose I could just edit it in CVS myself

Re: The good ol' JUnit problem

2005-11-08 Thread Steve Loughran
Jon Skeet wrote: Steve wrote: ${ant.home}/lib ${user.home}/.ant/lib Having just checked the source, it's even easier than that (for the first one): ${ant.library.dir} Both ant.home and ant.library.dir work from Eclipse, too, which I had worried about a little bit... Assuming I actually *do

RE: The good ol' JUnit problem

2005-11-08 Thread Jon Skeet
Steve wrote: > ${ant.home}/lib > ${user.home}/.ant/lib Having just checked the source, it's even easier than that (for the first one): ${ant.library.dir} Both ant.home and ant.library.dir work from Eclipse, too, which I had worried about a little bit... Assuming I actually *do* still have write-

Re: The good ol' JUnit problem

2005-11-08 Thread Steve Loughran
Jon Skeet wrote: This is a similar issue with the xalan classes in the 1.4 jdk. they're exposed directly by sun (and other jvm's) as org.apache.*. basically they just imported xalan and possibly other apache classes into the jvm. this gives your entire application (jvm) one chance to override

RE: The good ol' JUnit problem

2005-11-08 Thread Jon Skeet
> This is a similar issue with the xalan classes in the 1.4 jdk. > they're exposed directly by sun (and other jvm's) as org.apache.*. > basically they just imported xalan and possibly other apache > classes into the jvm. this gives your entire application > (jvm) one chance to override the ver

Re: The good ol' JUnit problem

2005-11-04 Thread Mark Lybarger
Jon, This is a similar issue with the xalan classes in the 1.4 jdk. they're exposed directly by sun (and other jvm's) as org.apache.*. basically they just imported xalan and possibly other apache classes into the jvm. this gives your entire application (jvm) one chance to override the version u

The good ol' JUnit problem

2005-10-28 Thread Jon Skeet
Currently, our build uses a modified distribution of Ant - all the optional libraries we need are bundled into the lib directory. We use a similarly modified version of Eclipse (i.e. the Ant part has the same changes made). Needless to say, this is somewhat suboptimal. I want to move to a system w