[jira] Commented: (GUMP-40) non-committers can modify (some) descriptors

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-40?page=comments#action_61590 ]
 
Leo Simons commented on GUMP-40:


yet another possibility would be to have a publicly writable subversion 
repository. Much easier :-D

> non-committers can modify (some) descriptors
> 
>
>  Key: GUMP-40
>  URL: http://issues.apache.org/jira/browse/GUMP-40
>  Project: Gump
> Type: Wish
>   Components: Object Model (GOM)
> Versions: unspecified
> Reporter: Leo Simons
>  Fix For: unspecified

>
> It would be nice if people who are not committers @ the ASF have a way to 
> modify descriptors, in particular developers of non-ASF projects maintaining 
> the descriptors of those projects. This is currently done by putting those 
> descriptors in a seperate cvs module and accessing them through ViewCVS, but 
> this has several downsides as has been discussed here:
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=681442
> Possible alternatives could be a publicly writeable repository, an 
> access-by-request repository, a web application with granular auth&access 
> control, or all of the above.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (GUMP-55) Gump metadata loading requires optimization

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-55?page=history ]
 
Leo Simons closed GUMP-55:
--

 Assign To: (was: Sam Ruby)
Resolution: Invalid

the model code in gumpy was completely rewritten a long time ago.

> Gump metadata loading requires optimization
> ---
>
>  Key: GUMP-55
>  URL: http://issues.apache.org/jira/browse/GUMP-55
>  Project: Gump
> Type: Improvement
>   Components: Python
> Reporter: Adam Jack

>
> This takes way more cycles, and way too long. It need optimization.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (GUMP-88) ./gump fails with SyntaxError on Solaris8

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-88?page=comments#action_61592 ]
 
Leo Simons commented on GUMP-88:


why is it bad to depend on bash?

> ./gump fails with SyntaxError on Solaris8
> -
>
>  Key: GUMP-88
>  URL: http://issues.apache.org/jira/browse/GUMP-88
>  Project: Gump
> Type: Bug
>   Components: Python
>  Environment: Solaris v2.8
> Gump trunk
> Python v2.4
> Reporter: Graham Leggett

>
> If an attempt is made to check the gump code out of svn onto a solaris8 
> machine with python v2.4 installed, the following error results:
> bash-2.03$ ./gump validate
> ./gump: function: not found
>   Run the DTD validation tools on the metadata.
>   Usage:
> ./gump validate
> ./gump: function: not found
> ./gump: validate
> Adding the python -d flag, results in the following:
> bash-2.03$ python -d gump validate
>   File "gump", line 25
> function usage
>  ^
> SyntaxError: invalid syntax
> Checking out the same gump code from svn onto a MacOSX machine and running it 
> against python v2.3 shows that the same gump script works.
> It looks like gump in it's current form is not compatible with python v2.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-29) new user howto

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-29?page=history ]

Leo Simons updated GUMP-29:
---

Component: Documentation

> new user howto
> --
>
>  Key: GUMP-29
>  URL: http://issues.apache.org/jira/browse/GUMP-29
>  Project: Gump
> Type: Improvement
>   Components: Documentation
> Versions: unspecified
> Reporter: Leo Simons
> Assignee: Leo Simons
>  Fix For: unspecified

>
> New users seem weary of editing gump descriptors (especially when they don't 
> live in their "own" cvs module but they have to change things in the gump 
> repository), and most of them are very sketchy as to the steps one takes to 
> fix things. Niclas Hedhman' recent experience in getting some of avalon to 
> build using gump and the talk resulting from it on avalon-dev and 
> gump-general are a good example of a new user we need to talk through things.
> We need a howto. Not just the technical explanation, but some philosophy 
> ("Everyone is free to work on gump. Everyone." Stuff like that) intertwined.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-36) Generate source diff report on build failure

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-36?page=history ]

Leo Simons updated GUMP-36:
---

Component: Python

> Generate source diff report on build failure
> 
>
>  Key: GUMP-36
>  URL: http://issues.apache.org/jira/browse/GUMP-36
>  Project: Gump
> Type: New Feature
>   Components: Python
> Reporter: Vincent Massol

>
> When a project fails to build, generate a report containing the following 
> information:
> - CVS source diff on the project itself between the last success build and 
> the current checked out sources
> - CVS source diffs on the project first level dependencies between the last 
> success build and the current checked out sources
> - CVS source diff on Gump project files between the last success build and 
> the current checked out sources.
> The idea is to help devlopers of the failed project in indentifying the 
> reason of the failure.
> See 
> http://blogs.codehaus.org/people/vmassol/archives/000644_diffing_continuous_build_results.html
>  for more details.
> Thanks
> -Vincent

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-85) A package typo or mis-naming or mis-match crashes Gump

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-85?page=history ]

Leo Simons updated GUMP-85:
---

Component: Python

> A package typo or mis-naming or mis-match crashes Gump
> --
>
>  Key: GUMP-85
>  URL: http://issues.apache.org/jira/browse/GUMP-85
>  Project: Gump
> Type: Bug
>   Components: Python
> Reporter: Adam Jack
> Priority: Critical

>
> Gump ought not react so poorly to this.
> INFO:gump:Build Project: #[(122, 706)] : saxon6 :  [state:Unset]
> Traceback (most recent call last):
>   File "bin/integrate.py", line 109, in ?
> irun()
>   File "bin/integrate.py", line 86, in irun
> result = getRunner(run).perform()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/runner.py", line
> 213, in perform
> return self.performRun()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/demand.py", line
> 186, in performRun
> module=project.getModule()
>   File "/usr/local/gump/public/gump/python/gump/core/model/project.py", line
> 663, in getModule
> if not self.inModule(): raise RuntimeError, 'Project [' + self.name + ']
> not in a module.]'
> RuntimeError: Project [jdox] not in a module.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-57) A 'stale' state is needed

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-57?page=history ]

Leo Simons updated GUMP-57:
---

Component: Python

> A 'stale' state is needed
> -
>
>  Key: GUMP-57
>  URL: http://issues.apache.org/jira/browse/GUMP-57
>  Project: Gump
> Type: Improvement
>   Components: Python
> Reporter: Adam Jack

>
> We need a 'stale' state (for when CVS|sVN updates fail, but we build off 
> 'older' code)
> We need a matching SVG
> We need propogation logic to ensure we know that this project was build off 
> something stale N level below.
> We could set any project not on CVS|SVN head as stale..

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (GUMP-30) put installed packages under version control

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-30?page=comments#action_61594 ]
 
Leo Simons commented on GUMP-30:


I started this in http://svn.apache.org/repos/asf/gump/packages/, which is only 
accessible by apache committers, so we avoid licensing headache. However, since 
we have /so/ /many/ packages, it takes a looong time to import everything. 
Would be great if someone could write a script to automate that import. In 
addition, it would be great if our installed packages could be cleaned up (a 
lot!)

> put installed packages under version control
> 
>
>  Key: GUMP-30
>  URL: http://issues.apache.org/jira/browse/GUMP-30
>  Project: Gump
> Type: New Feature
> Versions: unspecified
> Reporter: Leo Simons
>  Fix For: unspecified

>
> some parts of each gump installations are currently manually maintained and 
> rsynced over between various machines, because they can't live in the public 
> tree. This is undesireable. Thought about it in the past. We need a private 
> CVS tree (as in non-browseable by non-asf people) that contains these 
> packages. It'll enable us to be aware of when someone updates a package.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-81) Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-81?page=history ]

Leo Simons updated GUMP-81:
---

Component: Python

> Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames
> 
>
>  Key: GUMP-81
>  URL: http://issues.apache.org/jira/browse/GUMP-81
>  Project: Gump
> Type: Bug
>   Components: Python
> Reporter: Adam Jack

>
> A circumstance was found whereby 'resume.xml' (with an e acute) in a module 
> (XOM, FWIIW) was checked out of the repository, but the (Python code) 'sync' 
> to a working directory failed. It failed because Python's os.listdir returned 
> a string for it, not Unicode (although it returned unicode for al lthe plain 
> file). This seems related to the fact that the default filesystem encoding on 
> the platofrm was 'ascii', and this file was not ascii.
> We need to create a test for such files, then work with Gump to resolve this 
> issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-83) The

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-83?page=history ]

Leo Simons updated GUMP-83:
---

Component: Object Model (GOM)
   Python

> The  --
>
>  Key: GUMP-83
>  URL: http://issues.apache.org/jira/browse/GUMP-83
>  Project: Gump
> Type: Improvement
>   Components: Python, Object Model (GOM)
> Reporter: Adam Jack

>
> Gump knows that certain CLASSPATH directories needs to be built prior to the 
> build tool's JVM being started, or they will be dropped. As such the  element was added. This can be removed, and we can automatically do this for 
> all work directories, hence automatic the process and simplifying it for 
> users.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (GUMP-58) Respect list prefixing requests (like jakarta-commons) has

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-58?page=comments#action_61595 ]
 
Leo Simons commented on GUMP-58:


what does that mean? Longer summary would be nice, or link to the mailing list 
archive...

> Respect list prefixing requests (like jakarta-commons) has
> --
>
>  Key: GUMP-58
>  URL: http://issues.apache.org/jira/browse/GUMP-58
>  Project: Gump
> Type: Improvement
> Reporter: Adam Jack

>
> Allow a prefix attribute and place that prior to Gump's prefix.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (GUMP-89) support

[Leo Simons (JIRA)]

support http://issues.apache.org/jira/browse/GUMP-89
 Project: Gump
Type: New Feature
  Components: Python  
Reporter: Leo Simons


Gump should support :

  http://gump.apache.org/metadata/project.html#junitreport

the referenced directories should be published as part of the logs whether or 
not the project build is successful, and linked to from the gump html pages, 
probably as part of the "Output Artifacts" section on the "details" page of a 
project.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-84) Packages defined in built modules are shown as "green" but they should be "blue"

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-84?page=history ]

Leo Simons updated GUMP-84:
---

Component: Python

> Packages defined in built modules are shown as "green" but they should be 
> "blue"
> 
>
>  Key: GUMP-84
>  URL: http://issues.apache.org/jira/browse/GUMP-84
>  Project: Gump
> Type: Bug
>   Components: Python
> Reporter: Stefano Mazzocchi

