cvs commit: gump/python/gump/document/xdocs xdoc.py documenter.py

ajack 2004/07/13 16:01:31 Modified:python/gump/document/xdocs xdoc.py documenter.py Log: Too terse... Revision ChangesPath 1.7 +6 -6 gump/python/gump/document/xdocs/xdoc.py Index: xdoc.py

cvs commit: gump/python/gump/build abstract.py

ajack 2004/07/13 15:53:37 Modified:python/gump/build abstract.py Log: Experimenting with "import X" not "from X import Y". Revision ChangesPath 1.5 +3 -2 gump/python/gump/build/abstract.py Index: abstract.py

cvs commit: gump/python/gump/stats statsdb.py

ajack 2004/07/13 14:43:32 Modified:python/gump/document/xdocs documenter.py python/gump/stats statsdb.py Log: Docs tweaks (less is more). Revision ChangesPath 1.15 +46 -35gump/python/gump/document/xdocs/documenter.py Index: documenter.py =

Re: Ant on JDK 1.5

> Questions; Will Gump use JDK1.5 by default later? Will it be possible > to tell Gump which version of the JDK to use for the build? > > > Things are getting increasingly complicated. > Avalon doesn't build with 1.5 (not yet anyway). > Avalon requires 1.3, and other projects 'promises' JDK 1.1, b

Re: cvs commit: gump ARTIFACT_DISCLAIMER.html

Could I get folks to review this, and (preferably) improve upon it? regards Adam - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 13, 2004 3:14 PM Subject: cvs commit: gump ARTIFACT_DISCLAIMER.html > ajack 2004/07/13 14:14:28 > > Added:

cvs commit: gump ARTIFACT_DISCLAIMER.html

ajack 2004/07/13 14:14:28 Added: .ARTIFACT_DISCLAIMER.html Log: Proposed disclaimer. Revision ChangesPath 1.1 gump/ARTIFACT_DISCLAIMER.html Index: ARTIFACT_DISCLAIMER.html

Re: legalities of jar publishing

> > Seems a key point to me. So can we say that these artifacts are NOT > > considered release? > > I would say so, yes. Gump creates artifacts that should *NOT* be > considered released and officially endorsed by the ASF, any use of those > artifacts, if made available, should come with a big WARN

Re: legalities of jar publishing

Stefano Mazzocchi wrote: I would like to hear comments from others and when we reach consensus I can run this thru the board and see what they think. I think we are all in agreement that *if* putting in place some disclaimers and the like makes publishing jars acceptable, we would very much like

Re: Ant on JDK 1.5

Adam R. B. Jack wrote: There are some interesting errors given here: http://brutus.apache.org/gump/jdk15/ant/bootstrap-ant/gump_work/buildscript_ant_bootstrap-ant.html Ought we be publishing these to the Ant dev community? Questions; Will Gump use JDK1.5 by default later? Will it be possible to t

Re: legalities of jar publishing

Adam R. B. Jack wrote: Stefano wrote: NOTE: board hat off. Noted. NOTE: board hat continously off unless explicitly stated. (I do this because I use the same email address for all apache communication and that might create problems understanding which hat I'm wearing) apologies if this seems lik

Re: legalities of jar publishing

Stefano wrote: > NOTE: board hat off. Noted. BTW: I've been quiet on this 'til now 'cos it is now that I need to get past this (if possible) again, so I can extend functionality. > If a nightly build is a release, then it is a svn|cvs checkout and if > you want the PMC to approve any checkout,

Re: build.sysclasspath management

On Mon, 12 Jul 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote: > Stefan Bodewig wrote: > The issue comes down to the conflict of interest between the two > following scenarios: > >(a) I stack the initial classloader with everything that is >needed (plugins, lib, directories, etc.)

Re: build.sysclasspath management

On Mon, 12 Jul 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote: If you overload the property, you should use one of the supported values. "last" or even "none" seems to be what you want for Magic. >>> I haven't located docs on this.

Re: heresy - a controversial or unorthodox opinion or doctrine

On Mon, 12 Jul 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote: > So basically I agree - Magic is exposing a potential for abuse but > at the same time it is very questionable why someone would invest > time into setup and usage of magic with that in mind - ant's > would be a much quicker solut

Re: Ant on JDK 1.5

On Tue, 13 Jul 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > There are some interesting errors given here: Hmm, looks like an encoding issue on first glance, all the other things are just warnings (and should go away in the "normal" Ant run since we pass a proper -source argument here). The

Ant on JDK 1.5

There are some interesting errors given here: http://brutus.apache.org/gump/jdk15/ant/bootstrap-ant/gump_work/buildscript_ant_bootstrap-ant.html Ought we be publishing these to the Ant dev community? regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try

Re: [RT] Was python a good idea?

Stefan wrote: > The reasons the Python rewrite started AFAIR: > > * get more people involved: > > didn't work, there are even less people working on Gump's code base > than before. But we have a lot more people 'sniffing around'. ;-) That said, likely this is 'cos the daily/nightly Gump coverage

Re: Dymystifying Gump Code...

> What I am trying to say... I would love to help out with Gump at code > level, but Python is a hinder that I won't try to climb. Fishing > sounds more tantalizing. ;o) Yes, that was clear. Unfortunately, Gump is currently written in Python, so your offer of assistance comes with too great a sti