[jira] [Resolved] (GUMP-172) Gump DOAP file has an error

[Stefan Bodewig (Jira)]

 [ 
https://issues.apache.org/jira/browse/GUMP-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig resolved GUMP-172.
-
Resolution: Fixed

Thank you, fixed by 
https://svn.apache.org/viewvc/gump/site/doap_Gump.rdf?r1=1909299&r2=1909298&pathrev=1909299

> Gump DOAP file has an error
> ---
>
> Key: GUMP-172
> URL: https://issues.apache.org/jira/browse/GUMP-172
> Project: Gump
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: Gump3-alpha-5
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 41, col: 41] \{W002}  Code: 57/REQUIRED_COMPONENT_MISSING in 
> HOST: A component that is required by the scheme is missing.
> [1] http://svn.apache.org/repos/asf/gump/site/doap_Gump.rdf
> [2] 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Deleted] (GUMP-171) Acer Help

[Stefan Bodewig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GUMP-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig deleted GUMP-171:



> Acer Help
> -
>
> Key: GUMP-171
> URL: https://issues.apache.org/jira/browse/GUMP-171
> Project: Gump
>  Issue Type: New Feature
>Reporter: Soya Black
>  Labels: Computer, Hardware, Laptop
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Call at Acer Laptop Support Number at 0800-046-5242 UK for Acer Support, Acer 
> Customer Support, Acer Technical Support, Acer Laptop Support
> [Acer Support|http://acer-support.uk/]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Deleted] (GUMP-170) W@tchFULL~ Watch UFC 182 Live Stream Online - Jones vs. Cormier

[Stefan Bodewig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GUMP-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig deleted GUMP-170:



> W@tchFULL~ Watch UFC 182 Live Stream Online - Jones vs. Cormier
> ---
>
> Key: GUMP-170
> URL: https://issues.apache.org/jira/browse/GUMP-170
> Project: Gump
>  Issue Type: Bug
>Reporter: biboy man
>
> W@tchFULL~ Watch UFC 182 Live Stream Online - Jones vs. Cormier
> Watch @ http://ufc182live.blogspot.com/
> Watch @ http://ufc182live.blogspot.com/
> Watch @ http://ufc182live.blogspot.com/
> 1 day ago - UFC 182 live PPV results stream: Full coverage and play-by-play 
> for "Jones vs. Cormier" MMA event online, which takes place on Sat., Jan.
> UFC 182 weigh-in video for Jones vs. Cormier - Bloody Elbow
> 10 hours ago - Bloody Elbow is the place to be for live streaming video of 
> UFC 182: Jones vs. Cormier weigh-ins in Las Vegas, Nevada on Friday, January 
> 2nd ...
> Watch today's UFC 182 weigh-ins live on MMAjunkie at 7 ...
> 19 hours ago - LAS VEGAS – UFC 182 fighter weigh-ins take place today, and 
> you can catch a live stream of the proceedings here on MMAjunkie.
> Ultimate Fighting Championship
> Event information, results, video and fighter information for UFC 182. ... 
> Fight Card; Live Stats; Odds. Light Heavyweight ... Some fights may not be 
> broadcast. .
> ‎Hector Lombard - ‎Josh Burkman - ‎Print
> Watch UFC 182 Live Streaming. Jones vs Cormier - YouTube
> Cormier' Live Stream on Pay-Per-View (PPV) Full Fight Online 2015. ... 
> preview, 2015 projections and more ...
> Watch the UFC Official 182: Jones vs. Cormier Weigh-in Live
> 12 hours ago - Watch the official weigh-in for UFC 182: Jones vs. Cormier 
> streaming live on Friday from the MGM Grand Garden Arena at 7 p.m. ET.
> UFC 182: Jones vs Cormier Live Stream | Facebook
> ufc 182 live, ufc 182 online, ufc 182 streaming, ufc 182 live fight, ufc 182 
> live online, ufc 182 live stream, ufc 182 live streaming, ufc 182 live stream 
> ppv, ufc 182 ...
> UFC 182 Start Time: Full Card, TV Info, Live Stream and ...
> 13 hours ago - UFC 182 is almost guaranteed to start the new year off with a 
> bang. In addition to a long-awaited main event featuring reigning light ...
> Several different sports on Wiziwig; live and free. Boxing ... for free on 
> your pc. All live Sports events! ... Competition, Time, Home-team, Away-team, 
> Broadcast ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Commented] (GUMP-169) Build fails due to missing plugin that is not missing.

[Stefan Bodewig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GUMP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485668#comment-13485668
 ] 

Stefan Bodewig commented on GUMP-169:
-

yes, this is what our mirror logs

INFO: Redirecting via client connector to: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-metadata.xml
Oct 28, 2012 4:46:23 PM com.noelios.restlet.LogFilter afterHandle
INFO: 2012-10-2816:46:23127.0.0.1   -   
people.apache.org   -1  GET 
/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-metadata.xml
  -   404 313 -   62  http://localhost:8192   
Apache-Maven/2.2 (Java 1.7.0_05; Linux 2.6.32-41-server) maven-artifact/2.2.1   
-
Oct 28, 2012 4:46:23 PM org.apache.gump.mvnrepoproxy.resources.GumpArtifact log
INFO: proxying .pom artifact for groupId 'org.apache.maven.plugins' and 
artifactId 'maven-pdf-plugin'
Oct 28, 2012 4:46:23 PM org.restlet.Redirector handle
INFO: Redirecting via client connector to: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-pdf-plugin-1.2-SNAPSHOT.pom
Oct 28, 2012 4:46:23 PM com.noelios.restlet.LogFilter afterHandle
INFO: 2012-10-2816:46:23127.0.0.1   -   127.0.0.1   
8192GET 
/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-pdf-plugin-1.2-SNAPSHOT.pom
   -   404 311 -   5   http://localhost:8192   
Apache-Maven/2.2 (Java 1.7.0_05; Linux 2.6.32-41-server) maven-artifact/2.2.1   
-

which kind of indicates the timestamp has been swallowed.  I can't promise a 
fix soon, but I think I know where to look and how to deal with it.  The code 
is in http://svn.apache.org/repos/asf/gump/mvnrepo/trunk/ if you want to have a 
look yourself.

> Build fails due to missing plugin that is not missing.
> --
>
> Key: GUMP-169
> URL: https://issues.apache.org/jira/browse/GUMP-169
> Project: Gump
>  Issue Type: Bug
>  Components: Java-based Gump
>Reporter: Ralph Goers
>
> The Logging Log4j 2 build is failing every night due to the following message:
> [INFO] 
> 
> [INFO] snapshot org.apache.maven.plugins:maven-pdf-plugin:1.2-SNAPSHOT: 
> checking for updates from apache.snapshots
> Downloading: 
> http://localhost:8192/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-pdf-plugin-1.2-SNAPSHOT.pom
> [INFO] Unable to find resource 
> 'org.apache.maven.plugins:maven-pdf-plugin:pom:1.2-SNAPSHOT' in repository 
> apache.snapshots (http://repository.apache.org/snapshots)
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> However this artifact is in the listed repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Commented] (GUMP-169) Build fails due to missing plugin that is not missing.

[Stefan Bodewig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GUMP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485661#comment-13485661
 ] 

Stefan Bodewig commented on GUMP-169:
-

Actually Gump provides a mirror of its own as man-in-the-middle but passes 
through all kinds of requests it doesn't recognize (like for 
maven-metadata.xml) so I'd expect mvn to figure out the matching pom the same 
way it'd always do.  I'll have to dig through the logs to see what actually 
happens.  Don't hold your breath, please.

> Build fails due to missing plugin that is not missing.
> --
>
> Key: GUMP-169
> URL: https://issues.apache.org/jira/browse/GUMP-169
> Project: Gump
>  Issue Type: Bug
>  Components: Java-based Gump
>Reporter: Ralph Goers
>
> The Logging Log4j 2 build is failing every night due to the following message:
> [INFO] 
> 
> [INFO] snapshot org.apache.maven.plugins:maven-pdf-plugin:1.2-SNAPSHOT: 
> checking for updates from apache.snapshots
> Downloading: 
> http://localhost:8192/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-pdf-plugin-1.2-SNAPSHOT.pom
> [INFO] Unable to find resource 
> 'org.apache.maven.plugins:maven-pdf-plugin:pom:1.2-SNAPSHOT' in repository 
> apache.snapshots (http://repository.apache.org/snapshots)
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> However this artifact is in the listed repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Commented] (GUMP-169) Build fails due to missing plugin that is not missing.

[Stefan Bodewig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GUMP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485659#comment-13485659
 ] 

Stefan Bodewig commented on GUMP-169:
-

It looks as if Gump wasn't smart enough to deal with -SNAPSHOTs, yet.  Right 
now I see maven-pdf-plugin-1.2-20121026.125617-721.pom amound files with other 
timestamps there but Gump explicitly only looks for a file without timestamp.

I must admit I'm not sure how maven itself handles SNAPSHOTs.  It looks as if 
we'd have to read maven-metadata.xml and use (one of) the version(s) listed 
there.

> Build fails due to missing plugin that is not missing.
> --
>
> Key: GUMP-169
> URL: https://issues.apache.org/jira/browse/GUMP-169
> Project: Gump
>  Issue Type: Bug
>  Components: Java-based Gump
>Reporter: Ralph Goers
>
> The Logging Log4j 2 build is failing every night due to the following message:
> [INFO] 
> 
> [INFO] snapshot org.apache.maven.plugins:maven-pdf-plugin:1.2-SNAPSHOT: 
> checking for updates from apache.snapshots
> Downloading: 
> http://localhost:8192/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-pdf-plugin/1.2-SNAPSHOT/maven-pdf-plugin-1.2-SNAPSHOT.pom
> [INFO] Unable to find resource 
> 'org.apache.maven.plugins:maven-pdf-plugin:pom:1.2-SNAPSHOT' in repository 
> apache.snapshots (http://repository.apache.org/snapshots)
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> However this artifact is in the listed repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Resolved] (GUMP-165) Upgrade JUnit to 3.8.2 on vmgump.apache.org

[Stefan Bodewig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GUMP-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig resolved GUMP-165.
-

Resolution: Fixed

Ant's descriptor was leaking JUnit 3.x into other builds, this has been fixed 
now and FOP's tests build in Gump successfuly now (against JUnit's git head, 
which is 4.9.x).

> Upgrade JUnit to 3.8.2 on vmgump.apache.org
> ---
>
> Key: GUMP-165
> URL: https://issues.apache.org/jira/browse/GUMP-165
> Project: Gump
>  Issue Type: Wish
>  Components: Infrastructure
>Reporter: Vincent Hennebert
>
> Apache FOP has recently started to use the 
> TestSuite(java.lang.Class[],java.lang.String) constructor that was introduced 
> in JUnit 3.8.2. Would it be possible to upgrade the version of JUnit on 
> vmgump.apache.org?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Commented] (GUMP-165) Upgrade JUnit to 3.8.2 on vmgump.apache.org