>
> packages are colored "blue" when they are not built by gump. Modules are 
> allowed to have their own internal packages, wrapping some of the jars they 
> contain in their repository. Gump should treat those the same as packages, 
> but currently it does not and it misleads the statistics.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-87) Be able to view unit tests (and other files) generated by Maven builds

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-87?page=history ]

Leo Simons updated GUMP-87:
---

Component: Python

> Be able to view unit tests (and other files) generated by Maven builds
> --
>
>  Key: GUMP-87
>  URL: http://issues.apache.org/jira/browse/GUMP-87
>  Project: Gump
> Type: New Feature
>   Components: Python
> Reporter: Eric Pugh

>
> Hi all,
> I notice that gump links in a lot of files that it generates, like the
> project.properties etc.  However, the output from running unit tests is not
> available.  Is there anyway to find this?
> A couple of the Fulcrum projects are failing on their tests...
> http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/i
> ndex.html
> I wondered if I could see them by pulling up a directory like:
> http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/g
> ump_file/target/test-reports
> but no joy...
> Eric

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-61) Gump generated pages need a 'powered by python' logo

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-61?page=history ]

Leo Simons updated GUMP-61:
---

Component: Python

> Gump generated pages need a 'powered by python' logo
> 
>
>  Key: GUMP-61
>  URL: http://issues.apache.org/jira/browse/GUMP-61
>  Project: Gump
> Type: Improvement
>   Components: Python
> Reporter: Adam Jack
> Priority: Minor

>
> See: http://www.python.org/community/logos.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-58) Respect list prefixing requests (like jakarta-commons) has

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-58?page=history ]

Leo Simons updated GUMP-58:
---

Component: Object Model (GOM)
   Python

> Respect list prefixing requests (like jakarta-commons) has
> --
>
>  Key: GUMP-58
>  URL: http://issues.apache.org/jira/browse/GUMP-58
>  Project: Gump
> Type: Improvement
>   Components: Python, Object Model (GOM)
> Reporter: Adam Jack

>
> Allow a prefix attribute and place that prior to Gump's prefix.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (GUMP-4) usage.html does not mention "ant check" (or gump check)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-4?page=history ]
 
Leo Simons closed GUMP-4:
-

 Assign To: (was: Gump Development Team)
Resolution: Won't Fix

The java version of gump is not maintained anymore and won't be maintained 
anymore. Sorry!

> usage.html does not mention "ant check" (or gump check)
> ---
>
>  Key: GUMP-4
>  URL: http://issues.apache.org/jira/browse/GUMP-4
>  Project: Gump
> Type: Bug
>   Components: Java/XSLT
> Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
> Reporter: Adam Jack

>
> http://jakarta.apache.org/gump/usage.html -- perhaps it ougt be step #3. This 
> is a critical step, perhaps the biggest time wasteer if not done.
> Also, perhaps this issues ought go on usage.html or other:
> Can these go on usage.html or a known issues page?
> Known problems you may face:
> * Win2K and earlier have limitations on environment variable lengths
> * bash with cygwin on win32 may have worked at one time, it'scurrent status
>   is unknown.
> Things to avoid:
> * don't try to intelligently subset this build and learn gump and verify
> your installation all at once.  Build the full system.  Then learn by
> trying things and asking questions.  Then try to intelligently subset the
> build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (GUMP-1) Gump performs builds on stale code

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-1?page=history ]
 
Leo Simons closed GUMP-1:
-

 Assign To: (was: Gump Development Team)
Resolution: Won't Fix

The java version of gump is not maintained anymore and won't be maintained 
anymore. Sorry!

> Gump performs builds on stale code
> --
>
>  Key: GUMP-1
>  URL: http://issues.apache.org/jira/browse/GUMP-1
>  Project: Gump
> Type: Bug
>   Components: Java/XSLT
> Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
> Reporter: Adam Jack

>
> Gump is using out of date stuff:
> Note: At time of writting these links were useful, but since they go 
> to "latest" their value may change over time.
>   ---
>   http://cvs.apache.org/builds/gump/latest/cvs_krysalis-version.html
>   cvs -z3 -d
> :pserver:[EMAIL PROTECTED]:/cvsroot/metamorphosis
> update -P -d -A krysalis-version
>   cvs [update aborted]: recv() from server 
> cvs.metamorphosis.sourceforge.net:
> EOF
>   cvs server: Updating krysalis-version
>   ...
>   /home/rubys/bin/timeout: timed out
>   cvs [update aborted]: received termination signal
>   ---
> SourceForge have knobbled their CVS server against such accesses (in the
> name of making developer lives easier) and much as this is an SF.net user
> woe, two things:
> 1) Even if/when gump detects that CVS fails it only seems to mark the CVS
> index in red, it doesn't mark the main build dashboard in red. As such, such
> failures can go unnoticed.
>   http://cvs.apache.org/builds/gump/latest/cvs_index.html krysalis-
> version =
> FAILED
>   http://cvs.apache.org/builds/gump/latest/index.html krysalis-version =
> SUCCESS.
> 2) The reason the build dashboard isn't in red is that Gump doesn't (it
> seems to me) clean out it's CVS area each time, so it has a "stale" copy of
> the code with which to "update" the build area and with which to build.
> FWIIW:
> 3) Gump doesn't seem to clean out it's work area each time, which can be
> confusing when profiles change and projects get renamed or go away.
> This is one of the things I mean to log in the bug tracker, now Sam's
> created it.
> BTW: I suspect a fix might be in adding to the gump.sh script that Sam
> wrote, and Nick Chalko and I built upon. Not elegant (yet another language
> in the mix, and no PC version) but easiest...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (GUMP-6) Gump does not detect cvs update failure due to renamed projects

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-6?page=history ]
 
Leo Simons closed GUMP-6:
-

 Assign To: (was: Gump Development Team)
Resolution: Won't Fix

The java version of gump is not maintained anymore and won't be maintained 
anymore. Sorry!


> Gump does not detect cvs update failure due to renamed projects
> ---
>
>  Key: GUMP-6
>  URL: http://issues.apache.org/jira/browse/GUMP-6
>  Project: Gump
> Type: Bug
>   Components: Java/XSLT
> Versions: unspecified
>  Environment: Operating System: All
> Platform: All
> Reporter: Michael Davey

>
> The update script does not detect when cvs fails to update due to the
> project being renamed.  As a result, cvs_index.html shows a "SUCCESS" status. 
> This can currently be seen with the Apache James project:
> cvs -z3 -d :ext:[EMAIL PROTECTED]:/home/cvs update -P -d -A jakarta-james cvs
> server: Updating jakarta-james cvs server: cannot open directory
> /home/cvs/jakarta-james: No such file or directory cvs server: skipping
> directory jakarta-james
> http://cvs.apache.org/builds/gump/latest/cvs_index.html
> http://cvs.apache.org/builds/gump/latest/cvs_jakarta-james.html
> Perhaps a new status of "SKIPPED" could be introduced.  Either way, the 
> current
> implementation can cause changes to go un-noticed for some time.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (GUMP-41) stress-testing using gump on new ASF hardware

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-41?page=history ]
 
Leo Simons resolved GUMP-41:


Resolution: Fixed

stress-testing was done a long time ago :-D

> stress-testing using gump on new ASF hardware
> -
>
>  Key: GUMP-41
>  URL: http://issues.apache.org/jira/browse/GUMP-41
>  Project: Gump
> Type: Task
> Versions: unspecified
>  Environment: linux, freebsd
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Apache will be stresstesting some new machines using gump. One of them will 
> keep running gump (probably on linux, but that's what the test is for), 
> others will be reassigned.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-25) document actual gump installations

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-25?page=history ]

Leo Simons updated GUMP-25:
---

Version: (was: unspecified)

> document actual gump installations
> --
>
>  Key: GUMP-25
>  URL: http://issues.apache.org/jira/browse/GUMP-25
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Reporter: Leo Simons
> Priority: Minor
>  Fix For: unspecified

>
> Add some docs on the wiki about the actual gump setups on various machines, 
> how they were set up, and how they are being maintained.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-26) keep around build logs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-26?page=history ]

Leo Simons updated GUMP-26:
---

Version: (was: unspecified)

> keep around build logs
> --
>
>  Key: GUMP-26
>  URL: http://issues.apache.org/jira/browse/GUMP-26
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Java gump used to keep around 5 days worth of build reports. We should have 
> something similar in gumpy, with the last five days kept in full, and perhaps 
> the last five weeks, and the last five months (ie your average backup 
> schedule policy). Maybe we can do compression using diffs, but not sure what 
> is the right space/computation tradeoff. We could put the logs in svn :-D

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-28) document gumpy internals

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-28?page=history ]

Leo Simons updated GUMP-28:
---

Version: (was: unspecified)

> document gumpy internals
> 
>
>  Key: GUMP-28
>  URL: http://issues.apache.org/jira/browse/GUMP-28
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Whilst gump user documentation and model documentation is quite reasonable, 
> gumpy's source is not the easiest to read atm. Some pydoc (is that what it's 
> called?) is in order, along with some high-level architecture info.
> Some of this stuff is already at
> http://wiki.apache.org/gump/GumpInternals
> but more work is to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-32) support configure/make/automake

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-32?page=history ]

Leo Simons updated GUMP-32:
---

Version: (was: unspecified)

> support configure/make/automake
> ---
>
>  Key: GUMP-32
>  URL: http://issues.apache.org/jira/browse/GUMP-32
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Gump currently knows how to interact with ant, and work is in progress on 
> interacting with maven, but gump doesn't know how to behave like (for 
> example) a C programmer.
> To build these kinds of projects, the GOM needs to change to have things like 
> , ,  and . In addition, I think we 
> need to have a , because building many projects is a sequence of 
> commands. Example (incomplete snippets):
> 
>   
> 
> 
>   value="--with-apxs=${installdir}"/>
>   
> 
> 
>   
> 
> 
>   
>   
>   
> 
> 
>   
>   
> 
> Besides changing the GOM, we need to check for the existence of these tools 
> (and figure out what to check for). Maybe we also need to implement some 
> generic property expansion...
> ...an option for getting this in place quickly is delegating these new tags 
> to ant buildfiles. The disadvantage from calling the tools directly might be 
> that what ant does differs a little from what the tools do by themselves...
> ...but if we go through ant for integrating these things, we can work 
> incrementally by creating some manual ant files for the first few projects 
> first. That might give good insight in what these tags need to look like.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-19) Support encoding of international characters in nag mail headers

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-19?page=history ]

