Re: unable to run jetty
Try mvn jetty:run instead (not ketty:run)? :-)
Seriously, I assume you have the xml snippet within pluginManagement? (I
believe so as the specified version of the plugin is being used)
For the commons-dbcp dependency you've specified system scope, but no path.
That's wrong. It exists at central so just remove the scope.
Have your tried any other version of the plugin? There is a bunch of them
for v7:
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/
/Anders
On Fri, May 21, 2010 at 00:34, fachhoch fachh...@gmail.com wrote:
I added this plugin to my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webAppConfig
contextPath/artms/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/webAppConfig
reloadautomatic/reload
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopesystem/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
/dependency
/dependencies
/plugin
when I run the ketty:run I get this error
please tell me what is wrong
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\sairamm\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\dev\apache-maven-2.1.0-bin\apache-maven-2.1.0\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: gov.audit:Audit.gov:pom:1 of project:
gov.audit:audit.war:war:1 in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: gov.audit:audit.war:war:1
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8
for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for
project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.gmaven:gmaven:pom:1.2 for
project: null:gmaven-plugin:maven-plugin:null from the repository.
[DEBUG] Adding managed dependencies for unknown:gmaven-plugin
[DEBUG] org.slf4j:slf4j-api:jar:1.5.10
[DEBUG] org.sonatype.gossip:gossip:jar:1.2
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-13
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.5
[DEBUG] org.apache.maven:maven-core:jar:2.0.10
[DEBUG] org.apache.maven:maven-project:jar:2.0.10
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0.10
[DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4.1
[DEBUG] org.apache.maven.shared:file-management:jar:1.2.1
[DEBUG] org.sonatype.gshell:gshell-io:jar:2.0
[DEBUG] jline:jline:jar:0.9.94
[DEBUG] com.thoughtworks.qdox:qdox:jar:1.8
[DEBUG] commons-lang:commons-lang:jar:2.4
[DEBUG] junit:junit:jar:3.8.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-api:jar:1.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-support:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-api:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-support:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-loader:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.5:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.6:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-1.7:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-mojo:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-mojo-support:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-plugin:jar:1.2
[DEBUG] org.codehaus.gmaven:gmaven-packaging:jar:1.2
[DEBUG] Retrieving parent-POM:
org.mortbay.jetty:modules-extra:pom:7.0.0.pre5 for project:
Re: Setting environment variables in the exec plugin
It works !
Thank you.
Now my problem is that I wanted to do this :
environmentVariables
key${path.name}/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
Because on Mac, the environment variable is DYLD_LIBRARY_PATH, on Linux, its
LD_LIBRARY_PATH and on Windows PATH.
I guess I can't do it anymore... Is there a wa to do it ? Using profiles maybe ?
Thanks
Benoît
Le 21 mai 2010 à 04:52, Marshall Schor a écrit :
Maybe you need to set the environmentVariables this way (see [1]):
environmentVariables
DYLD_LIBRARY_PATH
${project.build.directory}/thirdparty/vtk/lib/vtk-5.4/
/DYLD_LIBRARY_PATH
/environmentVariables
-Marshall Schor
[1]
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Maps
On 5/20/2010 9:48 AM, Thiébault Benoît wrote:
Hi everyone,
I'm trying to execute a Java program accessing native components, following
the very good blog post http://www.buildanddeploy.com/node/17
I however have a problem setting environment variables within the exec
plugin. Here is an extract of my POM :
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1/version
executions
execution
goals
goalexec/goal
/goals
/execution
/executions
configuration
environmentVariables
keyDYLD_LIBRARY_PATH/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
executablejava/executable
arguments
argument-classpath/argument
classpath /
argument
com.artenum.vtk.maven.ConeDemo
/argument
/arguments
/configuration
/plugin
When I run it, I have a java.lang.UnsatisfiedLinkError.
If I do
export DYLD_LIBRARY_PATH=mypath
then it works...
Do you know what is wrong in my exec configuration ?
Thank you
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
Hi, How did you configure the site plugin version in your pom ? 2010/5/20 Kalle Korhonen kalle.o.korho...@gmail.com: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
Are you sure you are using site-plugin-2.1? This should already be pulling in doxia-1.1. Also the line number 791 doesn't exist in XhtmlSink in doxia-1.1... it looks like you have an old doxia being mixed in by something else. If you can't track it, please attach a complete test project with error logs at http://jira.codehaus.org/browse/DOXIA. Thanks, -Lukas Kalle Korhonen wrote: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamyol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Setting environment variables in the exec plugin
I think I found the answer by myself : I will include the execution directly in
the profile, as explained here :
http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/
Le 21 mai 2010 à 08:55, Thiébault Benoît a écrit :
It works !
Thank you.
Now my problem is that I wanted to do this :
environmentVariables
key${path.name}/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
Because on Mac, the environment variable is DYLD_LIBRARY_PATH, on Linux, its
LD_LIBRARY_PATH and on Windows PATH.
I guess I can't do it anymore... Is there a wa to do it ? Using profiles
maybe ?
Thanks
Benoît
Le 21 mai 2010 à 04:52, Marshall Schor a écrit :
Maybe you need to set the environmentVariables this way (see [1]):
environmentVariables
DYLD_LIBRARY_PATH
${project.build.directory}/thirdparty/vtk/lib/vtk-5.4/
/DYLD_LIBRARY_PATH
/environmentVariables
-Marshall Schor
[1]
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Maps
On 5/20/2010 9:48 AM, Thiébault Benoît wrote:
Hi everyone,
I'm trying to execute a Java program accessing native components, following
the very good blog post http://www.buildanddeploy.com/node/17
I however have a problem setting environment variables within the exec
plugin. Here is an extract of my POM :
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1/version
executions
execution
goals
goalexec/goal
/goals
/execution
/executions
configuration
environmentVariables
keyDYLD_LIBRARY_PATH/key
value${project.build.directory}/thirdparty/vtk/lib/vtk-5.4//value
/environmentVariables
executablejava/executable
arguments
argument-classpath/argument
classpath /
argument
com.artenum.vtk.maven.ConeDemo
/argument
/arguments
/configuration
/plugin
When I run it, I have a java.lang.UnsatisfiedLinkError.
If I do
export DYLD_LIBRARY_PATH=mypath
then it works...
Do you know what is wrong in my exec configuration ?
Thank you
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo Command Line Properties
Hi Olivier,
It returned same data as System.getProperties() . But I think that this is
better in terms of maven perspective.
Thanks
Olivier Lamy wrote:
Hi,
Try with
/**
* The Maven Session Object
*
* @parameter expression=${session}
* @required
* @readonly
*/
protected MavenSession session;
session.getExecutionProperties()
2010/5/20 Sessizlik cem.koc@gmail.com:
Hi,
How can I access command line properties via a Mojo SubClass.
Now I had this:
/** @parameter default-value=${project} */
private MavenProject mavenProject;
However when I tried to get properties via mavenProject.getProperties(),
I
can not access command line properties that I passed.
Any help?
Thanks
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28619934.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28630618.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo Command Line Properties
The point is that if your mojo is invoked from an IDE (i.e. using maven
embedded) then the equivalent of command line properties will only be
available from MavenSession and you mojo will be broken if you use
System.getProperties to get them.
So it's not just better to use MavenSession, but it is the ___only correct
way___
-Stephen
On 21 May 2010 08:38, Sessizlik cem.koc@gmail.com wrote:
Hi Olivier,
It returned same data as System.getProperties() . But I think that this is
better in terms of maven perspective.
Thanks
Olivier Lamy wrote:
Hi,
Try with
/**
* The Maven Session Object
*
* @parameter expression=${session}
* @required
* @readonly
*/
protected MavenSession session;
session.getExecutionProperties()
2010/5/20 Sessizlik cem.koc@gmail.com:
Hi,
How can I access command line properties via a Mojo SubClass.
Now I had this:
/** @parameter default-value=${project} */
private MavenProject mavenProject;
However when I tried to get properties via mavenProject.getProperties(),
I
can not access command line properties that I passed.
Any help?
Thanks
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28619934.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Mojo---Command-Line-Properties-tp28619934p28630618.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631100.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Wayne Fay wrote: On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I assure you I did hit the button ONLY ONE TIME in the past. And yes, I saw that on both times it replicated the message posted 4 times. The last post I send, a few minutes ago I hit the post message using the keyboard, just to test the behavior. This post will also be submitted with keyboard, just to make sure. This was not a n00b navigation action. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631153.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Wayne Fay wrote: On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I assure you I did hit the button ONLY ONE TIME in the past. And yes, I saw that on both times it replicated the message posted 4 times. The last post I send, a few minutes ago I hit the post message using the keyboard, just to test the behavior. This post will also be submitted with keyboard, just to make sure. This was not a n00b navigation action. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631155.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Wayne Fay wrote: On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I assure you I did hit the button ONLY ONE TIME in the past. And yes, I saw that on both times it replicated the message posted 4 times. The last post I send, a few minutes ago I hit the post message using the keyboard, just to test the behavior. This post will also be submitted with keyboard, just to make sure. This was not a n00b navigation action. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631157.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Wayne Fay wrote: On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I assure you I did hit the button ONLY ONE TIME in the past. And yes, I saw that on both times it replicated the message posted 4 times. The last post I send, a few minutes ago I hit the post message using the keyboard, just to test the behavior. This post will also be submitted with keyboard, just to make sure. This was not a n00b navigation action. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631158.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Wayne Fay wrote: On Thu, May 20, 2010 at 10:41 AM, zm _m...@hotmail.com wrote: zm, can you PLEASE hit the send button ONLY ONE TIME in the future?? This is ridiculous. If you aren't sure if a message made it through to the list, check the list archive at Nabble.com. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I assure you I did hit the button ONLY ONE TIME in the past. And yes, I saw that on both times it replicated the message posted 4 times. The last post I send, a few minutes ago I hit the post message using the keyboard, just to test the behavior. This post will also be submitted with keyboard, just to make sure. This was not a n00b navigation action. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28631156.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade
to latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore
the warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
I am using project-info-reports 2.2 and the maven-site-plugin 2.1 and
still get the warnings. So I guess I can ignore them in that case?!?
Raphael
On Fri, May 21, 2010 at 11:04, Lukas Theussl ltheu...@apache.org wrote:
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade to
latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore the
warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
Yes, it can be ignored AFAICT. I have opened a JIRA though:
http://jira.codehaus.org/browse/MPIR-194
Cheers,
-Lukas
Raphael Ackermann wrote:
I am using project-info-reports 2.2 and the maven-site-plugin 2.1 and
still get the warnings. So I guess I can ignore them in that case?!?
Raphael
On Fri, May 21, 2010 at 11:04, Lukas Theusslltheu...@apache.org wrote:
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade to
latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore the
warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available
thanks
On Fri, May 21, 2010 at 11:56, Lukas Theussl ltheu...@apache.org wrote:
Yes, it can be ignored AFAICT. I have opened a JIRA though:
http://jira.codehaus.org/browse/MPIR-194
Cheers,
-Lukas
Raphael Ackermann wrote:
I am using project-info-reports 2.2 and the maven-site-plugin 2.1 and
still get the warnings. So I guess I can ignore them in that case?!?
Raphael
On Fri, May 21, 2010 at 11:04, Lukas Theusslltheu...@apache.org wrote:
It's a warning about a maven-internal plugin, in this case the
project-info-reports plugin. Which version do you use? (If you upgrade to
latest 2.2, you also need site-plugin 2.1). Otherwise you can ignore the
warning.
HTH,
-Lukas
Raphael Ackermann wrote:
When running mvn clean install site on our own maven plugins I get the
following warnings
[INFO] Preparing javadoc:javadoc
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [enforcer:enforce {execution: enforce-no-snapshots}]
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Parent project loaded from repository.
[INFO] Generating About report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Project Summary report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Dependencies report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
I am using the m-javadoc-p in version 2.7
mvn 2.2.1
Any hints as to what needs to be updated? Do I need to update code in
my plugin or plugin dependencies?
Raphael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Jar Plugin 2.3.1 Released
The Maven team is pleased to announce the release of the Maven Jar Plugin, version 2.3.1 This plugin provides the capability to build jars. http://maven.apache.org/plugins/maven-jar-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.3.1/version /plugin Release Notes - Maven 2.x Jar Plugin - Version 2.3.1 ** Bug * [MJAR-137] - Avoid possible data corruption issues and deadlocks ** Improvement * [MJAR-136] - Add @threadSafe support for maven3 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven EAR Plugin 2.4.2 Released
The Maven team is pleased to announce the release of the Maven Ear Plugin, version 2.4.2 This version fixed possible corruption/incorrect data issues that can occur on non-windows machines due to threading issues. It also adds @threadSafe support for maven3. http://maven.apache.org/plugins/maven-ear-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId version2.4.2/version /plugin Release Notes - Maven 2.x Ear Plugin - Version 2.4.2 ** Bug * [MEAR-125] - EAR plugin is not thread safe * [MEAR-127] - Avoid possible data corruption issues and deadlocks Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Compiler Plugin 2.3.1 Released
The Maven team is pleased to announce the release of the Maven Compiler Plugin, version 2.3.1 This plugin is used to compile the sources of your project. http://maven.apache.org/plugins/maven-compiler-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.3.1/version /plugin Release Notes - Maven 2.x Compiler Plugin - Version 2.3.1 ** Improvement * [MCOMPILER-127] - Mark compiler plugin as @threadSafe for maven3 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Resources Plugin 2.4.3 Released
The Maven team is pleased to announce the release of the Maven Resources Plugin, version 2.4.3 This plugin filters non-Java resource files, replacing expressions with values from the POM or any of the filtering properties files you choose to configure. Please see the plugin's site for details: http://maven.apache.org/plugins/maven-resources-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.4.3/version /plugin Release Notes - Maven 2.x Resources Plugin - Version 2.4.3 ** Improvement * [MRESOURCES-123] - Mark resources plugin as @threadSafe Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Install Plugin 2.3.1 Released
The Maven team is pleased to announce the release of the Maven Install Plugin, version 2.3.1 The Install Plugin is used during the install phase to add artifact(s) to the local repository. http://maven.apache.org/plugins/maven-install-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-install-plugin/artifactId version2.3.1/version /plugin Release Notes - Maven 2.x Install Plugin - Version 2.3.1 ** New Feature * [MINSTALL-75] - Add @threadSafe support for maven3 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
zm wrote: Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. I've just tried it, and as far as I can tell, an EJB requires manifest classpath to resolve dependencies, but a WAR module requires no WEB-INF\lib and no manifest classpath to resolve them, as long as all dependencies are available in the EAR package itself. Now this just doesn't seem like a good practice ... but maintaining dependencies on a big project really is a PITA ... One strange thing I noticed when using an EJB client, was that although in the WAR pom I only have a dependency to type ejb-client, it correctly inserts the client EJB on manifest classpath, but the WEB-INF\lib folder ended with the full EJB package. Don't know if it is a bug on the war plugin, but anyway I'll test this again. Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28632616.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
zm wrote: Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. I've just tried it, and as far as I can tell, an EJB requires manifest classpath to resolve dependencies, but a WAR module requires no WEB-INF\lib and no manifest classpath to resolve them, as long as all dependencies are available in the EAR package itself. Now this just doesn't seem like a good practice ... but maintaining dependencies on a big project really is a PITA ... One strange thing I noticed when using an EJB client, was that although in the WAR pom I only have a dependency to type ejb-client, it correctly inserts the client EJB on manifest classpath, but the WEB-INF\lib folder ended with the full EJB package. Don't know if it is a bug on the war plugin, but anyway I'll test this again. Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28632618.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
zm wrote: Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. I've just tried it, and as far as I can tell, an EJB requires manifest classpath to resolve dependencies, but a WAR module requires no WEB-INF\lib and no manifest classpath to resolve them, as long as all dependencies are available in the EAR package itself. Now this just doesn't seem like a good practice ... but maintaining dependencies on a big project really is a PITA ... One strange thing I noticed when using an EJB client, was that although in the WAR pom I only have a dependency to type ejb-client, it correctly inserts the client EJB on manifest classpath, but the WEB-INF\lib folder ended with the full EJB package. Don't know if it is a bug on the war plugin, but anyway I'll test this again. Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28632619.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
zm wrote: Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. I've just tried it, and as far as I can tell, an EJB requires manifest classpath to resolve dependencies, but a WAR module requires no WEB-INF\lib and no manifest classpath to resolve them, as long as all dependencies are available in the EAR package itself. Now this just doesn't seem like a good practice ... but maintaining dependencies on a big project really is a PITA ... One strange thing I noticed when using an EJB client, was that although in the WAR pom I only have a dependency to type ejb-client, it correctly inserts the client EJB on manifest classpath, but the WEB-INF\lib folder ended with the full EJB package. Don't know if it is a bug on the war plugin, but anyway I'll test this again. Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28632617.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
zm wrote: Anders Hammar wrote: I'm not sure we understand each other. I'm asking you to just skip this part of the war-plugin configuration: archive manifest addClasspathtrue/addClasspath classpathPrefixlib//classpathPrefix /manifest /archive You should still keep this: warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes /Anders I'll will try that, and see the results. I've just tried it, and as far as I can tell, an EJB requires manifest classpath to resolve dependencies, but a WAR module requires no WEB-INF\lib and no manifest classpath to resolve them, as long as all dependencies are available in the EAR package itself. Now this just doesn't seem like a good practice ... but maintaining dependencies on a big project really is a PITA ... One strange thing I noticed when using an EJB client, was that although in the WAR pom I only have a dependency to type ejb-client, it correctly inserts the client EJB on manifest classpath, but the WEB-INF\lib folder ended with the full EJB package. Don't know if it is a bug on the war plugin, but anyway I'll test this again. Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28632620.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2 WebSphere AS and Portal Plugins
I feared that WAS and WPS are not mavenized. What's worse it looks like I will have to manage close to 50 jar files. Thanks, Dave On May 20, 2010, at 10:37 PM, Balazs Tothfalussy balazs.tothfalu...@gmail.com wrote: Hi Dave, in the past I had some experiences with was6-maven-plugin ( http://mojo.codehaus.org/was6-maven-plugin/) and successfully used it to generate the needed codes for simple EJB and Webservice projects. You have to know, that this plugin actually delegates this work to the tools created by IBM and needs an installed WebSphere AS, Process Server or Portal Server on the machine you do the build. As far as I can remember, Portal projects are built into a simple war file, so strictly speaking the build should not be a problem. It is usually a problem, that into the deployment descriptors of such project you want to put environment-specific information, which may introduce the topic of maven profiles, but maybe others can give you better advice on this. As I do not know too much about your projects, but the more IBM-specific things you use, the more harder it will be to handle those situations. Another issue is that I suppose you use IBM-specific jars in your projects, that are not in the standard repositories, so you need to add them manually to your repository. Best regards, Balazs 2010/5/21 D D dawi...@gmail.com Hello, I'm setting up a build for a series of projects that reference WebSphere Application Server 6 and Portal 6.1. Does anyone know of maven plugin that deals with those products? Please share your experiences. Thanks in advance! Dave PS. I queried the user group through google (websphere inurl: http://mail-archives.apache.org/mod_mbox/maven-users/) and found only 2 threads. Does any one know if the user group is indexed/searchable through google? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
The answer to this question depends very much on what appserver (vendor and version) you are using. If it is a JEE5 compliant server (JBoss 5.x, WebLogic 10.x, WebSphere 7.x)*, then you do not need manifest classpaths to be generated at all. All jars placed in the lib directory of the EAR will be visible to both EJB and WAR classes. If it is an earlier version, the answer becomes vendor dependent as some support the JEE5 behaviour (as a vendor extension) and some don't. Unfortunately, setting Maven up to put the correct jars in a WAR's WEB-INF/lib and an EAR's lib directory has to be done by hand with explicit dependency control in the case of the EAR and controlled use of warSourceExcludes in the war plugin configuration. Cheers, Steve C * There's others, such as glassfish, but I'm not familiar with them. On 20/05/2010, at 6:48 PM, zm wrote: Hi, I'm having some trouble setting up a basic maven project structure. In this case, I'm setting up an EAR project with an EJB and a WAR project inside. I can successfully build the project, but the problem is as follows: I define a defaultJavaBundleDir lib/ on the ear pom. I want every jar dependency to be inside that folder, except the ear modules ejb and war, respectively. It all works well, but looking at the manifest, I see a problem ... the manifest of the war module has every entry with prefixed lib/, so the ejb it depends on is defined in the manifest as lib/my-ejb.jar, when in reality it is stored on the ear root. I was expecting every jar to be prefixed with lib/ except the webModule and ejbModule entries defined in maven-ear-plugin. Isn't it supposed to be like that? How can I make such setup? Note: I'm not generating the ejb client (not using generateClient in ejb pom), should this be a requirement? I'm new to maven+ejb setup like this, so I need a bit of light ... Thanks -- View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-jars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28618592.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Stephen Coy wrote: The answer to this question depends very much on what appserver (vendor and version) you are using. If it is a JEE5 compliant server (JBoss 5.x, WebLogic 10.x, WebSphere 7.x)*, then you do not need manifest classpaths to be generated at all. All jars placed in the lib directory of the EAR will be visible to both EJB and WAR classes. Are you sure about this? I'm asking because this is not the behaviour I'm seeing for a WAR deployed to Websphere 7.0.0.7. In order for the containing EAR's jar's to be visible from the WAR I have to specify them explicitly in the WAR's manifest. This, on the other hand, is not necessary for JBoss 5.1, as you say. This wouldn't be so bad if it weren't for the fact that all transitive dependencies have to be specified in the POM, so that they are explicitly mentioned in the manifest classpath. Cheers, Nicola Musatti [...] - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: javadoc throws NPE
Martin, thanks for reply.
I'm using default values:
outputDirectory: ${project.build.directory}/apidocs
reportOutputDirectory: ${project.reporting.outputDirectory}/apidocs
Maven/javadoc plugin generate javadoc.bat in target\site\apidocs:
C:\Program Files\Java\jdk1.6.0_20\jre\..\bin\javadoc.exe @options
@packages @argfile
When I run that javadoc.bat from prompt javadoc throws same exception:
...
Generating
C:/ci/svn/project/project-name/trunk/target/site/apidocs\mypackage/\pack
age-use.ht
ml...
java.lang.NullPointerException
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P
ackageUseWriter.java:180)
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageList(
PackageUseWriter.java:124)
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P
ackageUseWriter.java:110)
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUseFi
le(PackageUseWriter.java:99)
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generate(PackageUseW
riter.java:78)
at
com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWrite
r.java:116)
at
com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoc
let.java:92)
at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(Ab
stractDoclet.java:122)
at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDocl
et.java:64)
at
com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
at
com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
at
com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
at com.sun.tools.javadoc.Start.begin(Start.java:128)
at com.sun.tools.javadoc.Main.execute(Main.java:41)
at com.sun.tools.javadoc.Main.main(Main.java:31)
options file in same folder:
-classpath
'C:/ci/svn/XXX.jar'
-encoding
'Cp1250'
-protected
-sourcepath
'C:/ci/svn/project/project-name/trunk/src/main/java'
-author
-bottom
'Copyright #169; 2006-2010 a
href=http://www.example.com;Example/a. All Rights Reserved.'
-charset
'UTF-8'
-d
'C:/ci/svn/project/project-name/trunk/target/site/apidocs'
-docencoding
'UTF-8'
-doctitle
'PROJECT_NAME PROJECT_VERSION-SNAPSHOT API'
-link
'http://java.sun.com/javase/6/docs/api'
-use
-version
-windowtitle
'PROJECT_NAME PROJECT_VERSION-SNAPSHOT API'
packages file in same folder:
mypackage
mypackage.management
mypackage.management.statistika
argfile file in same folder:
'C:/ci/svn/project/project-name/trunk/src/main/java/ABCMain.java'
'C:/ci/svn/project/project-name/trunk/src/main/java/XYZ.java'
Regards,
Denis
-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Thursday, May 20, 2010 7:21 PM
To: users@maven.apache.org
Subject: RE: javadoc throws NPE
Denis-
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
can you provide us the configuration parameters for:
outputDirectory
reportOutputDirectory
thanks,
Martin--
__
Jogi és Bizalmassági kinyilatkoztatás
Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük,
hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és
semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek
könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet
ezen üzenet tartalma miatt.
Subject: javadoc throws NPE
Date: Thu, 20 May 2010 18:10:57 +0200
From: denis.kranj...@srce.hr
To: users@maven.apache.org
I am trying to generate javadoc for a project but javadoc throws NPE
without any information.
Maven output:
Generating
C:/ci/svn/project/project-name/trunk/target/site/apidocs\package-use.htm
l...
Generating C:/ci/svn/project/project-name
/trunk/target/site/apidocs\mypackage/\package-use.ht
ml...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report:
Exit code: 1 - java.lang.NullPointerException
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageUse(P
ackageUseWriter.java:180)
at
com.sun.tools.doclets.formats.html.PackageUseWriter.generatePackageList(
PackageUseWriter.java:124)
at
Question about surefire, forking, and file.encoding
If I set -Dfile.encoding=utf8 in my MAVEN_OPTS, should I expect forked JVMs from surefire to inherit this, or not? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: enforcer BeanShell script, retrieving escaped stuff from ExpressionEvaluator
lukewpatterson wrote:
evaluateBeanshell rule:
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/evaluateBeanshell.html
... ${project.basedir} results in a String with '\' characters, which must
be escaped in Java/BeanShell
I created http://jira.codehaus.org/browse/MENFORCER-100
lukewpatterson wrote:
... I'm trying to verify that my projects only have /pom.xml and /src/**
on the root
a cookbook hack with gmaven: http://pastebin.com/ddFZJj0e
--
View this message in context:
http://old.nabble.com/enforcer-BeanShell-script%2C-retrieving-escaped-stuff-from-ExpressionEvaluator-tp28626298p28633372.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
Note: I have no clue why some of my posts are multi-submitted ... I'm starting to suspect of my FF browser ... but it's strange, though. :-| I'll post this one with keyboard only. Perhaps try submitting your questions via Nabble.com instead of Hotmail. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Issue with release plugin and javasvn provider
Hi,
I'm trying to use javasvn provider with the release plugin. But it seems there
is an issue as scmCommentPrefix is not taken into account during tagging. Can
someone check my configuration and then tell me if I did something wrong or if
I should report a bug (bug fore release plugin? scm-api? svnjava provider?)
I have configured my pom like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0/version
configuration
providerImplementations
svnjavasvn/svn
/providerImplementations
/configuration
dependencies
dependency
groupIdcom.google.code.maven-scm-provider-svnjava/groupId
artifactIdmaven-scm-provider-svnjava/artifactId
version1.10/version
/dependency
/dependencies
/plugin
In my organisation we need to provide a specific comment during any svn write
operation (commit, tag) so I am using -DscmCommentPrefix option:
mvn release:prepare -DscmCommentPrefix=[XYZ]
The commit in trunk was done successfully but the tag failed:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0:prepare' with basic
configurator --
[DEBUG] (f) addSchema = true
[DEBUG] (f) allowReleasePluginSnapshot = false
[DEBUG] (f) allowTimestampedSnapshots = false
[DEBUG] (f) autoVersionSubmodules = true
[DEBUG] (s) basedir = D:\myproject
[DEBUG] (f) commitByProject = false
[DEBUG] (f) dryRun = false
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) javaHome = C:\Program Files\Java\jdk1.6.0_20\jre
[DEBUG] (f) localCheckout = false
[DEBUG] (f) mavenExecutorId = invoker
[DEBUG] (f) mavenHome = D:\apache-maven-3.0-beta-1
[DEBUG] (f) preparationGoals = clean verify
[DEBUG] (f) project = MavenProject: com.mycompany:myproject:2.3.0 @
D:\myproject\pom.xml
[DEBUG] (f) providerImplementations = {svn=javasvn}
[DEBUG] (f) reactorProjects = [MavenProject: com.mycompany:myproject:2.3.0 @
D:\myproject\pom.xml]
[DEBUG] (f) remoteTagging = true
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [XYZ]
[DEBUG] (f) session = org.apache.maven.execution.mavensess...@bf7916
[DEBUG] (f) settings = org.apache.maven.execution.settingsadap...@1478a2d
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label myproject-2.3.0...
[DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
[DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
[INFO] SVN checkout directory: D:\myproject
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.109s
[INFO] Finished at: Fri May 21 12:01:10 CEST 2010
[INFO] Final Memory: 5M/15M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project myproject: Unable to tag SCM
Provider message:
SVN tag failed.
Command output:
svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
Associations are required on commit.
Thanks
Julien
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Issue with release plugin and javasvn provider
Hi,
It's an issue in svnjava provider. The scm prefix is not used.
You can create an issue in this project.
The fix is easy
2010/5/21 Julien HENRY henr...@yahoo.fr:
Hi,
I'm trying to use javasvn provider with the release plugin. But it seems
there is an issue as scmCommentPrefix is not taken into account during
tagging. Can someone check my configuration and then tell me if I did
something wrong or if I should report a bug (bug fore release plugin?
scm-api? svnjava provider?)
I have configured my pom like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0/version
configuration
providerImplementations
svnjavasvn/svn
/providerImplementations
/configuration
dependencies
dependency
groupIdcom.google.code.maven-scm-provider-svnjava/groupId
artifactIdmaven-scm-provider-svnjava/artifactId
version1.10/version
/dependency
/dependencies
/plugin
In my organisation we need to provide a specific comment during any svn write
operation (commit, tag) so I am using -DscmCommentPrefix option:
mvn release:prepare -DscmCommentPrefix=[XYZ]
The commit in trunk was done successfully but the tag failed:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0:prepare' with basic
configurator --
[DEBUG] (f) addSchema = true
[DEBUG] (f) allowReleasePluginSnapshot = false
[DEBUG] (f) allowTimestampedSnapshots = false
[DEBUG] (f) autoVersionSubmodules = true
[DEBUG] (s) basedir = D:\myproject
[DEBUG] (f) commitByProject = false
[DEBUG] (f) dryRun = false
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) javaHome = C:\Program Files\Java\jdk1.6.0_20\jre
[DEBUG] (f) localCheckout = false
[DEBUG] (f) mavenExecutorId = invoker
[DEBUG] (f) mavenHome = D:\apache-maven-3.0-beta-1
[DEBUG] (f) preparationGoals = clean verify
[DEBUG] (f) project = MavenProject: com.mycompany:myproject:2.3.0 @
D:\myproject\pom.xml
[DEBUG] (f) providerImplementations = {svn=javasvn}
[DEBUG] (f) reactorProjects = [MavenProject: com.mycompany:myproject:2.3.0
@ D:\myproject\pom.xml]
[DEBUG] (f) remoteTagging = true
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [XYZ]
[DEBUG] (f) session = org.apache.maven.execution.mavensess...@bf7916
[DEBUG] (f) settings = org.apache.maven.execution.settingsadap...@1478a2d
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label myproject-2.3.0...
[DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
[DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
[INFO] SVN checkout directory: D:\myproject
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.109s
[INFO] Finished at: Fri May 21 12:01:10 CEST 2010
[INFO] Final Memory: 5M/15M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project myproject: Unable to tag SCM
Provider message:
SVN tag failed.
Command output:
svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
Associations are required on commit.
Thanks
Julien
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: unable to run jetty
I tried7.0.0.RC6
and now I get this
2010-05-21 12:51:41.871:INFO::jetty-7.0.0.RC6
2010-05-21 12:51:41.888:WARN::Failed startup of context
jettywebappcont...@ad2c11@ad2c11/artms,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/
java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/sairamm/.m2/repository/org/mortbay/jetty/jetty-maven-plugin/7.0.0.RC6/jetty-maven-plugin-7.0.0.RC6.jar
at java.net.URI$Parser.fail(URI.java:2809)
please help me .
Anders Hammar wrote:
Try mvn jetty:run instead (not ketty:run)? :-)
Seriously, I assume you have the xml snippet within pluginManagement? (I
believe so as the specified version of the plugin is being used)
For the commons-dbcp dependency you've specified system scope, but no
path.
That's wrong. It exists at central so just remove the scope.
Have your tried any other version of the plugin? There is a bunch of them
for v7:
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/
/Anders
On Fri, May 21, 2010 at 00:34, fachhoch fachh...@gmail.com wrote:
I added this plugin to my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webAppConfig
contextPath/artms/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/webAppConfig
reloadautomatic/reload
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopesystem/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
/dependency
/dependencies
/plugin
when I run the ketty:run I get this error
please tell me what is wrong
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\sairamm\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\dev\apache-maven-2.1.0-bin\apache-maven-2.1.0\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: gov.audit:Audit.gov:pom:1 of project:
gov.audit:audit.war:war:1 in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: gov.audit:audit.war:war:1
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins:pom:8
for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for
project: org.apache.maven.plugins:maven-plugins:pom:8 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.gmaven:gmaven:pom:1.2 for
project: null:gmaven-plugin:maven-plugin:null from the repository.
[DEBUG] Adding managed dependencies for unknown:gmaven-plugin
[DEBUG] org.slf4j:slf4j-api:jar:1.5.10
[DEBUG] org.sonatype.gossip:gossip:jar:1.2
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-13
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.5
[DEBUG] org.apache.maven:maven-core:jar:2.0.10
[DEBUG] org.apache.maven:maven-project:jar:2.0.10
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0.10
[DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4.1
[DEBUG] org.apache.maven.shared:file-management:jar:1.2.1
[DEBUG] org.sonatype.gshell:gshell-io:jar:2.0
[DEBUG] jline:jline:jar:0.9.94
[DEBUG] com.thoughtworks.qdox:qdox:jar:1.8
[DEBUG] commons-lang:commons-lang:jar:2.4
[DEBUG] junit:junit:jar:3.8.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-api:jar:1.2
[DEBUG] org.codehaus.gmaven.feature:gmaven-feature-support:jar:1.2
[DEBUG] org.codehaus.gmaven.runtime:gmaven-runtime-api:jar:1.2
[DEBUG]
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
Deeply sorry for the noise - this is Apache Shiro using apache:apache:7 as the parent - I really thought I had verified it's using 2.1 site plugin but alas, it declares 2.0.1. Overrode to 2.1 and all is good. Kalle On Fri, May 21, 2010 at 12:06 AM, Lukas Theussl ltheu...@apache.org wrote: Are you sure you are using site-plugin-2.1? This should already be pulling in doxia-1.1. Also the line number 791 doesn't exist in XhtmlSink in doxia-1.1... it looks like you have an old doxia being mixed in by something else. If you can't track it, please attach a complete test project with error logs at http://jira.codehaus.org/browse/DOXIA. Thanks, -Lukas Kalle Korhonen wrote: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamyol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency on assembly?
Thank you, that is exactly what I was looking for! On Thu, May 20, 2010 at 9:56 PM, Marshall Schor m...@schor.com wrote: On 5/20/2010 11:29 AM, C. Benson Manica wrote: Let's say I have a dependency that looks something like dependency groupIdcom.foo/groupId artifactIdbar/artifactId version1.0/version /dependency This artifact gets deployed with an additional assembly, baz.tar.gz, that I want to make use of in this project. Is baz.tar.gz accessible from this project? Yes, I think so. If so, how do I reference it? The name baz.tar.gz is probably more likely formatted like: artifactId - version - classifier . tar.gz where artifactId = bar and the version is 1.0. So the name would be more like: bar-1.0-baz.tar.gz You can write a dependency on this using groupIdcom.foo/groupId artifactIdbar/artifactId classifierbazclassifer typetar.gz/type Followup question, what I really want to do is extract baz.tar.gz to directory baz and arrange for baz to be included in an assembly to be built by this project - how would I arrange for that to happen? The assembly descriptor supports this directly, I think: use dependencySet and specify unpack. -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- C. Benson Manica cbman...@gmail.com
Re: unable to run jetty
Maybe you should move this to a jetty forum.
/Anders
On Fri, May 21, 2010 at 18:52, fachhoch fachh...@gmail.com wrote:
I tried7.0.0.RC6
and now I get this
2010-05-21 12:51:41.871:INFO::jetty-7.0.0.RC6
2010-05-21 12:51:41.888:WARN::Failed startup of context
jettywebappcont...@ad2c11
@ad2c11/artms,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/
java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/sairamm/.m2/repository/org/mortbay/jetty/jetty-maven-plugin/7.0.0.RC6/jetty-maven-plugin-7.0.0.RC6.jar
at java.net.URI$Parser.fail(URI.java:2809)
please help me .
Anders Hammar wrote:
Try mvn jetty:run instead (not ketty:run)? :-)
Seriously, I assume you have the xml snippet within pluginManagement? (I
believe so as the specified version of the plugin is being used)
For the commons-dbcp dependency you've specified system scope, but no
path.
That's wrong. It exists at central so just remove the scope.
Have your tried any other version of the plugin? There is a bunch of them
for v7:
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/
/Anders
On Fri, May 21, 2010 at 00:34, fachhoch fachh...@gmail.com wrote:
I added this plugin to my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webAppConfig
contextPath/artms/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/webAppConfig
reloadautomatic/reload
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopesystem/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
/dependency
/dependencies
/plugin
when I run the ketty:run I get this error
please tell me what is wrong
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents
and
Settings\sairamm\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\dev\apache-maven-2.1.0-bin\apache-maven-2.1.0\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: gov.audit:Audit.gov:pom:1 of project:
gov.audit:audit.war:war:1 in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: gov.audit:audit.war:war:1
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins:pom:8
for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for
project: org.apache.maven.plugins:maven-plugins:pom:8 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.gmaven:gmaven:pom:1.2 for
project: null:gmaven-plugin:maven-plugin:null from the repository.
[DEBUG] Adding managed dependencies for unknown:gmaven-plugin
[DEBUG] org.slf4j:slf4j-api:jar:1.5.10
[DEBUG] org.sonatype.gossip:gossip:jar:1.2
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-13
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.5
[DEBUG] org.apache.maven:maven-core:jar:2.0.10
[DEBUG] org.apache.maven:maven-project:jar:2.0.10
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.10
[DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0.10
[DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4.1
[DEBUG] org.apache.maven.shared:file-management:jar:1.2.1
[DEBUG] org.sonatype.gshell:gshell-io:jar:2.0
[DEBUG] jline:jline:jar:0.9.94
[DEBUG] com.thoughtworks.qdox:qdox:jar:1.8
[DEBUG] commons-lang:commons-lang:jar:2.4
[DEBUG] junit:junit:jar:3.8.2
[DEBUG]
RE: unable to run jetty
possibly a corrupt jar
can you download the project...compile,package and install to local repository
(that way you have a non-corrupt jar to work with)
http://mojo.codehaus.org/jetty-maven-plugin/usage.html
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Fri, 21 May 2010 09:52:51 -0700
From: fachh...@gmail.com
To: users@maven.apache.org
Subject: Re: unable to run jetty
I tried 7.0.0.RC6
and now I get this
2010-05-21 12:51:41.871:INFO::jetty-7.0.0.RC6
2010-05-21 12:51:41.888:WARN::Failed startup of context
jettywebappcont...@ad2c11@ad2c11/artms,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/,file:/E:/workspace/Audit.gov/audit.war/src/main/webapp/
java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/sairamm/.m2/repository/org/mortbay/jetty/jetty-maven-plugin/7.0.0.RC6/jetty-maven-plugin-7.0.0.RC6.jar
at java.net.URI$Parser.fail(URI.java:2809)
please help me .
Anders Hammar wrote:
Try mvn jetty:run instead (not ketty:run)? :-)
Seriously, I assume you have the xml snippet within pluginManagement? (I
believe so as the specified version of the plugin is being used)
For the commons-dbcp dependency you've specified system scope, but no
path.
That's wrong. It exists at central so just remove the scope.
Have your tried any other version of the plugin? There is a bunch of them
for v7:
http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/
/Anders
On Fri, May 21, 2010 at 00:34, fachhoch fachh...@gmail.com wrote:
I added this plugin to my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webAppConfig
contextPath/artms/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/webAppConfig
reloadautomatic/reload
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopesystem/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
/dependency
/dependencies
/plugin
when I run the ketty:run I get this error
please tell me what is wrong
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\sairamm\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\dev\apache-maven-2.1.0-bin\apache-maven-2.1.0\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: gov.audit:Audit.gov:pom:1 of project:
gov.audit:audit.war:war:1 in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: gov.audit:audit.war:war:1
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins:pom:8
for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for
project: org.apache.maven.plugins:maven-plugins:pom:8 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.gmaven:gmaven:pom:1.2 for
project: null:gmaven-plugin:maven-plugin:null from the repository.
[DEBUG] Adding managed dependencies for unknown:gmaven-plugin
[DEBUG] org.slf4j:slf4j-api:jar:1.5.10
[DEBUG] org.sonatype.gossip:gossip:jar:1.2
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:1.2-alpha-13
[DEBUG]
RE: unable to run jetty
That got resolved , but now a new problem java.lang.IllegalArgumentException: Object is not of type class org.mortbay.jetty.webapp.WebAppContext at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:195) at org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:95) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:975) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:608) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:155) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:349) at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:102) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:162) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92) at org.eclipse.jetty.server.Server.doStart(Server.java:231) at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:69) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:433) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:377) at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:546) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) 2010-05-21 13:45:10.731:INFO::Started selectchannelconnec...@0.0.0.0:8080 [INFO] Started Jetty Server [INFO] Starting scanner at interval of 10 seconds. here my jetty-env.xml Configure class=org.mortbay.jetty.webapp.WebAppContext Set name=parentLoaderPrioritytrue/Set New id=medis class=org.mortbay.jetty.plus.naming.Resource Arg/Arg Argjdbc/artmsDataSource/Arg Arg New class=org.apache.commons.dbcp.BasicDataSource Set name=driverClassNameoracle.jdbc.driver.OracleDriver/Set Set name=urljdbc:oracle:thin:@xx:1521:sacf3/Set Set name=usernameaudt/Set Set name=password/Set /New /Arg /New New id=medis1 class=org.mortbay.jetty.plus.naming.Resource Arg/Arg Argjdbc/gatesDataSource/Arg Arg New class=org.apache.commons.dbcp.BasicDataSource Set name=driverClassNameoracle.jdbc.driver.OracleDriver/Set Set name=urljdbc:oracle:thin:@xx:1521:sacf3/Set Set name=usernamegates/Set Set
Viewing CheckStyle violations in console output
Here is my configuration: 1) Using checkstyle with modules of varying severity (info, warning and error) 2) Failing build on checkstyle errors, configured as so execution goals goalcheck/goal /goals phasevalidate/phase configuration failsOnErrortrue/failsOnError /configuration /execution What I would like is to see exactly what violation fail the build. Adding this: consoleOutputtrue/consoleOutput Dumps everything to the console, including info and warning violations. This is not helpful, because this masks the few error violations that fail the build. The logViolationsToConsole property seems to have no effect. Is there something I am missing? Thanks. This email message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Unauthorized use, disclosure or distribution of this email is strictly forbidden. If you have received this message in error, please reply to the above sender notifying them of this error, and then kindly delete the message.
RE: unable to run jetty
finally I got to make it work with jetty7 the new problem I face is jetty takes 3 minutes after it logs this 2010-05-21 15:26:47.975:INFO::No annotation on initializer class org.apache.jasper.runtime.TldScanner log4j:ERROR Parsing error on line 10 and column 14 log4j:ERROR The content of element type layout must match (param)*. 2010-05-21 15:30:01.488:INFO:/artms:Initializing Spring root WebApplicationContext please tell me why is it taking so long after it writes to the log 2010-05-21 15:26:47.975:INFO::No annotation on initializer class org.apache.jasper.runtime.TldScanner fachhoch wrote: That got resolved , but now a new problem java.lang.IllegalArgumentException: Object is not of type class org.mortbay.jetty.webapp.WebAppContext at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:195) at org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:95) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:975) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:608) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:155) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:349) at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:102) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:162) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92) at org.eclipse.jetty.server.Server.doStart(Server.java:231) at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:69) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:433) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:377) at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:546) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) 2010-05-21 13:45:10.731:INFO::Started selectchannelconnec...@0.0.0.0:8080 [INFO] Started Jetty Server [INFO] Starting scanner at interval of 10 seconds. here my jetty-env.xml Configure class=org.mortbay.jetty.webapp.WebAppContext Set name=parentLoaderPrioritytrue/Set New id=medis class=org.mortbay.jetty.plus.naming.Resource Arg/Arg Argjdbc/artmsDataSource/Arg Arg New class=org.apache.commons.dbcp.BasicDataSource Set name=driverClassNameoracle.jdbc.driver.OracleDriver/Set Set name=urljdbc:oracle:thin:@xx:1521:sacf3/Set Set name=usernameaudt/Set
Re: unable to run jetty
Isn't there a Jetty mailing list this would be more appropriate for? On 5/21/10 3:34 PM, fachhoch wrote: finally I got to make it work with jetty7 the new problem I face is jetty takes 3 minutes after it logs this 2010-05-21 15:26:47.975:INFO::No annotation on initializer class org.apache.jasper.runtime.TldScanner log4j:ERROR Parsing error on line 10 and column 14 log4j:ERROR The content of element type layout must match (param)*. 2010-05-21 15:30:01.488:INFO:/artms:Initializing Spring root WebApplicationContext please tell me why is it taking so long after it writes to the log 2010-05-21 15:26:47.975:INFO::No annotation on initializer class org.apache.jasper.runtime.TldScanner fachhoch wrote: That got resolved , but now a new problem java.lang.IllegalArgumentException: Object is not of type class org.mortbay.jetty.webapp.WebAppContext at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:195) at org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:95) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:975) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:608) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:155) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:349) at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:102) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:162) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92) at org.eclipse.jetty.server.Server.doStart(Server.java:231) at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:69) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:433) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:377) at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:546) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) 2010-05-21 13:45:10.731:INFO::Started selectchannelconnec...@0.0.0.0:8080 [INFO] Started Jetty Server [INFO] Starting scanner at interval of 10 seconds. here my jetty-env.xml Configure class=org.mortbay.jetty.webapp.WebAppContext Set name=parentLoaderPrioritytrue/Set New id=medis class=org.mortbay.jetty.plus.naming.Resource Arg/Arg Argjdbc/artmsDataSource/Arg Arg New class=org.apache.commons.dbcp.BasicDataSource Set name=driverClassNameoracle.jdbc.driver.OracleDriver/Set Set name=urljdbc:oracle:thin:@xx:1521:sacf3/Set
Re: Question about surefire, forking, and file.encoding
not you need to define what system properties to pass through in the config section of surefire plugin On 21 May 2010 13:24, Benson Margulies bimargul...@gmail.com wrote: If I set -Dfile.encoding=utf8 in my MAVEN_OPTS, should I expect forked JVMs from surefire to inherit this, or not? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Question about surefire, forking, and file.encoding
No special treatment for file.encoding? OK, that answers that. One might have thought that the plugin running the show and the forked JVM needed to be on the same (code)page. On Fri, May 21, 2010 at 3:47 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: not you need to define what system properties to pass through in the config section of surefire plugin On 21 May 2010 13:24, Benson Margulies bimargul...@gmail.com wrote: If I set -Dfile.encoding=utf8 in my MAVEN_OPTS, should I expect forked JVMs from surefire to inherit this, or not? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unable to run jetty
2010-05-21 15:26:47.975:INFO::No annotation on initializer class org.apache.jasper.runtime.TldScanner log4j:ERROR Parsing error on line 10 and column 14 log4j:ERROR The content of element type layout must match (param)*. 2010-05-21 15:30:01.488:INFO:/artms:Initializing Spring root WebApplicationContext please tell me why is it taking so long after it writes to the log It looks like you're having lots of issues getting Jetty to work, so I'd start there and rule Jetty out before you spend too much more time asking Maven people about Jetty issues: https://dev.eclipse.org/mailman/listinfo/jetty-users http://wiki.eclipse.org/Jetty/FAQ#How_do_I_ask_a_question.3F
toughest time trying to get a jsp filtered.. any help much appreciated
I'd like to have a jsp in the root of src/main/webapps filtered and the var
replaced with a property in the war's pom.
In my pom I have:
properties
foo.barFOO/foo.bar
/properties
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.2/version
configuration
webResources
resource
directorysrc/main/webapp/directory
includes
include**/*.jsp/include
/includes
filteringtrue/filtering
!--targetPath /targetPath tried also setting this to
src/main/webapps--
/resource
/webResources
/configuration
/plugin
I have an index.jsp with
${foo.bar} defined in it.
When I run mvn clean install, I never see this var replaced in the index.jsp
in the exploded dir in target.
Any ideas what I'm doing wrong?
I found this article online and it looks like I'm doing everything
correctly.
http://fogit.blogspot.com/2009/07/web-resources-filtering-with-maven-2.html
The difference in that article is he has his jsp's in a pages dir, and mine
are right out in the root (some are also under WEB-INF/jsp but the one I
want filtered is in the root of the webapp.)
[ANN] Maven Source Plugin 2.1.2 Released
The Maven team is pleased to announce the release of the Maven Source Plugin, version 2.1.2. The Source Plugin creates a jar archive of the source files of the current project. See the plugin's site for more details: http://maven.apache.org/plugins/maven-source-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId version2.1.2/version /plugin Release Notes - Maven 2.x Source Plugin - Version 2.1.2 ** Improvement * [MSOURCES-54] - Mark source plugin as @threadSafe Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
We've got the same problem in our enterprise pom. I just ran mvn dependency:resolve-plugins and discovered that there are many different versions of doxia that output: [dependency:resolve] Plugin Resolved: findbugs-maven-plugin-2.3.1.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.8.jar Plugin Dependency Resolved: maven-doxia-tools-1.0.jar Plugin Dependency Resolved: findbugs-ant-1.3.9.jar Plugin Dependency Resolved: plastic-1.2.0.jar Plugin Dependency Resolved: gmaven-mojo-1.0-rc-3.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-4.jar Plugin Dependency Resolved: plexus-utils-1.5.1.jar Plugin Resolved: clirr-maven-plugin-2.2.2.jar Plugin Dependency Resolved: clirr-core-0.6.jar Plugin Dependency Resolved: bcel-5.2.jar Plugin Dependency Resolved: doxia-site-renderer-1.0-alpha-8.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.jar Plugin Dependency Resolved: maven-artifact-manager-2.0.4.jar Plugin Dependency Resolved: plexus-i18n-1.0-beta-6.jar Plugin Resolved: maven-pmd-plugin-2.5.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-7.jar Plugin Dependency Resolved: plexus-utils-1.5.6.jar Plugin Dependency Resolved: pmd-jdk14-4.2.5.jar Plugin Dependency Resolved: xmlParserAPIs-2.6.2.jar Plugin Resolved: maven-surefire-report-plugin-2.5.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-container-default-1.0-alpha-9.jar Plugin Dependency Resolved: plexus-utils-1.5.9.jar Plugin Resolved: cobertura-maven-plugin-2.4.jar Plugin Dependency Resolved: cobertura-1.9.4.1.jar Plugin Dependency Resolved: cobertura-runtime-1.9.4.1.pom Plugin Dependency Resolved: java-getopt-1.0.9.jar Plugin Dependency Resolved: maven-artifact-2.0.jar Plugin Dependency Resolved: maven-plugin-api-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: maven-project-2.0.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: plexus-container-default-1.0-alpha-9.jar Plugin Dependency Resolved: commons-lang-2.4.jar Plugin Dependency Resolved: plexus-utils-2.0.2.jar Plugin Resolved: jdepend-maven-plugin-2.0-beta-2.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: jdepend-2.9.1.jar Plugin Resolved: javancss-maven-plugin-2.0.jar Plugin Dependency Resolved: plexus-utils-1.5.9.jar Plugin Dependency Resolved: maven-project-2.0.jar Plugin Dependency Resolved: maven-model-2.0.jar Plugin Dependency Resolved: maven-plugin-api-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: doxia-sink-api-1.0-alpha-4.jar Plugin Dependency Resolved: doxia-core-1.0-alpha-4.jar Plugin Dependency Resolved: dom4j-1.6.1.jar Plugin Dependency Resolved: jaxen-1.1-beta-6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: javancss-32.53.jar Plugin Resolved: maven-pmd-plugin-2.5.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-7.jar Plugin Dependency Resolved: plexus-utils-1.5.6.jar Plugin Dependency Resolved: pmd-jdk14-4.2.5.jar Plugin Dependency Resolved: xmlParserAPIs-2.6.2.jar Plugin Resolved: maven-site-plugin-2.1.jar Plugin Dependency Resolved: maven-artifact-2.0.6.jar Plugin Dependency Resolved: maven-artifact-manager-2.0.6.jar Plugin Dependency
[ANN] Versions Maven Plugin 1.2 released
The Mojo team is pleased to announce the release of the Versions Maven Plugin, version 1.2. The Versions Plugin has the following goals. * versions:display-dependency- updates scans a project's dependencies and produces a report of those dependencies which have newer versions available. * versions:display-plugin-updates scans a project's plugins and produces a report of those plugins which have newer versions available. * versions:display-property-updates scans a projectand produces a report of those properties which are used to control artifact versions and which properies have newer versions available. * versions:update-parent updates the parent section of a project so that it references the newest available version. For example, if you use a corporate root POM, this goal can be helpful if you need to ensure you are using the latest version of the corporate root POM. * versions:update-properties updates properties defined in a project so that they correspond to the latest available version of specific dependencies. This can be useful if a suite of dependencies must all be locked to one version. * versions:update-child-modules updates the parent section of the child modules of a project so the version matches the version of the current project. For example, if you have an aggregator pom that is also the parent for the projects that it aggregates and the children and parent versions get out of sync, this mojo can help fix the versions of the child modules. (Note you may need to invoke Maven with the -N option in order to run this goal if your project is broken so badly that it cannot build because of the version mis-match). * versions:lock-snapshots searches the pom for all -SNAPSHOT versions and replaces them with the current timestamp version of that -SNAPSHOT, e.g. -20090327.172306-4 * versions:unlock-snapshots searches the pom for all timestamp locked snapshot versions and replaces them with -SNAPSHOT. * versions:resolve-ranges finds dependencies using version ranges and resolves the range to the specific version being used. * versuibs:set can be used to set the project version from the command line. * versions:use-releases searches the pom for all -SNAPSHOT versions which have been released and replaces them with the corresponding release version. * versions:use-next-releases searches the pom for all non-SNAPSHOT versions which have been a newer release and replaces them with the next release version. * versions:use-latest-releases searches the pom for all non-SNAPSHOT versions which have been a newer release and replaces them with the latest release version. * versions:use-next-snapshots searches the pom for all non-SNAPSHOT versions which have been a newer -SNAPSHOT version and replaces them with the next -SNAPSHOT version. * versions:use-latest-snapshots searches the pom for all non-SNAPSHOT versions which have been a newer -SNAPSHOT version and replaces them with the latest -SNAPSHOT version. * versions:use-next-versions searches the pom for all versions which have been a newer version and replaces them with the next version. * versions:use-latest-versions searches the pom for all versions which have been a newer version and replaces them with the latest version. * versions:commit removes the pom.xml.versionsBackup files. Forms one half of the built-in Poor Man's SCM. * versions:revert restores the pom.xml files from the pom.xml.versionsBackup files. Forms one half of the built-in Poor Man's SCM. The artifacts have been deployed to the mojo repository and have been mirrored to central. The Mojo Team. Release Notes - Maven 2.x Versions Plugin - Version 1.2 ** Bug * [MVERSIONS-84] - versions:set fails to update dependencies when -f option points to a file with more than one subfolder in its path * [MVERSIONS-86] - NullPointerException in versions:display-dependency-updates with version range * [MVERSIONS-87] - missing text for property report.description * [MVERSIONS-88] - mvn versions:display-dependency-updates does not consider snapshots even if they are in local repository * [MVERSIONS-89] - NPE when generating site:site * [MVERSIONS-90] - update snapshots mojos parameter configuration incorrect and version increment logic is wrong * [MVERSIONS-99] - display-dependency-updates reports dependencies with ranges under wrong heading (when the range contains the latest version) * [MVERSIONS-100] - Misspelled goal on Verions Maven Plugin page * [MVERSIONS-105] - versions-maven-plugin display-plugin-updates fails on 3.0-beta-1 while working on 3.0-alph-* ** New Feature * [MVERSIONS-92] - Add new mojo to set dependencies to a specific version * [MVERSIONS-101] - Add processDependencies and processDependencyManagement parameters to display-dependency-updates goal Note: as of 01:26 IST (Irish Summer Time = GMT+1h) 22/05/2010 the versions-maven-plugin has not been pushed to maven central. If you cannot wait the
Re: Maven EAR + EJB ... jars with prefixed lib/ except for EJB
On 21/05/2010, at 10:14 PM, Nicola Musatti wrote: Are you sure about this? I'm asking because this is not the behaviour I'm seeing for a WAR deployed to Websphere 7.0.0.7. In order for the containing EAR's jar's to be visible from the WAR I have to specify them explicitly in the WAR's manifest. From JavaTM Platform, Enterprise Edition (Java EE) Specification, v5 EE.8.2.1Bundled Libraries 1. ... 2. A .ear file may contain a directory that contains libraries packaged in JAR files. The library-directory element of the.earfile’s deployment descriptor contains the name of this directory. If a library-directory element isn’t specified, or if the .ear file does not contain a deployment descriptor, the directory named lib is used. An empty library-directory element may be used to specify that there is no library directory. All files in this directory (but not subdirectories) with a .jar extension must be made available to all components packaged in the EAR file, including application clients. These libraries may reference other libraries, either bundled with the application or installed separately, using any of the techniques described herein. 3. A web application may include libraries in the WEB-INF/lib directory. See the Servlet specification for details. These libraries may reference other libraries, either bundled with the application or installed separately, using any of the techniques described herein. The usual reason for this not working is using an old (J2EE 1.3 or 1.4) DTD/schema in the application.xml file. Cheers, Steve C - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Tracking down a stray dependency on a plugin?
mvn -X shows me a dependency on a plugin that I can't explain. This is a plugin which, on its, has very few dependencies, and depends on explicit dependency declarations. -X is showing me something that should not be in there. dependency:tree doesn't look at plugins. Is there something else which will give me a clue? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: toughest time trying to get a jsp filtered.. any help much appreciated
properties foo.barFOO/foo.bar /properties If this is literally cut and paste from your pom.xml file, the problem should be pretty obvious. If you changed it and accidentally deleted the , that's another story. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: toughest time trying to get a jsp filtered.. any help much appreciated
On Fri, May 21, 2010 at 9:44 PM, Wayne Fay wayne...@gmail.com wrote: properties foo.barFOO/foo.bar /properties If this is literally cut and paste from your pom.xml file, the problem should be pretty obvious. If you changed it and accidentally deleted the , that's another story. Ha sorry. no it wasn't cut and paste:) I see the mistake above. I had several properties and then pasted them here and just screwed up making it more generic. Thanks though.
Re: toughest time trying to get a jsp filtered.. any help much appreciated
On Fri, May 21, 2010 at 11:53 PM, Rick R ric...@gmail.com wrote:
On Fri, May 21, 2010 at 9:44 PM, Wayne Fay wayne...@gmail.com wrote:
properties
foo.barFOO/foo.bar
/properties
If this is literally cut and paste from your pom.xml file, the problem
should be pretty obvious. If you changed it and accidentally deleted
the , that's another story.
Ha sorry. no it wasn't cut and paste:) I see the mistake above. I had
several properties and then pasted them here and just screwed up making it
more generic. Thanks though.
I also ended up getting around the problem (in a flex/java app) by
utilizing the flex mojos copy-flex-resources goal of the plugin.
However, I still would be curious why I wasn't have it filter correctly for
the jsp. The plugin section was copy and paste:
plugin
groupIdorg.apache.maven.
plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.2/version
configuration
webResources
resource
directorysrc/main/webapp/directory
includes
include**/*.jsp/include
/includes
filteringtrue/filtering
!--targetPath /targetPath tried also setting this to
src/main/webapps--
/resource
/webResources
/configuration
/plugin
The relevant property I was trying to replace.. copy and paste:
properties
swf.version1.0-SNAPSHOT/swf.version
/properties
and then from a snippet in the index.jsp
src, integrated-media-swf-${swf.version}.swf
