[GUMP] Project(s) dropped

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

Re: [GUMP] Build Failure - cocoon-block-web3

er week then that is fine. - Sam Ruby

Re: Gump on cocoondev.org

Steven Noels wrote: On 3/04/2003 13:43 Sam Ruby wrote: I will correct this - though the machine is located in Kansas, we prefer to have the clock on GMT+1 time, but the sysadmins apparently forgot to set the timezone consequently. Everything is virtual these days. ;-) Ha! :-) FYI: I've p

Re: Gump on cocoondev.org

machines? cocoondev: 1.4.1_01 nagoya: 1.4.0 lsd:1.4.0_01 rubix: 1.4.0_01 Note: nagoya is solaris, the rest are linux on intel. - Sam Ruby

Re: Gump on cocoondev.org

Sam Ruby wrote: Even if this were corrected, however, I do see a jar in the avalon-excalibur/compatibility/build/lib directory. What's odd is that it was built this morning, but has yesterday's date on it. This I can't explain either. Solved this problem. Something is m

Re: Gump on cocoondev.org

r jars are referenced. hmmm Stefano, if you could take a look at this, I'd appreciate it. oh no! Sam ruby is playing the jedy trick with me... gosh, I knew this would have happened one day or another. And he knows that if I dive into gump I'll be stuck there forever. Gosh. Chuckle. I c

Re: Gump on cocoondev.org

Sam Ruby wrote: Stefano Mazzocchi wrote: all right, here is what I did (precisely): $ ssh www.cocoondev.org $ cd /usr/serverlocal/gump/cocoon-2.1 $ cvs -q update $ cd /usr/serverlocal/gump/jakarta-gump $ cvs -q update $ cd $ build gump clean $ build gump verify $ build gump scripts

Re: Gump on cocoondev.org

Don't go looking for hard answers to easy problems. There's a perfectly mundane explanation for this. Excalibur-compatibility's build failed last night. http://gump.cocoondev.org/excalibur-compatibility.html - Sam Ruby

Re: Gump on cocoondev.org

Stefano Mazzocchi wrote: Sam Ruby wrote: Stefano Mazzocchi wrote: Ah, Sam, Steven, how do I access that cocoon-special gump stuff on cocoondev.org? that would likely reduce the try/fail cycle of 24 hours that is driving me nuts! Please try the instructions I left at the following URL and let

Re: [GUMP] Build Failure - Cocoon

Stephan Michels wrote: Shouldn't be the sratchpad excluded per default? Stephan. It was, when cocoon last built successfully (over a week ago). The question is: what has changed within cocoon since then? - Sam Ruby

Rhino @ cocoondev

added? http://www.ecma-international.org/news/ECMA%20E4X%20Final%20Final.pdf http://dev2dev.bea.com/articles/JSchneider_XML.jsp - Sam Ruby

Re: [GUMP] Build Failure - Cocoon

Sam Ruby wrote: Stefano Mazzocchi wrote: Sam, how do we proceed? From gump's perspective, there is only one rhino. Create a new project definition (e.g., cocoondev-rhino) and have cocoon depend on it. Let me add that gump's project name need not have any relationship with the name

Re: [GUMP] Build Failure - Cocoon

Stefano Mazzocchi wrote: Sam, how do we proceed? From gump's perspective, there is only one rhino. Create a new project definition (e.g., cocoondev-rhino) and have cocoon depend on it. - Sam Ruby

Re: [GUMP] Build Failure - Cocoon

t, renaming the codebase seems to be the next best solution. IMHO. - Sam Ruby

Re: [GUMP] Build Failure - Cocoon

hino? I'm gathering that this is an incompatible fork of the Mozilla codebase... one that doesn't even rename the Java package name. Is this a good idea? - Sam Ruby

Re: [GUMP] Build Failure - Cocoon

of Rhino. So the question is: how does one build a "continuations enabled" version of Rhino from cvs? Regards, Chris - Sam Ruby

Re: [GUMP] Project(s) dropped

://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104782633424953&w=2 - Sam Ruby

[GUMP] Project(s) dropped

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

[GUMP] Project(s) dropped

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

Re: Gump and CocoonDev

Steven Noels wrote: Sam Ruby wrote: *If* there are people who might be predisposed to make changes to /usr/serverlocal/gump, *then* I would like to be included as a member of whatever group they might have as their primary group. Ah. I'm pretty sure now we _do_ understand each

Re: Gump and CocoonDev

Steven Noels wrote: Sam Ruby wrote: What this requires is that whatever id is used to execute the nightly builds has ability to update any files that people might produce. Umask 002 is an important part of ths - and making sure that I (or whoever is running the nightly build) am in the all

Re: Gump and CocoonDev

Steven Noels wrote: Sam Ruby wrote: Ultimately, we'll have to discuss what groups people are assigned to and whether or not /etc/bashrc should be modified so that umask is set to 002 for everybody. What we need to ensure is that there is no problem with permissions of files that people c

Re: Gump and CocoonDev

ll keep everybody posted if I need anything else. - Sam Ruby

Gump and CocoonDev

that gump normally builds, but only contains those elements which are part of the greater cocoon ecosystem. Steven, let me know what you think and if this is the wrong mailing list to discuss these items. - Sam Ruby [1] http://cvs.apache.org/builds/gump/latest/packages.html

Re: [RT] Cocoon's own publishing system