Leo Simons updated GUMP-19:
---

Version: (was: unspecified)

> Support encoding of international characters in nag mail headers
> 
>
>  Key: GUMP-19
>  URL: http://issues.apache.org/jira/browse/GUMP-19
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Stefan Bodewig

>
> As wittnessed by the failing nag mails to log4j.
> Escaping of non-ASCII characters is well defined, sounds like a rather simple 
> fix that might make a good candidate fix for somebody with a very low working 
> knowledge of Python.  Read, I'll look into it unless anybody beats me.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-62) Module docs needs to point to fully qualified viewcvs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-62?page=history ]

Leo Simons updated GUMP-62:
---

Version: unspecified

> Module docs needs to point to fully qualified viewcvs
> -
>
>  Key: GUMP-62
>  URL: http://issues.apache.org/jira/browse/GUMP-62
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> If available allow user to click on a link to view source for a module.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-3)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-3?page=history ]

Leo Simons updated GUMP-3:
--

Version: (was: unspecified)

>  ---
>
>  Key: GUMP-3
>  URL: http://issues.apache.org/jira/browse/GUMP-3
>  Project: Gump
> Type: Bug
>   Components: Object Model (GOM)
> Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
> Reporter: Adam Jack
> Assignee: Adam Jack
> Priority: Blocker

>
> Today to get a package to work one needs a  definition, to teach Gump the outputs (jars) from the project/package.
> e.g.
>package="krysalis-centipede-1.0.0-beta5"/>
>   
> Unfortunately any  to 
> check out and/or build the project. Having to create a copy of the module.xml 
> in order to remove these tags is counterproductive.
> I beleive when Gump sees  module.xml.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-38) Does NOT cope with circular dependencies

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-38?page=history ]

Leo Simons updated GUMP-38:
---

Version: unspecified

> Does NOT cope with circular dependencies
> 
>
>  Key: GUMP-38
>  URL: http://issues.apache.org/jira/browse/GUMP-38
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack

>
> 1) Circular includes in metadata(href links that circle) are not detected. 
> Logic will spin until it crashes.
> 2) Circular dependencies (perhaps within project property based dependencies) 
> are not detected. Logic will spin until it crashes.
> (most recent call last):
>File "gump/integrate.py", line 85, in ?
>  irun()
>File "gump/integrate.py", line 56, in irun
>  workspace=WorkspaceLoader().load(ws, 0)
>File "/data3/gump/gump-install/python/gump/model/loader.py", line 96,
> in load
>  XMLServer.map, XMLTracker.map)
>File "/data3/gump/gump-install/python/gump/model/workspace.py", line
> 384, in complete
>  project.complete(self)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> << really big snip of identical errors >>
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 461, in complete
>  if self.ant: self.ant.expand(self,workspace)
>File "/data3/gump/gump-install/python/gump/model/ant.py", line 52, in
> expand
>  self.expandProperties(project,workspace)
>File "/data3/gump/gump-install/python/gump/model/ant.py", line 61, in
> expandProperties
>  self.importProperty(property)
>File "/data3/gump/gump-install/python/gump/model/property.py", line
> 164, in importProperty
>  self.addProperty(Property(xmlproperty,self))
>File "/data3/gump/gump-install/python/gump/model/property.py", line
> 27, in __init__
>  NamedModelObject.__init__(self,xml.getName(),xml,parent)
>File "/data3/gump/gump-install/python/gump/model/object.py", line
> 138, in __init__
>  ModelObject.__init__(self,xml,owner)
>File "/data3/gump/gump-install/python/gump/model/object.py", line 40,
> in __init__
>  FileHolder.__init__(self)
>File "/data3/gump/gump-install/python/gump/utils/file.py", line 154,
> in __init__
>  self.filelist=FileList(self)
>File "/data3/gump/gump-install/python/gump/utils/file.py", line 118,
> in __init__
>  Ownable.__init__(self,owner)
>File "/data3/gump/gump-install/python/gump/utils/owner.py", line 27,
> in __init__
>  self.setOwner(owner)
>File "/data3/gump/gump-install/python/gump/utils/owner.py", line 33,
> in setOwner
>  if self == owner:
> RuntimeError: maximum recursion depth exceeded
> Integration completed with exit code :  1
> Failed to integrate, exited with [1], exiting...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-61) Gump generated pages need a 'powered by python' logo

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-61?page=history ]

Leo Simons updated GUMP-61:
---

Version: unspecified

> Gump generated pages need a 'powered by python' logo
> 
>
>  Key: GUMP-61
>  URL: http://issues.apache.org/jira/browse/GUMP-61
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> See: http://www.python.org/community/logos.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-53) Re-including repositories causes corruption

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-53?page=history ]

Leo Simons updated GUMP-53:
---

Version: unspecified

> Re-including repositories causes corruption
> ---
>
>  Key: GUMP-53
>  URL: http://issues.apache.org/jira/browse/GUMP-53
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> Including  
>   SourceForgeSourceForge
>   http://sourceforge.net/http://sourceforge.net/
>   
> http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/
>   
> cvs.sourceforge.netcvs.sourceforge.net
> anonymousanonymous
> /cvsroot/cvsroot
> 
> pserverpserver
>   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-35) Failed to kill errant children

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-35?page=history ]

Leo Simons updated GUMP-35:
---

Version: unspecified

> Failed to kill errant children
> --
>
>  Key: GUMP-35
>  URL: http://issues.apache.org/jira/browse/GUMP-35
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack

>
> Gumpy attempt to use pgrep to find "timing out" children of itself, in order 
> to kill them. Since Gumpy uses system() to spwn them, it kills the shell not 
> the real children (grandchildren, etc.)
> Need a portable way to detect and kill all progeny of Gumpy when a timeout 
> occurs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-84) Packages defined in built modules are shown as "green" but they should be "blue"

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-84?page=history ]

Leo Simons updated GUMP-84:
---

Version: unspecified

> Packages defined in built modules are shown as "green" but they should be 
> "blue"
> 
>
>  Key: GUMP-84
>  URL: http://issues.apache.org/jira/browse/GUMP-84
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Stefano Mazzocchi

>
> packages are colored "blue" when they are not built by gump. Modules are 
> allowed to have their own internal packages, wrapping some of the jars they 
> contain in their repository. Gump should treat those the same as packages, 
> but currently it does not and it misleads the statistics.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-85) A package typo or mis-naming or mis-match crashes Gump

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-85?page=history ]

Leo Simons updated GUMP-85:
---

Version: unspecified

> A package typo or mis-naming or mis-match crashes Gump
> --
>
>  Key: GUMP-85
>  URL: http://issues.apache.org/jira/browse/GUMP-85
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Critical

>
> Gump ought not react so poorly to this.
> INFO:gump:Build Project: #[(122, 706)] : saxon6 :  [state:Unset]
> Traceback (most recent call last):
>   File "bin/integrate.py", line 109, in ?
> irun()
>   File "bin/integrate.py", line 86, in irun
> result = getRunner(run).perform()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/runner.py", line
> 213, in perform
> return self.performRun()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/demand.py", line
> 186, in performRun
> module=project.getModule()
>   File "/usr/local/gump/public/gump/python/gump/core/model/project.py", line
> 663, in getModule
> if not self.inModule(): raise RuntimeError, 'Project [' + self.name + ']
> not in a module.]'
> RuntimeError: Project [jdox] not in a module.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-3)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-3?page=history ]

Leo Simons updated GUMP-3:
--

Version: unspecified

>  ---
>
>  Key: GUMP-3
>  URL: http://issues.apache.org/jira/browse/GUMP-3
>  Project: Gump
> Type: Bug
>   Components: Object Model (GOM)
> Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
> Reporter: Adam Jack
> Assignee: Adam Jack
> Priority: Blocker

>
> Today to get a package to work one needs a  definition, to teach Gump the outputs (jars) from the project/package.
> e.g.
>package="krysalis-centipede-1.0.0-beta5"/>
>   
> Unfortunately any  to 
> check out and/or build the project. Having to create a copy of the module.xml 
> in order to remove these tags is counterproductive.
> I beleive when Gump sees  module.xml.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-88) ./gump fails with SyntaxError on Solaris8

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-88?page=history ]

Leo Simons updated GUMP-88:
---

Version: unspecified

> ./gump fails with SyntaxError on Solaris8
> -
>
>  Key: GUMP-88
>  URL: http://issues.apache.org/jira/browse/GUMP-88
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
>  Environment: Solaris v2.8
> Gump trunk
> Python v2.4
> Reporter: Graham Leggett

>
> If an attempt is made to check the gump code out of svn onto a solaris8 
> machine with python v2.4 installed, the following error results:
> bash-2.03$ ./gump validate
> ./gump: function: not found
>   Run the DTD validation tools on the metadata.
>   Usage:
> ./gump validate
> ./gump: function: not found
> ./gump: validate
> Adding the python -d flag, results in the following:
> bash-2.03$ python -d gump validate
>   File "gump", line 25
> function usage
>  ^
> SyntaxError: invalid syntax
> Checking out the same gump code from svn onto a MacOSX machine and running it 
> against python v2.3 shows that the same gump script works.
> It looks like gump in it's current form is not compatible with python v2.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-19) Support encoding of international characters in nag mail headers

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-19?page=history ]

Leo Simons updated GUMP-19:
---

Version: unspecified

> Support encoding of international characters in nag mail headers
> 
>
>  Key: GUMP-19
>  URL: http://issues.apache.org/jira/browse/GUMP-19
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Stefan Bodewig

>
> As wittnessed by the failing nag mails to log4j.
> Escaping of non-ASCII characters is well defined, sounds like a rather simple 
> fix that might make a good candidate fix for somebody with a very low working 
> knowledge of Python.  Read, I'll look into it unless anybody beats me.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-16) Support for

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-16?page=history ]

Leo Simons updated GUMP-16:
---

Version: unspecified

> Support for  ---
>
>  Key: GUMP-16
>  URL: http://issues.apache.org/jira/browse/GUMP-16
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
>  Environment: All
> Reporter: Adam Jack

>
> Gumpy needs to support  http://jakarta.apache.org/gump/metadata/project.html#nag

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-56) Project Stats Summary ought reflect Gumped/Not Gumped

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-56?page=history ]

