BATCH: All dressed up, with nowhere to go...

2012-04-17 Thread gump
Dear Gumpmeisters,

The following 5 notifys should have been sent

*** G U M P
[GUMP@vmgump]: Project args4j-site (in module args4j) failed
[GUMP@vmgump]: Project google-docbkx-maven-builder (in module google-docbkx) 
failed
[GUMP@vmgump]: Project google-docbkx-maven-plugin (in module google-docbkx) 
failed
[GUMP@vmgump]: Project cocoon-rest (in module cocoon3) failed
[GUMP@vmgump]: Project cocoon-optional (in module cocoon3) failed
*** G U M P
[GUMP@vmgump]: Project args4j-site (in module args4j) failed
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general@gump.apache.org.

Project args4j-site has an issue affecting its community integration.
This issue affects 4 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- args4j :  Java command line options parser
- args4j-site :  Java command line options parser
- args4j-tests :  Java command line options parser
- args4j-tools :  Java command line options parser


Full details are available at:
http://vmgump.apache.org/gump/public/args4j/args4j-site/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole pom output [pom.xml] identifier set to project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/args4j/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/args4j/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/args4j/args4j-site/gump_work/build_args4j_args4j-site.html
Work Name: build_args4j_args4j-site (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven3/bin/mvn --batch-mode -Dpackaging=pom -DgroupId=args4j 
-Dfile=pom.xml -DartifactId=args4j-site -Dversion=2.0.20-SNAPSHOT --settings 
/srv/gump/public/workspace/args4j/gump_mvn_settings.xml install:install-file 
[Working Directory: /srv/gump/public/workspace/args4j]
M2_HOME: /opt/maven3
-
[INFO] Scanning for projects...
Downloading: 
http://maven.glassfish.org/content/groups/public/org/kohsuke/pom/1/pom-1.pom
[WARNING] Checksum validation failed, expected html but is 
6c9fd3d150b8a5f0ca676f49b8ed603793cabebb for 
http://maven.glassfish.org/content/groups/public/org/kohsuke/pom/1/pom-1.pom
[WARNING] Checksum validation failed, expected html but is 
6c9fd3d150b8a5f0ca676f49b8ed603793cabebb for 
http://maven.glassfish.org/content/groups/public/org/kohsuke/pom/1/pom-1.pom
Downloaded: 
http://maven.glassfish.org/content/groups/public/org/kohsuke/pom/1/pom-1.pom 
(185 B at 0.2 KB/sec)
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]   
[ERROR]   The project args4j:args4j-site:2.0.20-SNAPSHOT 
(/srv/gump/public/workspace/args4j/pom.xml) has 1 error
[ERROR] Non-parseable POM 
/srv/gump/public/workspace/mvnlocalrepo/shared/org/kohsuke/pom/1/pom-1.pom: 
Expected root element 'project' but found 'html' (position: START_TAG seen 
html... @1:6)  @ 
/srv/gump/public/workspace/mvnlocalrepo/shared/org/kohsuke/pom/1/pom-1.pom, 
line 1, column 6 - [Help 2]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/ModelParseException
-

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/args4j/args4j-site/rss.xml
- Atom: http://vmgump.apache.org/gump/public/args4j/args4j-site/atom.xml

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 05001217042012, vmgump.apache.org:vmgump:05001217042012
Gump E-mail Identifier (unique within run) #1.

*** G U M P
[GUMP@vmgump]: Project google-docbkx-maven-builder (in module google-docbkx) 
failed
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general@gump.apache.org.

Project google-docbkx-maven-builder has an issue affecting its community 
integration.
This issue affects 1 projects.
The 

Resolving reference to commons-io-*[0-9T].jar file in a property

2012-04-17 Thread Konstantin Kolinko
Hi!

It is essentially the same issue that I wrote about a year ago, [1]

Now it is occurring in jakarta-tomcat-catalina project [2]. It
started to nagging dev@tomcat on April 12th, but I do not see what
could cause it. I guess that earlier it did not run due to some
dependency. Another change is that commons-io 2.3 was released about
that time.


The problem: When Tomcat 5.5 builds it needs to copy commons-io.jar
into its Manager webapp. There is the following code in its Ant
file:

/tomcat/tc5.5.x/trunk/container/webapps/manager/build.xml
[[[
  target name=copy-io.jar
copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib
file=${commons-io.jar}/
  /target
]]]

In Gump this is configured in project/jakarta-tomcat-catalina.xml as
ant ...
  depend property=commons-io.jar project=commons-io /
