RE: Maven filter and hsqldb mem hibernate.hbm2ddl.auto
Hello Stephane Do you want to do something like this?? https://svn.codehaus.org/mojo/trunk/sandbox/hibernate3-maven-plugin/src/it/m hibernate-65 Johann Reyes -Original Message- From: Stephane Eybert [mailto:mittiprove...@yahoo.se] Sent: Sunday, May 09, 2010 4:06 PM To: users@maven.apache.org Subject: Re: Maven filter and hsqldb mem hibernate.hbm2ddl.auto Hi Jemos, Thanks for your reply. But I wonder how come the file in the target directory shows all the properties being filtered fine. A look at the file core/target/classes/spring-hibernate.xml shows the property place holders replaced by the corresponding values. But a look at the file core/target/test-classes/spring-hibernate.xml shows that the property place holders were NOT replaced. So, the filtering works in a way that escapes me... It seems to filter something, creating a filtered file at core/target/classes/spring-hibernate.xml but not doing it for the file core/target/test-classes/spring-hibernate.xml What puzzles me is that I only run an integration test with the command: mvn clean test -Pitest Here are the generated files in the target directory, one in classes/ filtered fine and the other one in test-classes not filtered: http://old.nabble.com/file/p28505207/spring-hibernate.xml spring-hibernate.xml http://old.nabble.com/file/p28505207/spring-hibernate.xml spring-hibernate.xml -- View this message in context: http://old.nabble.com/Maven-filter-and-hsqldb-mem-hibernate.hbm2ddl.auto-tp2 8504415p28505207.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: Problems with mvn protocol handler in maven 3 beta 1
No I haven't but it's a good idea - I will do that. Thanks, /Bengt 2010/5/9 Justin Edelson justinedel...@gmail.com: Have you posted this to a pax mailing list? On May 9, 2010, at 5:42 AM, Bengt Rodehav be...@rodehav.com wrote: Thanks for you reply Marshal, I've tried to add the artifacts pax-url-mvn and pax-url-commons as extensions as follows: build extensions extension groupIdorg.ops4j.pax.url/groupId artifactIdpax-url-mvn/artifactId version1.1.2/version /extension extension groupIdorg.ops4j.pax.url/groupId artifactIdpax-url-commons/artifactId version1.1.2/version /extension /extensions ... I also added extensionstrue/extensions to the configuration of the features-maven-plugin. However, there is no difference. I still get unknown protocol: null I also note that I was wrong in my previous post. The features-maven-plugin does not work under the 3.0-alpha-7 either. Seems like the problem has to do with maven 3, and possibly the class loading changes that you mentioned. Just can't get it to work though. Any more ideas? /Bengt 2010/5/8 Marshall Schor m...@schor.com: On 5/8/2010 2:55 AM, Bengt Rodehav wrote: No one has any ideas? Here's an idea - Maven 3 has been doing more class loader isolation stuff. Perhaps an extensions element is needed? See https://cwiki.apache.org/MAVEN/maven-3x-class-loading.html -Marshall I'm thinking along the lines that something that wasn't bundled with maven alpha is now bundled with maven beta. Something that takes precedence over what's need for customised url handlers to work. Does anyone know if something has changed in that respect from the alpha to the beta version that could break url handlers. /Bengt 2010/5/7 Bengt Rodehav be...@rodehav.com: I'm using the features-maven-plugin included in Apache Felix. It in turn uses pax-url-mvn (version 1.1.2) to enable the protocol mvn:. This works fine in maven 2.2.1 and also in maven 3.0-alpha-7. However, with everything else the same, it fails under maven 3.0-beta-1. I get java.net.MalformedURLException: unknown protocol: null This happens in a call to uri.toURL() where the uri is created from the string: mvn:org.apache.felix.karaf/apache-felix-karaf/1.4.0/ xml/features It seems that the combination of pax-url-mvn and and maven 3.0- beta-1 does not work. Has anyone got any ideas as to what is wrong and possibly a workaround? /Bengt --- -- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problems with mvn protocol handler in maven 3 beta 1
Marshall, I tried the explicit dependenciesdependency for the plugin already. No difference. Using the -X option was a good idea since you get a lot of information there. I can't see exactly what the plugin classpath looks like though. How do I determine that from the -X output? I do get the following: [DEBUG] Created new class realm pluginorg.apache.felix.karaf.tooling:features-maven-plugin:1.5.0-SNAPSHOT [DEBUG] Populating class realm pluginorg.apache.felix.karaf.tooling:features-maven-plugin:1.5.0-SNAPSHOT [DEBUG] Included: org.apache.felix.karaf.tooling:features-maven-plugin:maven-plugin:1.5.0-SNAPSHOT [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.1 [DEBUG] Included: junit:junit:jar:3.8.1 [DEBUG] Included: org.apache.felix:maven-bundle-plugin:jar:2.1.0-SNAPSHOT [DEBUG] Included: biz.aQute:bndlib:jar:0.0.357 [DEBUG] Included: net.sf.kxml:kxml2:jar:2.2.2 [DEBUG] Included: xmlpull:xmlpull:jar:1.1.3.1 [DEBUG] Included: org.apache.felix:org.apache.felix.bundlerepository:jar:1.5.0-SNAPSHOT [DEBUG] Included: org.osgi:org.osgi.core:jar:4.1.0 [DEBUG] Included: org.easymock:easymock:jar:2.4 [DEBUG] Included: org.apache.felix:org.osgi.core:jar:1.4.0 [DEBUG] Included: org.apache.felix:org.osgi.service.obr:jar:1.0.1 [DEBUG] Included: org.apache.maven:maven-archiver:jar:2.2 [DEBUG] Included: org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 [DEBUG] Included: org.apache.maven.shared:maven-dependency-tree:jar:1.2 [DEBUG] Included: org.apache.felix.karaf.features:org.apache.felix.karaf.features.core:jar:1.5.0-SNAPSHOT [DEBUG] Included: org.apache.felix.karaf:org.apache.felix.karaf.commons:jar:1.5.0-SNAPSHOT [DEBUG] Included: org.apache.felix.karaf.shell:org.apache.felix.karaf.shell.console:jar:1.5.0-SNAPSHOT [DEBUG] Included: jline:jline:jar:0.9.95.20100209 [DEBUG] Included: org.fusesource.jansi:jansi:jar:1.2 [DEBUG] Included: org.apache.aries.blueprint:org.apache.aries.blueprint:jar:0.1-incubating-SNAPSHOT [DEBUG] Included: org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT [DEBUG] Included: org.slf4j:slf4j-api:jar:1.4.3 [DEBUG] Included: org.apache.felix.gogo:org.apache.felix.gogo.runtime:jar:0.2.2 [DEBUG] Included: org.apache.felix.gogo:org.apache.felix.gogo.commands:jar:0.2.2 [DEBUG] Included: org.apache.felix.karaf.shell:org.apache.felix.karaf.shell.obr:jar:1.5.0-SNAPSHOT [DEBUG] Included: org.ops4j.pax.url:pax-url-mvn:jar:1.1.2 [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.9 [DEBUG] Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2 [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.9 [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.9 [DEBUG] Excluded: org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.9 [DEBUG] Configuring mojo org.apache.felix.karaf.tooling:features-maven-plugin:1.5.0-SNAPSHOT:add-features-to-repo from plugin realm ClassRealm[pluginorg.apache.felix.karaf.tooling:features-maven-plugin:1.5.0-SNAPSHOT, parent: ClassRealm[plexus.core, parent: null]] I interpret the above as the classpath and it includes the pax-url-mvn jar. Just to be sure I modified the source code for the features-maven-plugin so that it actually instantiates the handler (org.ops4j.pax.url.mvn.Handler) - this works fine. Thus, it seems like the handler class is available but the JVM hasn't picked it up as a URL handler. I'm not sure how that mechanism works (I'll start studying the subject). I imagine the registration is done at JVM startup. At that time the handler class is probably not available. This seems like it could be a general problem in maven 3. Is that a difference in maven 3 compared to maven 2? Would the handler class be available to the JVM at startup in maven 2 (not sure I'm using the corret terminology here but I hope you understand)? /Bengt 2010/5/9 Marshall Schor m...@schor.com: One more idea to try: Each plugin element in build can define its own additional things to put on the classpath, by including dependenciesdependency elements. See http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_plugin - the dependency element is defined as Additional dependencies that this project needs to introduce to the plugin's classloader. So, for the felix features-maven-plugin, inside the plugin element for it, try adding a dependency on the artifact(s) that implement the mvn: protocol. If you try this (adding pax-url-mvn version 1.1.2) and it doesn't work, check 2 more things: Run
Re: feature request: more verbose error messages
Feature request: when it fails, output more information than normal. In this case it was that that particular class didn't exist--but you can't tell that from the error output. This is not a good place to put feature requests -- they are simply lost in the general noise of the list. If you want this to ever be seen by someone who might possible implement your suggestion, you must file it in Jira. Otherwise you are quite literally talking to a brick wall. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error installing artifact's metadata
I'm facing the same error too . Could anyone assist here by shedding light on this ? What is the solution to the problem ? Thanks Nanditha -- View this message in context: http://maven-users.828.n2.nabble.com/Re-Error-installing-artifact-s-metadata-tp529914p5029851.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: feature request: more verbose error messages
If you want this to ever be seen by someone who might possible implement your suggestion, you must file it in Jira. Otherwise you are quite literally talking to a brick wall. Really, Wayne? Literally? Where is the wall? -K, who thinks Wayne meant figuratively. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: feature request: more verbose error messages
Literally - http://xkcd.com/725/ -Original Message- From: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org] Sent: 10 May 2010 15:15 PM To: Maven Users List Subject: Re: feature request: more verbose error messages If you want this to ever be seen by someone who might possible implement your suggestion, you must file it in Jira. Otherwise you are quite literally talking to a brick wall. Really, Wayne? Literally? Where is the wall? -K, who thinks Wayne meant figuratively. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Standard Bank email disclaimer and confidentiality note Please go to http://www.standardbank.co.za/site/homepage/emaildisclaimer.html to read our email disclaimer and confidentiality note. Kindly email disclai...@standardbank.co.za (no content or subject line necessary) if you cannot view that page and we will email our email disclaimer and confidentiality note to you. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: feature request: more verbose error messages
quite literally talking to a brick wall. Really, Wayne? Literally? Where is the wall? -K, who thinks Wayne meant figuratively. But what you don't realize is that I have a special computer with text to speech software set up in my basement that reads all my email to me. And when I'm not around, only the brick walls can hear it. Wayne, who is known to exaggerate and simply wanted to communicate that the maven users list is a poor place to post feature requests - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: feature request: more verbose error messages
Indeed. I think you made your point. I just couldn't help myself. And to Neil, I read xkcd regularly. Sometimes it leaves me bewildered, sometimes it just doesn't work for me, and sometimes it's hilarious or insightful. -K On May 10, 2010, at 9:59 AM, Wayne Fay wrote: quite literally talking to a brick wall. Really, Wayne? Literally? Where is the wall? -K, who thinks Wayne meant figuratively. But what you don't realize is that I have a special computer with text to speech software set up in my basement that reads all my email to me. And when I'm not around, only the brick walls can hear it. Wayne, who is known to exaggerate and simply wanted to communicate that the maven users list is a poor place to post feature requests - 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: feature request: more verbose error messages
On 10/05/2010 10:59 AM, Wayne Fay wrote: quite literally talking to a brick wall. Really, Wayne? Literally? Where is the wall? -K, who thinks Wayne meant figuratively. But what you don't realize is that I have a special computer with text to speech software set up in my basement that reads all my email to me. And when I'm not around, only the brick walls can hear it. Glad you clarified this. I thought it meant literally talking to a figurative brick wall. Ron Wayne, who is known to exaggerate and simply wanted to communicate that the maven users list is a poor place to post feature requests The list is not a bad place to discuss ideas before you post them, to see if someone can provide a counter argument before it becomes a permanent record in the JIRA as long as you are aware that it does not formally count as anything more than idle talk until it is in the JIRA. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven filter and hsqldb mem hibernate.hbm2ddl.auto
I just realized that I had attached the module pom.xml file instead of the parent one, so you could not really see the setup I have.. Here is the parent pom.xml file: http://old.nabble.com/file/p28512487/pom.xml pom.xml -- View this message in context: http://old.nabble.com/Maven-filter-and-hsqldb-mem-hibernate.hbm2ddl.auto-tp28504415p28512487.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: feature request: more verbose error messages
The list is not a bad place to discuss ideas before you post them, to see if someone can provide a counter argument before it becomes a permanent record in the JIRA as long as you are aware that it does not formally count as anything more than idle talk until it is in the JIRA. Agreed. But this was posted as feature request rather than feature discussion. And I think everyone on this list would like to see more useful error messages out of every piece of Maven that might possibly break. And I believe this is being addressed (at least a bit) in M3. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eXist native XML database
2010/5/9 Wayne Fay wayne...@gmail.com I'm working on maven project and I need to use embedded eXist database. Unfortunatelly, there is only 5 years old version in repo1.maven.org. You need to get the eXist people to do the uploads for newer versions of their files. If enough eXist users and developers care about Maven, they will do it. how could I tell maven developers to add required packages to the repository? You don't. If you can't get the eXist folks to get it done, you will need to (less ideally) manually install them into your own local repo cache on each machine that will build your project or (more ideally) install something like Nexus, Archiva, Artifactory and install them there so your coworkers can use the artifacts too. I think there is another option also, if the eXist folks don't respond to the need for uploading files to the maven central you can do it yourself, probably with a different groupId. check out the following link for more details (someone correct me if this is not the case) http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/ Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Freaking out: javac works, maven-compiler-plugin does not
I tracked down the problem. I have the OpenJPA 2.0.0 jar in my classpath during compilation, which registers an annotation processor automatically via META-INF/services/javax.annotation.processing.Processor. When I remove that file from META-INF/services, everything compiles ok. I'll have to file a bug against OpenJPA for that one. Thanks for your help anyway, Matthew -- View this message in context: http://maven-users.828.n2.nabble.com/Freaking-out-javac-works-maven-compiler-plugin-does-not-tp5016302p5032882.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: Missing archetype.xml in new archetype created from project
Thanks for the link. Unfortunately it didn't help with my understanding of how to create an archetype or the structure of one. I'm using Maven 2.2.1. I set up a skeleton project (MyProject) that I want to use to create the archetype (minimal classes, mainly config files and the pom.xml set up with the dependencies). Everything in my project is contained in the MyProject/src directory except for its pom.xml which is under MyProject. I ran the archetype:create-from-project command for the project. I now have a new target\generated-sources\archetype directory in my project directory which has a pom.xml file in it. The pom.xml has an artifactId of Project-archetype and a a packaging of maven-archetype. It also has two sub-directories: MyProject\target\generated-sources\archetype\src MyProject\target\generated-sources\archetype\target Both of these subdirectories contains a pom.xml and an archetype-metadata.xml which are identical. What exactly is the archetype? Everything under the MyProject\target directory or one of these directories: MyProject\target\generated-sources\archetype\ MyProject\target\generated-sources\archetype\src MyProject\target\generated-sources\archetype\target Do I need to update any files before installing the archetype? If so which ones? Thanks in advance for all help. Shelli -Original Message- From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] Sent: Thursday, May 06, 2010 1:54 PM To: Maven Users List Subject: Re: Missing archetype.xml in new archetype created from project perhaps http://maven.apache.org/guides/mini/guide-creating-archetypes.html will help you It has been written for 1.x (old) archetype, but principles are the same Regards, Hervé Le mercredi 05 mai 2010, Shelli Orton a écrit : Thank you. Is there any documentation (online or paper) that is better than what's in the Maven documentation (http://maven.apache.org/archetype/maven-archetype-plugin/create-from-proj ect-mojo.html and http://maven.apache.org/archetype/maven-archetype-plugin/advanced-usage.ht ml)? Something that includes some explanation as to what is being done/created and why? For someone new to Maven, most of the documentation is very cryptic. Thanks again! -Original Message- From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] Sent: Wednesday, May 05, 2010 3:37 PM To: Maven Users List Subject: Re: Missing archetype.xml in new archetype created from project see http://jira.codehaus.org/browse/ARCHETYPE-292 archetype.xml is old archetype descriptor Regards, Hervé Le mercredi 05 mai 2010, Shelli Orton a écrit : Hi, I am using Maven 2.2.1. and am new to Maven. I am trying to create an archetype based on an existing project. I have been using this blog post as a guide: http://blog.inflinx.com/category/m2eclipse/ Step 7 says The next step is to verify that the generated archetype.xml (located under srcmainresourcesMETA-INFmaven (sic)) has all the files listed and they are located in the right directories. My generated archetype does not have an archetype.xml. It does have an archetype-metadata.xml file though. There aren't any errors in the output from calling archetype:create-from-project, just a couple of warnings about using platform encoding (Cp1252). Any thoughts on why this file wasn't generated? Thanks in advance! Shelli - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Freaking out: javac works, maven-compiler-plugin does not
...and it's filed: https://issues.apache.org/jira/browse/OPENJPA-1659 -matthew -- View this message in context: http://maven-users.828.n2.nabble.com/Freaking-out-javac-works-maven-compiler-plugin-does-not-tp5016302p5033026.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: Missing archetype.xml in new archetype created from project
Well, to partially answer one of my questions, it appears I need to fix all my
xml config files where the create archetype process changed all references to
?xml version=1.0 encoding=UTF-8? to ?xml version=${version}
encoding=UTF-8?
:(
-Original Message-
From: Shelli Orton
Sent: Monday, May 10, 2010 3:06 PM
To: Maven Users List
Subject: RE: Missing archetype.xml in new archetype created from project
Thanks for the link. Unfortunately it didn't help with my understanding of how
to create an archetype or the structure of one.
I'm using Maven 2.2.1.
I set up a skeleton project (MyProject) that I want to use to create the
archetype (minimal classes, mainly config files and the pom.xml set up with the
dependencies). Everything in my project is contained in the MyProject/src
directory except for its pom.xml which is under MyProject.
I ran the archetype:create-from-project command for the project. I now have a
new target\generated-sources\archetype directory in my project directory
which has a pom.xml file in it. The pom.xml has an artifactId of
Project-archetype and a a packaging of maven-archetype.
It also has two sub-directories:
MyProject\target\generated-sources\archetype\src
MyProject\target\generated-sources\archetype\target
Both of these subdirectories contains a pom.xml and an archetype-metadata.xml
which are identical.
What exactly is the archetype? Everything under the MyProject\target directory
or one of these directories:
MyProject\target\generated-sources\archetype\
MyProject\target\generated-sources\archetype\src
MyProject\target\generated-sources\archetype\target
Do I need to update any files before installing the archetype? If so which
ones?
Thanks in advance for all help.
Shelli
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Thursday, May 06, 2010 1:54 PM
To: Maven Users List
Subject: Re: Missing archetype.xml in new archetype created from project
perhaps http://maven.apache.org/guides/mini/guide-creating-archetypes.html
will help you
It has been written for 1.x (old) archetype, but principles are the same
Regards,
Hervé
Le mercredi 05 mai 2010, Shelli Orton a écrit :
Thank you.
Is there any documentation (online or paper) that is better than what's in
the Maven documentation
(http://maven.apache.org/archetype/maven-archetype-plugin/create-from-proj
ect-mojo.html and
http://maven.apache.org/archetype/maven-archetype-plugin/advanced-usage.ht
ml)? Something that includes some explanation as to what is being
done/created and why? For someone new to Maven, most of the documentation
is very cryptic.
Thanks again!
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Wednesday, May 05, 2010 3:37 PM
To: Maven Users List
Subject: Re: Missing archetype.xml in new archetype created from project
see http://jira.codehaus.org/browse/ARCHETYPE-292
archetype.xml is old archetype descriptor
Regards,
Hervé
Le mercredi 05 mai 2010, Shelli Orton a écrit :
Hi,
I am using Maven 2.2.1. and am new to Maven. I am trying to create an
archetype based on an existing project. I have been using this blog post
as a guide: http://blog.inflinx.com/category/m2eclipse/
Step 7 says The next step is to verify that the generated archetype.xml
(located under srcmainresourcesMETA-INFmaven (sic)) has all the files
listed and they are located in the right directories.
My generated archetype does not have an archetype.xml. It does have an
archetype-metadata.xml file though. There aren't any errors in the
output from calling archetype:create-from-project, just a couple of
warnings about using platform encoding (Cp1252).
Any thoughts on why this file wasn't generated?
Thanks in advance!
Shelli
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Preserving attributes on resources
I have a sh file in src/main/resources that is 755 but its copied to target/classes with different permissions. I know that assembly plugin can set new fileModes but is there a way to do this using the resource plugin? Thanks :)
Sign existing artifacts in repository
Hi, we have an existing repository which I want to batch sign all the artifacts within. I do have file system access. Is there any tool available that will go though our existing repository and allow me to sign the artifacts (all of which have been created by me in the past)? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sign existing artifacts in repository
You can loop over them using shell and gpg. You can use an agent to store the password so it doesn't need to be typed in every time, or have it read from an argument. On 11/05/2010, at 10:51 AM, Mark Diggory wrote: Hi, we have an existing repository which I want to batch sign all the artifacts within. I do have file system access. Is there any tool available that will go though our existing repository and allow me to sign the artifacts (all of which have been created by me in the past)? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Automate build and test process in maven
We are using Maven as the build automation tool. The build process generates a jar file. The requirement here is to start execution of the java application which will be generated by the build - Wait for a few seconds to let the application start completely and then move onto the test phase, which will perform start a test tool (SoapUI) that will issue soap calls against the java application that was just started. We tried using the exec plugin, to start the java application. However, when we moved onto the test phase, the java application terminated. Also, we couldn't figure out how to introduce a delay before the start of the soapUI tests. What will be the best way to achieve the above? -- View this message in context: http://old.nabble.com/Automate-build-and-test-process-in-maven-tp28519524p28519524.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
Advice: How do you setup your Maven project for Continuous Integration?
I'm struggling to work out the best way to get my maven projects and continuous integration to play nicely together. Here's some background: Our build takes approximately 8 minutes to complete. To help keep the build time down the developers build doesn't do things like: * create source jars * create javadoc jars * run the integration test suite These extra tasks are all done when we release our software, or the integration tests suite can also be invoked via profiles. What I'd like to do is make sure that our continuous integration environment does these extra tasks. Ideally I'd like to define this once in our corporate parent pom and have it inherited. But profiles don't work this way (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) It looks like the best I can do is to have a per-project profile (which I duplicate across all projects) at the root pom of the project to enable these extra tasks. I've also looked at the way maven development process enforces some common tasks during the release process. e.g. in org.apache:apache:7 pom uses plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration useReleaseProfilefalse/useReleaseProfile goalsdeploy/goals arguments-Papache-release/arguments /configuration /plugin and further down defines the profile profile idapache-release/id I have no idea how this actually manages to get that profile to run since help:effective-pom doesn't list it as a valid profile. So my question is how are you doing continuous integration? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automate build and test process in maven
Have you considered running your application test as a unit test? Then you can use the existing maven test infrastructure, conventions, and tools. If your application is managed using a dependency-injection-based framework such as spring, and your test tool can be used programmatically, you can run your entire test using mock objects to mediate access. Nothing hits the network. See for example GeoServerTestSupport: https://svn.codehaus.org/geoserver/trunk/src/main/src/test/java/org/geoserver/test/GeoServerTestSupport.java https://svn.codehaus.org/geoserver/trunk/src/main/src/test/java/org/geoserver/test/GeoServerAbstractTestSupport.java This example uses JUnit 3, but one-time fixture setup is even easier in JUnit 4 using @BeforeClass. Every instance is a complete, running GeoServer, except for listening on the network. All tests are mock requests. A big advantage of using mock objects to avoid network connections is that your tests will not mysteriously fail when something else is using your server network ports. Kind regards, Ben. On 11/05/10 11:16, AnshuGupta wrote: We are using Maven as the build automation tool. The build process generates a jar file. The requirement here is to start execution of the java application which will be generated by the build - Wait for a few seconds to let the application start completely and then move onto the test phase, which will perform start a test tool (SoapUI) that will issue soap calls against the java application that was just started. We tried using the exec plugin, to start the java application. However, when we moved onto the test phase, the java application terminated. Also, we couldn't figure out how to introduce a delay before the start of the soapUI tests. What will be the best way to achieve the above? -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