Leo Simons updated GUMP-56:
---

Version: unspecified

> Project Stats Summary ought reflect Gumped/Not Gumped
> -
>
>  Key: GUMP-56
>  URL: http://issues.apache.org/jira/browse/GUMP-56
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> Project Statustics (the Summary) ought reflect active projects verses 
> packages, and it ought also reflect active (but not Gump built).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-54) wrap corrupts the data

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-54?page=history ]

Leo Simons updated GUMP-54:
---

Version: unspecified

> wrap corrupts the data
> --
>
>  Key: GUMP-54
>  URL: http://issues.apache.org/jira/browse/GUMP-54
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> Line wrap appears to corrupt the data, which make it almost unreadable. 
> [Note: The main build data is no longer wrapped,
> making this a minor issue.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-83) The

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-83?page=history ]

Leo Simons updated GUMP-83:
---

Version: unspecified

> The  --
>
>  Key: GUMP-83
>  URL: http://issues.apache.org/jira/browse/GUMP-83
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump, Object Model (GOM)
> Versions: unspecified
> Reporter: Adam Jack

>
> Gump knows that certain CLASSPATH directories needs to be built prior to the 
> build tool's JVM being started, or they will be dropped. As such the  element was added. This can be removed, and we can automatically do this for 
> all work directories, hence automatic the process and simplifying it for 
> users.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-76) Install Mono 1.0 on brutus

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-76?page=history ]

Leo Simons updated GUMP-76:
---

Version: unspecified

> Install Mono 1.0 on brutus
> --
>
>  Key: GUMP-76
>  URL: http://issues.apache.org/jira/browse/GUMP-76
>  Project: Gump
> Type: Wish
>   Components: Infrastructure
> Versions: unspecified
> Reporter: Stefan Bodewig
> Assignee: Stefan Bodewig
> Priority: Minor

>
> See  for
> context, it would immediately benefit Ant which has unit tests for
> some of its .NET tasks.
> Debian packages are available from http://pkg-mono.alioth.debian.org/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-17) Failed to 'list .HTML files as work'

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-17?page=history ]

Leo Simons updated GUMP-17:
---

Version: unspecified

> Failed to 'list .HTML files as work'
> 
>
>  Key: GUMP-17
>  URL: http://issues.apache.org/jira/browse/GUMP-17
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor

>
> listFilesAsWork generates a sub page, names that page, and displays the 
> contents. This somehow fails when the file is a .html, since it gets a 
> .html.html extension & breaks (perhaps in Forrest).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-87) Be able to view unit tests (and other files) generated by Maven builds

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-87?page=history ]

Leo Simons updated GUMP-87:
---

Version: unspecified

> Be able to view unit tests (and other files) generated by Maven builds
> --
>
>  Key: GUMP-87
>  URL: http://issues.apache.org/jira/browse/GUMP-87
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Eric Pugh

>
> Hi all,
> I notice that gump links in a lot of files that it generates, like the
> project.properties etc.  However, the output from running unit tests is not
> available.  Is there anyway to find this?
> A couple of the Fulcrum projects are failing on their tests...
> http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/i
> ndex.html
> I wondered if I could see them by pulling up a directory like:
> http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/g
> ump_file/target/test-reports
> but no joy...
> Eric

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-71) Gump Run GUID should use hostname and FQDN

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-71?page=history ]

Leo Simons updated GUMP-71:
---

Version: unspecified

> Gump Run GUID should use hostname and FQDN
> --
>
>  Key: GUMP-71
>  URL: http://issues.apache.org/jira/browse/GUMP-71
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Nick Chalko
> Priority: Minor

>
> The gump run is looks like this
> brutus:brutus-public:20040624 21:00:11
> it should look like  
> brutus.apache.org:brutus-public:20040624 21:00:11

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-20) Dependecies/Dependees are over counted

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-20?page=history ]

Leo Simons updated GUMP-20:
---

Version: unspecified

> Dependecies/Dependees are over counted
> --
>
>  Key: GUMP-20
>  URL: http://issues.apache.org/jira/browse/GUMP-20
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack

>
> This list is clearly wrong:
> http://lsd.student.utwente.nl/gump/scarab/scarab_details.html#Full+Project+Dependencies
> The primary reason is that this count of unique dependency objects (an entity 
> which links to projects) not the results of the dependency itself -- the 
> dependent project. Dependency objects are owned (they form a bi-directional 
> link) and the owner is part of the __eq__ (equality check) which I think is 
> probably valid (albeit annoying here.)
> As such when we attempt to count only unique dependencies and does 'if not 
> depend in depends:' -- the __eq__ says no. The problem becomes worsened when 
> on considered jars ids. Are two depends on the same project equal if they 
> reference different ids? I'd say no.
> I suspect the best thing to do is to keep this up at the project level, find 
> a way to compare two dependencies only by the project they reference. I 
> wonder if Gumpy needs a way to optimize/merge dependencies, so repeats are 
> reduced. That said, there are multiple areas (not jsut counters/lists) that 
> need to have the right answer, and doing this wrong could dork classpaths.
> Honestly, I don't know the right way to fix this, hence this JIRA posting to 
> let the thought sit openly for a while...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-62) Module docs needs to point to fully qualified viewcvs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-62?page=history ]

Leo Simons updated GUMP-62:
---

Component: Python

> Module docs needs to point to fully qualified viewcvs
> -
>
>  Key: GUMP-62
>  URL: http://issues.apache.org/jira/browse/GUMP-62
>  Project: Gump
> Type: Improvement
>   Components: Python
> Reporter: Adam Jack
> Priority: Minor

>
> If available allow user to click on a link to view source for a module.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-54) wrap corrupts the data

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-54?page=history ]

Leo Simons updated GUMP-54:
---

Fix Version: unspecified

> wrap corrupts the data
> --
>
>  Key: GUMP-54
>  URL: http://issues.apache.org/jira/browse/GUMP-54
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: unspecified

>
> Line wrap appears to corrupt the data, which make it almost unreadable. 
> [Note: The main build data is no longer wrapped,
> making this a minor issue.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-62) Module docs needs to point to fully qualified viewcvs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-62?page=history ]

Leo Simons updated GUMP-62:
---

Fix Version: unspecified

> Module docs needs to point to fully qualified viewcvs
> -
>
>  Key: GUMP-62
>  URL: http://issues.apache.org/jira/browse/GUMP-62
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: unspecified

>
> If available allow user to click on a link to view source for a module.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-35) Failed to kill errant children

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-35?page=history ]

Leo Simons updated GUMP-35:
---

Fix Version: unspecified

> Failed to kill errant children
> --
>
>  Key: GUMP-35
>  URL: http://issues.apache.org/jira/browse/GUMP-35
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
>  Fix For: unspecified

>
> Gumpy attempt to use pgrep to find "timing out" children of itself, in order 
> to kill them. Since Gumpy uses system() to spwn them, it kills the shell not 
> the real children (grandchildren, etc.)
> Need a portable way to detect and kill all progeny of Gumpy when a timeout 
> occurs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-82) Keep only the jars from the last successful build

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-82?page=history ]

Leo Simons updated GUMP-82:
---

Fix Version: unspecified

> Keep only the jars from the last successful build
> -
>
>  Key: GUMP-82
>  URL: http://issues.apache.org/jira/browse/GUMP-82
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Stefano Mazzocchi
>  Fix For: unspecified

>
> Currently, gump saves all jars and then a cron job removes them after a week. 
> I think it's a waste of space since what we really need is just the latest 
> one that was built.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-46) Gumpy not creating valid classpath

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-46?page=history ]

Leo Simons updated GUMP-46:
---

Fix Version: unspecified

> Gumpy not creating valid  classpath
> 
>
>  Key: GUMP-46
>  URL: http://issues.apache.org/jira/browse/GUMP-46
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Vincent Massol
>  Fix For: unspecified

>
> It seems the following configuration which was working fine with Gump is no 
> longer working with Gumpy:
> 
> [...]
>   
>   
> [...]
> 
> It seems the properties are correctly created by the classpath does not 
> include correctly the 2 jar.
> A possible workaround is:
> 
> [...]
>   
>id="standard"/>
> [...]
> 
> 
> 
> But it's not as nice as before...
> Thanks
> -Vincent

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-61) Gump generated pages need a 'powered by python' logo

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-61?page=history ]

Leo Simons updated GUMP-61:
---

Fix Version: unspecified

> Gump generated pages need a 'powered by python' logo
> 
>
>  Key: GUMP-61
>  URL: http://issues.apache.org/jira/browse/GUMP-61
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: unspecified

>
> See: http://www.python.org/community/logos.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-71) Gump Run GUID should use hostname and FQDN

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-71?page=history ]

Leo Simons updated GUMP-71:
---

Fix Version: unspecified

> Gump Run GUID should use hostname and FQDN
> --
>
>  Key: GUMP-71
>  URL: http://issues.apache.org/jira/browse/GUMP-71
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Nick Chalko
> Priority: Minor
>  Fix For: unspecified

>
> The gump run is looks like this
> brutus:brutus-public:20040624 21:00:11
> it should look like  
> brutus.apache.org:brutus-public:20040624 21:00:11

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-81) Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-81?page=history ]

Leo Simons updated GUMP-81:
---

Fix Version: unspecified

> Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames
> 
>
>  Key: GUMP-81
>  URL: http://issues.apache.org/jira/browse/GUMP-81
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
>  Fix For: unspecified

>
> A circumstance was found whereby 'resume.xml' (with an e acute) in a module 
> (XOM, FWIIW) was checked out of the repository, but the (Python code) 'sync' 
> to a working directory failed. It failed because Python's os.listdir returned 
> a string for it, not Unicode (although it returned unicode for al lthe plain 
> file). This seems related to the fact that the default filesystem encoding on 
> the platofrm was 'ascii', and this file was not ascii.
> We need to create a test for such files, then work with Gump to resolve this 
> issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-72) Requirement for multiple license file declarations.

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-72?page=history ]

Leo Simons updated GUMP-72:
---

Fix Version: unspecified

> Requirement for multiple license file declarations.
> ---
>
>  Key: GUMP-72
>  URL: http://issues.apache.org/jira/browse/GUMP-72
>  Project: Gump
> Type: Improvement
>   Components: Object Model (GOM)
> Versions: GOM-0.4
> Reporter: Stephen McConnell
> Priority: Minor
>  Fix For: GOM-0.5

