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.(JarInputStream.java:65) at java.util.jar.JarInputStream.(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: Unable to download artifact from repository
Thanks Wandy, yeah I removed proxy information from setting.xml and blown up the "org" (org.apache.maven.maven-parent) directory from the local repo...but with no luck. On Tue, Dec 22, 2009 at 2:25 AM, Wendy Smoak wrote: > On Mon, Dec 21, 2009 at 2:46 AM, amaresh mourya > wrote: > > I ran the org.apache.maven.project.MavenProject build() method from > > DeafultMavenProjectBuilder for maven-artifact's pom.xml (see A) to build > > Maven Project for maven-artifact, but since it is derived from > > org.apache.maven:maven:2.2.0 's pom.xml which has parent entry like shown > > below (see B), and maven-parent is not located at relative path is gives > me > > the following error (see C): > > If maven-parent is not available at relative path it should download it > from > > the central. > > > > 1. I haven't touched my local repo. > > 2. my setting.xml resides at \apache-maven-2.1.0\conf\settings.xml and > have > > just proxy information > > Did you try this build once before adding your proxy information to > settings.xml? If so, Maven may be "remembering" that failure. By > default it only tries to download an artifact once per day. > > After checking the central repo and confirming that the artifact does > exist, try deleting at least that sub-tree from your local repository, > and try the build again. You can also try adding -U on the command > line to force updates. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: HOWTO: Maven project for Pivot with executable jar
I'm no Maven expert myself, but putting the WTKX files in the resources directory seems like a good idea. Cross-posting to the Maven user list in case anyone has any suggestions! Greg On Dec 22, 2009, at 8:02 PM, Michael Bushe wrote: > I posted this HOWTO on developing with Pivot using Maven and making an > executable jar. Comments welcome, especially with respect to a common > project structure. Should wtkx files be under src/main/resources? > > http://michaelbushe.wordpress.com/2009/12/22/creating-an-executable-apache-pivot-app-using-maven/ > > Michael Bushe > Software Architect/Developer > mich...@bushe.com > www.bushe.com
Re: java 1.4 versus the maven-eclipse-plugin
A parent pom which I thought was setting source/target for all modules was not. This was masked by the fact that some of the other modules have their own settings of source/target. So, what I thought was the eclipse plugin enforcing the old policy of maven plugins running under 1.4 was really just what you said it was. On Tue, Dec 22, 2009 at 5:22 PM, Barrie Treloar wrote: > On Mon, Dec 21, 2009 at 12:25 PM, Benson Margulies > wrote: >> While I read the doc, it didn't seem applicable. Now that you tell me >> that there's no special trickery going on that tries to force 1.4 on >> mojo projects, I'm off to revisit all the poms to see there's >> something I missed. > > Can you post with an update when you get this fixed? > > - > 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: java 1.4 versus the maven-eclipse-plugin
On Mon, Dec 21, 2009 at 12:25 PM, Benson Margulies wrote: > While I read the doc, it didn't seem applicable. Now that you tell me > that there's no special trickery going on that tries to force 1.4 on > mojo projects, I'm off to revisit all the poms to see there's > something I missed. Can you post with an update when you get this fixed? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to skip generating source jar files
I'ld suggest putting the source plugin in a release or full build profile. That way your release manager or continuous build system and create the source jar and developers can optionally include it if you want. 2009/12/16 Anders Hammar > Sorry, I was a little bit too quite there. Didn't really see the "skip" > word. :-) > > Why is the source jar being generated in the first place? Normally > (standard > Maven) it's only done when the release-profile profile is activated. > > /Anders > > On Wed, Dec 16, 2009 at 09:10, Anders Hammar wrote: > > > http://maven.apache.org/plugins/maven-source-plugin/usage.html > > > > /Anders > > > > > > On Wed, Dec 16, 2009 at 06:38, Vikram Pyati > wrote: > > > >> Hi, > >> > >> While invoking the maven target 'package', I need to skip generation of > >> source jars. Is there any way I can do this? It will save a lot of time. > >> > >> -- > >> Regards, > >> Vikram > >> > > > > >
Referencing external properties in children pom files
I need help figuring out how to reference external properties in a child/module
pom file.
I have tried using filters, properties-maven-plugin - all the same - the
properties propagate to children project resources but do not resolve in the
pom files themselves, thus causing pom validation errors.
Specific example:
my-filter.properties contains:
foo=bar
parent pom contains:
${my.basedir}/src/main/filters/my-filter.properties
src/main/resources
true
child pom contains:
<[any-element]> ${foo}
Expect: during initialization phase in the child project, the variable value is
substituted with "bar".
Instead, getting this error:
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot find lifecycle mapping for packaging: '${foo}'.
Component descriptor cannot be found in the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMapping${foo}.
I am using maven 2.2.1
Any help would be appreciated!
Thanks!
-Leonid
Re: Links to artifacts in a snapshot repository
The nexus FAQ shows the link syntax: http://nexus.sonatype.org/nexus-faq.html#25 --Brian (mobile) On Dec 22, 2009, at 12:37 PM, Johannes Schneider wrote: Hi, at the moment I am creating a page for a project of mine. And because not everybody out there uses maven (don't understand why), I want to provide a link to the latest artifact for manual download. Of course that is not possible since every snapshot artifact has the build date prepended. How could that be solved? Sincerly, Johannes Sample repository: http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/ - 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: Links to artifacts in a snapshot repository
This is the link you're looking for: http://nexus.sonatype.org/nexus-faq.html#25 However, this only works if the snapshot is hosted in Nexus powered repository. /Anders On Tue, Dec 22, 2009 at 18:44, Hayes, Peter wrote: > This works: > > > http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT > > There is some documentation out there on this though I'm unable to pull it > at the moment. > > These are the parameters: > > r = repository name (cannot be a group I'm pretty sure) > g = group Id > a = artifact Id > v = version > p = packaging type > c = classifier > > -Original Message- > From: Johannes Schneider [mailto:maili...@cedarsoft.com] > Sent: Tuesday, December 22, 2009 12:38 PM > To: Maven Users List > Subject: Links to artifacts in a snapshot repository > > Hi, > > at the moment I am creating a page for a project of mine. > And because not everybody out there uses maven (don't understand why), I > want to provide a link to the latest artifact for manual download. > > Of course that is not possible since every snapshot artifact has the > build date prepended. > How could that be solved? > > > Sincerly, > > Johannes > > > Sample repository: > > http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/ > > - > 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: surefire-2.4.2 plugin
You should always pin down the version of all plugins used. You do that through the use of the pluginManagement section. In your case I believe v2.4.2 is defined through the pluginManagement section of Maven's super pom. However, that version will change whenever you change version of Maven, which could make your build behave differently - and you won't understand why. Regarding the link to the pom: don't use the java.net repo. Use central instead (which is the default), http://repo1.maven.org/maven2/. /Anders On Tue, Dec 22, 2009 at 18:39, Steve Cohen wrote: > I'm trying to build the test goal of a project. Something in my setup > (not sure what, I'm using m2eclipse with all the default settings) is > translating that to using surefire-2.4.2 but apparently this plugin is > no good. > > > > 301 Moved Permanently > > Moved Permanently > The document has moved href=" > http://download.java.net/maven/1/org.apache.maven.plugins/poms/maven-surefire-plugin-2.4.2.pom > ">here. > > Apache Server at maven-repository.dev.java.net Port 443 > > > > The > > http://download.java.net/maven/1/org.apache.maven.plugins/poms/maven-surefire-plugin-2.4.2.pom > is not good either. > > What's going on here and how might I get around it? > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: BASH port of mercury?
What we are doing is using the maven repository as a binary artifact repository... SVN for source code... They needed somewhere to keep their binary artifacts we have RPMs of our Java modules that get installed into the stuff they build... and we already have a geo-redundant maven repository... so the path of least resistance and they accepted storing artifacts in our maven repository... but install Java... no way man! -Stephen 2009/12/22 Stephen Connolly > They do not want to install java on their machine! > > I did warn that they are java-phobes... > > -Stephen > > (I have toyed with using GCJ to compile a cli tool for them and package > that up as an RPM for them to install... but I'm convinced that some BASH > scripting should be able to do it all) > > 2009/12/22 Jesse Farinacci > > Why not the maven-cli-plugin[1]? This seems fairly close. Or are the >> shell-bigots too bigoted to drop into a subshell? :-) >> >> [1] http://wiki.github.com/mrdon/maven-cli-plugin >> >> -Jesse >> >> On Tue, Dec 22, 2009 at 9:56 AM, Stephen Connolly >> wrote: >> > Hi there, >> > >> > we have some Java-phobes... >> > >> > We want to use the Maven Repository to share binary artifacts across >> > teams... >> > >> > Has anyone got any BASH scripts which replicate Maven / ANT Tasks / >> Mercury? >> > >> >> >> >> -- >> There are 10 types of people in this world, those >> that can read binary and those that can not. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
Re: BASH port of mercury?
They do not want to install java on their machine! I did warn that they are java-phobes... -Stephen (I have toyed with using GCJ to compile a cli tool for them and package that up as an RPM for them to install... but I'm convinced that some BASH scripting should be able to do it all) 2009/12/22 Jesse Farinacci > Why not the maven-cli-plugin[1]? This seems fairly close. Or are the > shell-bigots too bigoted to drop into a subshell? :-) > > [1] http://wiki.github.com/mrdon/maven-cli-plugin > > -Jesse > > On Tue, Dec 22, 2009 at 9:56 AM, Stephen Connolly > wrote: > > Hi there, > > > > we have some Java-phobes... > > > > We want to use the Maven Repository to share binary artifacts across > > teams... > > > > Has anyone got any BASH scripts which replicate Maven / ANT Tasks / > Mercury? > > > > > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
default settings.xml?
Previous versions of the m2eclipse plugin used to allow settings.xml not to exist and use defaults. Now it errors out if the file is not present. So the question becomes, what is in a starter settings.xml, what are the default settings? Is there a way to generate a default version of this file (which may later be edited)? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: BASH port of mercury?
Why not the maven-cli-plugin[1]? This seems fairly close. Or are the shell-bigots too bigoted to drop into a subshell? :-) [1] http://wiki.github.com/mrdon/maven-cli-plugin -Jesse On Tue, Dec 22, 2009 at 9:56 AM, Stephen Connolly wrote: > Hi there, > > we have some Java-phobes... > > We want to use the Maven Repository to share binary artifacts across > teams... > > Has anyone got any BASH scripts which replicate Maven / ANT Tasks / Mercury? > -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Links to artifacts in a snapshot repository
On 12/22/2009 06:44 PM, Hayes, Peter wrote: > This works: > > http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT Thanks a lot! Sincerly, Johannes > > There is some documentation out there on this though I'm unable to pull it at > the moment. > > These are the parameters: > > r = repository name (cannot be a group I'm pretty sure) > g = group Id > a = artifact Id > v = version > p = packaging type > c = classifier > > -Original Message- > From: Johannes Schneider [mailto:maili...@cedarsoft.com] > Sent: Tuesday, December 22, 2009 12:38 PM > To: Maven Users List > Subject: Links to artifacts in a snapshot repository > > Hi, > > at the moment I am creating a page for a project of mine. > And because not everybody out there uses maven (don't understand why), I > want to provide a link to the latest artifact for manual download. > > Of course that is not possible since every snapshot artifact has the > build date prepended. > How could that be solved? > > > Sincerly, > > Johannes > > > Sample repository: > http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/ > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Links to artifacts in a snapshot repository
This works: http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT There is some documentation out there on this though I'm unable to pull it at the moment. These are the parameters: r = repository name (cannot be a group I'm pretty sure) g = group Id a = artifact Id v = version p = packaging type c = classifier -Original Message- From: Johannes Schneider [mailto:maili...@cedarsoft.com] Sent: Tuesday, December 22, 2009 12:38 PM To: Maven Users List Subject: Links to artifacts in a snapshot repository Hi, at the moment I am creating a page for a project of mine. And because not everybody out there uses maven (don't understand why), I want to provide a link to the latest artifact for manual download. Of course that is not possible since every snapshot artifact has the build date prepended. How could that be solved? Sincerly, Johannes Sample repository: http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/ - 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
surefire-2.4.2 plugin
I'm trying to build the test goal of a project. Something in my setup (not sure what, I'm using m2eclipse with all the default settings) is translating that to using surefire-2.4.2 but apparently this plugin is no good. 301 Moved Permanently Moved Permanently The document has moved http://download.java.net/maven/1/org.apache.maven.plugins/poms/maven-surefire-plugin-2.4.2.pom";>here. Apache Server at maven-repository.dev.java.net Port 443 The http://download.java.net/maven/1/org.apache.maven.plugins/poms/maven-surefire-plugin-2.4.2.pom is not good either. What's going on here and how might I get around it? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Links to artifacts in a snapshot repository
Hi, at the moment I am creating a page for a project of mine. And because not everybody out there uses maven (don't understand why), I want to provide a link to the latest artifact for manual download. Of course that is not possible since every snapshot artifact has the build date prepended. How could that be solved? Sincerly, Johannes Sample repository: http://nexus.cedarsoft.com/content/groups/public-snapshots/com/cedarsoft/serialization/1.0.0-beta2-SNAPSHOT/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ear-plugin and profiles: poor cooperation?
I believe that the behavior you see is correct. Maybe not what you want though...:-) If you explain why you sometimes would like to add more jars wee could suggest a different solution. /Anders On Tue, Dec 22, 2009 at 16:12, Rebholz Paul wrote: > > Hi all! > > > > We have a project producing an ear artifact. The contents of the ear > > file are configured with the maven-ear-plugin. In profiles we want to > > be able to flexibly add more artifacts to the ear file as shown in the > > example below. Our tests so far revealed a different behaviour than > > expected. When adding a jar file with the jarModule element, all other > > entries corresponding to jarModules disappear in the application.xml > > and even some other jar files disappear completely from the ear. > > Moreover, when adding a second profile adding jars, the first is > > eclipsed. Is this a bug in the maven-ear-plugin implementation? > > > > Regards, Paul > > > > > > > > my_test > > > > > > my_switch > > true > > > > > > > > > > > > maven-ear-plugin > > > > > > > > quartz > > quartz > > > > true > > > > > > > > > > > > > > > > > > quartz > > quartz > > jar > > 1.5.2 > > > > > > > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. If you receive > this message in error, please notify the sender urgently and then > immediately delete the message and any copies of it from your system. Please > also immediately destroy any hardcopies of the message. > The sender's company reserves the right to monitor all e-mail > communications through their networks. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: "incubating" tests
Or use the excludes config of the surefire plugin to exclude those tests in an incubating phase, then when they grow up to be proper tests remove the name from the surefire plugin config. See http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html Ben On 22 Dec 2009, at 15:04, Frederic Camblor wrote: > I'm lovin this solution (looks like I forgotten the KISS principle this case > ... :-)) > > Thanks > Frédéric > > On Tue, Dec 22, 2009 at 3:46 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> Don't have your tests end in Test or TestCase or start with Test. That way >> you can keep them in src/test/java and they will be compiled, but surefire >> will not execute them >> >> 2009/12/22 Frederic Camblor >> >>> Hi all ! >>> >>> I'm facing a problem which looks simple but I've not succeeded resolving >> it >>> yet :-) >>> >>> I'd like to create "incubation tests" in my project. >>> >>> "incubation tests" are : >>> - part of tests hierarchy, but dissociated with test classes (that is to >>> say, I will locate them in something like src/incubating_test/java) >>> - should be compiled in the test-compile phase >>> - but not executed in the test phase (they will never be executed : they >>> are >>> in incubation !) >>> >>> If I add the src/incubating_test/java test source with the build helper >>> plugin, my incubating test will be executed >>> If I don't, they won't be compiled >>> I could add src/incubating_test/java directly to src ... but it will be >>> really confusing ! >>> >>> I precise : I don't search a "junit/testng" solution which will "disable" >>> my >>> tests at runtime. >>> >>> It is a maven build solution (surely with the help of >> maven-compiler-plugin >>> and maven-build-helper-plugin) that I'm looking for :-) >>> >>> Thanks for you help. >>> Frédéric >>> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
ear-plugin and profiles: poor cooperation?
> Hi all! > > We have a project producing an ear artifact. The contents of the ear > file are configured with the maven-ear-plugin. In profiles we want to > be able to flexibly add more artifacts to the ear file as shown in the > example below. Our tests so far revealed a different behaviour than > expected. When adding a jar file with the jarModule element, all other > entries corresponding to jarModules disappear in the application.xml > and even some other jar files disappear completely from the ear. > Moreover, when adding a second profile adding jars, the first is > eclipsed. Is this a bug in the maven-ear-plugin implementation? > > Regards, Paul > > > > my_test > > > my_switch > true > > > > > > maven-ear-plugin > > > > quartz > quartz > > true > > > > > > > > > quartz > quartz > jar > 1.5.2 > > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. The sender's company reserves the right to monitor all e-mail communications through their networks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: "incubating" tests
I'm lovin this solution (looks like I forgotten the KISS principle this case ... :-)) Thanks Frédéric On Tue, Dec 22, 2009 at 3:46 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Don't have your tests end in Test or TestCase or start with Test. That way > you can keep them in src/test/java and they will be compiled, but surefire > will not execute them > > 2009/12/22 Frederic Camblor > > > Hi all ! > > > > I'm facing a problem which looks simple but I've not succeeded resolving > it > > yet :-) > > > > I'd like to create "incubation tests" in my project. > > > > "incubation tests" are : > > - part of tests hierarchy, but dissociated with test classes (that is to > > say, I will locate them in something like src/incubating_test/java) > > - should be compiled in the test-compile phase > > - but not executed in the test phase (they will never be executed : they > > are > > in incubation !) > > > > If I add the src/incubating_test/java test source with the build helper > > plugin, my incubating test will be executed > > If I don't, they won't be compiled > > I could add src/incubating_test/java directly to src ... but it will be > > really confusing ! > > > > I precise : I don't search a "junit/testng" solution which will "disable" > > my > > tests at runtime. > > > > It is a maven build solution (surely with the help of > maven-compiler-plugin > > and maven-build-helper-plugin) that I'm looking for :-) > > > > Thanks for you help. > > Frédéric > > >
BASH port of mercury?
Hi there,
we have some Java-phobes...
We want to use the Maven Repository to share binary artifacts across
teams...
Has anyone got any BASH scripts which replicate Maven / ANT Tasks / Mercury?
At the moment the best I have is:
repo_dir=$(echo "${groupId}" | sed -n -e
"s:\.:/:gp")/${artifactId}/${version/-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]\.[0-9][0-9][0-9][0-9][0-9][0-9]-[0-9]*/-SNAPSHOT}/
repo_path=$repo_dir/${artifactId}-${version}${classifier:+-}${classifier}.${packaging}
local_path=~/.m2/repository/${repo_path}
remote_path=http://repo.mycompany.org/content/repositories/$(if [[
"$version" =~ ".*-SNAPSHOT|.*-[0-9]{8}\.[0-9]{6}-[0-9][0-9]*" ]] ; then echo
"snapshot"; else echo "release"; fi)/${repo_path}
1. Deploy:
curl -s -T ${file} ${remote_path}
2. Install
cp -f ${file} ${local_path}
3. Get
if [ -f $local_path ] ; then
if [[ "$version" =~ ".*-SNAPSHOT|.*-[0-9]{8}\.[0-9]{6}-[0-9][09-]*"
]] ; then
remote_status=$(curl --silent --remote-time --head -w
"%{http_code}" $remote_path -o /dev/null)
if [ 200 -eq $remote_status ] ; then
curl --silent --remote-time -z $local_path
$remote_path;
else
exit 1;
fi
fi
echo $local_path
exit 0
else
mkdir -p $repo_dir
remote_status=$(curl --silent --remote-time --head -w "%{http_code}"
$remote_path -o /dev/null)
echo $remote_status
if [ 200 -eq $remote_status ] ; then
curl --silent --remote-time -o $local_path $remote_path;
else
exit 1;
fi
echo $local_path
exit 0;
fi
But I'm wondering has any bash wizard got the metadata parsing working (so
that I can do proper time-stampped snapshots)
Re: "incubating" tests
Don't have your tests end in Test or TestCase or start with Test. That way you can keep them in src/test/java and they will be compiled, but surefire will not execute them 2009/12/22 Frederic Camblor > Hi all ! > > I'm facing a problem which looks simple but I've not succeeded resolving it > yet :-) > > I'd like to create "incubation tests" in my project. > > "incubation tests" are : > - part of tests hierarchy, but dissociated with test classes (that is to > say, I will locate them in something like src/incubating_test/java) > - should be compiled in the test-compile phase > - but not executed in the test phase (they will never be executed : they > are > in incubation !) > > If I add the src/incubating_test/java test source with the build helper > plugin, my incubating test will be executed > If I don't, they won't be compiled > I could add src/incubating_test/java directly to src ... but it will be > really confusing ! > > I precise : I don't search a "junit/testng" solution which will "disable" > my > tests at runtime. > > It is a maven build solution (surely with the help of maven-compiler-plugin > and maven-build-helper-plugin) that I'm looking for :-) > > Thanks for you help. > Frédéric >
Re: how to use buildnumber-maven-plugin
amit,
You can use the same Nick suggestion using two execution tags to same plugin
tag. Try this:
org.codehaus.mojo
buildnumber-maven-plugin
0.9.6
generate-buildnumber
validate
create
{0,date,MM-DD-}
timestamp
buildDateToDirectory
generate-timestamp
validate
create
{0,date,MM-DD--HH-mm}
timestamp
buildDateToJar
Use ${buildDateToDirectory} and ${buildDateToJar} instead of ${buildNumber}.
Sergio M C Figueiredo
my blog in "pt-BR": http://devdelver.wordpress.com/
amit kumar-18 wrote:
>
> I am inheriting the ${build.directory} property from the root project and
> then in children projects i am trying to give the as -
> ${buildNumber} but its taking the format same as I defined in the root
> pom.
> Any ideas?
>
> Amit
>
> On Tue, Apr 29, 2008 at 2:50 PM, amit kumar
> wrote:
>
>> Can I have two separate variables containing build number values in
>> different format?
>> Actually want to use build number for both the build directory name and
>> the time stamp in jar file names.
>> so a buildnumber with format MM-DD- be the build directory name
>> and MM-DD--HH-mm gets appended to the jar names and in the manifest
>> file.
>>
>>
>> Regards,
>> Amit
>>
>>
>> On Tue, Mar 11, 2008 at 7:09 PM, Rex Huang
>> wrote:
>>
>> > Thank you for your suggestion,
>> > but it seems not working correcttly for the bug of this plugin.
>> >
>> > the results as below:
>> > [buildnumber:create {execution: generate-buildnumber}]
>> > Storing buildNumber: 16 at timestamp: 1205242293453
>> > [buildnumber:create {execution: generate-timestamp}]
>> > Storing buildNumber: Tue Mar 11 14:31 CET 2008 at timestamp:
>> > 1205242293453
>> >
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/how-to-use-buildnumber-maven-plugin-tp15875096p26889432.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: Transitive dependency omitted if prior dependency resolved first then subsquently omitted
Sorry I neglected to include both versions of projectD. File updated. http://old.nabble.com/file/p26889403/omitted_dependency_example.zip omitted_dependency_example.zip Anders Hammar wrote: > > I tried your example, but it doesn't work. It's complaining about > test.projects:projectD:jar:1.0.0-SNAPSHOT missing. > > /Anders > > On Thu, Dec 17, 2009 at 20:23, egroesbeck wrote: > >> >> No problem: >> >> http://old.nabble.com/file/p26833532/omitted_dependency_example.zip >> omitted_dependency_example.zip >> >> >> >> Wayne Fay wrote: >> > >> >> eventually omitted. The fact that I can change the dependency order >> in >> >> artifact A and get a different list of resolved artifacts leads me to >> >> believe this is more likely to be a defect but I wanted to be sure I >> > >> > If you can build a (small) sample project that demonstrates the issue >> > very clearly, then someone can more easily look at it and potentially >> > resolve it, if it is in fact a bug. >> > >> > Wayne >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Transitive-dependency-omitted-if-prior-dependency-resolved-first-then-subsquently-omitted-tp26818594p26833532.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 >> >> > > -- View this message in context: http://old.nabble.com/Transitive-dependency-omitted-if-prior-dependency-resolved-first-then-subsquently-omitted-tp26818594p26889403.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
"incubating" tests
Hi all ! I'm facing a problem which looks simple but I've not succeeded resolving it yet :-) I'd like to create "incubation tests" in my project. "incubation tests" are : - part of tests hierarchy, but dissociated with test classes (that is to say, I will locate them in something like src/incubating_test/java) - should be compiled in the test-compile phase - but not executed in the test phase (they will never be executed : they are in incubation !) If I add the src/incubating_test/java test source with the build helper plugin, my incubating test will be executed If I don't, they won't be compiled I could add src/incubating_test/java directly to src ... but it will be really confusing ! I precise : I don't search a "junit/testng" solution which will "disable" my tests at runtime. It is a maven build solution (surely with the help of maven-compiler-plugin and maven-build-helper-plugin) that I'm looking for :-) Thanks for you help. Frédéric
RE: how to use buildnumber-maven-plugin
Thanks Nick. This works to me. Now I have two variables: a build number and a
human readable current date. I only modified your suggestion setting up a
new name for the variables in each execution using "buildNumberPropertyName"
tag:
org.codehaus.mojo
buildnumber-maven-plugin
generate-buildnumber
validate
create
{0,number}
buildNumber0
buildNumberSeq
generate-timestamp
validate
create
{0,date,dd-MM-}
timestamp
buildDate
Now, I can use this data using ${buildDate} and ${buildNumberSeq} instead of
${buildNumber}.
Sergio M C Figueiredo
(my blog: http://devdelver.wordpress.com/ - in "pt-BR")
Nick Stolwijk wrote:
>
> I don't know for certain if this is gonna work, but you can give it a try:
>
> <...>
>
> Hth,
>
> Nick S.
>
>
--
View this message in context:
http://old.nabble.com/how-to-use-buildnumber-maven-plugin-tp15875096p26889184.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: Question concerning maven-compiler-plugin
> My question is: what is the reason that the maven compiler plugin does not > recompile the Client.java in the scenario described above? It only > recompiles it if the Client.class is deleted, i.e. by calling "mvn clean > compile". That's the way javac works (and maven-compiler-plugin just invokes javac). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Question concerning maven-compiler-plugin
I created a minimal example maven project with the following directory
structure:
C:\SAMPLE.PRJ1
| pom.xml
|
\---src
\---main
\---java
\---sample
Client.java
Library.java
with the content of files Library.java and Client.java as shown below:
package sample;
public class Library {
public int calcSum(int summand1, int summand2) {
return summand1 + summand2;
}
}
package sample;
public class Client {
public Client() {
Library lib = new Library();
int result = lib.calcSum(1, 2);
System.out.println(result);
}
}
Obviously Client.java depends on Library.java because it calls method
calcSum() from inside the constructor. Now I do a "mvn compile" and both
classes are compiled to the target directory as I expect it. Now I change
the signature of the method "calcSum()" in Library.java to
public int calcSum(int summand1, int summand2, int summand3) {
}
If the Client.java would be compiled against this Library.java this would
result in an compile error. But a call to "mvn compile" succeeds, because it
seems as only Library.java is compiled whereas Client.java is ignored.
My question is: what is the reason that the maven compiler plugin does not
recompile the Client.java in the scenario described above? It only
recompiles it if the Client.class is deleted, i.e. by calling "mvn clean
compile".
Regards,
Meikel
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maik Ebert is out of the office.
I am out of the office until 31.12.2010. In urgent cases please contact Wotan von Klass, phone: +49 (0) 6227 385 38 33, e-mail: wotan.vonkl...@icw.de. Ich bin bis 31.12.2010 außer Haus. In dringenden Fällen wenden Sie sich bitte an Wotan von Klass, Tel.: +49 (0) 6227 385 38 33, E-Mail: wotan.vonkl...@icw.de. Note: This is an automated response to your message "[ANN] Maven Site Plugin 2.1 Released" sent on 22.12.2009 07:40:16. This is the only notification you will receive while this person is away. InterComponentWare AG: Vorstand: Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to download every dependency we need at once?
I work in a sandbox network and have similar issues. What I do: 1) Internet Connected Host 1.1) Create pom contain all dependencies and plugins used. 1.2) mvn -s settings.xml clean install site 1.3) find, grep -v, sort -u, echo, cat sort -u, echo (obtain list of group id's downloaded) 1.4) rsync list generated in 1.3 1.5) diff latest rsync with representation of offline repo 1.6) generate diff file, usually a tar.gz 1.7) update representation of offline repo with contents of step 1.6 1.8) burn step 1.6 to disk 2) Standalone Network Host 2.1) same as step 1.7, update repo with contents contained in step 1.6 2.2) Do a full build from the repo updated in step 2.1 to confirm it still works. 3) Handling updates 3.1) update pom created in step 1.1 or manually update list in step 1.3 3.2) repeat step 1 and 2 when required to download the latest update and dependencies, sometimes it takes a few attempts to fix all dependencies. I've worked with offline maven development for a few years and usually I'm the one managing the repo and it my best solution at this moment. If you want to commands i execute let me know and I'll post them. John 2009/12/16 Anders Hammar > Why not use a corporate repository manager like Nexus or Artifactory? All > users would then configure their Maven to use that as the remote repo for > all artifacts. This will give you a central point where you manage all > artifacts, including both external and internal ones. His instance would > then proxy any remote repos on Internet (if you allow it too). > > Any other solution is a hack. > > /Anders > > On Tue, Dec 15, 2009 at 14:19, Gajo Csaba wrote: > > > This seems to be almost perfect except it requires a project to exist. > But > > I'll use it if there's nothing else :) > > > > Thanks, Csaba > > > > > > > > Jesse Farinacci wrote: > > > >> Hi Gajo, > >> > >> 2009/12/15 Gajo Csaba : > >> > >> > >>> Is there some cleaner way to do this? I know exactly which dependencies > >>> are > >>> needed (it's a large list), so is there some maven command to not build > >>> anything, just download these dependencies into the local .m2 > directory? > >>> > >>> > >>> > >> > >> Check out the maven-dependency-plugin:go-offline goal: > >> > >> > >> > http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html > >> > >> -Jesse Farinacci > >> > >> - > >> 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: Transitive dependency omitted if prior dependency resolved first then subsquently omitted
I tried your example, but it doesn't work. It's complaining about test.projects:projectD:jar:1.0.0-SNAPSHOT missing. /Anders On Thu, Dec 17, 2009 at 20:23, egroesbeck wrote: > > No problem: > > http://old.nabble.com/file/p26833532/omitted_dependency_example.zip > omitted_dependency_example.zip > > > > Wayne Fay wrote: > > > >> eventually omitted. The fact that I can change the dependency order in > >> artifact A and get a different list of resolved artifacts leads me to > >> believe this is more likely to be a defect but I wanted to be sure I > > > > If you can build a (small) sample project that demonstrates the issue > > very clearly, then someone can more easily look at it and potentially > > resolve it, if it is in fact a bug. > > > > Wayne > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > View this message in context: > http://old.nabble.com/Transitive-dependency-omitted-if-prior-dependency-resolved-first-then-subsquently-omitted-tp26818594p26833532.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: Use filter files from parent project
Something which might work for you.
parent
| -- src/main/filters
| -- pom.xml (pomP)
| -- module-a
| -- src/main/resources
| -- pom.xml (pomA)
| -- module-b
| -- src/main/resources
| -- pom.xml (pomB)
pomP
${relpath-to-parent}\src\main\filters\${env}-filter.properties
.
pomA
..
pomB
..
This approache could also work for any level depth modules. I use a similar
technique for defining where modules, sub modules, sub-sub modules are
located in the SCM.
project parent pom
${scm-url}
${scm-url}
HEAD
cruisecontrol
perforce
1666
//depot/project/trunk
scm:perforce:${scm-username}@
${scm-host}:${scm-port}:${scm-baseurl}${scm-relurl}
This then means in sub modules you simply define scm-relurl for that
specific project, plus the boiler plate scm details otherwise it doesn't
work:
${scm-url}
${scm-url}
HEAD
sub-project/sub-module
John
2009/12/15 Anders Hammar
> One way that springs to mind is to put the filter properties files in a
> separate project, then in each project use the dependency plugin to unpack
> that artifact and then use the properties files.
> However, using filtering in each and every one of your projects with the
> same properties files makes me wondering if there isn't a better option (a
> "nice" way of saying that there might be something wrong in your build
> design :-) ).
>
> /Anders
>
> On Tue, Dec 15, 2009 at 09:44, Michael Ebert
> wrote:
>
> > Hi,
> >
> > i'm facing the following issue:
> >
> > I've got a multi module project and resources filtering is activated
> > in every module:
> >
> >
> >
> >src/main/resources
> >true
> >
> >
> >
> > The directory layout:
> >
> > parent
> > | -- src/main/filters
> > | -- pom.xml
> > | -- module-a
> > | -- src/main/resources
> > | -- pom.xml
> > | -- module-b
> > | -- src/main/resources
> > | -- pom.xml
> >
> > My filter files currently reside under src/main/filters in the parent
> > project and are referenced from within the submodules via
> >
> >
> > ..\src\main\filters\${env}-filter.properties
> >
> >
> > So far so good, that works. But I'm getting into troubles when I try
> > to build the modules separately, precise when continuum does so.
> > Continuum checks out the modules in a flat hierarchy and builds the
> > modules --non-recursive (one can get around that but that's not my
> > intention):
> >
> > parent
> > | -- src/main/filters
> > | -- pom.xml
> > module-a
> > | -- src/main/resources
> > | -- pom.xml
> > module-b
> > | -- src/main/resources
> > | -- pom.xml
> >
> > Obviously, the relative referenced
> > ..\src\main\filters\${env}-filter.properties doesn't work any more.
> >
> > Is there any possibility for having my filter files at another common
> > place, that is reachable for every module, regardless of the directory
> > layout? That must be a common problem but I haven't found any solution
> > so far.
> >
> > Thanks,
> > micha.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
Re: Patch releases using Maven
I don't see it as maven issue, I see it as a source control management or people issue. Getting a clear understanding of how version numbers will be increased, how people should be using source control, once you know that maven can do what ever you need it to do. Issues you'll need to think about. 1) Source Control Management, does everyone work in trunk, or do you have branches for trunk, development, releases, patches, bugs, refactoring? 2) What is the version number string, we use something like major.minor.component.build.patch. This give us the ability to release patches for specific component builds. 3) Do you have a internal company repo, project repo or per release repo. This means when doing patches where do you get the other components for that release. The project I'm on went from ant to maven, speed of releases improved, we are slow getting it to where developers on what ever branch only need to build the xml schema's, war and ears plus the bits they are developing, everything else comes from that release branch repo. John 2009/12/16 svenkat.cm > > Hi There > > I would like to understand how effective you are doing your patch > releases > on maven based projects > > Our scenario: >We have made the release to the customer.There might be > requests from the customer(s) for some emergency fixes - say couple of jars > to be replaced with the fixes etc., Also subsequent patches should be > cumulative of all the patches to be released. > > Our plan or proposal is that: > - since our build time is long, so we don't want to do full build every > time we make patches > - since patches are specific to components, is it ok to apply the code > fix to the specific components and (re)build that particular component > > Questions: >Do you foresee any issues with approach? >what other better way you are handling in your projects? >do you use maven reactor plugin > > Thanks > -Venkat > > > -- > View this message in context: > http://old.nabble.com/Patch-releases--using-Maven-tp26806933p26806933.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-ant-tasks 2.1 regression from 2.0.10 ?
Hi, Apache Pivot uses maven-ant-tasks to get it's ant build products into a maven repo. This works if the classpath has maven-ant-tasks version 2.0.10 but does not work with maven-ant-tasks 2.1 on the classpath. The error using 2.1 is: maven-install: [artifact:install] An error has occurred while processing the Maven artifact tasks. [artifact:install] Diagnosis: [artifact:install] [artifact:install] You must specify a file and/or an attached artifact to install to the local repository. This error message was added between 2.1 and 2.0.10: http://svn.apache.org/viewvc/maven/ant-tasks/trunk/src/main/java/org/apache/maven/artifact/ant/DeployTask.java?view=diff&r1=884303&r2=884304&pathrev=884304 The Apache Pivot build.xml's relevant target is: Is there something that Pivot can do to adjust? To reproduce and for more info, please follow this thread: http://mail-archives.apache.org/mod_mbox/incubator-pivot-dev/200912.mbox/browser Thanks, Michael Bushe Software Architect/Developer mich...@bushe.com www.bushe.com