[Stefan Bodewig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GUMP-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086819#comment-13086819
 ] 

Stefan Bodewig commented on GUMP-165:
-

Actually there currently are two versions of JUnit on the classpath while 
building fop-test.  I'll investigate where the JUni3 version is coming from and 
will eliminate that.

> Upgrade JUnit to 3.8.2 on vmgump.apache.org
> ---
>
> Key: GUMP-165
> URL: https://issues.apache.org/jira/browse/GUMP-165
> Project: Gump
>  Issue Type: Wish
>  Components: Infrastructure
>Reporter: Vincent Hennebert
>
> Apache FOP has recently started to use the 
> TestSuite(java.lang.Class[],java.lang.String) constructor that was introduced 
> in JUnit 3.8.2. Would it be possible to upgrade the version of JUnit on 
> vmgump.apache.org?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Commented] (GUMP-165) Upgrade JUnit to 3.8.2 on vmgump.apache.org

[Stefan Bodewig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GUMP-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086818#comment-13086818
 ] 

Stefan Bodewig commented on GUMP-165:
-

Hi Vincent,

I don't remember why FOP is using a packaged JUnit rather than the bleeding 
edge version at all.  Using a specific version is so un-Gumpy.

Rather than upgrading the JUnit 3.x version I'd like to try using JUnit's git 
tip - will change the descriptor.  If that fails I'll revert and update the 
installed JUnit package.