>
> Gump currently limits the declaration of a license to a single file however, 
> the ASL two separates the license into LICENSE.TXT and NOTICE.TXT.  What is 
> needed is something like:
>   
> 
> 
> ..
>   
> Or alternatively:
>   
> 
> 
> ..
>   
> Steve.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-17) Failed to 'list .HTML files as work'

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-17?page=history ]

Leo Simons updated GUMP-17:
---

Fix Version: unspecified

> Failed to 'list .HTML files as work'
> 
>
>  Key: GUMP-17
>  URL: http://issues.apache.org/jira/browse/GUMP-17
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: unspecified

>
> listFilesAsWork generates a sub page, names that page, and displays the 
> contents. This somehow fails when the file is a .html, since it gets a 
> .html.html extension & breaks (perhaps in Forrest).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-36) Generate source diff report on build failure

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-36?page=history ]

Leo Simons updated GUMP-36:
---

Fix Version: unspecified

> Generate source diff report on build failure
> 
>
>  Key: GUMP-36
>  URL: http://issues.apache.org/jira/browse/GUMP-36
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Vincent Massol
>  Fix For: unspecified

>
> When a project fails to build, generate a report containing the following 
> information:
> - CVS source diff on the project itself between the last success build and 
> the current checked out sources
> - CVS source diffs on the project first level dependencies between the last 
> success build and the current checked out sources
> - CVS source diff on Gump project files between the last success build and 
> the current checked out sources.
> The idea is to help devlopers of the failed project in indentifying the 
> reason of the failure.
> See 
> http://blogs.codehaus.org/people/vmassol/archives/000644_diffing_continuous_build_results.html
>  for more details.
> Thanks
> -Vincent

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-85) A package typo or mis-naming or mis-match crashes Gump

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-85?page=history ]

Leo Simons updated GUMP-85:
---

Fix Version: unspecified

> A package typo or mis-naming or mis-match crashes Gump
> --
>
>  Key: GUMP-85
>  URL: http://issues.apache.org/jira/browse/GUMP-85
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
> Priority: Critical
>  Fix For: unspecified

>
> Gump ought not react so poorly to this.
> INFO:gump:Build Project: #[(122, 706)] : saxon6 :  [state:Unset]
> Traceback (most recent call last):
>   File "bin/integrate.py", line 109, in ?
> irun()
>   File "bin/integrate.py", line 86, in irun
> result = getRunner(run).perform()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/runner.py", line
> 213, in perform
> return self.performRun()
>   File "/usr/local/gump/public/gump/python/gump/core/runner/demand.py", line
> 186, in performRun
> module=project.getModule()
>   File "/usr/local/gump/public/gump/python/gump/core/model/project.py", line
> 663, in getModule
> if not self.inModule(): raise RuntimeError, 'Project [' + self.name + ']
> not in a module.]'
> RuntimeError: Project [jdox] not in a module.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-57) A 'stale' state is needed

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-57?page=history ]

Leo Simons updated GUMP-57:
---

Fix Version: unspecified

> A 'stale' state is needed
> -
>
>  Key: GUMP-57
>  URL: http://issues.apache.org/jira/browse/GUMP-57
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Adam Jack
>  Fix For: unspecified

>
> We need a 'stale' state (for when CVS|sVN updates fail, but we build off 
> 'older' code)
> We need a matching SVG
> We need propogation logic to ensure we know that this project was build off 
> something stale N level below.
> We could set any project not on CVS|SVN head as stale..

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-49) Build start and end times (in UTC)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-49?page=history ]

Leo Simons updated GUMP-49:
---

Fix Version: unspecified

> Build start and end times (in UTC)
> --
>
>  Key: GUMP-49
>  URL: http://issues.apache.org/jira/browse/GUMP-49
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
>  Environment: n/a
> Reporter: Michael Davey
> Priority: Trivial
>  Fix For: unspecified

>
> As requested by Adam, I'm logging this as an RFE:
> Please put the build start and end times (in UTC) at the following places:
> 1) The proposed page comparing the entities where a status differs (on the N 
> servers any Gump is aware of).
> 2) On pages like this one 
> 
> Cheers,
> -- 
> Michael

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-80) Documentation needs updating (validating)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-80?page=history ]

Leo Simons updated GUMP-80:
---

Fix Version: unspecified

> Documentation needs updating (validating)
> -
>
>  Key: GUMP-80
>  URL: http://issues.apache.org/jira/browse/GUMP-80
>  Project: Gump
> Type: Bug
>   Components: Documentation
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump2

>
> A new user ought be able to read the documentation (on gump.apache.org w/o 
> need to go to wiki.apache.org/gump) and run Gump without questions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-19) Support encoding of international characters in nag mail headers

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-19?page=history ]

Leo Simons updated GUMP-19:
---

Fix Version: unspecified

> Support encoding of international characters in nag mail headers
> 
>
>  Key: GUMP-19
>  URL: http://issues.apache.org/jira/browse/GUMP-19
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Stefan Bodewig
>  Fix For: unspecified

>
> As wittnessed by the failing nag mails to log4j.
> Escaping of non-ASCII characters is well defined, sounds like a rather simple 
> fix that might make a good candidate fix for somebody with a very low working 
> knowledge of Python.  Read, I'll look into it unless anybody beats me.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-88) ./gump fails with SyntaxError on Solaris8

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-88?page=history ]

Leo Simons updated GUMP-88:
---

Fix Version: unspecified

> ./gump fails with SyntaxError on Solaris8
> -
>
>  Key: GUMP-88
>  URL: http://issues.apache.org/jira/browse/GUMP-88
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: unspecified
>  Environment: Solaris v2.8
> Gump trunk
> Python v2.4
> Reporter: Graham Leggett
>  Fix For: unspecified

>
> If an attempt is made to check the gump code out of svn onto a solaris8 
> machine with python v2.4 installed, the following error results:
> bash-2.03$ ./gump validate
> ./gump: function: not found
>   Run the DTD validation tools on the metadata.
>   Usage:
> ./gump validate
> ./gump: function: not found
> ./gump: validate
> Adding the python -d flag, results in the following:
> bash-2.03$ python -d gump validate
>   File "gump", line 25
> function usage
>  ^
> SyntaxError: invalid syntax
> Checking out the same gump code from svn onto a MacOSX machine and running it 
> against python v2.3 shows that the same gump script works.
> It looks like gump in it's current form is not compatible with python v2.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-25) document actual gump installations

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-25?page=history ]

Leo Simons updated GUMP-25:
---

Version: unspecified

> document actual gump installations
> --
>
>  Key: GUMP-25
>  URL: http://issues.apache.org/jira/browse/GUMP-25
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Leo Simons
> Priority: Minor
>  Fix For: unspecified

>
> Add some docs on the wiki about the actual gump setups on various machines, 
> how they were set up, and how they are being maintained.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-21) FOG factor is misleading and requires improvement

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-21?page=history ]

Leo Simons updated GUMP-21:
---

Fix Version: unspecified

> FOG factor is misleading and requires improvement
> -
>
>  Key: GUMP-21
>  URL: http://issues.apache.org/jira/browse/GUMP-21
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Daniel Savarese
> Assignee: Adam Jack
>  Fix For: unspecified

>
> FOG is defined right now as:
> def getFOGFactor(self):
> return round((float(self.successes) / (float(self.failures) + 
> float(self.prereqs))), 2)
> This is not helpful.  Last month, jakart-oro
> failed to build by coincidence around the time of a Gump
> run and the problem was fixed before the next Gump run,
> yet its FOG factor dropped in half.  The responsiveness
> to resolving build and integration problems is not taken
> into account.  It is likely that it is impossible for FOG
> to mean anything because the factors that determine
> a project's "health" (to borrow the term used by Adam Jack
> in an email to the commons-dev and gump lists) are largely
> orthogonal.  FOG should probably be a vector and if you really
> wanted a single number you could use the length of that vector.
> One of the major problems with the current factor is that
> a project's FOG factor continues to increase when no changes
> have been made to the repository.  It's not meaningful to
> count only successful builds towards improving the factor
> because no changes may have been made to the code base.
> Ideally, you count only builds that cause no failures after
> a change to the code base.  FOG doesn't factor in how quickly
> (or slowly) projects recover from build failures, and how often
> changes to a code base cause failures (either in itself or in
> other projects).  Right now, a project with few code changes
> (say once a month) that causes a failure 50% (1 every 2 months)
> of the time the code is changed with a mean time of failure
> correction of 1 week is deemed more reliable (higher FOG factor)
> than a project that makes frequent changes (say every day) to
> its code base and causes a failure 10% of the time (1 every 10
> days) with a mean time of failure correction of 1 day.  That's
> because FOG is based almost entirely on consecutive successful
> Gump builds, which is not useful.
> Rather than propose a new meaningless way of computing FOG, I
> suggest FOG stop being used temporarily.  It would be more
> useful to break out and report all of the independently useful
> metrics and through experience over time determine how each
> impacts the overall notion of FOG and eventually derive a
> way of condensing the information (perhaps a FOG factor,
> perhaps a vector) in a useful manner.  Right now the state
> of affairs is that someone decided FOG was a cool thing, so
> it's being reported and people see this number and mistakenly
> think a project with half the FOG factor of another is
> less dependable and therefore avoid using it.  Alternatively
> an explanation of what FOG is intended to compute and how
> it is computed should be placed on Gump reports that list
> FOG so that consumers of the information will not be misled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-29) new user howto

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-29?page=history ]

Leo Simons updated GUMP-29:
---

Version: unspecified

> new user howto
> --
>
>  Key: GUMP-29
>  URL: http://issues.apache.org/jira/browse/GUMP-29
>  Project: Gump
> Type: Improvement
>   Components: Documentation
> Versions: Gump3-beta, Gump3-alpha
> Reporter: Leo Simons
> Assignee: Leo Simons
>  Fix For: Gump3-beta

>
> New users seem weary of editing gump descriptors (especially when they don't 
> live in their "own" cvs module but they have to change things in the gump 
> repository), and most of them are very sketchy as to the steps one takes to 
> fix things. Niclas Hedhman' recent experience in getting some of avalon to 
> build using gump and the talk resulting from it on avalon-dev and 
> gump-general are a good example of a new user we need to talk through things.
> We need a howto. Not just the technical explanation, but some philosophy 
> ("Everyone is free to work on gump. Everyone." Stuff like that) intertwined.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-39) gump-check ant task

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-39?page=history ]