/ant

It results in
[[[
BUILD FAILED
/srv/gump/public/workspace/jakarta-tomcat-catalina/build.xml:74: The
following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/build.xml:58:
The following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/manager/build.xml:56:
Warning: Could not find file
/srv/gump/public/workspace/apache-commons/io/target/commons-io-*[0-9T].jar
to copy.
]]]

The actual name of the file is commons-io-2.4-SNAPSHOT.jar [3]

Should I change the dependency to explicitly name the file? Like this:

  property name=commons-io.jar project=commons-io
path=io/target/commons-io-2.4-SNAPSHOT.jar /

or there is a chance to make those patterns to work?


[1] Dependency on checkstyle.jar in tomcat-trunk-validate returns
glob instead of actual name, 2011-04
http://markmail.org/message/to3dvdwwciqzgrgh

[2] jakarta-tomcat-catalina project summary
http://vmgump.apache.org/gump/public/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html

[3] apache-commons/commons-io Build output
http://vmgump.apache.org/gump/public/apache-commons/commons-io/gump_work/build_apache-commons_commons-io.html

Best regards,
Konstantin Kolinko

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



Re: Resolving reference to commons-io-*[0-9T].jar file in a property

2012-04-17 Thread Stefan Bodewig
On 2012-04-18, Konstantin Kolinko wrote:

 It is essentially the same issue that I wrote about a year ago, [1]

Yes, I agree.

 Now it is occurring in jakarta-tomcat-catalina project [2]. It
 started to nagging dev@tomcat on April 12th, but I do not see what
 could cause it. I guess that earlier it did not run due to some
 dependency. Another change is that commons-io 2.3 was released about
 that time.


 The problem: When Tomcat 5.5 builds it needs to copy commons-io.jar
 into its Manager webapp. There is the following code in its Ant
 file:

 /tomcat/tc5.5.x/trunk/container/webapps/manager/build.xml
 [[[
 target name=copy-io.jar
   copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib
 file=${commons-io.jar}/
 /target
 ]]]

 In Gump this is configured in project/jakarta-tomcat-catalina.xml as
 ant ...
   depend property=commons-io.jar project=commons-io /
 /ant

 It results in
 [[[
 BUILD FAILED
 /srv/gump/public/workspace/jakarta-tomcat-catalina/build.xml:74: The
 following error occurred while executing this line:
 /srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/build.xml:58:
 The following error occurred while executing this line:
 /srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/manager/build.xml:56:
 Warning: Could not find file
 /srv/gump/public/workspace/apache-commons/io/target/commons-io-*[0-9T].jar
 to copy.
 ]]]

 The actual name of the file is commons-io-2.4-SNAPSHOT.jar [3]

 Should I change the dependency to explicitly name the file? Like this:

   property name=commons-io.jar project=commons-io
 path=io/target/commons-io-2.4-SNAPSHOT.jar /

 or there is a chance to make those patterns to work?

 [1] Dependency on checkstyle.jar in tomcat-trunk-validate returns
 glob instead of actual name, 2011-04
 http://markmail.org/message/to3dvdwwciqzgrgh

Unfortunately all I wrote back then is still true, including the I
can't promise part.  TBH I somehow forgot about it after a first quick
look and asserting that a fix wouldn't be trivial.  I've now put it on
my TODO list for the weekend, bug me if you don't hear anything by
Monday.  Of course if anybody else feels like diving into Gump's
codebase, you'd be more than welcome.

Stefan

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



Re: Resolving reference to commons-io-*[0-9T].jar file in a property

2012-04-17 Thread Bill Barker
I forgot some of my python coding basics, but can recheckin the fix to 
trunk, even if I haven't fully tested it (setting up packaged projects is a 
PIB). That is probably the best move, since it is now now failing for 
non-globbed projects in my test. So can see if it will run on trunk before 
moving to live.



-Original Message- 
From: Konstantin Kolinko

Sent: Tuesday, April 17, 2012 4:39 PM
To: Gump code and data
Subject: Resolving reference to commons-io-*[0-9T].jar file in a property

Hi!

It is essentially the same issue that I wrote about a year ago, [1]

Now it is occurring in jakarta-tomcat-catalina project [2]. It
started to nagging dev@tomcat on April 12th, but I do not see what
could cause it. I guess that earlier it did not run due to some
dependency. Another change is that commons-io 2.3 was released about
that time.


