Re: Trim string passed to extraClasspath for jetty plugin
You could offer a patch to the jetty plugin to clean up the string for itself. On Tue, Nov 6, 2012 at 2:53 AM, Rice Yeh rice...@gmail.com wrote: Hi, I have a need to pass a long string to the extraClasspath in jetty plugin. The content of the string is changed often and I like to format it for human readability as shown in the following section. However, it causes problem in jetty's classpath setting. Any way to get around this problem? extraClasspath![CDATA[ target/classes; target/test-classes; ../xs-authentication-personnel/target/classes; ../xs-workspace/target/classes; ../xs-personnel-web/target/classes; ../xs-personnel.web/target/test-classes; ../xs-personnel-calendar/target/classes; ../xs-personnel-calendar/target/test-classes; ../xs-personnel-attendance/target/classes; ../xs-personnel-attendance/target/test-classes; ../xs-bp-web/target/classes; ../xs-bp-web/target/test-classes; ../xs-bp-personnel/target/classes; ../xs-common-rs/target/classes; ../xs-common-rs/target/test-classes; ../xs-rs-cxf/target/classes; ../xs-scheduling-web/target/classes; ../xs-scheduling/target/test-classes]]/extraClasspath Rice
Re: Maven Jetty Plugin won't honor webAppSourceDirectory
This link helped me to solve my issue: http://maven.40175.n5.nabble.com/Does-the-lt-pluginGroup-gt-in-the-setting-xml-work-td115219.html my metadata file for org.mortbay.jetty had configured the prefix to always call jetty-maven-plugin vs maven-jetty-plugin. Both were in the file, but seems like the first one is the one that is honored. Removed the entry for the newer plugin artifact and then jetty:run worked like a charm with the older version and all configurations were honored. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4778595.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
Maven Jetty Plugin won't honor webAppSourceDirectory
Based on the documentation the Jetty plugin is supposed to allow you to be
able to change the default location of the webapp directory
(http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin)
when I issue a mvn jetty:run in the plugin configuration I keep seeing this:
...
[INFO] webAppSourceDirectory : [PROJ-PATH]\src\main\webapp\ does not exist.
Defaulting to [PROJ-PATH]\src\main\webapp.
...
[INFO] web.xml file = [PROJ-PATH]\src\main\webapp\WEB-INF\web.xml
[INFO] webapp directory = [PROJ-PATH]\src\main\webapp
...
In my directory structure I do have the src\main\webapp directory, so I an
not sure why jetty isn't seeing it. Also when I attempt to change the
webapp directory jetty doesn't see that and attempts to use the default
again.
directory structure:
PROJ
PROJ\src
PROJ\src\webapp
PROJ\src\webapp\WEB-INF
PROJ\src\webapp\WEB-INF]web.xml
PROJ\src\webapp2
PROJ\src\webapp2\WEB-INF
PROJ\src\webapp2\WEB-INF]web.xml
Plugin config:
...
plugin
groupIdorg.mortbay.jettygroupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
webXml${basedir}/src/main/webapp2/WEB-INF/web.xml/webXml
/configuration
plugin
...
I have tried to use the webapp2 for the source dir and it doesn't recognize
it at all, maven doesn't seem to be reading the configuration at all. Also
tried to use the webpp default configuration, and that initial error is
still displayed:
[INFO] webAppSourceDirectory : [PROJ-PATH]\src\main\webapp\ does not exist.
Defaulting to [PROJ-PATH]\src\main\webapp.
Any direction on this? All of the documentation suggests that this should
work.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774500.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 Jetty Plugin won't honor webAppSourceDirectory
You probably want to use the newer versions of Jetty, and the Jetty Maven
Plugin, which is now an Eclipse project[1]. You can find the mailing lists
here[2].
http://www.eclipse.org/jetty/mailinglists.php
[1]: http://www.eclipse.org/jetty/
[2]: http://www.eclipse.org/jetty/
On Sep 6, 2011, at 9:59 AM, dizzyd wrote:
Based on the documentation the Jetty plugin is supposed to allow you to be
able to change the default location of the webapp directory
(http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin)
when I issue a mvn jetty:run in the plugin configuration I keep seeing this:
...
[INFO] webAppSourceDirectory : [PROJ-PATH]\src\main\webapp\ does not exist.
Defaulting to [PROJ-PATH]\src\main\webapp.
...
[INFO] web.xml file = [PROJ-PATH]\src\main\webapp\WEB-INF\web.xml
[INFO] webapp directory = [PROJ-PATH]\src\main\webapp
...
In my directory structure I do have the src\main\webapp directory, so I an
not sure why jetty isn't seeing it. Also when I attempt to change the
webapp directory jetty doesn't see that and attempts to use the default
again.
directory structure:
PROJ
PROJ\src
PROJ\src\webapp
PROJ\src\webapp\WEB-INF
PROJ\src\webapp\WEB-INF]web.xml
PROJ\src\webapp2
PROJ\src\webapp2\WEB-INF
PROJ\src\webapp2\WEB-INF]web.xml
Plugin config:
...
plugin
groupIdorg.mortbay.jettygroupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
webXml${basedir}/src/main/webapp2/WEB-INF/web.xml/webXml
/configuration
plugin
...
I have tried to use the webapp2 for the source dir and it doesn't recognize
it at all, maven doesn't seem to be reading the configuration at all. Also
tried to use the webpp default configuration, and that initial error is
still displayed:
[INFO] webAppSourceDirectory : [PROJ-PATH]\src\main\webapp\ does not exist.
Defaulting to [PROJ-PATH]\src\main\webapp.
Any direction on this? All of the documentation suggests that this should
work.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774500.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
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
the course of true love never did run smooth ...
-- Shakespeare
Re: Maven Jetty Plugin won't honor webAppSourceDirectory
got this fixed, thanks for the suggestion Jason.
I changed this FROM:
plugin
groupIdorg.mortbay.jettygroupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
webXml${basedir}/src/main/webapp2/WEB-INF/web.xml/webXml
/configuration
plugin
TO
plugin
groupIdorg.mortbay.jettygroupId
artifactIdjetty-maven-plugin/artifactId--NOTE, changed name
to jetty-maven-plugin (looks like the artifact name changed in the newer
version)also removed the version number
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
/configuration
plugin
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774583.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 Jetty Plugin won't honor webAppSourceDirectory
Always specify a version number to ensure reproducable builds!
/Anders (mobile)
Den 6 sep 2011 16.26 skrev dizzyd delali.dzir...@gmail.com:
got this fixed, thanks for the suggestion Jason.
I changed this FROM:
plugin
groupIdorg.mortbay.jettygroupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
webXml${basedir}/src/main/webapp2/WEB-INF/web.xml/webXml
/configuration
plugin
TO
plugin
groupIdorg.mortbay.jettygroupId
artifactIdjetty-maven-plugin/artifactId --NOTE, changed name
to jetty-maven-plugin (looks like the artifact name changed in the newer
version)also removed the version number
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
/configuration
plugin
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774583.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 Jetty Plugin won't honor webAppSourceDirectory
Noted...added version number. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4774652.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 Jetty Plugin won't honor webAppSourceDirectory
A follow up.
We have a very large and complex system that is being deployed to jetty
6.1.22, so I'd like to try to keep things a close to the same as possible
with the plugin.
One issue I am running into is that, the config isn't being honored for:
plugin
groupIdorg.mortbay.jettygroupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.22/version
configuration
webAppSourceDirectory${basedir}/src/main/webapp2/webAppSourceDirectory
webXml${basedir}/src/main/webapp2/WEB-INF/web.xml/webXml
/configuration
plugin
when I do a mvn: jetty:run looks like it is looking for the newest version
of the plugin and defaulting to the jetty-maven-plugin (the newest one)
and skipping this configuration all together. I think this has something to
do with my plugin groups declaration in my settings.xml file:
...
pluginGroups
pluginGrouporg.mortbay.jetty/pluginGroup
/pluginGroups
...
to get it to actually use the 6.1.22 version I have to use the fully
qualified plugin name as such:
mvn org.mortbay.jetty:maven-jetty-plugin:run
This uses the correct version of the plugin, but why? What setting is
telling maven to use the newer one when I call jetty:run?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4775657.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
maven jetty plugin - running two jetty's with different ports
Hi List, is it possible to run two jetty instances one on port 8080 and one on port 8090? Both jetty's should start several webApps. Running Multiple Webapps is decribed in http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this works. Thanks Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven jetty plugin - running two jetty's with different ports
As that's a specific question for that plugin, you should probably ask on a mailing list specific for that plugin. I believe these are the appropriate ones: http://jetty.codehaus.org/jetty/maven-plugin/mail-lists.html /Anders On Mon, Feb 28, 2011 at 10:59, Hauschel Fred Robert fredrobert.hausc...@cirquent.de wrote: Hi List, is it possible to run two jetty instances one on port 8080 and one on port 8090? Both jetty's should start several webApps. Running Multiple Webapps is decribed in http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this works. Thanks Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: maven jetty plugin - running two jetty's with different ports
Thanks for the hint! Fredy -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 28. Februar 2011 11:14 An: Maven Users List Betreff: Re: maven jetty plugin - running two jetty's with different ports As that's a specific question for that plugin, you should probably ask on a mailing list specific for that plugin. I believe these are the appropriate ones: http://jetty.codehaus.org/jetty/maven-plugin/mail-lists.html /Anders On Mon, Feb 28, 2011 at 10:59, Hauschel Fred Robert fredrobert.hausc...@cirquent.de wrote: Hi List, is it possible to run two jetty instances one on port 8080 and one on port 8090? Both jetty's should start several webApps. Running Multiple Webapps is decribed in http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this works. Thanks Fredy - 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: Jetty Plugin Error:
If you think that the plugin should not require that the directory exists (which is apparently does), you should file a ticket for this specific plugin. /Anders On Sun, Feb 6, 2011 at 05:06, Jonthan DeMaagd jondema...@gmail.com wrote: My understanding is that these directories and files are created by default. Is this not true? From commandmvn jetty:run -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Saturday, February 05, 2011 10:58 PM To: Maven Users List Subject: Re: Jetty Plugin Error: [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] Did you read the error? It says blah\src\main\webapp does not exist. Fix that and try again. Wayne - 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
Jetty Plugin Error:
[INFO] Scanning for projects... [INFO] [INFO] [INFO] Building simple-webapp Maven Webapp 1.0-SNAPSHOT [INFO] [INFO] [INFO] maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp .. .. [INFO] maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp [INFO] [INFO] --- maven-jetty-plugin:6.1.10:run (default-cli) @ simple-webapp --- [INFO] Configuring Jetty for project: simple-webapp Maven Webapp [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.513s [INFO] Finished at: Sat Feb 05 12:47:58 EST 2011 [INFO] Final Memory: 3M/15M [INFO] [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException POM.xml .. .. plugins plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.10/version /plugin /plugins Followed Maven By Example and http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin Followed examples on site for command mvn jetty:run Results were still same! Please Help! Thanks!
Failed to execute goal with jetty-plugin
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.22:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Have tried several sources and results are the same Any lead? Thanks again.
Re: Jetty Plugin Error:
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] Did you read the error? It says blah\src\main\webapp does not exist. Fix that and try again. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Jetty Plugin Error:
My understanding is that these directories and files are created by default. Is this not true? From commandmvn jetty:run -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Saturday, February 05, 2011 10:58 PM To: Maven Users List Subject: Re: Jetty Plugin Error: [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.10:run (default-cli) on project simple-webapp: Webapp source directory C:\Users\jondemaagd\MavenProjects\simple-webapp\src\main\webapp does not exist - [Help 1] Did you read the error? It says blah\src\main\webapp does not exist. Fix that and try again. Wayne - 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: Jetty Plugin Error:
My understanding is that these directories and files are created by default. Is this not true? From commandmvn jetty:run Having this directory or not depends entirely on what archetype you used when you built your project. If you didn't create a war (webapp) project, then you probably don't have a src/main/webapp directory -- and given the error you're seeing, I'm guessing this is what's going on. You can fix this error by simply creating that directory yourself, and maybe copying a few files into it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
seeking simple maven jetty plugin fileserver example
Hi, Could anyone point me to an example of how to use the maven jetty plugin to simply serve files in the project root directory? I've seen one example of how to configure Jetty, outside of Maven, to act as a simple file server [0], but unfortunately, I was not able to get it to work. I was hoping that there might be another example that someone might be aware of. Please let me know. Thanks, Jake [0] http://docs.codehaus.org/display/JETTY/Newbie+Guide+to+Jetty#NewbieGuidetoJetty-FileServer%2COneHandler - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Run maven-jetty-plugin for webapp in other Maven module
Finally i can make the maven-jetty-plugin in the test project to start the
webapp of another maven module. just add the following configuration in the
pom.xml
contextPath/webapp_project_name/contextPath
webAppSourceDirectory${project.parent.basedir}/webapp_project_name/src/main/webapp/webAppSourceDirectory
webXml${project.parent.basedir}/webapp_project_name/src/main/webapp/WEB-INF/web.xml/webXml
classesDirectory${project.parent.basedir}/webapp_project_name/target/classes/classesDirectory
Thanks.
--
View this message in context:
http://maven.40175.n5.nabble.com/Run-maven-jetty-plugin-for-webapp-in-other-Maven-module-tp511054p511249.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
Run maven-jetty-plugin for webapp in other Maven module
Hi all, i got a maven parent project with 2 child modules 1. The webapp project (webapp) 2. The maven module for integration test (test) both modules runs without problem individually. but as i want to automate them together. i would like to configure the test project pom.xml such that in the pre-integration-test and post-integration-test life cycle. the webapp is started. i try to use the exec-maven-plugin (in test project) to start the webapp project using the maven-jetty-plugin (in webapp project). unfortunately this does not work as the exec:exec goal will hang as mvn jetty:run command does not return. i guess i could solve this problem by adding a at the end of the command but this will limited to only linux users. Since the above approach doesn't work. i wonder if i could add the maven-jetty-plugin in the test project to start the webpp in another maven module which is the webapp project in my case. i have checked the maven-jetty-plugin home page but i cannot figure out how to make it. Any ideas are welcome and thanks for your help. Regards, Kit -- View this message in context: http://maven.40175.n5.nabble.com/Run-maven-jetty-plugin-for-webapp-in-other-Maven-module-tp511054p511054.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: Run maven-jetty-plugin for webapp in other Maven module
You might get somewhere using dependency:upack-dependencies to unpack the webapp into your test module (or copy-dependencies and then jetty:run-war) On 24 June 2010 10:26, ykyuen yingkity...@gmail.com wrote: Hi all, i got a maven parent project with 2 child modules 1. The webapp project (webapp) 2. The maven module for integration test (test) both modules runs without problem individually. but as i want to automate them together. i would like to configure the test project pom.xml such that in the pre-integration-test and post-integration-test life cycle. the webapp is started. i try to use the exec-maven-plugin (in test project) to start the webapp project using the maven-jetty-plugin (in webapp project). unfortunately this does not work as the exec:exec goal will hang as mvn jetty:run command does not return. i guess i could solve this problem by adding a at the end of the command but this will limited to only linux users. Since the above approach doesn't work. i wonder if i could add the maven-jetty-plugin in the test project to start the webpp in another maven module which is the webapp project in my case. i have checked the maven-jetty-plugin home page but i cannot figure out how to make it. Any ideas are welcome and thanks for your help. Regards, Kit -- View this message in context: http://maven.40175.n5.nabble.com/Run-maven-jetty-plugin-for-webapp-in-other-Maven-module-tp511054p511054.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: Run maven-jetty-plugin for webapp in other Maven module
Thanks for your quick reply. actually my case is a little bit complicated. the webapp project is not a complete war project. it depends on some other maven modules under the same parent pom. so i cannot simply use the war since it is only part of the webapp. Regards, Kit -- View this message in context: http://maven.40175.n5.nabble.com/Run-maven-jetty-plugin-for-webapp-in-other-Maven-module-tp511054p511059.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: jetty plugin and gmaven
I can't say if the jetty plugin config is correct, but for it to apply when you run jetty:run you need to move it to the pluginManagement section. http://maven.apache.org/pom.html#Plugin_Management /Anders On Mon, May 3, 2010 at 20:45, Bill Smith ne...@weseewhathappens.com wrote: I am trying to create a web project that has a mixture of both groovy code and java code. I am using the following for my pom. When running maven jetty:run it can't see my groovy scripts. running mvn package I do see the compiled classes in the war file. Any ideas what I am doing wrong? build finalNameweb/finalName plugins plugin groupIdorg.codehaus.groovy.maven/groupId artifactIdgmaven-plugin/artifactId executions execution goals goalcompile/goal /goals /execution /executions /plugin plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.9/version configuration scanIntervalSeconds2/scanIntervalSeconds requestLog implementation=org.mortbay.jetty.NCSARequestLog filenametarget/_mm_dd.request.log/filename retainDays2/retainDays appendtrue/append extendedfalse/extended logTimeZoneGMT/logTimeZone /requestLog /configuration /plugin /plugins /build
Re: maven-jetty-plugin VS Tomcat
I found the failure reason. It was because i tried to replace some strings when copying the webapps folder using maven-antrun-plugin. and the .jar files in the ~/WEB-INF/lib were corrupted during the string replacement. that's y there were java.util.zip.ZipException and java.lang.ClassNotFoundException. The problem is solved. Thanks. Regards, Kit -- View this message in context: http://old.nabble.com/maven-jetty-plugin-VS-Tomcat-tp26897619p26950332.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
maven-jetty-plugin VS Tomcat
Hi all, i have created a war maven project and if i start in using maven-jetty plugin, everything works fine. but if i tried to deploy the war project to tomcat. there is an error in the calalina.log Dec 23, 2009 1:43:22 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.20 Dec 23, 2009 1:43:23 PM org.apache.catalina.core.StandardContext start SEVERE: Error in dependencyCheck java.util.zip.ZipException: invalid literal/length code at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147) at java.util.zip.ZipInputStream.read(ZipInputStream.java:146) at java.util.jar.JarInputStream.read(JarInputStream.java:177) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at java.util.jar.JarInputStream.getBytes(JarInputStream.java:88) at java.util.jar.JarInputStream.init(JarInputStream.java:65) at java.util.jar.JarInputStream.init(JarInputStream.java:43) at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:378) at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:189) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4258) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Dec 23, 2009 1:43:23 PM org.apache.catalina.core.StandardContext start SEVERE: Error getConfigured Dec 23, 2009 1:43:23 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/corvus] startup failed due to previous errors actually i also deployed the project to a standalone jetty, but it throws the following exception 2009-12-23 13:59:29.674::INFO: jetty-6.1.21 2009-12-23 13:59:29.910::WARN: failed StartupServlet: java.lang.NoClassDefFoundError: hk/hku/cecid/ piazza/commons/Sys 2009-12-23 13:59:29.910::WARN: EXCEPTION java.lang.ClassNotFoundException: hk.hku.cecid.piazza.commons.servlet.http.HttpDispatcher but i am sure the the HttpDispatcher and Sys classes are present in the .jar files inside the ~/WEB-INF/lib folder. Have i missed anything to run the project using other web containers instead of the maven-jetty-plugins? Thanks for your help. Regards, Kit -- View this message in context: http://old.nabble.com/maven-jetty-plugin-VS-Tomcat-tp26897619p26897619.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 jetty plugin and excluding activation jar
Okay, get it now...thanks for the hint! On Thu, Oct 15, 2009 at 4:16 PM, richard schmidt hangst...@gmail.comwrote: I am sorry but I dont understand what you mean? On Thu, Oct 15, 2009 at 3:24 PM, Wayne Fay wayne...@gmail.com wrote: How can I configure the maven-jetty-plugin to exclude the activation.jar when jetty starts up? Proper usage of profiles is nearly always the solution to these kinds of problems. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven jetty plugin and excluding activation jar
How do I exclude the activation jar when i start up jetty using the maven-jetty-plugin:run goal? The WAR we are developing is to be deployed to a tomcat server, which does NOT include the activation.jar in its lib directory. This means that we need to include the jar in the project WAR file. Jetty DOES include the activation.jar in its lib directory. If I use the maven-jetty-plugin to test our application, then I get all sorts of errors due to the VM finding multiple copies of the application.jar in its classpath How can I configure the maven-jetty-plugin to exclude the activation.jar when jetty starts up? Thanks Richard
Re: Maven jetty plugin and excluding activation jar
How can I configure the maven-jetty-plugin to exclude the activation.jar when jetty starts up? Proper usage of profiles is nearly always the solution to these kinds of problems. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven jetty plugin and excluding activation jar
I am sorry but I dont understand what you mean? On Thu, Oct 15, 2009 at 3:24 PM, Wayne Fay wayne...@gmail.com wrote: How can I configure the maven-jetty-plugin to exclude the activation.jar when jetty starts up? Proper usage of profiles is nearly always the solution to these kinds of problems. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
help getting maven jetty plugin and jmx to work
I have tried to understand: http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole But I do not have a jetty-jmx.xml that seems to work. I have tried this jetty-jmx.xml: http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ But I get deployment errors with this configuration. I am now trying to find out hot to add an OPTION as per: *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That is, instead of the above, use this: java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml * Any help would be greatly appreciated --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
Re: help getting maven jetty plugin and jmx to work
I might be a tad thick, but I'm having trouble seeing what your questionhas to do with maven. have you tried the jetty lists first? On Thursday, September 17, 2009, Mick Knutson mickknut...@gmail.com wrote: I have tried to understand: http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole But I do not have a jetty-jmx.xml that seems to work. I have tried this jetty-jmx.xml: http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ But I get deployment errors with this configuration. I am now trying to find out hot to add an OPTION as per: *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That is, instead of the above, use this: java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml * Any help would be greatly appreciated --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: help getting maven jetty plugin and jmx to work
Sorry... I am trying to start jetty with the Maven jetty plugin to allow me to see the JMX MBeans in Jetty. Specifically trying to track down JNDI errors, and according to the way you start the standalone Jetty, you pass in the JVM args. We How can I do this with the Maven plugin as there are no directions on the Jetty Wiki, and I have been trying different things all day with no luck at all. --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Thu, Sep 17, 2009 at 2:54 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I might be a tad thick, but I'm having trouble seeing what your questionhas to do with maven. have you tried the jetty lists first? On Thursday, September 17, 2009, Mick Knutson mickknut...@gmail.com wrote: I have tried to understand: http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole But I do not have a jetty-jmx.xml that seems to work. I have tried this jetty-jmx.xml: http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ But I get deployment errors with this configuration. I am now trying to find out hot to add an OPTION as per: *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That is, instead of the above, use this: java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml * Any help would be greatly appreciated --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Blank Page with Jetty Plugin
I am trying to get the Jetty plugin to work with Hibernate's c3p0 connection
pool. The server seems to start just fine with run-war, but when I navigate to
any URL at localhost:8080, I see nothing but a blank page. And I mean ANY. If
it is just literally localhost:8080, I see a blank page. If I navigate to a
good URL, I see a blank page. If I navigate to a bad URL, I a blank page
rather than a 404 or a 500 error.
Here is my configuration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.11/version
configuration
webApptarget/services.war/webApp
webAppConfig
contextPath/services/contextPath
/webAppConfig
jettyConfigsrc/test/resources/jetty/jetty.xml/jettyConfig
requestLog
implementation=org.mortbay.jetty.NCSARequestLog
filenametarget/_mm_dd.request.log/filename
retainDays90/retainDays
appendtrue/append
extendedfalse/extended
logTimeZoneGMT/logTimeZone
/requestLog
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port8080/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
executions
execution
idstart-jetty/id
phasepre-integration-test/phase
goals
goalrun/goal
/goals
configuration
scanIntervalSeconds0/scanIntervalSeconds
daemontrue/daemon
/configuration
/execution
execution
idstop-jetty/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
dependencies
dependency
groupIdc3p0/groupId
artifactIdc3p0/artifactId
version0.9.1.2/version
/dependency
dependency
groupIdcom.oracle.jdbc/groupId
artifactIdojdbc6/artifactId
version${oracle.driver.version}/version
/dependency
/dependencies
/plugin
Incidentally, the jetty.xml file in the jettyConfig element contains nothing
but c3p0 stuff being bound to a JNDI datasource. Also, the request log file is
created but blank as well.
As you can imagine, failure with no feedback is frustrating. Any insight is
appreciated.
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Blank Page with Jetty Plugin
Not sure about starting Jetty automatically, as I use Tomcat and Cargo for
that, but to just start Jetty and test manually, I created an index.html
file with some text to ensure the page was loaded, then I use this
declaration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
contextPath/${finalName}/contextPath
scanIntervalSeconds10/scanIntervalSeconds
scanTargetPatterns
scanTargetPattern
directorysrc/main/webapp/WEB-INF/directory
excludes
exclude**/*.jsp/exclude
exclude**/*.xhtml/exclude
/excludes
includes
include**/*.properties/include
include**/*.xml/include
/includes
/scanTargetPattern
/scanTargetPatterns
/configuration
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1.1/version
typejar/type
scopeprovided/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version${log4j.version}/version
typejar/type
scopeprovided/scope
/dependency
/dependencies
/plugin
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Wed, Sep 9, 2009 at 10:43 AM, Neil Chaudhuri
nchaudh...@potomacfusion.com wrote:
I am trying to get the Jetty plugin to work with Hibernate's c3p0
connection pool. The server seems to start just fine with run-war, but when
I navigate to any URL at localhost:8080, I see nothing but a blank page. And
I mean ANY. If it is just literally localhost:8080, I see a blank page. If I
navigate to a good URL, I see a blank page. If I navigate to a bad URL,
I a blank page rather than a 404 or a 500 error.
Here is my configuration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.11/version
configuration
webApptarget/services.war/webApp
webAppConfig
contextPath/services/contextPath
/webAppConfig
jettyConfigsrc/test/resources/jetty/jetty.xml/jettyConfig
requestLog
implementation=org.mortbay.jetty.NCSARequestLog
filenametarget/_mm_dd.request.log/filename
retainDays90/retainDays
appendtrue/append
extendedfalse/extended
logTimeZoneGMT/logTimeZone
/requestLog
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port8080/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
executions
execution
idstart-jetty/id
phasepre-integration-test/phase
goals
goalrun/goal
/goals
configuration
scanIntervalSeconds0/scanIntervalSeconds
daemontrue/daemon
/configuration
/execution
execution
idstop-jetty/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
dependencies
dependency
groupIdc3p0/groupId
artifactIdc3p0/artifactId
version0.9.1.2/version
/dependency
dependency
groupIdcom.oracle.jdbc/groupId
artifactIdojdbc6/artifactId
RE: Blank Page with Jetty Plugin
It turns out that the issue is the presence of the following:
stopKeyfoo/stopKey
stopPort8080/stopPort
When those are removed, everything works. However, when I remove them, Netbeans
gets mad, although my beloved IntelliJ is just fine.
Any insight into why these stop elements cause trouble and/or why the 2 IDEs
react differently to them is much appreciated.
Thanks.
-Original Message-
From: mknut...@baselogic.com on behalf of Mick Knutson
Sent: Wed 9/9/2009 9:50 AM
To: Maven Users List
Subject: Re: Blank Page with Jetty Plugin
Not sure about starting Jetty automatically, as I use Tomcat and Cargo for
that, but to just start Jetty and test manually, I created an index.html
file with some text to ensure the page was loaded, then I use this
declaration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
contextPath/${finalName}/contextPath
scanIntervalSeconds10/scanIntervalSeconds
scanTargetPatterns
scanTargetPattern
directorysrc/main/webapp/WEB-INF/directory
excludes
exclude**/*.jsp/exclude
exclude**/*.xhtml/exclude
/excludes
includes
include**/*.properties/include
include**/*.xml/include
/includes
/scanTargetPattern
/scanTargetPatterns
/configuration
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1.1/version
typejar/type
scopeprovided/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version${log4j.version}/version
typejar/type
scopeprovided/scope
/dependency
/dependencies
/plugin
---
Thank You.
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Wed, Sep 9, 2009 at 10:43 AM, Neil Chaudhuri
nchaudh...@potomacfusion.com wrote:
I am trying to get the Jetty plugin to work with Hibernate's c3p0
connection pool. The server seems to start just fine with run-war, but when
I navigate to any URL at localhost:8080, I see nothing but a blank page. And
I mean ANY. If it is just literally localhost:8080, I see a blank page. If I
navigate to a good URL, I see a blank page. If I navigate to a bad URL,
I a blank page rather than a 404 or a 500 error.
Here is my configuration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.11/version
configuration
webApptarget/services.war/webApp
webAppConfig
contextPath/services/contextPath
/webAppConfig
jettyConfigsrc/test/resources/jetty/jetty.xml/jettyConfig
requestLog
implementation=org.mortbay.jetty.NCSARequestLog
filenametarget/_mm_dd.request.log/filename
retainDays90/retainDays
appendtrue/append
extendedfalse/extended
logTimeZoneGMT/logTimeZone
/requestLog
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port8080/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
executions
execution
idstart-jetty/id
phasepre-integration-test/phase
goals
goalrun/goal
/goals
configuration
scanIntervalSeconds0/scanIntervalSeconds
daemontrue/daemon
/configuration
/execution
execution
idstop-jetty/id
phasepost-integration-test/phase
Re: Blank Page with Jetty Plugin
Create 2 different entries in separate profile's then switch each for the
different IDE's
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Wed, Sep 9, 2009 at 3:10 PM, Neil Chaudhuri nchaudh...@potomacfusion.com
wrote:
It turns out that the issue is the presence of the following:
stopKeyfoo/stopKey
stopPort8080/stopPort
When those are removed, everything works. However, when I remove them,
Netbeans gets mad, although my beloved IntelliJ is just fine.
Any insight into why these stop elements cause trouble and/or why the 2
IDEs react differently to them is much appreciated.
Thanks.
-Original Message-
From: mknut...@baselogic.com on behalf of Mick Knutson
Sent: Wed 9/9/2009 9:50 AM
To: Maven Users List
Subject: Re: Blank Page with Jetty Plugin
Not sure about starting Jetty automatically, as I use Tomcat and Cargo for
that, but to just start Jetty and test manually, I created an index.html
file with some text to ensure the page was loaded, then I use this
declaration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
contextPath/${finalName}/contextPath
scanIntervalSeconds10/scanIntervalSeconds
scanTargetPatterns
scanTargetPattern
directorysrc/main/webapp/WEB-INF/directory
excludes
exclude**/*.jsp/exclude
exclude**/*.xhtml/exclude
/excludes
includes
include**/*.properties/include
include**/*.xml/include
/includes
/scanTargetPattern
/scanTargetPatterns
/configuration
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1.1/version
typejar/type
scopeprovided/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version${log4j.version}/version
typejar/type
scopeprovided/scope
/dependency
/dependencies
/plugin
---
Thank You.
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Wed, Sep 9, 2009 at 10:43 AM, Neil Chaudhuri
nchaudh...@potomacfusion.com wrote:
I am trying to get the Jetty plugin to work with Hibernate's c3p0
connection pool. The server seems to start just fine with run-war, but
when
I navigate to any URL at localhost:8080, I see nothing but a blank page.
And
I mean ANY. If it is just literally localhost:8080, I see a blank page.
If I
navigate to a good URL, I see a blank page. If I navigate to a bad
URL,
I a blank page rather than a 404 or a 500 error.
Here is my configuration:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.11/version
configuration
webApptarget/services.war/webApp
webAppConfig
contextPath/services/contextPath
/webAppConfig
jettyConfigsrc/test/resources/jetty/jetty.xml/jettyConfig
requestLog
implementation=org.mortbay.jetty.NCSARequestLog
filenametarget/_mm_dd.request.log/filename
retainDays90/retainDays
appendtrue/append
extendedfalse/extended
logTimeZoneGMT/logTimeZone
/requestLog
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port8080/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
executions
execution
Very weird jetty-plugin behaviour (excluding plugin dependency when run from parent module)
hi, my setting is as follows: rootModule -webapp In pre-integration-test I start webapp with jetty plugin (webapp/pom.xml): plugin org.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.18/version dependencies dependency groupIdorg.hsqldb/groupId artifactIdhsqldb/artifactId version1.8.0.10/version /dependency /dependencies /plugin -- When running 'mvn pre-integration-test' inside webapp/ jetty starts up fine with the hsqdlb. But it fails when running the same command inside rootModule/ with ClassNotFoundError hsql.jdbcDriver. Why the heck is the dependencies section ignored for jetty plugin when running it from the parent module? It is a real miracle because the reactor itself should do nothing as also descending to the webapp/ folder and run the maven command. thanks. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/Very-weird-jetty-plugin-behaviour-%28excluding-plugin-dependency-when-run-from-parent-module%29-tp24205952p24205952.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: Very weird jetty-plugin behaviour (excluding plugin dependency when run from parent module)
I checked out a newer version of jetty plugin (http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/7.0.0.1beta2/). The problem is gone there. It seems that my problem is a bug of jetty plugin 6.1.18. aldana wrote: hi, my setting is as follows: rootModule -webapp In pre-integration-test I start webapp with jetty plugin (webapp/pom.xml): plugin org.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.18/version dependencies dependency groupIdorg.hsqldb/groupId artifactIdhsqldb/artifactId version1.8.0.10/version /dependency /dependencies /plugin -- When running 'mvn pre-integration-test' inside webapp/ jetty starts up fine with the hsqdlb. But it fails when running the same command inside rootModule/ with ClassNotFoundError hsql.jdbcDriver. Why the heck is the dependencies section ignored for jetty plugin when running it from the parent module? It is a real miracle because the reactor itself should do nothing as also descending to the webapp/ folder and run the maven command. thanks. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/Very-weird-jetty-plugin-behaviour-%28excluding-plugin-dependency-when-run-from-parent-module%29-tp24205952p24206510.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: Very weird jetty-plugin behaviour (excluding plugin dependency when run from parent module)
aaargh, the real cause was different. Inside the parent-pom I mistakenly added the plugin-definition to build instead of pluginManagement. So in the end i dependencies section resolved to an empty set. Though I find it a bit weird that when doing a multimodule build a parent-module can override the dependencies setting of a plugin of a child module. I would expect the opposite. aldana wrote: I checked out a newer version of jetty plugin (http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/7.0.0.1beta2/). The problem is gone there. It seems that my problem is a bug of jetty plugin 6.1.18. aldana wrote: hi, my setting is as follows: rootModule -webapp In pre-integration-test I start webapp with jetty plugin (webapp/pom.xml): plugin org.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.18/version dependencies dependency groupIdorg.hsqldb/groupId artifactIdhsqldb/artifactId version1.8.0.10/version /dependency /dependencies /plugin -- When running 'mvn pre-integration-test' inside webapp/ jetty starts up fine with the hsqdlb. But it fails when running the same command inside rootModule/ with ClassNotFoundError hsql.jdbcDriver. Why the heck is the dependencies section ignored for jetty plugin when running it from the parent module? It is a real miracle because the reactor itself should do nothing as also descending to the webapp/ folder and run the maven command. thanks. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/Very-weird-jetty-plugin-behaviour-%28excluding-plugin-dependency-when-run-from-parent-module%29-tp24205952p24207485.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
multimodule project: jetty plugin running two webapp-modules on same port
hi, I got following project structure: app1/ -core-stuff -webapp1/ -webapp2/ I tried to put jetty plugin config to app1/pom.xml and expected that submodules with war packaging would inherit this setting. This does not work because jetty plugin moans about core-stuff/ not having a webapp folder. Now my questions are: -Is it possible to tell a plugin run only to be applied on a certain packaging (war in my case). Is there a possiblity to configure a plugin execution by packaging type? If yes, is maven reactor so clever that both apps are indeed deployed to the same port and no adress-already-in-use problem occurs? -Is there another alternative to run two sub-module webapps under the same port with maven jetty plugin? thanks. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24138613.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: multimodule project: jetty plugin running two webapp-modules on same port
you'll need another module that depends on the two web apps On Sunday, June 21, 2009, aldana ald...@gmx.de wrote: hi, I got following project structure: app1/ -core-stuff -webapp1/ -webapp2/ I tried to put jetty plugin config to app1/pom.xml and expected that submodules with war packaging would inherit this setting. This does not work because jetty plugin moans about core-stuff/ not having a webapp folder. Now my questions are: -Is it possible to tell a plugin run only to be applied on a certain packaging (war in my case). Is there a possiblity to configure a plugin execution by packaging type? If yes, is maven reactor so clever that both apps are indeed deployed to the same port and no adress-already-in-use problem occurs? -Is there another alternative to run two sub-module webapps under the same port with maven jetty plugin? thanks. - manuel aldana aldana((at))gmx.de http://gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24138613.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: multimodule project: jetty plugin running two webapp-modules on same port
I tried this out, but it would not work, because jetty:run config is not merged to both webapps and they are deployed at once to the same port, but jetty:run goal is executed sequentially for both webapps. Stephen Connolly-2 wrote: you'll need another module that depends on the two web apps On Sunday, June 21, 2009, aldana ald...@gmx.de wrote: hi, I got following project structure: app1/ -core-stuff -webapp1/ -webapp2/ I tried to put jetty plugin config to app1/pom.xml and expected that submodules with war packaging would inherit this setting. This does not work because jetty plugin moans about core-stuff/ not having a webapp folder. Now my questions are: -Is it possible to tell a plugin run only to be applied on a certain packaging (war in my case). Is there a possiblity to configure a plugin execution by packaging type? If yes, is maven reactor so clever that both apps are indeed deployed to the same port and no adress-already-in-use problem occurs? -Is there another alternative to run two sub-module webapps under the same port with maven jetty plugin? thanks. - manuel aldana aldana((at))gmx.de http://gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24138613.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 - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24139869.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: multimodule project: jetty plugin running two webapp-modules on same port
which is why you need a third module... the third module is the one that you run jetty:run in. 2009/6/22 aldana ald...@gmx.de: I tried this out, but it would not work, because jetty:run config is not merged to both webapps and they are deployed at once to the same port, but jetty:run goal is executed sequentially for both webapps. Stephen Connolly-2 wrote: you'll need another module that depends on the two web apps On Sunday, June 21, 2009, aldana ald...@gmx.de wrote: hi, I got following project structure: app1/ -core-stuff -webapp1/ -webapp2/ I tried to put jetty plugin config to app1/pom.xml and expected that submodules with war packaging would inherit this setting. This does not work because jetty plugin moans about core-stuff/ not having a webapp folder. Now my questions are: -Is it possible to tell a plugin run only to be applied on a certain packaging (war in my case). Is there a possiblity to configure a plugin execution by packaging type? If yes, is maven reactor so clever that both apps are indeed deployed to the same port and no adress-already-in-use problem occurs? -Is there another alternative to run two sub-module webapps under the same port with maven jetty plugin? thanks. - manuel aldana aldana((at))gmx.de http://gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24138613.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 - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/multimodule-project%3A-jetty-plugin-running-two-webapp-modules-on-same-port-tp24138613p24139869.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
maven jetty plugin does not rebuild war
maven plugin in my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
contextPath/audit/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopecompile/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
scopecompile/scope
/dependency
/dependencies
/plugin
/plugins
any time I make changes to java code and run jetty:run the changes are not
picked up , I have to do a clean and which deletes the war file , if there
is war file in target then this plugin does not rebuild the war , please
help me how to resolve this ?
Re: Using buildnumber-maven-plugin together with jetty plugin
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very
straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend
on each
others. Is that right?
The major problem for integration in our process now is that
Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is
too
old. It's probably the IDEA SVN client implementation that returns
a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not
changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with
the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only
for
creating WAR to deploy, and that's perfect here. People should be
able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with
the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com
wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly,
does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin
directly
rather than a lifecycle phase, the buildNumber obviously doesn't
get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com
wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable
when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2615332.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Re: Using buildnumber-maven-plugin together with jetty plugin
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very
straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend
on each
others. Is that right?
The major problem for integration in our process now is that
Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is
too
old. It's probably the IDEA SVN client implementation that returns
a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not
changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with
the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only
for
creating WAR to deploy, and that's perfect here. People should be
able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with
the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com
wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly,
does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin
directly
rather than a lifecycle phase, the buildNumber obviously doesn't
get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com
wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable
when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2615332.html
Sent from the maven users mailing list archive at Nabble.com
Re: Using buildnumber-maven-plugin together with jetty plugin
Thanks, sorry about that, I was limiting the artifacts to javax/* only.
I still don't understand: [WARNING] Attempting to build MavenProject instance
for Artifact
(org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of
type: maven-plugin; constructing POM artifact instead.
but it seems to appear from time to time only (probably on Maven first launch
of the day)
thanks!
You have to configure your repo manager (artifactory as I can see in your logs).
Because the pom is really here [1].
--
Olivier
[1] http://download.java.net/maven/2/net/java/dev/jna/jna/3.0.5/
2009/4/17 nodje nodje...@gmail.com:
Olivier,
i'm getting those log lines for each mavengoal invoked:
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of
type: maven-plugin; constructing POM artifact instead.
[06:46:25] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
[06:46:26] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
I don't understand the warning and I'm wondering why it has to re-download
the jna artifacts each time?
Can you elaborate a bit on this please?
thanks
-nodje
2009/4/14 Olivier Lamy ol...@apache.org:
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn
providerImplementation doesn't actually call the svn info to get the
revision number.
Arghhh, I will check that.
Should be fixed with last deployed SNAPSHOT.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though
Re: Using buildnumber-maven-plugin together with jetty plugin
You have to configure your repo manager (artifactory as I can see in your logs).
Because the pom is really here [1].
--
Olivier
[1] http://download.java.net/maven/2/net/java/dev/jna/jna/3.0.5/
2009/4/17 nodje nodje...@gmail.com:
Olivier,
i'm getting those log lines for each mavengoal invoked:
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of
type: maven-plugin; constructing POM artifact instead.
[06:46:25] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
[06:46:26] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
I don't understand the warning and I'm wondering why it has to re-download
the jna artifacts each time?
Can you elaborate a bit on this please?
thanks
-nodje
2009/4/14 Olivier Lamy ol...@apache.org:
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn
providerImplementation doesn't actually call the svn info to get the
revision number.
Arghhh, I will check that.
Should be fixed with last deployed SNAPSHOT.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on
each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem
Re: Using buildnumber-maven-plugin together with jetty plugin
Olivier,
i'm getting those log lines for each mavengoal invoked:
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3-20090414.214556-8) of
type: maven-plugin; constructing POM artifact instead.
[06:46:25] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
[06:46:26] Downloading:
http://allence:8081/artifactory/repo/net/java/dev/jna/jna/3.0.5/jna-3.0.5.pom
I don't understand the warning and I'm wondering why it has to re-download the
jna artifacts each time?
Can you elaborate a bit on this please?
thanks
-nodje
2009/4/14 Olivier Lamy ol...@apache.org:
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn providerImplementation
doesn't actually call the svn info to get the revision number.
Arghhh, I will check that.
Should be fixed with last deployed SNAPSHOT.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6
Re: Using buildnumber-maven-plugin together with jetty plugin
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn providerImplementation
doesn't actually call the svn info to get the revision number.
Arghhh, I will check that.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod
Re: Using buildnumber-maven-plugin together with jetty plugin
2009/4/14 Olivier Lamy ol...@apache.org:
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn providerImplementation
doesn't actually call the svn info to get the revision number.
Arghhh, I will check that.
Should be fixed with last deployed SNAPSHOT.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
Re: Using buildnumber-maven-plugin together with jetty plugin
It works fine now, thanks a lot!
-nodje
2009/4/14 Olivier Lamy ol...@apache.org:
2009/4/14 nodje nodje...@gmail.com:
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as
it was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/Users/nodje/Documents/project/company/project svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/company/project
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn providerImplementation
doesn't actually call the svn info to get the revision number.
Arghhh, I will check that.
Should be fixed with last deployed SNAPSHOT.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
yes I do
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate
Re: Using buildnumber-maven-plugin together with jetty plugin
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get executed 4
times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I understand,
it's not currently possible to make plugin goals depend on each others. Is that
right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too old.
It's probably the IDEA SVN client implementation that returns a fancy 'svn
info' response.
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to learn
to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin
Re: Using buildnumber-maven-plugin together with jetty plugin
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.html
Sent from the maven users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail
Re: Using buildnumber-maven-plugin together with jetty plugin
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin
Re: Using buildnumber-maven-plugin together with jetty plugin
Thanks for the info Stephen. I didn't expected a new release of SVN so soon!
SVNKIT's probably gonna solve the problem.
Changing the SVN CLI's not gonna help anyway, and as far as I'm concerned no
Macport available for 1.6 yet! I'll be watching that.
cheers
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2
Re: Using buildnumber-maven-plugin together with jetty plugin
Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as it
was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd /Users/nodje/Documents/project/company/project
svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
From the trace differences, it looks like the javasvn providerImplementation
doesn't actually call the svn info to get the revision number.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/4/13 nodje nodje...@gmail.com
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
profile
idbuild-jetty/id
build
defaultGoalvalidate/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.16/version
executions
execution
phasevalidate/phase
goals
goalrun-exploded/goal
/goals
/execution
/executions
/plugin
And it works pretty fine, even though the builnumber:create goal get
executed 4 times in the process.
This is definitely an option even though it's not very straightforward.
Can someone confirm this is the only solution today, since, as I
understand, it's not currently possible to make plugin goals depend on each
others. Is that right?
The major problem for integration in our process now is that Intellij IDEA
doesn't seem to support the plugin. It would say your SVN client is too
old. It's probably the IDEA SVN client implementation that returns a
fancy 'svn info' response.
That's because IntelliJ uses SVNKIT and not the SVN CLI.
have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
Seemingly once SVNKIT 1.3 is released, providing they have not changed the
API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
version and you'd be fine.
-Stephen
I keep the plugin for our PROD and TEST profiles that are used only for
creating WAR to deploy, and that's perfect here. People should be able to
learn to do that outside of IDEA.
thanks
-nodje
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals
Re: Using buildnumber-maven-plugin together with jetty plugin
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any jetty
invocation, but then it would call the builnumber:create twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal validate
anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly, i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2615332.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: Using buildnumber-maven-plugin together with jetty plugin
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myPod] ;-)
On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote:
thanks.
It works when you chain the goals manually:
mvn buildnumber:create jetty:run-exploded does work.
Now, I can already hear the developers complaining.
Is there a way to tell jetty plugin to execute buildnumber:create?
I could add an execution section to link the create goal to any
jetty invocation, but then it would call the builnumber:create
twice, wouldn't it?
I can't really understand why
mvn buildnumber:create jetty:run-exploded
is different from a regular
mvn jetty:run-exploded
since buildnumber:create is link to the very first lifecycle goal
validate anyway.
cheers
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly,
i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r$
{buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a
message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2615332.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: Using buildnumber-maven-plugin together with jetty plugin
Or make a batch file magic.bat/magic.sh in your project top directory which calls Maven with the proper parameters... I wouldn't suggest doing this as a regular thing, but its OK for dev purposes. Wayne On Fri, Apr 10, 2009 at 2:11 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: because executing mojos directly never invokes the lifecycle. you could have a profile with a default goal of validate and with the plugins you want bound to the validate phase of the lifecycle then mvn -Pmagic would do it for you (if your profile id is magic) Sent from my [rhymes with myPod] ;-) On 10 Apr 2009, at 10:01, nodje nodje...@gmail.com wrote: thanks. It works when you chain the goals manually: mvn buildnumber:create jetty:run-exploded does work. Now, I can already hear the developers complaining. Is there a way to tell jetty plugin to execute buildnumber:create? I could add an execution section to link the create goal to any jetty invocation, but then it would call the builnumber:create twice, wouldn't it? I can't really understand why mvn buildnumber:create jetty:run-exploded is different from a regular mvn jetty:run-exploded since buildnumber:create is link to the very first lifecycle goal validate anyway. cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using buildnumber-maven-plugin together with jetty plugin
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a message from Jetty
stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it check the
name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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: Using buildnumber-maven-plugin together with jetty plugin
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
-D
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it check
the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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: Using buildnumber-maven-plugin together with jetty plugin
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran dant...@gmail.com wrote:
I may be wrong, but i think finalName is constructed early in the
cycle and therefor buildNumber var is not propagate properly, does
maven 2.1.0 help?
No, the problem is that since Nodje is executing jetty plugin directly
rather than a lifecycle phase, the buildNumber obviously doesn't get
evaluated. Would it work if you execute both of them explicitly, i.e. mvn
buildnumber:create jetty:run-exploded?
Kalle
On Wed, Apr 8, 2009 at 11:40 PM, nodje nodje...@gmail.com wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
finalName${project.artifactId}-${project.version}-r${buildNumber}/finalName
as name for my artifacts.
But now when I try to run 'mvn jetty:run-exploded', I get a message from
Jetty stating it can't find
appname-1.1-rnull.
So it seems Jetty isn't aware of the ${buildNumber} variable when it
check the name of the war it has to deploy.
Did anyone successfully use both plugin together?
cheers
-nodje
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.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
Can JNDI be configured in the Jetty plugin configuration/ section?
I'm switching my app to use JNDI to find its datasource, but I'd really rather not have to drop a jetty-env.xml file into my source tree. I figured I could put my configure/ for the JNDI resource into the maven-jetty-plugin's configuration/ section. Now that I've done that and altered my Spring config to grab that resource, I get a NameNotFound exception. So, I'm wondering now if this will even work? If not, does someone have a solution better than dropping that xml file into the source tree? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetty Plugin Heap Size
It runs within the same VM, so the standard MAVEN_OPTS variable used before Maven works. - Brett On 25/11/2008, at 6:36 AM, David C. Hicks wrote: Is there a way to control the heap size for the Jetty Plugin? I've been looking, but I don't see anything. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetty Plugin Heap Size
As a fast copy paste example, this is the line I use for running my Alfresco Maven powered projects (a 70MB webapp): MAVEN_OPTS=-Xms256m -Xmx512m -XX:PermSize=128m mvn jetty:run HTH, Gab 2008/11/26 Brett Porter [EMAIL PROTECTED] It runs within the same VM, so the standard MAVEN_OPTS variable used before Maven works. - Brett On 25/11/2008, at 6:36 AM, David C. Hicks wrote: Is there a way to control the heap size for the Jetty Plugin? I've been looking, but I don't see anything. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gabriele Columbro Alfresco ECM Product Strategy Consultant +31 627 565 103 Sourcesense - Making sense of open Source (http://www.sourcesense.com)
Jetty Plugin Heap Size
Is there a way to control the heap size for the Jetty Plugin? I've been looking, but I don't see anything. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
set up log4j with maven jetty plugin
Please help me setup log4j with maven jetty plugin . here my configration for maven jetty plugin plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.12.rc4/version configuration /systemproperty /configuration /plugin /plugins pleas help me with the required configration for log4j setup . -- View this message in context: http://www.nabble.com/set-up-log4j-with-maven--jetty--plugin-tp20312187p20312187.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: set up log4j with maven jetty plugin
Does this help: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin Near the bottom is some stuff about logging. miro wrote: Please help me setup log4j with maven jetty plugin . here my configration for maven jetty plugin plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.12.rc4/version configuration /systemproperty /configuration /plugin /plugins pleas help me with the required configration for log4j setup . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: command line debug args for jetty plugin?
Worked great. THanks On Thu, Oct 2, 2008 at 1:07 PM, Andrew Robinson [EMAIL PROTECTED] wrote: jetty runs inside of maven, so just pass those settings in your MAVEN_OPTS environment variable and attach to maven. That has worked for me. -Andrew On Thu, Oct 2, 2008 at 1:48 PM, Mick Knutson [EMAIL PROTECTED] wrote: I am trying to connect to my Jetty application, but want to know how to add the following to the jetty plugin: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com
command line debug args for jetty plugin?
I am trying to connect to my Jetty application, but want to know how to add the following to the jetty plugin: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com
Re: command line debug args for jetty plugin?
jetty runs inside of maven, so just pass those settings in your MAVEN_OPTS environment variable and attach to maven. That has worked for me. -Andrew On Thu, Oct 2, 2008 at 1:48 PM, Mick Knutson [EMAIL PROTECTED] wrote: I am trying to connect to my Jetty application, but want to know how to add the following to the jetty plugin: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: command line debug args for jetty plugin?
Perso I use : mvnDebug jetty:run (and you have a debugger on port 8080) 2008/10/2 Mick Knutson [EMAIL PROTECTED]: I am trying to connect to my Jetty application, but want to know how to add the following to the jetty plugin: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing artifact org.apache.maven.plugins:maven-jetty-plugin
Just for others that may be confused. Brian showed me how to do this on IRC... In my settings.xml, I put pluginGroups pluginGrouporg.mortbay.jetty/pluginGroup /pluginGroups On Tue, Apr 8, 2008 at 4:52 PM, Brier, Frederick (IHG Temp) [EMAIL PROTECTED] wrote: Thank you. I made a silly mistake. -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 5:57 PM To: Maven Users List Subject: Re: Missing artifact org.apache.maven.plugins:maven-jetty-plugin This is not an official plugin, so it has a different groupId than the normal official plugins. Therefor you have to specify the groupId to be able to use it: org.mortbay.jetty:maven-jetty-plugin Brier, Frederick (IHG Temp) wrote: I was attempting to use AppFuse. Created a project from an archetype and then tried mvn jetty:run-war. I got a BUILD ERROR - The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found. So I checked. Sure enough, the plugin is missing from the repository. How do we request that it be fixed? I double checked this with two different archetypes on two different machines to make sure it was not a problem with AppFuse. I actually built a project with this archetype this weekend. Thank you for any help. Fred -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Missing artifact org.apache.maven.plugins:maven-jetty-plugin
I was attempting to use AppFuse. Created a project from an archetype and then tried mvn jetty:run-war. I got a BUILD ERROR - The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found. So I checked. Sure enough, the plugin is missing from the repository. How do we request that it be fixed? I double checked this with two different archetypes on two different machines to make sure it was not a problem with AppFuse. I actually built a project with this archetype this weekend. Thank you for any help. Fred
Re: Missing artifact org.apache.maven.plugins:maven-jetty-plugin
Brier, Frederick (IHG Temp) wrote: I was attempting to use AppFuse. Created a project from an archetype and then tried mvn jetty:run-war. I got a BUILD ERROR - The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found. So I checked. Sure enough, the plugin is missing from the repository. How do we request that it be fixed? I double checked this with two different archetypes on two different machines to make sure it was not a problem with AppFuse. I actually built a project with this archetype this weekend. Thank you for any help. you have declare the jetty plugin in your build/plugins tag! -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing artifact org.apache.maven.plugins:maven-jetty-plugin
This is not an official plugin, so it has a different groupId than the normal official plugins. Therefor you have to specify the groupId to be able to use it: org.mortbay.jetty:maven-jetty-plugin Brier, Frederick (IHG Temp) wrote: I was attempting to use AppFuse. Created a project from an archetype and then tried mvn jetty:run-war. I got a BUILD ERROR - The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found. So I checked. Sure enough, the plugin is missing from the repository. How do we request that it be fixed? I double checked this with two different archetypes on two different machines to make sure it was not a problem with AppFuse. I actually built a project with this archetype this weekend. Thank you for any help. Fred -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Missing artifact org.apache.maven.plugins:maven-jetty-plugin
Thank you. I made a silly mistake. -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 5:57 PM To: Maven Users List Subject: Re: Missing artifact org.apache.maven.plugins:maven-jetty-plugin This is not an official plugin, so it has a different groupId than the normal official plugins. Therefor you have to specify the groupId to be able to use it: org.mortbay.jetty:maven-jetty-plugin Brier, Frederick (IHG Temp) wrote: I was attempting to use AppFuse. Created a project from an archetype and then tried mvn jetty:run-war. I got a BUILD ERROR - The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found. So I checked. Sure enough, the plugin is missing from the repository. How do we request that it be fixed? I double checked this with two different archetypes on two different machines to make sure it was not a problem with AppFuse. I actually built a project with this archetype this weekend. Thank you for any help. Fred -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Jetty Plugin and filtered resources
I have the same problem as explained below. Does someone know of a solution or alternative? Thanks, Bruno On 26/10/2006, Martin Gilday [EMAIL PROTECTED] wrote: Hi, I am trying to use the Jetty plugin for Maven but have my web.xml filtered with properties. This is mainly as I have a sandbox profile which when active would change the spring config file being used. I have tried using the WAR plugin to define some filtered resources plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration webResources resource directorysrc/main/webapp/directory filteringtrue/filtering /resource /webResources /configuration /plugin /plugins When I use mvn package the web.xml is filtered correctly, for both profiles. However when I use mvn jetty:run the properties are not substituted. Is it possible to do this? Thanks, Martin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
I follow the http://appfuse.org/display/APF/AppFuse+QuickStart to practise to use the maven. Then I encounter a problem saying 'The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist' when issuing command 'maven jetty:run-war' I checked the archive - http://www.mail-archive.com/[EMAIL PROTECTED]/msg02587.html, but it seems no use. Either issuing command mvn -U or mvn -cpu does not help to run the jetty. How can I install this plugin? Thank you very much. __ Sent from Yahoo! Mail. A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist
Yup, it doesn't exist, it is not an apache plugin, so has to be qualified: plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.7/version /plugin -Andrew On Thu, Feb 28, 2008 at 8:32 AM, Neo Anderson [EMAIL PROTECTED] wrote: I follow the http://appfuse.org/display/APF/AppFuse+QuickStart to practise to use the maven. Then I encounter a problem saying 'The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist' when issuing command 'maven jetty:run-war' I checked the archive - http://www.mail-archive.com/[EMAIL PROTECTED]/msg02587.html, but it seems no use. Either issuing command mvn -U or mvn -cpu does not help to run the jetty. How can I install this plugin? Thank you very much. __ Sent from Yahoo! Mail. A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Configure maven-jetty-plugin logging
Hi, I have some serious logging configuration problems with Maven, slf4j and Jetty. The jetty plugin was configured this way http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#Logging but all I see are the log outputs from jetty, none from my webapp made with slf4j :-( Did I something wrong? Is there any approach? Thx -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Configure maven-jetty-plugin logging
Hi, I have some serious logging configuration problems with Maven, slf4j and Jetty. The jetty plugin was configured this way http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#Logging but all I see are the log outputs from jetty, none from my webapp made with slf4j :-( Did I something wrong? Is there any approach? Thx -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven jetty plugin
Thanks, but is that possible using the Mavenide? I'd like to be able to easy run jetty with or without debug, the control being in a profile. TIA John -Original Message- From: Hugo Palma [mailto:[EMAIL PROTECTED] Sent: 14 November 2007 17:27 To: Maven Users List Subject: Re: maven jetty plugin Just provide those parameters to the maven JVM and jetty will use them. I usually just set the env variable MAVEN_OPTS with: MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 and then just run: mvn jetty:run John Coleman wrote: Hi, How do I run the jetty goal with jetty configured with a debug socket? I need to pass -Xdebug and other properties to jetty. TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jetty plugin
Just provide those parameters to the maven JVM and jetty will use them. I usually just set the env variable MAVEN_OPTS with: MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 and then just run: mvn jetty:run John Coleman wrote: Hi, How do I run the jetty goal with jetty configured with a debug socket? I need to pass -Xdebug and other properties to jetty. TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven jetty plugin
Hi, How do I run the jetty goal with jetty configured with a debug socket? I need to pass -Xdebug and other properties to jetty. TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.
Debugging with the Maven Jetty Plugin in Netbeans
There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.
Re: Debugging with the Maven Jetty Plugin in Netbeans
John Coleman wrote: There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? run the jetty plugin externally (not with the embedded version of maven in netbeans, but in different jvm) with the proper debugging switches and the n attach the debugger in netbeans? Milos TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Debugging with the Maven Jetty Plugin in Netbeans
Thanks for that suggestion, not really a slick solution. Would it be possible for the plugin to spawn another thread to run jetty in debug, then perhaps the debug settings could be put in a jetty config file somewhere? It would be nice not to have to set up jetty somewhere else, as the dev team have to learn a lot of extra non-business related stuff. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:06 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans John Coleman wrote: There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? run the jetty plugin externally (not with the embedded version of maven in netbeans, but in different jvm) with the proper debugging switches and the n attach the debugger in netbeans? Milos TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging with the Maven Jetty Plugin in Netbeans
On 8/17/07, John Coleman [EMAIL PROTECTED] wrote: Thanks for that suggestion, not really a slick solution. Would it be possible for the plugin to spawn another thread to run jetty in debug, then perhaps the debug settings could be put in a jetty config file somewhere? I guess it's as slick as the eclipse solution. Spawn a new jvm with the debug parameters. and attach to it. I'm not fluent with the jetty plugin to tell if it's possible to configure to run externally (and thus be able to set the parameters via plugin config) but I always supposed that jetty is running in the same VM as maven build is. Then it's impossible to influence from the plugin. It would be nice not to have to set up jetty somewhere else, as the dev team have to learn a lot of extra non-business related stuff. netbeans own deployment maybe? AFAIK there's not an jetty module/plugin for netbeans though.. Milos John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:06 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans John Coleman wrote: There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? run the jetty plugin externally (not with the embedded version of maven in netbeans, but in different jvm) with the proper debugging switches and the n attach the debugger in netbeans? Milos TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Debugging with the Maven Jetty Plugin in Netbeans
Well I found this tip for Hudson users... $ cd main/war $ export MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000 $ mvn -o jetty:run Looks linux, but is there any way to use this with NetBeans/Mavenide+ WinXP? John -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:27 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans On 8/17/07, John Coleman [EMAIL PROTECTED] wrote: Thanks for that suggestion, not really a slick solution. Would it be possible for the plugin to spawn another thread to run jetty in debug, then perhaps the debug settings could be put in a jetty config file somewhere? I guess it's as slick as the eclipse solution. Spawn a new jvm with the debug parameters. and attach to it. I'm not fluent with the jetty plugin to tell if it's possible to configure to run externally (and thus be able to set the parameters via plugin config) but I always supposed that jetty is running in the same VM as maven build is. Then it's impossible to influence from the plugin. It would be nice not to have to set up jetty somewhere else, as the dev team have to learn a lot of extra non-business related stuff. netbeans own deployment maybe? AFAIK there's not an jetty module/plugin for netbeans though.. Milos John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:06 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans John Coleman wrote: There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? run the jetty plugin externally (not with the embedded version of maven in netbeans, but in different jvm) with the proper debugging switches and the n attach the debugger in netbeans? Milos TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging with the Maven Jetty Plugin in Netbeans
yup. that's it! you run this on command line and then attach the netbeans debugger to port 8000. you cannot set the same options to the build running from netbeans as it's maven build is running within the same JVM as the IDE itself. Milos PS: in future versions of maven support, you can delegate building to external copy of maven binaries, however that probably doesn't entirely solve your problem. On 8/17/07, John Coleman [EMAIL PROTECTED] wrote: Well I found this tip for Hudson users... $ cd main/war $ export MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000 $ mvn -o jetty:run Looks linux, but is there any way to use this with NetBeans/Mavenide+ WinXP? John -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:27 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans On 8/17/07, John Coleman [EMAIL PROTECTED] wrote: Thanks for that suggestion, not really a slick solution. Would it be possible for the plugin to spawn another thread to run jetty in debug, then perhaps the debug settings could be put in a jetty config file somewhere? I guess it's as slick as the eclipse solution. Spawn a new jvm with the debug parameters. and attach to it. I'm not fluent with the jetty plugin to tell if it's possible to configure to run externally (and thus be able to set the parameters via plugin config) but I always supposed that jetty is running in the same VM as maven build is. Then it's impossible to influence from the plugin. It would be nice not to have to set up jetty somewhere else, as the dev team have to learn a lot of extra non-business related stuff. netbeans own deployment maybe? AFAIK there's not an jetty module/plugin for netbeans though.. Milos John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 12:06 To: Maven Users List Subject: Re: Debugging with the Maven Jetty Plugin in Netbeans John Coleman wrote: There's documentation for Debugging with the Maven Jetty Plugin in Eclipse, but does such exist for NetBeans? Anyone know how to do this if not? run the jetty plugin externally (not with the embedded version of maven in netbeans, but in different jvm) with the proper debugging switches and the n attach the debugger in netbeans? Milos TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JETTY PLUGIN]
On Friday 03 August 2007 17:05:50 Craig Ching wrote: Hallo, Maybe I'm wrong about this, but I don't think there would be a way to set those in the pom as the jetty plugin runs inside the same JVM that maven runs in and I don't know of a way to set those after the JVM has been created. I think you're going to need to find a way (maybe using MAVEN_OPTS as you've tried, but I don't know much about that) to invoke the java command with your settings. the xmlbeans:xmlbeans plugin starts another VM and allows to set some memory parameters in the pom. Maybe you can steal the relevant parts of the code and create a patch for the JETTY Plugin. Jan -- Jan Torben HeuerInstitute for Geoinformatics [EMAIL PROTECTED] Robert-Koch-Strasse 26-28 +49 251 83-3196048151 Münster, Germany pgppsrYN2hmXs.pgp Description: PGP signature
Re: [JETTY PLUGIN]
Ok, Will try again the MAVEN_OPTS Thanks for your response, Regards, João Kreuzberg On 8/3/07, Craig Ching [EMAIL PROTECTED] wrote: Hi Joao Maybe I'm wrong about this, but I don't think there would be a way to set those in the pom as the jetty plugin runs inside the same JVM that maven runs in and I don't know of a way to set those after the JVM has been created. I think you're going to need to find a way (maybe using MAVEN_OPTS as you've tried, but I don't know much about that) to invoke the java command with your settings. Cheers, Craig On 8/2/07, João Kreuzberg [EMAIL PROTECTED] wrote: Hello Guys, I need to setup some memory config from my maven-jetty plugin. Tried to set MAVEN_OPTS=-Xms1024M -Xmx1024M -XX:PermSize=96M -XX:MaxPermSize=128M but didn't work. The best scenario for me would be configure this within my pom.xml file. Any idea if that is possible? Any solution that allow me to configure the memory just for running jetty will be ok. Best Regards, -- João Kreuzberg -- João Kreuzberg
Re: [JETTY PLUGIN]
Hi Joao Maybe I'm wrong about this, but I don't think there would be a way to set those in the pom as the jetty plugin runs inside the same JVM that maven runs in and I don't know of a way to set those after the JVM has been created. I think you're going to need to find a way (maybe using MAVEN_OPTS as you've tried, but I don't know much about that) to invoke the java command with your settings. Cheers, Craig On 8/2/07, João Kreuzberg [EMAIL PROTECTED] wrote: Hello Guys, I need to setup some memory config from my maven-jetty plugin. Tried to set MAVEN_OPTS=-Xms1024M -Xmx1024M -XX:PermSize=96M -XX:MaxPermSize=128M but didn't work. The best scenario for me would be configure this within my pom.xml file. Any idea if that is possible? Any solution that allow me to configure the memory just for running jetty will be ok. Best Regards, -- João Kreuzberg
[JETTY PLUGIN]
Hello Guys, I need to setup some memory config from my maven-jetty plugin. Tried to set MAVEN_OPTS=-Xms1024M -Xmx1024M -XX:PermSize=96M -XX:MaxPermSize=128M but didn't work. The best scenario for me would be configure this within my pom.xml file. Any idea if that is possible? Any solution that allow me to configure the memory just for running jetty will be ok. Best Regards, -- João Kreuzberg
jetty plugin from Mavenide
Hi, Does anyone know how to stop the jetty plugin after staring it using Mavenide please? Hitting the orange X button doesn't seem to do anything. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.
Re: jetty plugin from Mavenide
exiting the IDE should help I suppose. That's not a good solution though. Please file a bug against mevenide, I'll take a look what can be done. What version of netbeans/mevenide are you using? Milos On 7/31/07, John Coleman [EMAIL PROTECTED] wrote: Hi, Does anyone know how to stop the jetty plugin after staring it using Mavenide please? Hitting the orange X button doesn't seem to do anything. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jetty plugin from Mavenide
NetBeans 5.5 Mavenide 2.3 Where do I file a bug pls? Thanks, John -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: 31 July 2007 14:28 To: Maven Users List Subject: Re: jetty plugin from Mavenide exiting the IDE should help I suppose. That's not a good solution though. Please file a bug against mevenide, I'll take a look what can be done. What version of netbeans/mevenide are you using? Milos On 7/31/07, John Coleman [EMAIL PROTECTED] wrote: Hi, Does anyone know how to stop the jetty plugin after staring it using Mavenide please? Hitting the orange X button doesn't seem to do anything. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jetty plugin from Mavenide
http://jira.codehaus.org/browse/MEVENIDE Milos On 7/31/07, John Coleman [EMAIL PROTECTED] wrote: NetBeans 5.5 Mavenide 2.3 Where do I file a bug pls? Thanks, John -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: 31 July 2007 14:28 To: Maven Users List Subject: Re: jetty plugin from Mavenide exiting the IDE should help I suppose. That's not a good solution though. Please file a bug against mevenide, I'll take a look what can be done. What version of netbeans/mevenide are you using? Milos On 7/31/07, John Coleman [EMAIL PROTECTED] wrote: Hi, Does anyone know how to stop the jetty plugin after staring it using Mavenide please? Hitting the orange X button doesn't seem to do anything. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
