AW: Gump build failure...

Yep - another time Gump has found the second between a commit and the forgotten add/commit :) Jan > -Ursprüngliche Nachricht- > Von: Stephen McConnell [mailto:[EMAIL PROTECTED] > Gesendet am: Samstag, 10. Juli 2004 22:08 > An: Ant Developers List > Betreff: Re: Gum

Re: Gump build failure...

Ignore me - it was a missing class in CVS. Stephen McConnell wrote: Just did a build of ant (ant building ant) and that passed without problem so I took a look at the bootstrap.sh script and noticed that the package in question is not included in the build: "${JAVAC}" $BOOTJAVAC_OPTS -d ${CLASSD

Re: Gump build failure...

Just did a build of ant (ant building ant) and that passed without problem so I took a look at the bootstrap.sh script and noticed that the package in question is not included in the build: "${JAVAC}" $BOOTJAVAC_OPTS -d ${CLASSDIR} ${TOOLS}/bzip2/*.java ${TOOLS}/tar/*.java ${TOOLS}/zip/*.java \

Gump build failure...

FYI: http://brutus.apache.org/~gump/public/ant/bootstrap-ant/index.htm which leads to : http://brutus.apache.org/~gump/public/ant/bootstrap-ant/gump_work/buildscript_ant_bootstrap-ant.html ... Bootstrapping Ant Distribution ... Compiling Ant Classes src/main/org/apache/tools/ant/types/selector

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Thu, 11 Sep 2003, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > In case you are not yet tired of this :) should I? 8-) > - Am using the same ant jars ("Ant version 1.6alpha compiled on > September 6 2003") picked up from nightly build area fails on nagoya > (SunOS) and works on win2k. Just

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

Stefan, In case you are not yet tired of this :) - Am using the same ant jars ("Ant version 1.6alpha compiled on September 6 2003") picked up from nightly build area fails on nagoya (SunOS) and works on win2k. - Checked in your suggested fix (http://marc.theaimsgroup.com/?l=axis-dev&m=10632349

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Wed, 10 Sep 2003, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Can you please explain why on WIN2K, both 1.5.X and CVS HEAD both > work fine? 1.5.x works on both platforms as most bugs in Ant are cross-platform, too. Maybe you've picked up a CVS HEAD version after Peter Reilly has committed

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

Stefan, Can you please explain why on WIN2K, both 1.5.X and CVS HEAD both work fine? (and we see the failure only on nagoya?). If this was the problem, then we'd see failures on both platforms. Thanks, -- dims --- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Sorry for coming back contardicting

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Wed, 10 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote: > Should I roll back the change? Not for me, I think this fixes a bug (but may be worth a note in the "could break your build" section). Others? Stefan - To unsubscr

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Wednesday 10 September 2003 15:40, Stefan Bodewig wrote: > On Wed, 10 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > I did not really understand the original code, > > I think setProject has initially been package private so recreating > the Property tasks from the new project has been th

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Wed, 10 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote: > I did not really understand the original code, I think setProject has initially been package private so recreating the Property tasks from the new project has been the only option then. > The code is a bit strange, it would have been

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Wednesday 10 September 2003 13:28, Stefan Bodewig wrote: > On 10 Sep 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > > (I'll soon commit a version that should make Axis happy for the next > > - i.e. tomorrow's - Gump run). > > I could use some help here. > > The Axis build works if I back out

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

Sorry for coming back contardicting my previous mails again. On 10 Sep 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > I'd say the Axis build works with Ant 1.5.x by accident It relies on a bug that has been fixed[1]. > (I'll soon commit a version that should make Axis happy for the next > -

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On 10 Sep 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > (I'll soon commit a version that should make Axis happy for the next > - i.e. tomorrow's - Gump run). I could use some help here. The Axis build works if I back out Peter's change for Ant.java's revision 1.84 - and I don't have a good g

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On 10 Sep 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Ant 1.5.x will use the last one to finally set the property Not really true. Even 1.5.4 uses the first definition if you use multiple tags in Ant. I'd say the Axis build works with Ant 1.5.x by accident (I'll soon commit a version tha

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Mon, 08 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: > FYI: a recent change (few weeks back?) is breaking Axis in its > iterative build (uses a descendent of ant-contrib's foreach) I think I've tracked this down, finally. target compileJunit in buildTest contains a task that under the

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On 10 Sep 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > I'll try to get Gump into using 1.5.4 next, to see whether it really > is a problem with a recent change in Ant. At least it gets past the compilation - it is running the tests know which is known to take ages 8-) Next is a line by line

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

so far I haven't found anything too helpful while trying to debug the situation, but ... On Tue, 09 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: > Dims says: > > one more data point (nagoya, jdk13, ant-nightly): > "ant -f buildSamples.xml compile" (FAILS - compiles same build.xml > many t

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Tue, 09 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: >> OK, I've found a SOAPStruct.java in interop3/groupE. > >> Could it be that your compilation depends on the order of the files >> in a fileset? > > Anything is possible, but I think maybe some other change w/ > classloading, vms, o

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

Stefan Bodewig wrote: On Mon, 08 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: FYI: a recent change (few weeks back?) is breaking Axis in its iterative build (uses a descendent of ant-contrib's foreach) fails as it cannot find SOAPStruct and in fact a find xml-axis -name \*SOAPStruct.class

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

On Mon, 08 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: > FYI: a recent change (few weeks back?) is breaking Axis in its > iterative build (uses a descendent of ant-contrib's foreach) fails as it cannot find SOAPStruct and in fact a find xml-axis -name \*SOAPStruct.class comes up empty

Re: GUMP failure caused by ANT (Re: [GUMP] Build Failure - Axis)

FYI: a recent change (few weeks back?) is breaking Axis in its iterative build (uses a descendent of ant-contrib's foreach) Davanum Srinivas wrote: Tried both j2sdk-1.3.1_08 and j2sdk-1.4.1_03 on nagoya. Problem occurs on both with latest ANT nightly. -- dims --- Davanum Srinivas <[EMAIL PROTECT

Re: [FWD] [GUMP] Build Failure - bootstrap-ojb

r failonerror="true", fork="false" using new Permissions(true) Cheers, Antoine - Original Message - From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 29, 2003 1:43 PM Subject: Re: [FWD] [GUMP] Build Failu

Re: [FWD] [GUMP] Build Failure - bootstrap-ojb

On Fri, 29 Aug 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: > and probably due to the fact that the permission to read the system > property "file.encoding" is not in the default hard coded set of > permissions in Permissions#init(). I think we shouldn't even try to hard code the set of

Re: [FWD] [GUMP] Build Failure - bootstrap-ojb

ded set of permissions in Permissions#init(). I am going to add this one, hoping that the build will be successful with it. Antoine - Original Message - From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 29, 2003 11:33 AM Subject: [FWD] [GUM

[FWD] [GUMP] Build Failure - bootstrap-ojb

This happpend during my Gump run last night, I'd expect the same to show up this afternoon (my time), when Sam posts his results. Stefan Buildfile: build.xml useDate: splash: set-archive-name: set-archive-name-date: detect-jdk: check-jdk12proxy-classes: check-jndi-classes: use-jdk12: use

[GUMP] Build Failure - ant-testutil

This email is autogenerated from the output from: Buildfile: build.xml prepare: check_for_optional_packages: build: [co

[GUMP] Build Failure - ant-embed-optional

This email is autogenerated from the output from: Buildfile: build.xml init: [mkdir] Created dir: /home/rubys/jakart

Re: [FWD] [GUMP] Build Failure - dist-ant

"Victor J. Orlikowski" <[EMAIL PROTECTED]> writes: > > Ugh. Replying to my own post. > So, the 5 parameter version was in 2.2; and the line, column, and > source info were *utterly* unused in that version. I put them in .. as a start towards making BSF scripts debuggable in a larger context. > S

Re: [FWD] [GUMP] Build Failure - dist-ant

On Thu, Jul 10, 2003 at 11:29:07PM +0600, Sanjiva Weerawarana wrote: > > Ugh. Replying to my own post. > > So, the 5 parameter version was in 2.2; and the line, column, and > > source info were *utterly* unused in that version. > > I put them in .. as a start towards making BSF scripts debuggable

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 02:47:00PM -0400, Victor J. Orlikowski wrote: > On Tue, Jul 08, 2003 at 02:29:36PM -0400, Victor J. Orlikowski wrote: > > Ugh, quite right. Neither had the two-arg version. My mistake. > > > > OK, I'm perfectly amenable to putting back the 5-arg versions, and > > marking th

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 02:29:36PM -0400, Victor J. Orlikowski wrote: > Ugh, quite right. Neither had the two-arg version. My mistake. > > OK, I'm perfectly amenable to putting back the 5-arg versions, and > marking them as deprecated; your patch covers that, Stefan, though > I may make minor chan

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, Jul 08, 2003 at 04:57:34PM +0200, Stefan Bodewig wrote: > On Tue, 8 Jul 2003, Victor J. Orlikowski > <[EMAIL PROTECTED]> wrote: > > > Hence, the BSFManager exec() method should now take the language > > and script parameters only, as was the case in 2.2. > > Neither 2.2 nor 2.3.0-rc have

Re: [FWD] [GUMP] Build Failure - dist-ant

On Tue, 8 Jul 2003, Victor J. Orlikowski <[EMAIL PROTECTED]> wrote: > Hence, the BSFManager exec() method should now take the language > and script parameters only, as was the case in 2.2. Neither 2.2 nor 2.3.0-rc have a two-arg version of BSFManager#exec. If I change Ant to pass only two argumen

Re: [FWD] [GUMP] Build Failure - dist-ant

> > build: > > [javac] Compiling 56 source files to > > /home/rubys/jakarta/ant/build/classes > > [javac] > > /home/rubys/jakarta/ant/src/main/org/apache/tools/ant/taskdefs/optional/Script.java:122: > > exec(java.lang.String,java.lang.Object) in org.apache.bsf.BSFManager > > cannot be a

[FWD] [GUMP] Build Failure - dist-ant

Dear BSF developers, hi Victor 8-) what is the recommended upgrade route for this method? > build: > [javac] Compiling 56 source files to /home/rubys/jakarta/ant/build/classes > [javac] > /home/rubys/jakarta/ant/src/main/org/apache/tools/ant/taskdefs/optional/Script.java:122: > exec(jav

[GUMP] Build Failure - ant-testutil

This email is autogenerated from the output from: Buildfile: build.xml prepare: check_for_optional_packages: build: [jav

[GUMP] Build Failure - dist-ant

This email is autogenerated from the output from: Buildfile: build.xml main_distribution: [mkdir] Created dir: /home/rubys/jak

Re: [GUMP] Build Failure - ant-embed

On Sun, 29 Jun 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > We have moved fully to the 1.6 branch, so Krysalis projects are no > longer dependent on ant-embed core. OK, I'm going to remove the project definition from Gump then. Stefan ---

Re: [GUMP] Build Failure - ant-embed

Stefan Bodewig wrote, On 27/06/2003 16.00: ... Keep in mind that ant-embed is supposed to be used with Ant 1.5 - if it doesn't compile against Ant 1.6, that's fine IMHO. We just would need to remove it from Gump and ensure that the Krysalis stuff doesn't depend on it. We have moved fully to the 1.

Re: [Fwd: [GUMP] Build Failure - Axis]

ne 27, 2003 9:02 AM > > To: axis-dev@xml.apache.org > > Subject: [GUMP] Build Failure - Axis > > > > > > > > This email is autogenerated from the outp

[Fwd: [GUMP] Build Failure - Axis]

: Friday, June 27, 2003 9:02 AM To: axis-dev@xml.apache.org Subject: [GUMP] Build Failure - Axis This email is autogenerated from the output from: <http://cvs.apache.org/builds/gump/2003-06-27/xml-axis.h

Re: [GUMP] Build Failure - ant-embed

On 27 Jun 2003, peter reilly <[EMAIL PROTECTED]> wrote: > I can fix the specific issues but am unsure > as how to compile and test ant-embed. I don't know either - apart from looking at the Gump descriptor to see what dependencies there are, and which target to call in which build file, that is.

Re: [GUMP] Build Failure - ant-embed

I can fix the specific issues but am unsure as how to compile and test ant-embed. Looking at the code, it appears that TaskDef2 has copied all the code from it's super class Definer. It may be better in this case just not to extend Definer. Alternatively the gump target could build embed-optional

[GUMP] Build Failure - ant-embed

This email is autogenerated from the output from: Buildfile: build.xml init: main-ant15: [echo] Embed is no longer supporte

[GUMP] Build Failure - ant-xdocs-proposal

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details.