> Upgrade JUnit to 3.8.2 on vmgump.apache.org
> ---
>
> Key: GUMP-165
> URL: https://issues.apache.org/jira/browse/GUMP-165
> Project: Gump
>  Issue Type: Wish
>  Components: Infrastructure
>Reporter: Vincent Hennebert
>
> Apache FOP has recently started to use the 
> TestSuite(java.lang.Class[],java.lang.String) constructor that was introduced 
> in JUnit 3.8.2. Would it be possible to upgrade the version of JUnit on 
> vmgump.apache.org?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] [Resolved] (GUMP-163) patch for forrest config to apply trademark to logos

[Stefan Bodewig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GUMP-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig resolved GUMP-163.
-

Resolution: Fixed

I've committed the patch, many thanks.

Personally I'm reasonably happy with the outcome and could merge the two svgs 
directly (but then again don't know enough about svg to not mess up).


> patch for forrest config to apply trademark to logos
> 
>
> Key: GUMP-163
> URL: https://issues.apache.org/jira/browse/GUMP-163
> Project: Gump
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: David Crossley
> Attachments: logo-tm.txt
>
>
> Use the new Forrest "logo" input plugin to apply a trademark.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] Resolved: (GUMP-162) Doc: Remove the feedback from bottom strip, fix link colours in footer

[Stefan Bodewig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GUMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig resolved GUMP-162.
-

Resolution: Fixed

committed, thanks!

> Doc: Remove the feedback from bottom strip, fix link colours in footer
> --
>
> Key: GUMP-162
> URL: https://issues.apache.org/jira/browse/GUMP-162
> Project: Gump
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: David Crossley
>Priority: Minor
> Attachments: patch-gump-skinconf.txt
>
>
> The attached patch-gump-skinconf.txt removes the feedback link and fixes the 
> CSS colours for the links in footer.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

[jira] Commented: (GUMP-157) Gump builds fail on Windows when projects include tags

[Stefan Bodewig (JIRA)]

[ 
http://issues.apache.org/jira/browse/GUMP-157?page=comments#action_12357010 ] 

Stefan Bodewig commented on GUMP-157:
-

Apache committers only have commit access to the metadata, but not Gump's code. 
 Only people asking for access get karma to the later - and I just considered 
this entry such a request ;-)

Go ahead, Bill.

> Gump builds fail on Windows when projects include  tags
> 
>
>  Key: GUMP-157
>  URL: http://issues.apache.org/jira/browse/GUMP-157
>  Project: Gump
> Type: Bug
>   Components: Python-based Gump
>  Environment: Windows
> Reporter: Bill Barker
> Priority: Minor
>  Attachments: maven.diff
>
> Currently, any Gump project with a  tag fails when running on a 
> Windows platform.  The underlying reason is that Maven (or at least v1.0.2) 
> is too brain-dead to parse 'project.properties' other than by using 
> j.u.Properties.  As a result, the standard Windows File.separator of "\" is 
> considered to be a quote character, and is dropped from the jarpath of the 
> dependancies.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Resolved: (GUMP-135) gump.apache.com needs to point to vmgump (not brutus)

[Stefan Bodewig (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-135?page=all ]
 
Stefan Bodewig resolved GUMP-135:
-

Resolution: Fixed

I've regenerated the site (I'm using Forrest 0.6).

I had manually patched skin/screen.css to provide a black
background, the diff is

http://svn.apache.org/viewcvs.cgi/gump/site/skin/screen.css?rev=169427&r1=111999&r2=169427

It certainly would have been better if the logo itself wasn't transparent and 
designed for a white background.

> gump.apache.com needs to point to vmgump (not brutus)
> -
>
>  Key: GUMP-135
>  URL: http://issues.apache.org/jira/browse/GUMP-135
>  Project: Gump
> Type: Task
> Reporter: Adam Jack

>
> I've upadted (and commit) the xdoc change but I can no longer build the 
> forrest pages w/ my older Forrest. So, I downloaded the new Forrest, and it 
> runs -- but the "ApacheCON" logo comes out terribly (black.) I think I'm 
> stuck between forrest versions.
> Could somebody (perhaps whoever addded ApacheCON) build/update the site?

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

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

[Stefan Bodewig (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-54?page=comments#action_63159 ]
 
Stefan Bodewig commented on GUMP-54:


I think this was about Gump line-wrapping the build-output in the webpages, 
making long lines unreadable.

It no longer does so, so we probably can close this.

> 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-2.4
> Reporter: Adam Jack
> Priority: Minor
>  Fix For: Gump2-2.4

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

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

[Stefan Bodewig (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-81?page=comments#action_63158 ]
 
Stefan Bodewig commented on GUMP-81:


I think this is fixed by now, at least Gump works for Xalan after Adam changed 
some things.

> 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-2.4
> Reporter: Adam Jack
>  Fix For: Gump2-2.4

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

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

[Stefan Bodewig (JIRA)]

 [ http://issues.apache.org/jira/browse/GUMP-81?page=comments#action_61732 ]
 
Stefan Bodewig commented on GUMP-81:


Seems we have our test in Xalan now - affecting 600+ projects since
xml-xalan2 doesn't get built.

> 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-88) ./gump fails with SyntaxError on Solaris8

[Stefan Bodewig (JIRA)]

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

Stefan Bodewig updated GUMP-88:
---

Summary: ./gump fails with SyntaxError on Solaris8  (was: ./gump fails with 
SyntaxError on python v2.4/Solaris8)

Later research by Graham showed that the problem is not Python 2.4 but
that the script isn't a portable Bourne Shell script - it seems to
require bash ATM.

I've modified the she-bang line in trunk, but the real solution should
be a proper /bin/sh script.

> ./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] Resolved: (GUMP-75) Move Ant nightly builds from user bodewig to nightlybuild

[Stefan Bodewig (JIRA)]

 [ http://nagoya.apache.org/jira/browse/GUMP-75?page=history ]
 
Stefan Bodewig resolved GUMP-75:


Resolution: Fixed

Looks good, I've modified all links pointing to it and removed the entry
from my crontab.

We may want to add a .htaccess that allows more characters of the
filenames to be visible in the directory listings, as well as some
of the AddType and RemoveEncoding directives present in
www.apache.org/dist.


> Move Ant nightly builds from user bodewig to nightlybuild
> -
>
>  Key: GUMP-75
>  URL: http://nagoya.apache.org/jira/browse/GUMP-75
>  Project: Gump
> Type: Wish
>   Components: configuration of live servers
> Reporter: Stefan Bodewig
> Assignee: Leo Simons

>
> There is a shell script in bodewig's home dir on brutus that has
> been successful in producing nightly builds of Ant in
> .  Please add the script to
> the experimental system of user nightlybuild and disable bodewig's
> script after that.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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-75) Move Ant nightly builds from user bodewig to nightlybuild

[Stefan Bodewig (JIRA)]

 [ http://nagoya.apache.org/jira/browse/GUMP-75?page=comments#action_55527 ]
 
Stefan Bodewig commented on GUMP-75:


OK, I've re-installed my cron script and will start serving Ant nightly builds
from my home dir on brutus now.

I'll be happy to disable again once we've resolved this.

> Move Ant nightly builds from user bodewig to nightlybuild
> -
>
>  Key: GUMP-75
>  URL: http://nagoya.apache.org/jira/browse/GUMP-75
>  Project: Gump
> Type: Wish
>   Components: configuration of live servers
> Reporter: Stefan Bodewig
> Assignee: Leo Simons
> Priority: Minor

>
> There is a shell script in bodewig's home dir on brutus that has
> been successful in producing nightly builds of Ant in
> .  Please add the script to
> the experimental system of user nightlybuild and disable bodewig's
> script after that.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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-86) Install/use Jikes with Kaffe, not their default compiler.

[Stefan Bodewig (JIRA)]

 [ http://nagoya.apache.org/jira/browse/GUMP-86?page=comments#action_54940 ]
 
Stefan Bodewig commented on GUMP-86:


The things we need (see http://marc.theaimsgroup.com/?l=gump&m=109931478727785&w=2 )

(1) install jikes and jikes-kaffe via apt-get
(2) set JAVAC env variable in shell script that starts "Kaffe Gump" to point to
jikes-kaffe
(3) set ANT_OPTS env variable in shell script that starts "Kaffe Gump" to set
build.compiler to jikes

this should get us through the bootstrap process for Ant.

I can't do (1) for lack of permissions.

After that we'll want to set the build.compiler property to jikes in the
workspace for Kaffe Gump as well.

> Install/use Jikes with Kaffe, not their default compiler.
> -
>
>  Key: GUMP-86
>  URL: http://nagoya.apache.org/jira/browse/GUMP-86
>  Project: Gump
> Type: Task
>   Components: configuration of live servers
> Reporter: Adam Jack
> Assignee: Stefano Mazzocchi

>
> Per dalibor and jpick on IRC, this is the best compiler to use with Kaffe.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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]