Leo Simons updated GUMP-39:
---

Version: unspecified

> gump-check ant task
> ---
>
>  Key: GUMP-39
>  URL: http://issues.apache.org/jira/browse/GUMP-39
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Leo Simons
>  Fix For: unspecified

>
> You want the ability to verify a project state is consistent with what gump 
> expects it to be after a build, but only gump can verify that.
> Maybe we could have an ant task that talks to the gump repository to keep 
> (nay, improve on) that functionality.
>  
>  
>   
>  
>  
>  
>  
> the gump-check task would get a list of requirements from the gump server 
> (ie, what jars should exist, what directories, licenses, ...)
> and compare that info to the filesystem. It would warn the user of any errors.
> Mailing list thread @ http://nagoya.apache.org/eyebrowse/[EMAIL 
> PROTECTED]&by=thread&from=682505

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-28) document gumpy internals

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-28?page=history ]

Leo Simons updated GUMP-28:
---

Version: unspecified

> document gumpy internals
> 
>
>  Key: GUMP-28
>  URL: http://issues.apache.org/jira/browse/GUMP-28
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Whilst gump user documentation and model documentation is quite reasonable, 
> gumpy's source is not the easiest to read atm. Some pydoc (is that what it's 
> called?) is in order, along with some high-level architecture info.
> Some of this stuff is already at
> http://wiki.apache.org/gump/GumpInternals
> but more work is to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-32) support configure/make/automake

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-32?page=history ]

Leo Simons updated GUMP-32:
---

Version: unspecified

> support configure/make/automake
> ---
>
>  Key: GUMP-32
>  URL: http://issues.apache.org/jira/browse/GUMP-32
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: unspecified
> Reporter: Leo Simons
>  Fix For: unspecified

>
> Gump currently knows how to interact with ant, and work is in progress on 
> interacting with maven, but gump doesn't know how to behave like (for 
> example) a C programmer.
> To build these kinds of projects, the GOM needs to change to have things like 
> , ,  and . In addition, I think we 
> need to have a , because building many projects is a sequence of 
> commands. Example (incomplete snippets):
> 
>   
> 
> 
>   value="--with-apxs=${installdir}"/>
>   
> 
> 
>   
> 
> 
>   
>   
>   
> 
> 
>   
>   
> 
> Besides changing the GOM, we need to check for the existence of these tools 
> (and figure out what to check for). Maybe we also need to implement some 
> generic property expansion...
> ...an option for getting this in place quickly is delegating these new tags 
> to ant buildfiles. The disadvantage from calling the tools directly might be 
> that what ant does differs a little from what the tools do by themselves...
> ...but if we go through ant for integrating these things, we can work 
> incrementally by creating some manual ant files for the first few projects 
> first. That might give good insight in what these tags need to look like.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-29) new user howto

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-29?page=history ]

Leo Simons updated GUMP-29:
---

Version: Gump3-beta

> new user howto
> --
>
>  Key: GUMP-29
>  URL: http://issues.apache.org/jira/browse/GUMP-29
>  Project: Gump
> Type: Improvement
>   Components: Documentation
> Versions: Gump3-beta, Gump3-alpha
> Reporter: Leo Simons
>  Fix For: Gump3-beta

>
> New users seem weary of editing gump descriptors (especially when they don't 
> live in their "own" cvs module but they have to change things in the gump 
> repository), and most of them are very sketchy as to the steps one takes to 
> fix things. Niclas Hedhman' recent experience in getting some of avalon to 
> build using gump and the talk resulting from it on avalon-dev and 
> gump-general are a good example of a new user we need to talk through things.
> We need a howto. Not just the technical explanation, but some philosophy 
> ("Everyone is free to work on gump. Everyone." Stuff like that) intertwined.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-29) new user howto

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-29?page=history ]

Leo Simons updated GUMP-29:
---

  Assign To: (was: Leo Simons)
Version: Gump3-alpha
 (was: unspecified)
Fix Version: Gump3-beta
 (was: unspecified)

> new user howto
> --
>
>  Key: GUMP-29
>  URL: http://issues.apache.org/jira/browse/GUMP-29
>  Project: Gump
> Type: Improvement
>   Components: Documentation
> Versions: Gump3-beta, Gump3-alpha
> Reporter: Leo Simons
>  Fix For: Gump3-beta

>
> New users seem weary of editing gump descriptors (especially when they don't 
> live in their "own" cvs module but they have to change things in the gump 
> repository), and most of them are very sketchy as to the steps one takes to 
> fix things. Niclas Hedhman' recent experience in getting some of avalon to 
> build using gump and the talk resulting from it on avalon-dev and 
> gump-general are a good example of a new user we need to talk through things.
> We need a howto. Not just the technical explanation, but some philosophy 
> ("Everyone is free to work on gump. Everyone." Stuff like that) intertwined.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-66) Run gump as a service

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-66?page=history ]

Leo Simons updated GUMP-66:
---

Version: Gump2
 (was: unspecified)
  Component: Python-based Gump
 (was: Infrastructure)
Fix Version: Gump2
 (was: unspecified)

> Run gump as a service
> -
>
>  Key: GUMP-66
>  URL: http://issues.apache.org/jira/browse/GUMP-66
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
>  Environment: Brutus (and similar)
> Reporter: Adam Jack
>  Fix For: Gump2

>
> Currently Gump runs from cron, at intervals, *if* Gump is not still running 
> (from a previous run). This is somewhat haphazard, and a waste of spare 
> cycles. Gump needs to be able to be run continuously, starting a new run a 
> soon as the last has completed. This seems like some sort of 'service' 
> script, but it is likely OS specific.
> The script that runs this countinuously could call gumpy.sh (or gumpy.py) and 
> launch runs with varied commandline parameters. For example, it could make 
> every Nth run an official run, or make N-1 'optimized' (only compile if 
> something changed) and the Nth full, etc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-30) put installed packages under version control

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-30?page=history ]

Leo Simons updated GUMP-30:
---

Environment: brutus  (was: )

> put installed packages under version control
> 
>
>  Key: GUMP-30
>  URL: http://issues.apache.org/jira/browse/GUMP-30
>  Project: Gump
> Type: New Feature
>   Components: Infrastructure
> Versions: unspecified
>  Environment: brutus
> Reporter: Leo Simons
>  Fix For: unspecified

>
> some parts of each gump installations are currently manually maintained and 
> rsynced over between various machines, because they can't live in the public 
> tree. This is undesireable. Thought about it in the past. We need a private 
> CVS tree (as in non-browseable by non-asf people) that contains these 
> packages. It'll enable us to be aware of when someone updates a package.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-40) non-committers can modify (some) descriptors

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-40?page=history ]

Leo Simons updated GUMP-40:
---

  Version: GOM-0.4
   GOM-0.5
   (was: unspecified)
Component: Infrastructure
   (was: Object Model (GOM))

> non-committers can modify (some) descriptors
> 
>
>  Key: GUMP-40
>  URL: http://issues.apache.org/jira/browse/GUMP-40
>  Project: Gump
> Type: Wish
>   Components: Infrastructure
> Versions: GOM-0.4, GOM-0.5
> Reporter: Leo Simons
>  Fix For: unspecified

>
> It would be nice if people who are not committers @ the ASF have a way to 
> modify descriptors, in particular developers of non-ASF projects maintaining 
> the descriptors of those projects. This is currently done by putting those 
> descriptors in a seperate cvs module and accessing them through ViewCVS, but 
> this has several downsides as has been discussed here:
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=681442
> Possible alternatives could be a publicly writeable repository, an 
> access-by-request repository, a web application with granular auth&access 
> control, or all of the above.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-58) Respect list prefixing requests (like jakarta-commons) has

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-58?page=history ]

Leo Simons updated GUMP-58:
---

Version: Gump2
 GOM-0.4
 (was: unspecified)
Fix Version: Gump2
 GOM-0.4
 (was: unspecified)

> Respect list prefixing requests (like jakarta-commons) has
> --
>
>  Key: GUMP-58
>  URL: http://issues.apache.org/jira/browse/GUMP-58
>  Project: Gump
> Type: Improvement
>   Components: Object Model (GOM), Python-based Gump
> Versions: Gump2, GOM-0.4
> Reporter: Adam Jack
>  Fix For: Gump2, GOM-0.4

>
> Allow a prefix attribute and place that prior to Gump's prefix.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-21) FOG factor is misleading and requires improvement

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-21?page=history ]

Leo Simons updated GUMP-21:
---

Fix Version: Gump2
 (was: unspecified)

> FOG factor is misleading and requires improvement
> -
>
>  Key: GUMP-21
>  URL: http://issues.apache.org/jira/browse/GUMP-21
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Daniel Savarese
> Assignee: Adam Jack
>  Fix For: Gump2

>
> FOG is defined right now as:
> def getFOGFactor(self):
> return round((float(self.successes) / (float(self.failures) + 
> float(self.prereqs))), 2)
> This is not helpful.  Last month, jakart-oro
> failed to build by coincidence around the time of a Gump
> run and the problem was fixed before the next Gump run,
> yet its FOG factor dropped in half.  The responsiveness
> to resolving build and integration problems is not taken
> into account.  It is likely that it is impossible for FOG
> to mean anything because the factors that determine
> a project's "health" (to borrow the term used by Adam Jack
> in an email to the commons-dev and gump lists) are largely
> orthogonal.  FOG should probably be a vector and if you really
> wanted a single number you could use the length of that vector.
> One of the major problems with the current factor is that
> a project's FOG factor continues to increase when no changes
> have been made to the repository.  It's not meaningful to
> count only successful builds towards improving the factor
> because no changes may have been made to the code base.
> Ideally, you count only builds that cause no failures after
> a change to the code base.  FOG doesn't factor in how quickly
> (or slowly) projects recover from build failures, and how often
> changes to a code base cause failures (either in itself or in
> other projects).  Right now, a project with few code changes
> (say once a month) that causes a failure 50% (1 every 2 months)
> of the time the code is changed with a mean time of failure
> correction of 1 week is deemed more reliable (higher FOG factor)
> than a project that makes frequent changes (say every day) to
> its code base and causes a failure 10% of the time (1 every 10
> days) with a mean time of failure correction of 1 day.  That's
> because FOG is based almost entirely on consecutive successful
> Gump builds, which is not useful.
> Rather than propose a new meaningless way of computing FOG, I
> suggest FOG stop being used temporarily.  It would be more
> useful to break out and report all of the independently useful
> metrics and through experience over time determine how each
> impacts the overall notion of FOG and eventually derive a
> way of condensing the information (perhaps a FOG factor,
> perhaps a vector) in a useful manner.  Right now the state
> of affairs is that someone decided FOG was a cool thing, so
> it's being reported and people see this number and mistakenly
> think a project with half the FOG factor of another is
> less dependable and therefore avoid using it.  Alternatively
> an explanation of what FOG is intended to compute and how
> it is computed should be placed on Gump reports that list
> FOG so that consumers of the information will not be misled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-71) Gump Run GUID should use hostname and FQDN

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-71?page=history ]

