[jira] [Commented] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters

2012-08-04 Thread patrick garcia (JIRA)

[ 
https://issues.apache.org/jira/browse/MTOMCAT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428593#comment-13428593
 ] 

patrick garcia commented on MTOMCAT-124:


Hello,

How can a convince you to apply this simple and useful path? I can not even 
vote for my own contribution.

Take 15 minute to test it and you will be convince.

By advance think you,

Patrick (a little bit frustrate but confident!)


 tomcat-maven-archetype unused generation parameters
 ---

 Key: MTOMCAT-124
 URL: https://issues.apache.org/jira/browse/MTOMCAT-124
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Affects Versions: 2.0-beta-1
Reporter: patrick garcia
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Trivial
  Labels: archetype, maven, tomcat
 Fix For: 2.1

 Attachments: MTOMCAT-124-tomcat-maven-archetype.patch


 I found several problems on the superb and very useful 
 tomcat-maven-archetype
 The improvement I propos are the followings:
 1/
 groupId and version can have default values but should be prompt for user 
 value the same way as for version of 
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1 proposes a 
 default version and prompt the user for modification at the same time. 
 Pressing enter validate the default value.
 2/
 Following variables are not in used:
   artifactId-api
   artifactId-api-impl
   artifactId-webapp
   artifactId-webapp-exec
   artifactId-webapp-it
 This variables should impact the mvn archetype:generate behaviour
 3/
 I propos to change the default values of :
   artifactId-api = ${artifactId}-api
   artifactId-api-impl = ${artifactId}-api-impl
   artifactId-webapp = ${artifactId}-webapp
   artifactId-webapp-exec = ${artifactId}-webapp-exec
   artifactId-webapp-it = ${artifactId}-webapp-it
 4/
 rootArtifactId cat be renamed as artifactId with no default value
 I will propos patches for this later. I, first, have to understand 
 archetype framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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



[jira] [Commented] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters

2012-08-04 Thread *$^¨%`£

[ 
https://issues.apache.org/jira/browse/MTOMCAT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428671#comment-13428671
 ] 

Olivier Lamy (*$^¨%`£) commented on MTOMCAT-124:


Hi,
I tried to apply your patch but It doesn't build.
How did you generate your patch ? Can you post a new one ?
Thanks

 tomcat-maven-archetype unused generation parameters
 ---

 Key: MTOMCAT-124
 URL: https://issues.apache.org/jira/browse/MTOMCAT-124
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Affects Versions: 2.0-beta-1
Reporter: patrick garcia
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Trivial
  Labels: archetype, maven, tomcat
 Fix For: 2.1

 Attachments: MTOMCAT-124-tomcat-maven-archetype.patch


 I found several problems on the superb and very useful 
 tomcat-maven-archetype
 The improvement I propos are the followings:
 1/
 groupId and version can have default values but should be prompt for user 
 value the same way as for version of 
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1 proposes a 
 default version and prompt the user for modification at the same time. 
 Pressing enter validate the default value.
 2/
 Following variables are not in used:
   artifactId-api
   artifactId-api-impl
   artifactId-webapp
   artifactId-webapp-exec
   artifactId-webapp-it
 This variables should impact the mvn archetype:generate behaviour
 3/
 I propos to change the default values of :
   artifactId-api = ${artifactId}-api
   artifactId-api-impl = ${artifactId}-api-impl
   artifactId-webapp = ${artifactId}-webapp
   artifactId-webapp-exec = ${artifactId}-webapp-exec
   artifactId-webapp-it = ${artifactId}-webapp-it
 4/
 rootArtifactId cat be renamed as artifactId with no default value
 I will propos patches for this later. I, first, have to understand 
 archetype framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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



[jira] [Updated] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters

2012-08-04 Thread patrick garcia (JIRA)

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

patrick garcia updated MTOMCAT-124:
---

Attachment: MTOMCAT-124-tomcat-maven-archetype2.patch

Ok,

Here is a refreshed patch MTOMCAT-124-tomcat-maven-archetype2.patch done in 
repository version 1362736, while checked out 
https://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat-maven-archetype;

This patch replaces the old one.

I have tested it with the following commands under Windows:

mkdir %temp%\xxx
cd /d %temp%\xxx
svn co 
https://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat-maven-archetype
cd %temp%\xxx\tomcat-maven-archetype
svn patch C:\MTOMCAT-124-tomcat-maven-archetype2.patch