Stefano Mazzocchi wrote: Sam Ruby wrote: Steven Noels wrote: I'm happy to trigger scripts or check on their regular operations once they are installed, but am a bit swamped ATM to come up with some scripts myself. So anyone who wants to give it a whirl just tell me and I'll b

Re: [RT] Cocoon's own publishing system

Steven Noels wrote: Sam Ruby wrote: I have some scripts that do all that and more. But you already knew that. ;-) OK, I'm giving in. Given some time and energy, Cocoon, docs included, will be built regularily on cocoondev.org, along with some other projects, by means of some tool writt

Re: [RT] Cocoon's own publishing system

docs" with some nagging shouldn't be too hard, IIUC. And the rsync stuff has already been sorted out. I have some scripts that do all that and more. But you already knew that. ;-) - Sam Ruby

Re: [GUMP] Build Failure - Cocoon

target used by the main "coccon" project meant to include the fop-block? I presumed that these were to be built separately... - Sam Ruby

[GUMP] Project(s) dropped

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

[GUMP] Project(s) dropped

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

[GUMP] Project(s) dropped

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

Re: [GUMP] Build Failure - Cocoon2

oke their head into the fop-dev mailing list and simply let it be known that having fop build under gump is important to them, I would greatly appreciate it. - Sam Ruby

Re: [GUMP] Build Failure - Cocoon2

ns of everything in an effort to get more people talking, and talking earlier, with developers of components that they depend on. And I am willing to help. - Sam Ruby

Re: [GUMP] Build Failure - Cocoon2

nning the build. Imagine the possibilities of running Forrest on various sites (w/o necessarily publishing the output), for no other reason than to see if recent changes to cocoon will break something downstream. http://www.xptester.org/_ZABLE%5B0%5D_/tab/9/excerpts/xptestvalues.htm - Sam Ruby

[GUMP] Project(s) dropped

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

Re: [GUMP] Project(s) dropped

Stefano Mazzocchi wrote: Sam Ruby wrote: gen: [java] Dropping project proxy-block because of Exception java.lang.Exception: project "commons-logkit" not found processing project proxy-block what does this mean? is something we can fix? In xml-cocoon2/gump.xml there is a dependenc

[GUMP] Project(s) dropped

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

[PATCH] nag on prereq failures

I could be a smartass, and commit this patch, but figured that it merits further discussion. It *might* be worth committing the first block of the patch, however. - Sam Ruby Index: gump.xml === RCS file: /home/cvs/xml-cocoon2

Re: Gump Integration

descriptor will have to be dynamically generated by the analysis of the indirect dependency graph of the cocoon blocks. Works for me. As long as the dynamic dependency analyzer is, itself, bootstrapped statically, I'm happy. - Sam Ruby

[Fwd: Re: cvs commit: jakarta-gump/project xml-cocoon2.xml]

FYI Original Message Subject: Re: cvs commit: jakarta-gump/project xml-cocoon2.xml Date: Fri, 28 Feb 2003 15:47:12 +0100 From: Leo Simons <[EMAIL PROTECTED]> Reply-To: "Gump code and data" <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.gump References: <

Re: [New build system] Status of samples

you want. I'd recommend the [EMAIL PROTECTED] mailing list. But I am willing to discuss it anywhere. At the moment, the following is effectively the equivalent of an alias: We could make this simpler with a new tag that has the same effect. Thoughts? - Sam Ruby

Re: [New build system] Status of samples

and ensure that the descriptors can still be updated by the people who have been maintaining it to date: http://cvs.apache.org/viewcvs/jakarta-gump/project/Attic/xml-cocoon2.xml - Sam Ruby

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] - WARNING!

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] - WARNING!

[GUMP] Build Failure - xml-cocoon2

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

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

Re: [gump] cocoon2 build error

What's the status of this? Leo Simons wrote: Berin Loritsch wrote: Leo Simons wrote: hi, It looks like the problem is that an extra required first argument, namely role, was added to the ComponentHandler methods. This role in the end results in a call to ComponentProxyGenerator.getProxy(),

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -- [echo] Apache Cocoon

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] --

Re: The organization of xml.apache.org

t wish to participate will be encouraged to form their own separate projects (or move into incubation). What I like most about such a proposal is that it is completely up to the commiters to decide whether they want opt in or

Re: [PROPOSAL] Cocoon-apps CVS module

lear, posted, and auditable (e.g., votes are done on the mailing list). - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: [COCOON] New cocoon-docs mailing list

Nicola Ken Barozzi wrote: > Dear PMC, Dear root, > > The Cocoon project asks for the creation of a new mailing list to aid > the new Cocoon Documentation project. > > [EMAIL PROTECTED] List created, Initial moderator is [EMAIL PROTECTED] - Sam Ruby P.S. No need

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

I've unsubscribed minimalist@exolab.org

... from [EMAIL PROTECTED] - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

Re: Google Web APIs and Cocoon

wing: http://api.google.com:80/search/beta2";>     GETYOURSELFAKEY         0     10     true         false         latin1    latin1 - Sam Ruby - To unsubscribe, e-mail:

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

[GUMP] Build Failure - xml-cocoon2

This email is autogenerated from the output from: Buildfile: build.xml init: [echo] -

Re: JDK 1.3 vs JDK 1.4 issue

he response was that it only affected database vendors. I provided numerous counter examples, asked for support from jcp@apache and exchanged e-mail with the spec lead for JDBC. I was not successful. Below is one of the e-mails from the period: - Sam Ruby I'm looking for suggestions on how

  1   2   >