Leo Simons updated GUMP-71:
---

Fix Version: Gump2
 (was: unspecified)

> Gump Run GUID should use hostname and FQDN
> --
>
>  Key: GUMP-71
>  URL: http://issues.apache.org/jira/browse/GUMP-71
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Nick Chalko
> Priority: Minor
>  Fix For: Gump2

>
> The gump run is looks like this
> brutus:brutus-public:20040624 21:00:11
> it should look like  
> brutus.apache.org:brutus-public:20040624 21:00:11

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-16) Support for

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-16?page=history ]

Leo Simons updated GUMP-16:
---

Fix Version: Gump2
 (was: unspecified)

> Support for  ---
>
>  Key: GUMP-16
>  URL: http://issues.apache.org/jira/browse/GUMP-16
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
>  Environment: All
> Reporter: Adam Jack
>  Fix For: Gump2

>
> Gumpy needs to support  http://jakarta.apache.org/gump/metadata/project.html#nag

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-81) Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-81?page=history ]

Leo Simons updated GUMP-81:
---

Fix Version: Gump2
 (was: unspecified)

> Gump (or it's tools, CVS, etc.) does not cope with Unicode filenames
> 
>
>  Key: GUMP-81
>  URL: http://issues.apache.org/jira/browse/GUMP-81
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump2

>
> A circumstance was found whereby 'resume.xml' (with an e acute) in a module 
> (XOM, FWIIW) was checked out of the repository, but the (Python code) 'sync' 
> to a working directory failed. It failed because Python's os.listdir returned 
> a string for it, not Unicode (although it returned unicode for al lthe plain 
> file). This seems related to the fact that the default filesystem encoding on 
> the platofrm was 'ascii', and this file was not ascii.
> We need to create a test for such files, then work with Gump to resolve this 
> issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-61) Gump generated pages need a 'powered by python' logo

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-61?page=history ]

Leo Simons updated GUMP-61:
---

Fix Version: Gump2
 (was: unspecified)

> Gump generated pages need a 'powered by python' logo
> 
>
>  Key: GUMP-61
>  URL: http://issues.apache.org/jira/browse/GUMP-61
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> See: http://www.python.org/community/logos.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-28) document gumpy internals

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-28?page=history ]

Leo Simons updated GUMP-28:
---

Fix Version: Gump2
 (was: unspecified)

> document gumpy internals
> 
>
>  Key: GUMP-28
>  URL: http://issues.apache.org/jira/browse/GUMP-28
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump2

>
> Whilst gump user documentation and model documentation is quite reasonable, 
> gumpy's source is not the easiest to read atm. Some pydoc (is that what it's 
> called?) is in order, along with some high-level architecture info.
> Some of this stuff is already at
> http://wiki.apache.org/gump/GumpInternals
> but more work is to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-57) A 'stale' state is needed

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-57?page=history ]

Leo Simons updated GUMP-57:
---

Fix Version: Gump2
 (was: unspecified)

> A 'stale' state is needed
> -
>
>  Key: GUMP-57
>  URL: http://issues.apache.org/jira/browse/GUMP-57
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump2

>
> We need a 'stale' state (for when CVS|sVN updates fail, but we build off 
> 'older' code)
> We need a matching SVG
> We need propogation logic to ensure we know that this project was build off 
> something stale N level below.
> We could set any project not on CVS|SVN head as stale..

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-17) Failed to 'list .HTML files as work'

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-17?page=history ]

Leo Simons updated GUMP-17:
---

Fix Version: Gump2
 (was: unspecified)

> Failed to 'list .HTML files as work'
> 
>
>  Key: GUMP-17
>  URL: http://issues.apache.org/jira/browse/GUMP-17
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> listFilesAsWork generates a sub page, names that page, and displays the 
> contents. This somehow fails when the file is a .html, since it gets a 
> .html.html extension & breaks (perhaps in Forrest).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-26) keep around build logs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-26?page=history ]

Leo Simons updated GUMP-26:
---

Fix Version: Gump2
 (was: unspecified)

> keep around build logs
> --
>
>  Key: GUMP-26
>  URL: http://issues.apache.org/jira/browse/GUMP-26
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump2

>
> Java gump used to keep around 5 days worth of build reports. We should have 
> something similar in gumpy, with the last five days kept in full, and perhaps 
> the last five weeks, and the last five months (ie your average backup 
> schedule policy). Maybe we can do compression using diffs, but not sure what 
> is the right space/computation tradeoff. We could put the logs in svn :-D

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-89) support

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-89?page=history ]

Leo Simons updated GUMP-89:
---

Fix Version: Gump2
 (was: unspecified)

> support  
>
>  Key: GUMP-89
>  URL: http://issues.apache.org/jira/browse/GUMP-89
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump2

>
> Gump should support :
>   http://gump.apache.org/metadata/project.html#junitreport
> the referenced directories should be published as part of the logs whether or 
> not the project build is successful, and linked to from the gump html pages, 
> probably as part of the "Output Artifacts" section on the "details" page of a 
> project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-56) Project Stats Summary ought reflect Gumped/Not Gumped

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-56?page=history ]

Leo Simons updated GUMP-56:
---

Fix Version: Gump2
 (was: unspecified)

> Project Stats Summary ought reflect Gumped/Not Gumped
> -
>
>  Key: GUMP-56
>  URL: http://issues.apache.org/jira/browse/GUMP-56
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> Project Statustics (the Summary) ought reflect active projects verses 
> packages, and it ought also reflect active (but not Gump built).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-21) FOG factor is misleading and requires improvement

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-21?page=history ]

Leo Simons updated GUMP-21:
---

Version: Gump2
 (was: unspecified)

> FOG factor is misleading and requires improvement
> -
>
>  Key: GUMP-21
>  URL: http://issues.apache.org/jira/browse/GUMP-21
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Daniel Savarese
> Assignee: Adam Jack
>  Fix For: Gump2

>
> FOG is defined right now as:
> def getFOGFactor(self):
> return round((float(self.successes) / (float(self.failures) + 
> float(self.prereqs))), 2)
> This is not helpful.  Last month, jakart-oro
> failed to build by coincidence around the time of a Gump
> run and the problem was fixed before the next Gump run,
> yet its FOG factor dropped in half.  The responsiveness
> to resolving build and integration problems is not taken
> into account.  It is likely that it is impossible for FOG
> to mean anything because the factors that determine
> a project's "health" (to borrow the term used by Adam Jack
> in an email to the commons-dev and gump lists) are largely
> orthogonal.  FOG should probably be a vector and if you really
> wanted a single number you could use the length of that vector.
> One of the major problems with the current factor is that
> a project's FOG factor continues to increase when no changes
> have been made to the repository.  It's not meaningful to
> count only successful builds towards improving the factor
> because no changes may have been made to the code base.
> Ideally, you count only builds that cause no failures after
> a change to the code base.  FOG doesn't factor in how quickly
> (or slowly) projects recover from build failures, and how often
> changes to a code base cause failures (either in itself or in
> other projects).  Right now, a project with few code changes
> (say once a month) that causes a failure 50% (1 every 2 months)
> of the time the code is changed with a mean time of failure
> correction of 1 week is deemed more reliable (higher FOG factor)
> than a project that makes frequent changes (say every day) to
> its code base and causes a failure 10% of the time (1 every 10
> days) with a mean time of failure correction of 1 day.  That's
> because FOG is based almost entirely on consecutive successful
> Gump builds, which is not useful.
> Rather than propose a new meaningless way of computing FOG, I
> suggest FOG stop being used temporarily.  It would be more
> useful to break out and report all of the independently useful
> metrics and through experience over time determine how each
> impacts the overall notion of FOG and eventually derive a
> way of condensing the information (perhaps a FOG factor,
> perhaps a vector) in a useful manner.  Right now the state
> of affairs is that someone decided FOG was a cool thing, so
> it's being reported and people see this number and mistakenly
> think a project with half the FOG factor of another is
> less dependable and therefore avoid using it.  Alternatively
> an explanation of what FOG is intended to compute and how
> it is computed should be placed on Gump reports that list
> FOG so that consumers of the information will not be misled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-71) Gump Run GUID should use hostname and FQDN

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-71?page=history ]

Leo Simons updated GUMP-71:
---

Version: Gump2
 (was: unspecified)

> Gump Run GUID should use hostname and FQDN
> --
>
>  Key: GUMP-71
>  URL: http://issues.apache.org/jira/browse/GUMP-71
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Nick Chalko
> Priority: Minor
>  Fix For: Gump2

>
> The gump run is looks like this
> brutus:brutus-public:20040624 21:00:11
> it should look like  
> brutus.apache.org:brutus-public:20040624 21:00:11

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-20) Dependecies/Dependees are over counted

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-20?page=history ]

Leo Simons updated GUMP-20:
---

Version: Gump2
 (was: unspecified)

> Dependecies/Dependees are over counted
> --
>
>  Key: GUMP-20
>  URL: http://issues.apache.org/jira/browse/GUMP-20
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump2