set JAVA_HOME=c:\Program Files\Java\jdk1.6.0_25
mvn clean install
mvn clean


 tomcat-maven-archetype unused generation parameters
 ---

 Key: MTOMCAT-124
 URL: https://issues.apache.org/jira/browse/MTOMCAT-124
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Affects Versions: 2.0-beta-1
Reporter: patrick garcia
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Trivial
  Labels: archetype, maven, tomcat
 Fix For: 2.1

 Attachments: MTOMCAT-124-tomcat-maven-archetype.patch, 
 MTOMCAT-124-tomcat-maven-archetype2.patch


 I found several problems on the superb and very useful 
 tomcat-maven-archetype
 The improvement I propos are the followings:
 1/
 groupId and version can have default values but should be prompt for user 
 value the same way as for version of 
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1
 org.apache.maven.archetypes:maven-archetype-quickstart:1.1 proposes a 
 default version and prompt the user for modification at the same time. 
 Pressing enter validate the default value.
 2/
 Following variables are not in used:
   artifactId-api
   artifactId-api-impl
   artifactId-webapp
   artifactId-webapp-exec
   artifactId-webapp-it
 This variables should impact the mvn archetype:generate behaviour
 3/
 I propos to change the default values of :
   artifactId-api = ${artifactId}-api
   artifactId-api-impl = ${artifactId}-api-impl
   artifactId-webapp = ${artifactId}-webapp
   artifactId-webapp-exec = ${artifactId}-webapp-exec
   artifactId-webapp-it = ${artifactId}-webapp-it
 4/
 rootArtifactId cat be renamed as artifactId with no default value
 I will propos patches for this later. I, first, have to understand 
 archetype framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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



[GUMP@vmgump]: Project tomcat-trunk-validate-eoln (in module tomcat-trunk) failed

2012-08-04 Thread Bill Barker
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 gene...@gump.apache.org.

Project tomcat-trunk-validate-eoln has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 45 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-trunk-validate-eoln :  Tomcat 8.x, a web server implementing Java 
Servlet 3.1,
...


Full details are available at:

http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate-eoln/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate-eoln/gump_work/build_tomcat-trunk_tomcat-trunk-validate-eoln.html
Work Name: build_tomcat-trunk_tomcat-trunk-validate-eoln (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 sec
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml validate-eoln 
[Working Directory: /srv/gump/public/workspace/tomcat-trunk]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar
-
Buildfile: /srv/gump/public/workspace/tomcat-trunk/build.xml

build-prepare:
[mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/classes
[mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/build
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/bin
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/conf
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/lib
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/logs
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/temp
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/webapps

compile-prepare:
 [copy] Copying 1 file to 
/srv/gump/public/workspace/tomcat-trunk/java/org/apache/catalina/startup
 [copy] Copying 1 file to 
/srv/gump/public/workspace/tomcat-trunk/webapps/docs

validate-eoln:
[javac] Compiling 1 source file to 
/srv/gump/public/workspace/tomcat-trunk/output/classes
[javac] javac: invalid target release: 1.7
[javac] Usage: javac options source files
[javac] use -help for a list of possible options

BUILD FAILED
/srv/gump/public/workspace/tomcat-trunk/build.xml:523: Compile failed; see the 
compiler error output for details.

Total time: 1 second
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate-eoln/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate-eoln/atom.xml

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

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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



[GUMP@vmgump]: Project tomcat-trunk-dbcp (in module tomcat-trunk) failed

2012-08-04 Thread Bill Barker
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 gene...@gump.apache.org.

Project tomcat-trunk-dbcp has an issue affecting its community integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-trunk :  Tomcat 8.x, a web server implementing Java Servlet 3.1,
...
- tomcat-trunk-dbcp :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...
- tomcat-trunk-test :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...


Full details are available at:

http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-dbcp/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Made directory [/srv/gump/public/workspace/tomcat-trunk/tomcat-deps]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-dbcp/gump_work/build_tomcat-trunk_tomcat-trunk-dbcp.html
Work Name: build_tomcat-trunk_tomcat-trunk-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x 
-Dcommons-dbcp.home=/srv/gump/public/workspace/commons-dbcp-1.x 
-Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-05082012.jar
 -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps 
build-tomcat-dbcp 
[Working Directory: /srv/gump/public/workspace/tomcat-trunk]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar
-
Buildfile: /srv/gump/public/workspace/tomcat-trunk/build.xml

build-prepare:
   [delete] Deleting directory 
/srv/gump/public/workspace/tomcat-trunk/output/build/temp
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/build/temp

build-manifests:
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/manifests
 [copy] Copying 12 files to 
/srv/gump/public/workspace/tomcat-trunk/output/manifests

build-tomcat-dbcp:
 [copy] Copying 70 files to 
/srv/gump/public/workspace/tomcat-trunk/tomcat-deps
[patch] patching file 
src/java/org/apache/commons/dbcp/DelegatingCallableStatement.java
[patch] Hunk #1 succeeded at 661 (offset -113 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/cpdsadapter/DriverAdapterCPDS.java
[patch] patching file 
src/java/org/apache/commons/dbcp/DelegatingResultSet.java
[patch] Hunk #1 succeeded at 1079 (offset -195 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/PoolingDataSource.java
[patch] Hunk #1 succeeded at 437 (offset -52 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/DelegatingConnection.java
[patch] Hunk #1 succeeded at 678 (offset -126 lines).
[patch] patching file src/java/org/apache/commons/dbcp/PoolingDriver.java
[patch] Hunk #1 succeeded at 497 (offset -4 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/DelegatingStatement.java
[patch] Hunk #1 succeeded at 484 (offset -45 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/DelegatingDatabaseMetaData.java
[patch] Hunk #1 succeeded at 1204 (offset -173 lines).
[patch] patching file src/java/org/apache/commons/dbcp/BasicDataSource.java
[patch] Hunk #1 succeeded at 28 with fuzz 1.
[patch] Hunk #2 succeeded at 1782 (offset -19 lines).
[patch] patching file 
src/java/org/apache/commons/dbcp/datasources/InstanceKeyDataSource.java
[patch] Hunk #1 succeeded at 887 (offset -1 lines).
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/src/java/org/apache/tomcat/dbcp
 [move] Moving 75 files to 
/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/src/java/org/apache/tomcat/dbcp
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/classes
[javac] Compiling 66 source files to 

[GUMP@vmgump]: Project tomcat-trunk-validate (in module tomcat-trunk) failed

2012-08-04 Thread Bill Barker
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 gene...@gump.apache.org.

Project tomcat-trunk-validate has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-trunk-validate :  Tomcat 8.x, a web server implementing Java 
Servlet 3.1,
...


Full details are available at:

http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on checkstyle exists, no need to add for property 
checkstyle.jar.
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/gump_work/build_tomcat-trunk_tomcat-trunk-validate.html
Work Name: build_tomcat-trunk_tomcat-trunk-validate (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar
 -Dexecute.validate=true validate 
[Working Directory: /srv/gump/public/workspace/tomcat-trunk]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-05082012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-05082012.jar:/srv/gump/public/workspace/junit/dist/junit-05082012.jar:/srv/gump
 
/public/workspace/junit/dist/junit-dep-05082012.jar:/srv/gump/public/workspace/google-guava/guava/target/guava-*[0-9T].jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-05082012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-05082012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05082012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05082012-dep.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar
-
download-validate:

proxyflags:

setproxy:

testexist:
 [echo] Testing  for 
/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar

downloadzip:

validate:
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle

BUILD FAILED
/srv/gump/public/workspace/tomcat-trunk/build.xml:461: Could not create type 
checkstyle due to java.lang.NoClassDefFoundError: 
com/google/common/collect/Lists
at 
com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at 
org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328)
at 
org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274)
at 
org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219)
at 
org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206)
at 
org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286)
at 
org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264)
at 
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417)
at 

[GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed

2012-08-04 Thread Bill Barker
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 gene...@gump.apache.org.

Project tomcat-tc7.0.x-validate has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-tc7.0.x-validate :  Tomcat 7.x, a web server implementing Java 
Servlet 3.0,
...


Full details are available at:

http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on checkstyle exists, no need to add for property 
checkstyle.jar.
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html
Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar
 -Dexecute.validate=true validate 
[Working Directory: /srv/gump/public/workspace/tomcat-7.0.x]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-05082012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-05082012.jar:/srv/gump/public/workspace/junit/dist/junit-05082012.jar:/srv/gump
 
/public/workspace/junit/dist/junit-dep-05082012.jar:/srv/gump/public/workspace/google-guava/guava/target/guava-*[0-9T].jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-05082012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-05082012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05082012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05082012-dep.jar
-
download-validate:

proxyflags:

setproxy:

testexist:
 [echo] Testing  for 
/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar

downloadzip:

validate:
[mkdir] Created dir: 
/srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle

BUILD FAILED
/srv/gump/public/workspace/tomcat-7.0.x/build.xml:450: Could not create type 
checkstyle due to java.lang.NoClassDefFoundError: 
com/google/common/collect/Lists
at 
com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at 
org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328)
at 
org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274)
at 
org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219)
at 
org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206)
at 
org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286)
at 
org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264)
at 
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417)
at 
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
at 

[Bug 53653] New: Allow for wrapped source code example in config/context.html

2012-08-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53653

  Priority: P2
Bug ID: 53653
  Assignee: dev@tomcat.apache.org
   Summary: Allow for wrapped source code example in
config/context.html
  Severity: enhancement
Classification: Unclassified
OS: All
  Reporter: tere...@tmbsw.com
  Hardware: All
Status: NEW
   Version: 7.0.29
 Component: Documentation
   Product: Tomcat 7

Created attachment 29164
  -- https://issues.apache.org/bugzilla/attachment.cgi?id=29164action=edit
diff -u patch files for tomcat-docs.xsl and context.xml

Modify tomcat-docs.xsl and config/context.xml to allow last configuration
example on page to wrap. This provides for a more readable HTML document.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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