The problem: When Tomcat 5.5 builds it needs to copy commons-io.jar
into its Manager webapp. There is the following code in its Ant
file:

/tomcat/tc5.5.x/trunk/container/webapps/manager/build.xml
[[[
 target name=copy-io.jar
   copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib
file=${commons-io.jar}/
 /target
]]]

In Gump this is configured in project/jakarta-tomcat-catalina.xml as
ant ...
 depend property=commons-io.jar project=commons-io /
/ant

It results in
[[[
BUILD FAILED
/srv/gump/public/workspace/jakarta-tomcat-catalina/build.xml:74: The
following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/build.xml:58:
The following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/manager/build.xml:56:
Warning: Could not find file
/srv/gump/public/workspace/apache-commons/io/target/commons-io-*[0-9T].jar
to copy.
]]]

The actual name of the file is commons-io-2.4-SNAPSHOT.jar [3]

Should I change the dependency to explicitly name the file? Like this:

 property name=commons-io.jar project=commons-io
   path=io/target/commons-io-2.4-SNAPSHOT.jar /

or there is a chance to make those patterns to work?


[1] Dependency on checkstyle.jar in tomcat-trunk-validate returns
glob instead of actual name, 2011-04
http://markmail.org/message/to3dvdwwciqzgrgh

[2] jakarta-tomcat-catalina project summary
http://vmgump.apache.org/gump/public/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html

[3] apache-commons/commons-io Build output
http://vmgump.apache.org/gump/public/apache-commons/commons-io/gump_work/build_apache-commons_commons-io.html

Best regards,
Konstantin Kolinko

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



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



Re: Resolving reference to commons-io-*[0-9T].jar file in a property

2012-04-17 Thread Bill Barker

s/now now/now not/

-Original Message- 
From: Bill Barker

Sent: Tuesday, April 17, 2012 9:40 PM
To: Gump code and data
Subject: Re: Resolving reference to commons-io-*[0-9T].jar file in a 
property


I forgot some of my python coding basics, but can recheckin the fix to
trunk, even if I haven't fully tested it (setting up packaged projects is a
PIB). That is probably the best move, since it is now now failing for
non-globbed projects in my test. So can see if it will run on trunk before
moving to live.


-Original Message- 
From: Konstantin Kolinko

Sent: Tuesday, April 17, 2012 4:39 PM
To: Gump code and data
Subject: Resolving reference to commons-io-*[0-9T].jar file in a property

Hi!

It is essentially the same issue that I wrote about a year ago, [1]

Now it is occurring in jakarta-tomcat-catalina project [2]. It
started to nagging dev@tomcat on April 12th, but I do not see what
could cause it. I guess that earlier it did not run due to some
dependency. Another change is that commons-io 2.3 was released about
that time.


The problem: When Tomcat 5.5 builds it needs to copy commons-io.jar
into its Manager webapp. There is the following code in its Ant
file:

/tomcat/tc5.5.x/trunk/container/webapps/manager/build.xml
[[[
 target name=copy-io.jar
   copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib
file=${commons-io.jar}/
 /target
]]]

In Gump this is configured in project/jakarta-tomcat-catalina.xml as
ant ...
 depend property=commons-io.jar project=commons-io /
/ant

It results in
[[[
BUILD FAILED
/srv/gump/public/workspace/jakarta-tomcat-catalina/build.xml:74: The
following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/build.xml:58:
The following error occurred while executing this line:
/srv/gump/public/workspace/jakarta-tomcat-catalina/webapps/manager/build.xml:56:
Warning: Could not find file
/srv/gump/public/workspace/apache-commons/io/target/commons-io-*[0-9T].jar
to copy.
]]]

The actual name of the file is commons-io-2.4-SNAPSHOT.jar [3]

Should I change the dependency to explicitly name the file? Like this:

 property name=commons-io.jar project=commons-io
   path=io/target/commons-io-2.4-SNAPSHOT.jar /

or there is a chance to make those patterns to work?


[1] Dependency on checkstyle.jar in tomcat-trunk-validate returns
glob instead of actual name, 2011-04
http://markmail.org/message/to3dvdwwciqzgrgh

[2] jakarta-tomcat-catalina project summary
http://vmgump.apache.org/gump/public/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html

[3] apache-commons/commons-io Build output
http://vmgump.apache.org/gump/public/apache-commons/commons-io/gump_work/build_apache-commons_commons-io.html

Best regards,
Konstantin Kolinko

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


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



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