>
> This list is clearly wrong:
> http://lsd.student.utwente.nl/gump/scarab/scarab_details.html#Full+Project+Dependencies
> The primary reason is that this count of unique dependency objects (an entity 
> which links to projects) not the results of the dependency itself -- the 
> dependent project. Dependency objects are owned (they form a bi-directional 
> link) and the owner is part of the __eq__ (equality check) which I think is 
> probably valid (albeit annoying here.)
> As such when we attempt to count only unique dependencies and does 'if not 
> depend in depends:' -- the __eq__ says no. The problem becomes worsened when 
> on considered jars ids. Are two depends on the same project equal if they 
> reference different ids? I'd say no.
> I suspect the best thing to do is to keep this up at the project level, find 
> a way to compare two dependencies only by the project they reference. I 
> wonder if Gumpy needs a way to optimize/merge dependencies, so repeats are 
> reduced. That said, there are multiple areas (not jsut counters/lists) that 
> need to have the right answer, and doing this wrong could dork classpaths.
> Honestly, I don't know the right way to fix this, hence this JIRA posting to 
> let the thought sit openly for a while...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-54) wrap corrupts the data

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-54?page=history ]

Leo Simons updated GUMP-54:
---

Version: Gump2
 (was: unspecified)

> wrap corrupts the data
> --
>
>  Key: GUMP-54
>  URL: http://issues.apache.org/jira/browse/GUMP-54
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> Line wrap appears to corrupt the data, which make it almost unreadable. 
> [Note: The main build data is no longer wrapped,
> making this a minor issue.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-28) document gumpy internals

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-28?page=history ]

Leo Simons updated GUMP-28:
---

Version: Gump2
 (was: unspecified)

> document gumpy internals
> 
>
>  Key: GUMP-28
>  URL: http://issues.apache.org/jira/browse/GUMP-28
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump2

>
> Whilst gump user documentation and model documentation is quite reasonable, 
> gumpy's source is not the easiest to read atm. Some pydoc (is that what it's 
> called?) is in order, along with some high-level architecture info.
> Some of this stuff is already at
> http://wiki.apache.org/gump/GumpInternals
> but more work is to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-26) keep around build logs

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-26?page=history ]

Leo Simons updated GUMP-26:
---

Version: Gump2
 (was: unspecified)

> keep around build logs
> --
>
>  Key: GUMP-26
>  URL: http://issues.apache.org/jira/browse/GUMP-26
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump2

>
> Java gump used to keep around 5 days worth of build reports. We should have 
> something similar in gumpy, with the last five days kept in full, and perhaps 
> the last five weeks, and the last five months (ie your average backup 
> schedule policy). Maybe we can do compression using diffs, but not sure what 
> is the right space/computation tradeoff. We could put the logs in svn :-D

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-88) ./gump fails with SyntaxError on Solaris8

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-88?page=history ]

Leo Simons updated GUMP-88:
---

Version: Gump2
 (was: unspecified)

> ./gump fails with SyntaxError on Solaris8
> -
>
>  Key: GUMP-88
>  URL: http://issues.apache.org/jira/browse/GUMP-88
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
>  Environment: Solaris v2.8
> Gump trunk
> Python v2.4
> Reporter: Graham Leggett
>  Fix For: Gump2

>
> If an attempt is made to check the gump code out of svn onto a solaris8 
> machine with python v2.4 installed, the following error results:
> bash-2.03$ ./gump validate
> ./gump: function: not found
>   Run the DTD validation tools on the metadata.
>   Usage:
> ./gump validate
> ./gump: function: not found
> ./gump: validate
> Adding the python -d flag, results in the following:
> bash-2.03$ python -d gump validate
>   File "gump", line 25
> function usage
>  ^
> SyntaxError: invalid syntax
> Checking out the same gump code from svn onto a MacOSX machine and running it 
> against python v2.3 shows that the same gump script works.
> It looks like gump in it's current form is not compatible with python v2.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-35) Failed to kill errant children

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-35?page=history ]

Leo Simons updated GUMP-35:
---

Version: Gump2
 (was: unspecified)

> Failed to kill errant children
> --
>
>  Key: GUMP-35
>  URL: http://issues.apache.org/jira/browse/GUMP-35
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump2

>
> Gumpy attempt to use pgrep to find "timing out" children of itself, in order 
> to kill them. Since Gumpy uses system() to spwn them, it kills the shell not 
> the real children (grandchildren, etc.)
> Need a portable way to detect and kill all progeny of Gumpy when a timeout 
> occurs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-56) Project Stats Summary ought reflect Gumped/Not Gumped

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-56?page=history ]

Leo Simons updated GUMP-56:
---

Version: Gump2
 (was: unspecified)

> Project Stats Summary ought reflect Gumped/Not Gumped
> -
>
>  Key: GUMP-56
>  URL: http://issues.apache.org/jira/browse/GUMP-56
>  Project: Gump
> Type: Improvement
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> Project Statustics (the Summary) ought reflect active projects verses 
> packages, and it ought also reflect active (but not Gump built).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-53) Re-including repositories causes corruption

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-53?page=history ]

Leo Simons updated GUMP-53:
---

Version: Gump2
 (was: unspecified)

> Re-including repositories causes corruption
> ---
>
>  Key: GUMP-53
>  URL: http://issues.apache.org/jira/browse/GUMP-53
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2

>
> Including  
>   SourceForgeSourceForge
>   http://sourceforge.net/http://sourceforge.net/
>   
> http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/
>   
> cvs.sourceforge.netcvs.sourceforge.net
> anonymousanonymous
> /cvsroot/cvsroot
> 
> pserverpserver
>   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-38) Does NOT cope with circular dependencies

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-38?page=history ]

Leo Simons updated GUMP-38:
---

Fix Version: Gump3-beta
 (was: unspecified)

> Does NOT cope with circular dependencies
> 
>
>  Key: GUMP-38
>  URL: http://issues.apache.org/jira/browse/GUMP-38
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump3-beta

>
> 1) Circular includes in metadata(href links that circle) are not detected. 
> Logic will spin until it crashes.
> 2) Circular dependencies (perhaps within project property based dependencies) 
> are not detected. Logic will spin until it crashes.
> (most recent call last):
>File "gump/integrate.py", line 85, in ?
>  irun()
>File "gump/integrate.py", line 56, in irun
>  workspace=WorkspaceLoader().load(ws, 0)
>File "/data3/gump/gump-install/python/gump/model/loader.py", line 96,
> in load
>  XMLServer.map, XMLTracker.map)
>File "/data3/gump/gump-install/python/gump/model/workspace.py", line
> 384, in complete
>  project.complete(self)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> << really big snip of identical errors >>
> 468, in complete
>  dependency.getProject().complete(workspace)
>File "/data3/gump/gump-install/python/gump/model/project.py", line
> 461, in complete
>  if self.ant: self.ant.expand(self,workspace)
>File "/data3/gump/gump-install/python/gump/model/ant.py", line 52, in
> expand
>  self.expandProperties(project,workspace)
>File "/data3/gump/gump-install/python/gump/model/ant.py", line 61, in
> expandProperties
>  self.importProperty(property)
>File "/data3/gump/gump-install/python/gump/model/property.py", line
> 164, in importProperty
>  self.addProperty(Property(xmlproperty,self))
>File "/data3/gump/gump-install/python/gump/model/property.py", line
> 27, in __init__
>  NamedModelObject.__init__(self,xml.getName(),xml,parent)
>File "/data3/gump/gump-install/python/gump/model/object.py", line
> 138, in __init__
>  ModelObject.__init__(self,xml,owner)
>File "/data3/gump/gump-install/python/gump/model/object.py", line 40,
> in __init__
>  FileHolder.__init__(self)
>File "/data3/gump/gump-install/python/gump/utils/file.py", line 154,
> in __init__
>  self.filelist=FileList(self)
>File "/data3/gump/gump-install/python/gump/utils/file.py", line 118,
> in __init__
>  Ownable.__init__(self,owner)
>File "/data3/gump/gump-install/python/gump/utils/owner.py", line 27,
> in __init__
>  self.setOwner(owner)
>File "/data3/gump/gump-install/python/gump/utils/owner.py", line 33,
> in setOwner
>  if self == owner:
> RuntimeError: maximum recursion depth exceeded
> Integration completed with exit code :  1
> Failed to integrate, exited with [1], exiting...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-50) A portable/robust lock is needed (that the OS cleans up)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-50?page=history ]

Leo Simons updated GUMP-50:
---

Fix Version: Gump3-beta
 (was: unspecified)

> A portable/robust lock is needed (that the OS cleans up)
> 
>
>  Key: GUMP-50
>  URL: http://issues.apache.org/jira/browse/GUMP-50
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
>  Fix For: Gump3-beta

>
> A lock is required so two gump processes do not run at the same time, and 
> conflict. The mechanism employed today is flawed in that the OS can not clean 
> up the lock on process termination, so we get stray locks left around.
> P.S. Eventually we ought lock the workspace, and ensure that two workspaces 
> can run simultaneously. Right now even that is not true, with use fo 
> $GUMP/tmp.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-31) cvs dirs should be cleaned every month (or so)

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-31?page=history ]

Leo Simons updated GUMP-31:
---

Fix Version: Gump3-beta
 (was: unspecified)

> cvs dirs should be cleaned every month (or so)
> --
>
>  Key: GUMP-31
>  URL: http://issues.apache.org/jira/browse/GUMP-31
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Leo Simons
>  Fix For: Gump3-beta

>
> cvs hackery corrupts cvs trees. We should shield gump against this:
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=672035

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (GUMP-36) Generate source diff report on build failure

[Leo Simons (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-36?page=history ]

Leo Simons updated GUMP-36:
---

Fix Version: Gump3-beta
 (was: unspecified)

> Generate source diff report on build failure
> 
>
>  Key: GUMP-36
>  URL: http://issues.apache.org/jira/browse/GUMP-36
>  Project: Gump
> Type: New Feature
>   Components: Python-based Gump
> Versions: Gump2
> Reporter: Vincent Massol
>  Fix For: Gump3-beta

>
> When a project fails to build, generate a report containing the following 
> information:
> - CVS source diff on the project itself between the last success build and 
> the current checked out sources
> - CVS source diffs on the project first level dependencies between the last 
> success build and the current checked out sources
> - CVS source diff on Gump project files between the last success build and 
> the current checked out sources.
> The idea is to help devlopers of the failed project in indentifying the 
> reason of the failure.
> See 
> http://blogs.codehaus.org/people/vmassol/archives/000644_diffing_continuous_build_results.html
>  for more details.
> Thanks
> -Vincent

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]