Re: I want the pom.xml to disable junit test.
Thx! 2008/9/22 Wendy Smoak [EMAIL PROTECTED] On Sun, Sep 21, 2008 at 7:06 PM, 陈思淼 [EMAIL PROTECTED] wrote: I know i can use mvn intall -DskipTests to disable unit test when install. but how to configure it in the pom to disable it ? Thankx for help. http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html -- Wendy
pom depend on other pom
Hi All, 1)Can any one help how to run pom.xml of another project b4 running the current project pom.xml i.e my pom is dependent on other pom like in ant one target is dependent on other target. I need to run independent pom then after the dependent pom with single instruction . 2)One more thing how to create dependency of the other project in my pom . Like one proj is dbmanager and the other is controller proj. so in controller proj. pom.xml i have to write the dependency of dbmanager -- View this message in context: http://www.nabble.com/pom-depend-on-other-pom-tp19602786p19602786.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: Tuning multi-module assembly
Thanks Samuel, 1) How to prevent WAR plugin from putting each war's dependent JARs into the myappX.war:WEB-INF/lib ? 1 - Use the provided scope for all your war dependencies, see http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency and http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope 1) I already tried using provided has the dependency scope, but some dependencies require their transitives on the compile classpath, so that compile scope is required... 3) How to limit execution of assembly plugin to my_project ? i.e. prevent its execution for each individual module 3 - You can use the inherited flag on your assembly execution, see http://maven.apache.org/ref/current/maven-model/maven.html#class_execution 3) I tried to set the inherited element to 'false', but it seems assembly for modules still occurs... any idea why this is the case? Thanks *Olivier Gies* *Delivery Manager Customs Tax Software Engineering Center Bull, Architect of an Open World ^TM Phone: +86 (10) 65978001 - Ext 555 * *www.bull.com http://www.bull.com/* *This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuning multi-module assembly
3) I tried to set the inherited element to 'false', but it seems assembly for modules still occurs... any idea why this is the case? Never mind that, I actually set the inherited element at the plugin level, and now the assembly won't occur for modules, as desired... BR, Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using POM properties in XDoc
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in XDoc
You might have to hack filtering with the resource plugin
On 22 September 2008 09:22, Simone Tripodi [EMAIL PROTECTED] wrote:
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuning multi-module assembly
I actually solved my 3 questions, so I will give my solutions hereunder if anyone is also interested: 1) See this page from maven-war-plugin: http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html If config element packagingExcludes doesn't work, just use warSourceExcludes as indicated for deprecated version 2) Use moduleSets with following basic config: ... moduleSet includes includemypack:myapp1/include /includes binaries includeDependenciestrue/includeDependencies unpackfalse/unpack useDefaultExcludestrue/useDefaultExcludes outputDirectorylib/outputDirectory /binaries /moduleSet ... 3) Set inherited element to 'false' under assembly plugin element Regards, *Olivier Gies* *Delivery Manager Customs Tax Software Engineering Center Bull, Architect of an Open World ^TM Phone: +86 (10) 65978001 - Ext 555 * *www.bull.com http://www.bull.com/* *This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems using XSD
Hi All, I have few clarifications using XSD's from multiple Projects using Maven and then generating Java Objects using XMLBeans Plugin. Any help/guidance is appreciated: I have 2 Projects now. *Project 1*: Called as XSD-PROJECT which just holds all the xsd's. This Project builds a jar file which contains all the xsd's. *Project 2: *This Project is a web Project, in which, we have WSDL 1 more XSD under WEB-INF. Our requirement is to use *Project 1* as dependency for *Project 2 *and generate the Java Objects using XMLBeans plugin for the Project 2. The generated classes should include all the Java Object for all the XSD's from both the locations. We are using XMLBeans 2.3.0 Maven 2.0.9. -- Thanks, Ram
release pluging not workin?
hum, I need some help here please. The Maven Release plugin is somehow not working as expected. To put the problem simply: mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building commons-xml [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'com.company:company-parent' set to release? (yes/no) yes: : What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1.1-SNAPSHOT What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 2-SNAPSHOT What is the release version for commons-xml? (com.company.commons:commons-xml) 1.0: : In short, it would in this case never accept any values different than the default one. cheers nodje wrote: I'm a newbie with the release plugin and have a hard time already managing dependencies. After much thinking, I end up with this process: - branch first the current trunk version to a branch named 1.0-SNAPSHOT. The trunk version becomes 1.1-SNAPSHOT - release the branch version: the release is the 1.0 version, the branch becomes 1.0.1-SNAPSHOT I need the branch step first in order to be able to fix bug that could appear on the 1.0 version. A tag not being modifiable, I need to be able to rerelease from the 1.0-SNAPSHOT line. And so came the idea of the 1.0.1-SNAPSHOT version. If anyone has another solution for this problem, he is much welcome! Anyways, while trying this I'm confronted to a Maven release-plugin problem: I'm trying to release a component that depends only on the company-parent.pom (that follows the 1-SNAPSHOT - 2-SNAPSHOT release numbering pattern) I want the development version to be updated to depend on the released version 1 or 1.1-SNAPSHOT of the company-parent pom. here's the trace of the command: mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building commons-xml [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'com.company:company-parent' set to release? (yes/no) yes: : What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the
Antwort: Re: Attaching source zip to jar managed by maven
Hi, sorry for being a little unprecise. It is not that I don't want to have the sources locally, but don't want to manage the attaching on every developer machine as you have guessed. Therefore I tried the m2eclipse feature Download Artifact Sources and give it a try with dbunit-2.2.3 from repo1.maven.org which has Javadoc and sources attached. Unfortunately that doesn't work. Neither are the sources downloaded nor attached to the local jar. Do you have any idea what might be the problem? The other thing is: most of the jars we use do not have sources in the public repositories. Could you give me a short introduction on how to add these sources manually to our enterprise repository and attach to their jars? Thanks in advance, Ole Von: Baptiste MATHUS [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Datum: 18.09.2008 15:40 Betreff: Re: Attaching source zip to jar managed by maven Hi Ole, Well, the questions you ask seems quite antithetic to me. I mean, if you want maven to manage sources, then those sources will be present locally, after having been downloaded. Now, the thing is: if what you want is just no to have to do it manually on each developer machine, then yes, it's possible. The simplest way seems to select the Download Artifact Sources checkbox, in Window/Preferences/Maven. This way, if the jars you're using also provide their sources (for artifact-version.jar, it must be named artifact-version-sources.jar). Then m2e (this is not a core maven feature) will download and link those sources with the corresponding jars. Outside Eclipse, using the CLI, you can also do mvn dependency:sources in your project root. That will try and download all artifact sources (transitively, sure). Then it will display a summary of which sources could not be found. This is what we sometimes use to find projects that miss sources jars to manually deploy those sources in our corporate maven repo. HTH Cheers. PS : if you have very M2E specific questions, then you might prefer using the M2E users mailing list instead (see http://m2eclipse.codehaus.org/mail-lists.html). 2008/9/17 Ole Laurisch [EMAIL PROTECTED] Hello all, I'm using Maven 2 and the m2eclipse Maven integration for Eclipse. How can I attach a source zip to a jar (let's say jface.jar) without having to have this source zip locally stored on every developers machine? Is there a way to let the source zips be managed by Maven too? Thanks in advance, Ole -- engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack
Re: Version ranges, but excluding snapshots in local repo
You may be interested in these related issues: http://jira.codehaus.org/browse/MNG-3092 http://jira.codehaus.org/browse/MNG-2994 Cheers, Mark 2008/9/16 Borut Bolčina [EMAIL PROTECTED]: Hi list, using ranges for artifact resolution we achieved the goal of always resolving the latest version of modules. We decided to use ranges because the modules are released on a daily/week interval and nobody wants to raise versions in a great number of poms which are using them. We have two profiles - one picking dependencies only from release repos and one picking from snapshots repos also, so if one needs snapshot versions of jars, it builds with a profile which includes snapshots repos (virtual repo in Artifactory). But there is a catch. If for example there are these versions deployed to the Artifactory: myJar-1.0.0.jar myJar-1.0.0-SNAPSHOT.jar myJar-1.1.0-SNAPSHOT.jar and all of these are also in user's local repo, then when trying to do a release:prepare with the default profile which does not include snapshots repos, the release fails because the latest version is of course myJar-1.1.0-SNAPSHOT.jar. The workaround is manually deleting the myJar-1.1.0-SNAPSHOT.jar from the local repo and re-run the release:prepare which of course correctly takes myJar-1.0.0.jar. Is there an option or a way to tell maven to ignore local versions? Regards, Borut
Re: Using POM properties in XDoc
I'll try it, thank you very much :)
2008/9/22 Stephen Connolly [EMAIL PROTECTED]:
You might have to hack filtering with the resource plugin
On 22 September 2008 09:22, Simone Tripodi [EMAIL PROTECTED] wrote:
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
My LinkedIn profile: http://www.linkedin.com/in/simonetripodi
My GoogleCode profile: http://code.google.com/u/simone.tripodi/
My Picasa: http://picasaweb.google.com/simone.tripodi/
My Tube: http://www.youtube.com/user/stripodi
My Del.icio.us: http://del.icio.us/simone.tripodi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[docck-plugin]
Hi all Are there plans to release a new beta of the docck plugin? It looks like the released beta-2 is failing when using JDK1.5 specific stuff (e.g. type safety in HashMaps) within the custom plugin whereas a locally snapshot build of the docck plugin works well. Thanks and regards Felix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Attaching source zip to jar managed by maven
Hi Ole, It's hard to say without seing the logs. What's the output of mvn dependency:sources? Also have a look in the m2e console (inside Eclipse), activating debug output. Cheers. 2008/9/22 Ole Laurisch [EMAIL PROTECTED] Hi, sorry for being a little unprecise. It is not that I don't want to have the sources locally, but don't want to manage the attaching on every developer machine as you have guessed. Therefore I tried the m2eclipse feature Download Artifact Sources and give it a try with dbunit-2.2.3 from repo1.maven.org which has Javadoc and sources attached. Unfortunately that doesn't work. Neither are the sources downloaded nor attached to the local jar. Do you have any idea what might be the problem? The other thing is: most of the jars we use do not have sources in the public repositories. Could you give me a short introduction on how to add these sources manually to our enterprise repository and attach to their jars? Thanks in advance, Ole Von: Baptiste MATHUS [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Datum: 18.09.2008 15:40 Betreff: Re: Attaching source zip to jar managed by maven Hi Ole, Well, the questions you ask seems quite antithetic to me. I mean, if you want maven to manage sources, then those sources will be present locally, after having been downloaded. Now, the thing is: if what you want is just no to have to do it manually on each developer machine, then yes, it's possible. The simplest way seems to select the Download Artifact Sources checkbox, in Window/Preferences/Maven. This way, if the jars you're using also provide their sources (for artifact-version.jar, it must be named artifact-version-sources.jar). Then m2e (this is not a core maven feature) will download and link those sources with the corresponding jars. Outside Eclipse, using the CLI, you can also do mvn dependency:sources in your project root. That will try and download all artifact sources (transitively, sure). Then it will display a summary of which sources could not be found. This is what we sometimes use to find projects that miss sources jars to manually deploy those sources in our corporate maven repo. HTH Cheers. PS : if you have very M2E specific questions, then you might prefer using the M2E users mailing list instead (see http://m2eclipse.codehaus.org/mail-lists.html). 2008/9/17 Ole Laurisch [EMAIL PROTECTED] Hello all, I'm using Maven 2 and the m2eclipse Maven integration for Eclipse. How can I attach a source zip to a jar (let's say jface.jar) without having to have this source zip locally stored on every developers machine? Is there a way to let the source zips be managed by Maven too? Thanks in advance, Ole -- engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Nar Plugin Linking Problems (compile 32bit code on 64bit machine)
We are migrating our builds from maven1 to maven2 and therefore migrating to
the 2.0 nar plugin. One issue we are running into is that the build is on a
64bit machine but we need to build using -m32. With the m1 plugin this works
fine by specifying the following properties
i386.Linux.gcc.freehep.nar.linker.arg.mid=-m32
We've tried to do a similar thing w/ the m2 plugin by adding in linker
options of
linker
nameg++/name
options
option-m32/option
/options
/linker
this passes the correct -m32 flag to ld but then fails on the ar step with
the following error
[INFO] Linking...
[ERROR] /usr/bin/ar: illegal option -- 3
[ERROR] Usage: /usr/bin/ar [emulation options] [-]{dmpqrstx}[abcfilNoPsSuvV]
[member-name] [count] archive-file file...
[ERROR] /usr/bin/ar -M [mri-script]
[ERROR] commands:
[ERROR] d - delete file(s) from the archive
[ERROR] m[ab] - move file(s) in the archive
[ERROR] p - print file(s) found in the archive
[ERROR] q[f] - quick append file(s) to the archive
[ERROR] r[ab][f][u] - replace existing or insert new file(s) into the
archive
[ERROR] t - display contents of archive
[ERROR] x[o] - extract file(s) from the archive
[ERROR] command specific modifiers:
[ERROR] [a] - put file(s) after [member-name]
[ERROR] [b] - put file(s) before [member-name] (same as [i])
[ERROR] [N] - use instance [count] of name
[ERROR] [f] - truncate inserted file names
[ERROR] [P] - use full path names when matching
[ERROR] [o] - preserve original dates
[ERROR] [u] - only replace files that are newer than current archive
contents
[ERROR] generic modifiers:
[ERROR] [c] - do not warn if the library had to be created
[ERROR] [s] - create an archive index (cf. ranlib)
[ERROR] [S] - do not build a symbol table
[ERROR] [v] - be verbose
[ERROR] [V] - display the version number
[ERROR] @file - read options from file
[ERROR] emulation options:
[ERROR] No emulation specific options
[ERROR] /usr/bin/ar: supported targets: elf64-x86-64 elf32-i386
a.out-i386-linux efi-app-ia32 elf64-little elf64-big elf32-little elf32-big
srec symbolsrec tekhex binary ihex
It looks like the -m32 option is being passed to ld (which is good) then to
ar (which can not use it).
Anyone have a suggestion on what the correct configuration is w/ the m2
plugin?
Thanks,
Mark
--
View this message in context:
http://n2.nabble.com/Nar-Plugin-Linking-Problems-%28compile-32bit-code-on-64bit-machine%29-tp1109381p1109381.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]
Creating first Maven Project-Problem
Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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: Creating first Maven Project-Problem
Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene
javadoc-plugin / site generation
Hi all In the new version of the javadoc plugin 2.5 aggregatetrue/.. is deprecated. Using the new proposed configuration in the poms reporting section and running mvn site I don't get the javadoc report anymore (wether in the generated site navigation nor as target/site/apidocs directory). What am I missing? Deprectated, working reporting section: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin Nonworking adapted section: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version reportSets reportSet idhtml/id reports reportaggregate/report /reports /reportSet /reportSets /plugin Thanks and regards Felix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating first Maven Project-Problem
Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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: Creating first Maven Project-Problem
see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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] -- Mylene
Re: Creating first Maven Project-Problem
Thanks for the reply. I didnt hve a settings.xml in .m2 directory so i copied the settings.xml from apache-maven-2.0.9\conf and pasted it into .m2 directory and changed the proxy settings a little according the link which u gave to me. So the proxy part in settings.xml looks like this. I tried to create the first project again but still doesnt work. Would apprecaite for ur help. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol hosthttp-proxy.zx.basf-ag.de/host port8080/port /proxy -- /proxies mylene wrote: see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19608218.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]
Excluding empty directories from assembly
Hi, I'm using the maven assembly plugin to create an assembly of a source tree. My source tree sometimes contains empty directories (they have to be there, don't ask!). Is there a way I can get the assembly plugin to remove all empty directories from the assembly? Here's my descriptor: assembly idjrules-project-assembly/id formats formatzip/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directory / useDefaultExcludestrue/useDefaultExcludes includes include*.xml/include include*.sql/include include*.js/include include**/bom/**/include include**/queries/**/include include**/rules/**/include include**/templates/**/include include**/.ruleproject/include include**/.project/include includejrules-support/**/include /includes excludes exclude**/output/**/exclude exclude**/target/**/exclude exclude**/.rtserver/**/exclude exclude**/.settings/**/exclude /excludes /fileSet /assembly
RE: Re: [m2] archetype repository requires authentication
Last I looked at the sources, the Archetype plugin didn't support repositories that required authentication. The workaround I put in place was to basically copy org.apache.maven.archetypee.mojos.MavenArchetypeMojo and hard-code our internal repository and repository ID into it. I'd be interested if there was a better solution. Justin -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu Sent: Sunday, September 21, 2008 3:37 AM To: users@maven.apache.org Subject: Re: [m2] archetype repository requires authentication Hi Dave, and thanks for the fast reply. I already have a settings.xml and the build works by retrieving artifacts from the repositories defined in it. However, the archetypes are not searched in those repositories only in the central Maven repository :( I don't know why it does not use the settings.xml file to query for additional repositories... Adrian. Dave Newton wrote: --- On Sat, 9/20/08, Adrian Herscu wrote: I have written an archetype and deployed to my remote repository. The repository requires authentication. The problem is when somebody runs mvn archetype:generate ... -DarchetypeRepository=http://my.repo he gets a 401 from the server and generation fails of course. Is there any possibility to supply credentials? This might help, although I haven't tried it :/ http://maven.apache.org/guides/mini/guide-configuring-maven.html See the Security and Deployment Settings section; it sounds like the server element may do what you want. HTH, Dave - 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/Eclipse - Keeping them in sync?
Ok David. Is there any reason why you are not using the maven standard layout for your project? You just put all of your test code into the /src/test/java/ and maven adds it to the eclipse path... On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks [EMAIL PROTECTED] wrote: Thanks again. I'll check out the build-helper plugin. As for larger projects, that's exactly how I've done them in the past. It requires a little massaging of the pom.xml files, but I haven't found a cleaner way to handle it. Maybe one day between Eclipse and Maven this won't be such a mind twister. The primary reason I'm adding extra source folders is for test code. I really don't want to mix functional tests with my unit tests. It made sense, to me, to put them in a different tree, but it didn't seem like a good fit for a sub-module. Thanks for all the suggestions! Dave Stefan Hübner wrote: David, 2008/9/19 David C. Hicks [EMAIL PROTECTED]: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? You need to add additional source folders by using the build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the maven-eclipse-plugin happily add all your source folders to eclipse's project configuration. Also another hint on handling larger project setup with many submodules and maybe independent project side by side. In my last project to keep all my projects and submodules (40+) synced with eclipse I put all projects and multiprojects in the same subversion trunk and thus the same working folder in parallel subfolders. in the working folder's root I established a bootstapper-pom which included all projects as submodules. the project's parent pom resided in a parallel subfolder next to the projects as well. Also this parent-pom was included as a submodule by the bootstrapper-pom. With this setup we were able to invoke any maven commands on all projects at once. -Stefan - 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] -- (o_ \* / / ) | / \ / | O | v v
Re: Maven/Eclipse - Keeping them in sync?
Yes. I don't want functional test code mixed with unit test code. Thor wrote: Ok David. Is there any reason why you are not using the maven standard layout for your project? You just put all of your test code into the /src/test/java/ and maven adds it to the eclipse path... On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks [EMAIL PROTECTED] wrote: Thanks again. I'll check out the build-helper plugin. As for larger projects, that's exactly how I've done them in the past. It requires a little massaging of the pom.xml files, but I haven't found a cleaner way to handle it. Maybe one day between Eclipse and Maven this won't be such a mind twister. The primary reason I'm adding extra source folders is for test code. I really don't want to mix functional tests with my unit tests. It made sense, to me, to put them in a different tree, but it didn't seem like a good fit for a sub-module. Thanks for all the suggestions! Dave Stefan Hübner wrote: David, 2008/9/19 David C. Hicks [EMAIL PROTECTED]: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? You need to add additional source folders by using the build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the maven-eclipse-plugin happily add all your source folders to eclipse's project configuration. Also another hint on handling larger project setup with many submodules and maybe independent project side by side. In my last project to keep all my projects and submodules (40+) synced with eclipse I put all projects and multiprojects in the same subversion trunk and thus the same working folder in parallel subfolders. in the working folder's root I established a bootstapper-pom which included all projects as submodules. the project's parent pom resided in a parallel subfolder next to the projects as well. Also this parent-pom was included as a submodule by the bootstrapper-pom. With this setup we were able to invoke any maven commands on all projects at once. -Stefan - 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: Maven/Eclipse - Keeping them in sync?
Ok. Got it. the last mail was out of context... My regards... On Mon, Sep 22, 2008 at 9:05 AM, David C. Hicks [EMAIL PROTECTED] wrote: Yes. I don't want functional test code mixed with unit test code. Thor wrote: Ok David. Is there any reason why you are not using the maven standard layout for your project? You just put all of your test code into the /src/test/java/ and maven adds it to the eclipse path... On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks [EMAIL PROTECTED] wrote: Thanks again. I'll check out the build-helper plugin. As for larger projects, that's exactly how I've done them in the past. It requires a little massaging of the pom.xml files, but I haven't found a cleaner way to handle it. Maybe one day between Eclipse and Maven this won't be such a mind twister. The primary reason I'm adding extra source folders is for test code. I really don't want to mix functional tests with my unit tests. It made sense, to me, to put them in a different tree, but it didn't seem like a good fit for a sub-module. Thanks for all the suggestions! Dave Stefan Hübner wrote: David, 2008/9/19 David C. Hicks [EMAIL PROTECTED]: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? You need to add additional source folders by using the build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the maven-eclipse-plugin happily add all your source folders to eclipse's project configuration. Also another hint on handling larger project setup with many submodules and maybe independent project side by side. In my last project to keep all my projects and submodules (40+) synced with eclipse I put all projects and multiprojects in the same subversion trunk and thus the same working folder in parallel subfolders. in the working folder's root I established a bootstapper-pom which included all projects as submodules. the project's parent pom resided in a parallel subfolder next to the projects as well. Also this parent-pom was included as a submodule by the bootstrapper-pom. With this setup we were able to invoke any maven commands on all projects at once. -Stefan - 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] -- (o_ \* / / ) | / \ / | O | v v
Re: Maven/Eclipse - Keeping them in sync?
No sweat. The build-helper plugin solved my problem for me. I appreciate the input! Thor wrote: Ok. Got it. the last mail was out of context... My regards... On Mon, Sep 22, 2008 at 9:05 AM, David C. Hicks [EMAIL PROTECTED] wrote: Yes. I don't want functional test code mixed with unit test code. Thor wrote: Ok David. Is there any reason why you are not using the maven standard layout for your project? You just put all of your test code into the /src/test/java/ and maven adds it to the eclipse path... On Sat, Sep 20, 2008 at 8:48 AM, David C. Hicks [EMAIL PROTECTED] wrote: Thanks again. I'll check out the build-helper plugin. As for larger projects, that's exactly how I've done them in the past. It requires a little massaging of the pom.xml files, but I haven't found a cleaner way to handle it. Maybe one day between Eclipse and Maven this won't be such a mind twister. The primary reason I'm adding extra source folders is for test code. I really don't want to mix functional tests with my unit tests. It made sense, to me, to put them in a different tree, but it didn't seem like a good fit for a sub-module. Thanks for all the suggestions! Dave Stefan Hübner wrote: David, 2008/9/19 David C. Hicks [EMAIL PROTECTED]: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? You need to add additional source folders by using the build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/). Then the maven-eclipse-plugin happily add all your source folders to eclipse's project configuration. Also another hint on handling larger project setup with many submodules and maybe independent project side by side. In my last project to keep all my projects and submodules (40+) synced with eclipse I put all projects and multiprojects in the same subversion trunk and thus the same working folder in parallel subfolders. in the working folder's root I established a bootstapper-pom which included all projects as submodules. the project's parent pom resided in a parallel subfolder next to the projects as well. Also this parent-pom was included as a submodule by the bootstrapper-pom. With this setup we were able to invoke any maven commands on all projects at once. -Stefan - 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]
eclipse plugin, resolve dependencies to the projects in the workspace
Hello, everybody! I have the project A, which depends on the project B, both of the projects are located in the same workspace. When generating the eclipse project files for the project A, the project B reference is being taken from the repository as a JAR file. What I want is to include the project B as a project reference for the project A, so when the project A is opened in the Eclipse, the project B is opened as well as a dependency, and all changes in the project B are reflected in the project A (for example, if some interface contract was changed in the project B, the corresponding files in the project A will contain errors, or changes in the project A with refactoring will be merged to the project B as well). I found there is the property workspace described in http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#workspace, however neither using it as mvn eclipse:eclipse -Dworkspace=/home/user/workspace, nor specifying it in the plugin configuration did not give the desired results, and the project B is still referenced as a JAR file in the local repository. Do I miss something? Thank you! -- Eugene N Dzhurinsky pgpLyUy83eLnw.pgp Description: PGP signature
Re: Creating first Maven Project-Problem
You need to remove the comment start and end markers !-- and -- If you look carefully you'll see you have your lovely proxies definintion ignored inside a comment 2008/9/22 ashleyvijay [EMAIL PROTECTED] Thanks for the reply. I didnt hve a settings.xml in .m2 directory so i copied the settings.xml from apache-maven-2.0.9\conf and pasted it into .m2 directory and changed the proxy settings a little according the link which u gave to me. So the proxy part in settings.xml looks like this. I tried to create the first project again but still doesnt work. Would apprecaite for ur help. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol hosthttp-proxy.zx.basf-ag.de/host port8080/port /proxy -- /proxies mylene wrote: see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19608218.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: pom depend on other pom
In Maven, all projects are effectively independent. So you cannot run the pom.xml of another project before this one like you can set depends in your Ant targets. You can inherit the goals from another pom (assuming this is a child of that parent pom), however. You can establish a dependency on a pom by using typepom/type in the dependency declaration. Wayne On Sun, Sep 21, 2008 at 11:58 PM, sandyg [EMAIL PROTECTED] wrote: Hi All, 1)Can any one help how to run pom.xml of another project b4 running the current project pom.xml i.e my pom is dependent on other pom like in ant one target is dependent on other target. I need to run independent pom then after the dependent pom with single instruction . 2)One more thing how to create dependency of the other project in my pom . Like one proj is dbmanager and the other is controller proj. so in controller proj. pom.xml i have to write the dependency of dbmanager -- View this message in context: http://www.nabble.com/pom-depend-on-other-pom-tp19602786p19602786.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Directory deploy for ear project
We directory deploy our ear project during development. We've noticed that the most time spent in the build of our ear is while it is Building jar: Since we aren't using the .ear file during development it'd be nice if we could configure maven to stop short of actually building the jar file. Thanks for any help, Kem Elbrader ElementLine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems using XSD
What exactly is your question? I read the email twice, and there's no question in it. If the XMLBeans plugin supports reading XSD files from a Jar and generating the source, this should be pretty simple with a little configuration. If it does not, you will probably need to use the dependency plugin to unpack the XSD jar into Project 2's target folder so the XMLBeans plugin has XSD files to work on so it can generate the source properly. Or you could modify the XMLBeans plugin source code so it supports reading from Jars. Wayne On Mon, Sep 22, 2008 at 1:49 AM, RAM [EMAIL PROTECTED] wrote: Hi All, I have few clarifications using XSD's from multiple Projects using Maven and then generating Java Objects using XMLBeans Plugin. Any help/guidance is appreciated: I have 2 Projects now. *Project 1*: Called as XSD-PROJECT which just holds all the xsd's. This Project builds a jar file which contains all the xsd's. *Project 2: *This Project is a web Project, in which, we have WSDL 1 more XSD under WEB-INF. Our requirement is to use *Project 1* as dependency for *Project 2 *and generate the Java Objects using XMLBeans plugin for the Project 2. The generated classes should include all the Java Object for all the XSD's from both the locations. We are using XMLBeans 2.3.0 Maven 2.0.9. -- Thanks, Ram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using POM properties in XDoc
There is built in filtering in the site-plugin starting with version
2.0-beta-6. See the Filtering section at
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
I haven't tried it for xdoc files myself.
Simone Tripodi wrote:
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [docck-plugin]
Yes, its on my to-do list. Wanted to wait for a new parent release first. Felix Knecht wrote: Hi all Are there plans to release a new beta of the docck plugin? It looks like the released beta-2 is failing when using JDK1.5 specific stuff (e.g. type safety in HashMaps) within the custom plugin whereas a locally snapshot build of the docck plugin works well. Thanks and regards Felix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jetty and using src/test/webapp
I have a war project that was built that also has a src/test/webapp
directory. The idea was that test pages could be made in this
directory that would not be included in the normal war.
I have got it mostly working except for the classes. I need to have
both target/classes and target/test-classes on the classpath. Here is
what I have been attempting to use:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.12.rc2/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webXml${basedir}/src/test/webapp/WEB-INF/web.xml/webXml
webAppSourceDirectory${basedir}/src/test/webapp/webAppSourceDirectory
webAppConfig
contextPath/demo-test/contextPath
baseResource
implementation=org.mortbay.resource.ResourceCollection
resourcesAsCSV
src/test/webapp,src/main/webapp
/resourcesAsCSV
/baseResource
/webAppConfig
/configuration
Looking here:
http://docs.codehaus.org/display/JETTY/Which+files+are+scanned+by+the+Jetty+Maven+Plugin
It says that scanTargets are picked up, but that did not work.
I set classesDirectory to ${basedir}/target/test-classes, but then
the ${basedir}/target/classes were no longer on the classpath.
How can I get jetty to run off of the src/test/webapp and include both
${basedir}/target/test-classes and ${basedir}/target/classes?
Thanks,
Andrew
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting multi-POM project to be understood by IDE's properly?
CS Wong wrote: I have a multi-project POM that works fine for compilation and work as a whole but is very difficult to work with in IDEs and when it comes to compiling sub components separately. ... Furthermore, when loading the project in ...Eclipse (using ... m2eclipse ...), it's also unable to get the relevant dependencies from the EJBs module since it insists on locating the JAR file instead of treating it as a code project dependency. It would be good to see more details about issues you have with m2eclipse. Can you please submit a bug report and provide simple test projects that would allow us to reproduce this issue. Generally m2eclipse resolves projects from the Eclipse Workspace by default and I really wonder what is happening with your projects. Thanks Eugene -- View this message in context: http://www.nabble.com/Getting-multi-POM-project-to-be-understood-by-IDE%27s-properly--tp19592845p19613810.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: Using POM properties in XDoc
Hi Dennis,
Thank you for your suggestion,I read the page you linked many times
but I've always missed the right section!
Thank you again,best regards
Simone
Sent from my iPhone
On Sep 22, 2008, at 7:57 PM, Dennis Lundberg [EMAIL PROTECTED] wrote:
There is built in filtering in the site-plugin starting with version
2.0-beta-6. See the Filtering section at
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
I haven't tried it for xdoc files myself.
Simone Tripodi wrote:
Hi everybody,
using the site plugin, I would like to know if is allowed using pom's
properties in xdoc documents - I tried with ${pom.version},
unfortunatly without any good result, the text won't change.
Do you have any suggestion? Thanks in advance!
Best regards,
Simone
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
Configuring Javadoc and JXR to work together
Hi Folks. I have been trying to get this to work for the last few days and I cannot figure out what configuration will work. I am using Maven 2.0.9 with the following plugins: jxr 2.1 javadoc (default) Here is my major problem: When I generate the site using site:stage, all of the tools seem to run fine and produce a nice reports. The javadoc connection on the jxr report is showing the following url: /V:/common-2.0.0-SNAPSHOT/miscellaneous/common-types/target/site/apidocs/ca/medavie/lang/CallerInfo.html while the javadoc file is located at the following url: /V:/common-2.0.0-SNAPSHOT/target/staging/common/miscellaneous/common-util/xref/ca/medavie/lang/CallerInfo.html Here is the reporting section of my pom file: reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId configuration !--aggregatetrue/aggregate -- /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId version2.1/version configuration !-- aggregatetrue/aggregate -- linkJavadoctrue/linkJavadoc /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version configuration targetJdk1.5/targetJdk rulesets rulesetmedavie_pmd_ruleset.xml/ruleset /rulesets formatxml/format linkXreftrue/linkXref sourceEncodingutf-8/sourceEncoding minimumTokens100/minimumTokens /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration configLocationmedavie_checkstyle_checks.xml/configLocation /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdtaglist-maven-plugin/artifactId configuration tags tagTODO/tag tag@todo/tag tagFIXME/tag tagXXX/tag tagNOPMD/tag tag@SuppressWarnings/tag /tags /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version1.2/version configuration effortMax/effort thresholdLow/threshold xmlOutputtrue/xmlOutput /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.2/version /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjdepend-maven-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0.0-beta-1/version /plugin /plugins /reporting As you can see from the pom file, I have also tried using aggregation (it is currently commented out). When aggregation is used, none of the other (pmd, checkstyle and findbugs) reports can connect to the jxr report and the jxr report cannot connect to the javadoc. Any and all help would be greatly appreciated. Dale Chapman, Corporate Architect, Common Services Medavie 506-867-4430 [EMAIL PROTECTED] Debugging is at least twice as hard as programming. If your code is as clever as you can possibly make it, then by definition, you are not smart enough to debug it. - Brian Kernighan --- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l’entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous puissions effectuer la correction à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu de la transmission originale ainsi que toute réponse ultérieure. Merci.
List modules and versions
Is there an easy way to list all modules in a multi-module project and the current version that they are at, possibly their latest release version as well, since that's what I'm ultimately after anyway? -- View this message in context: http://www.nabble.com/List-modules-and-versions-tp19614503p19614503.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]
Help Maven Release to SVN ERROR
Hello, Here is the svn http://dev.ave7.net/svn/java/common/trunk My Issue is when command mvn releaser:prepare There always an error like: [INFO] Executing: svn --username ryan --password * --non-interactive commit --file C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-303817466.commit --targets C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-25566-targets [INFO] Working directory: F:\dev\ave7devws\common [INFO] Tagging release with the label common-parent-1.0... [INFO] Executing: svn --username ryan --password * --non-interactive copy --file C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-801681616.commit . http://dev.ave7.net/svn/java/common/tags/common-parent-1.0 [INFO] Working directory: F:\dev\ave7devws\common [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:144) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] [INFO] Total time: 1 minute 29 seconds [INFO] Finished at: Tue Sep 23 03:28:27 CST 2008 [INFO] Final Memory: 7M/15M [INFO] - Blog: http://www.ryanwong.name Can Use: English, Chinese -- View this message in context: http://www.nabble.com/Help-Maven-Release-to-SVN-ERROR-tp19614856p19614856.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: javadoc-plugin / site generation
Replying to myself: It's a problem when NOT using the deprecated configuration (aggregate). It already exists an issue [1] which I updated with some more info. [1] http://jira.codehaus.org/browse/MJAVADOC-181 I think a crosspost on the dev list is not needed. Felix Knecht schrieb: Hi all In the new version of the javadoc plugin 2.5 aggregatetrue/.. is deprecated. Using the new proposed configuration in the poms reporting section and running mvn site I don't get the javadoc report anymore (wether in the generated site navigation nor as target/site/apidocs directory). What am I missing? Deprectated, working reporting section: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin Nonworking adapted section: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version reportSets reportSet idhtml/id reports reportaggregate/report /reports /reportSet /reportSets /plugin Thanks and regards Felix - 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]
[ANNOUNCE] Continuum 1.2 Released
The Apache Continuum team is pleased to announce Apache Continuum 1.2. The latest release is now available here: http://continuum.apache.org/download.html If you have any questions, please consult: - the web site: http://continuum.apache.org - the continuum-user mailing list: http://continuum.apache.org/mail-lists.html New in Continuum 1.2 * Using Spring Continuum now uses the Spring Framework as it's underlying container instead of Plexus. This results in a boost in performance and stability for the web application in particular. *Repository Purge It's now possible to add purges which will cleanup : - m2 repositories (now it's possible to configure a local m2 repository per project group) - build output directory * Maven plugin groupId and artifactId change Now the maven plugin has the new groupId:artifactId org.apache.continuum:continuum-maven-plugin * New SCMs support Now continuum have two new scm providers : git and accurev. Change Log in Continuum 1.2 === ** Bug * [CONTINUUM-860] - multiple email addresses delimited with commas causes AddressException * [CONTINUUM-1054] - IllegalStateException stack adding pom * [CONTINUUM-1200] - Password Characters Not Supported in SCM Checkout * [CONTINUUM-1322] - Attempt to store value with more than 256 chars * [CONTINUUM-1336] - upgrade quartz - we use a very old version * [CONTINUUM-1360] - Prepended semicolon in svn password does not work * [CONTINUUM-1371] - NullPointer when Releasing with Ant and Default Project Group * [CONTINUUM-1433] - Wrong path in descripton on how to allow the file protocol. * [CONTINUUM-1489] - replace use of MungedHttpsURL with apache httpclient (4.0-beta1) * [CONTINUUM-1515] - SCM Tag does not have a default value * [CONTINUUM-1521] - NullPointerException in StarTeam changelog command * [CONTINUUM-1525] - Can't release project with Continuum on Geronimo 2.0.1 * [CONTINUUM-1528] - Continuum gets slower over time and eventually crashes * [CONTINUUM-1549] - LDAP Authenticated Continuum - NullPointerException when trying to see Members of a project group * [CONTINUUM-1575] - Confusing behavior when continuum can't construct MavenProject from pom * [CONTINUUM-1589] - updateBuildDefinitionForProjectGroup remove the description of the build definition * [CONTINUUM-1590] - updateBuildDefinitionForProjectGroup leads to a StackOverflowError * [CONTINUUM-1593] - Requires Javamail 1.5? Should be 1.4? * [CONTINUUM-1596] - The release perform doesn't work when a scm password is required * [CONTINUUM-1601] - Email address with '+' is not accepted in mail notifier * [CONTINUUM-1610] - Deployment Repository Directory does not work at all * [CONTINUUM-1623] - Checkbox not displaying when validation error in add Instalaction-Tool form * [CONTINUUM-1630] - Error attempting to delete project group * [CONTINUUM-1643] - Perform release page results to a blank page after submitted * [CONTINUUM-1644] - Test failures occur in tagged sources * [CONTINUUM-1646] - Empty recipient is allowed in mail notifier * [CONTINUUM-1647] - Incorrect alt and title text for releaseproject_disabled.gif * [CONTINUUM-1649] - Move Build Definition Template guide to Administrator's Guides * [CONTINUUM-1651] - Unable to delete user-created build definitions * [CONTINUUM-1659] - project admin cannot assign project roles to users * [CONTINUUM-1660] - Download page does not have source archives * [CONTINUUM-1672] - continuum plugin doesn't fails to add maven two projects * [CONTINUUM-1676] - deleting a project or group should cancel any current or scheduled builds, and prevent any from being queued * [CONTINUUM-1679] - Adding Null values for Project's Build Definition directs to a blank page * [CONTINUUM-1688] - Maximum length for name column in object ChangeFile is too small * [CONTINUUM-1693] - Continuum fills our server disk with SNAPSHOTs. * [CONTINUUM-1701] - No field validation when adding Ant and Shell projects * [CONTINUUM-1713] - JDOFatalUserException '.-..column NAME that has maximum length of 255. Please correct your data!' * [CONTINUUM-1715] - no response when adding a project * [CONTINUUM-1725] - Using the Cancel Button without an selected project will produce NPE * [CONTINUUM-1734] - Loop in getProjects methode * [CONTINUUM-1738] - Add schedule page doesn't use its properties file * [CONTINUUM-1739] - Import of Maven2 project fails if 2.0.9 feature depMgm. scopeimport used * [CONTINUUM-1742] - Duplicate installations (environment variables) in Profile are accepted * [CONTINUUM-1746] - Duplicate Profile names are accepted * [CONTINUUM-1748] - Duplicate Installation names are accepted * [CONTINUUM-1750] - unable to operate on a working directory that contains spaces * [CONTINUUM-1752] - Allowed duplication of group name when
Issues with Maven 2.1.0 resume from feature
Hi, I'm really interested in the new make feature which could greatly improve my team productivity. I think it's a great idea! Sadly, I failed to make it work and since I understand it is a M1 version so there's not much documentation yet, here I am. Lets start with my first issue. What is the command line? In attachment, there's a little multiproject project with A (parent), B (child of A), C (child of A), D (child of A but in profile). The compilation order is A, B, C and D (if the java profile is specified). If I want to resume from project B, what should I do? I tried from the root dir: mvn -rf B install But got: [INFO] Invalid task 'f': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal Thanks a lot for any information and tell me if you would like some jira issues to be created (with sample projects) - Henri P.S: Having mvn -help giving the syntax for -rf could be a great first thing to do to document. P.P.S: Should the B be a directory or a project? (maven 2.1.0 doc seems to say it's a directory but the maven-reactor-plugin uses a project) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help Maven Release to SVN ERROR
Read the stacktrace... svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists Delete the tag in your SCM and try the mvn release again. Wayne On Mon, Sep 22, 2008 at 12:29 PM, Ryan Wong [EMAIL PROTECTED] wrote: Hello, Here is the svn http://dev.ave7.net/svn/java/common/trunk My Issue is when command mvn releaser:prepare There always an error like: [INFO] Executing: svn --username ryan --password * --non-interactive commit --file C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-303817466.commit --targets C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-25566-targets [INFO] Working directory: F:\dev\ave7devws\common [INFO] Tagging release with the label common-parent-1.0... [INFO] Executing: svn --username ryan --password * --non-interactive copy --file C:\DOCUME~1\Ryan\LOCALS~1\Temp\maven-scm-801681616.commit . http://dev.ave7.net/svn/java/common/tags/common-parent-1.0 [INFO] Working directory: F:\dev\ave7devws\common [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/java/common/tags/common-parent-1.0/common-support/src/main/java/org/ave7/common/service/AbstractService.java' already exists at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:144) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] [INFO] Total time: 1 minute 29 seconds [INFO] Finished at: Tue Sep 23 03:28:27 CST 2008 [INFO] Final Memory: 7M/15M [INFO] - Blog: http://www.ryanwong.name Can Use: English, Chinese -- View this message in context: http://www.nabble.com/Help-Maven-Release-to-SVN-ERROR-tp19614856p19614856.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] - To unsubscribe, e-mail:
Re: Help Maven Release to SVN ERROR
On Mon, Sep 22, 2008 at 12:29 PM, Ryan Wong [EMAIL PROTECTED] wrote: Here is the svn http://dev.ave7.net/svn/java/common/trunk My Issue is when command mvn releaser:prepare There always an error like: ... If it's not just that the tag already exists, then some of the comments in this thread might be helpful: http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] Continuum 1.2 Released
The date on the release page is wrong, it says November 23, 2007. Ken On Mon, Sep 22, 2008 at 3:37 PM, Olivier Lamy [EMAIL PROTECTED] wrote: The Apache Continuum team is pleased to announce Apache Continuum 1.2. The latest release is now available here: http://continuum.apache.org/download.html If you have any questions, please consult: - the web site: http://continuum.apache.org - the continuum-user mailing list: http://continuum.apache.org/mail-lists.html New in Continuum 1.2 * Using Spring Continuum now uses the Spring Framework as it's underlying container instead of Plexus. This results in a boost in performance and stability for the web application in particular. *Repository Purge It's now possible to add purges which will cleanup : - m2 repositories (now it's possible to configure a local m2 repository per project group) - build output directory * Maven plugin groupId and artifactId change Now the maven plugin has the new groupId:artifactId org.apache.continuum:continuum-maven-plugin * New SCMs support Now continuum have two new scm providers : git and accurev. Change Log in Continuum 1.2 === ** Bug * [CONTINUUM-860] - multiple email addresses delimited with commas causes AddressException * [CONTINUUM-1054] - IllegalStateException stack adding pom * [CONTINUUM-1200] - Password Characters Not Supported in SCM Checkout * [CONTINUUM-1322] - Attempt to store value with more than 256 chars * [CONTINUUM-1336] - upgrade quartz - we use a very old version * [CONTINUUM-1360] - Prepended semicolon in svn password does not work * [CONTINUUM-1371] - NullPointer when Releasing with Ant and Default Project Group * [CONTINUUM-1433] - Wrong path in descripton on how to allow the file protocol. * [CONTINUUM-1489] - replace use of MungedHttpsURL with apache httpclient (4.0-beta1) * [CONTINUUM-1515] - SCM Tag does not have a default value * [CONTINUUM-1521] - NullPointerException in StarTeam changelog command * [CONTINUUM-1525] - Can't release project with Continuum on Geronimo 2.0.1 * [CONTINUUM-1528] - Continuum gets slower over time and eventually crashes * [CONTINUUM-1549] - LDAP Authenticated Continuum - NullPointerException when trying to see Members of a project group * [CONTINUUM-1575] - Confusing behavior when continuum can't construct MavenProject from pom * [CONTINUUM-1589] - updateBuildDefinitionForProjectGroup remove the description of the build definition * [CONTINUUM-1590] - updateBuildDefinitionForProjectGroup leads to a StackOverflowError * [CONTINUUM-1593] - Requires Javamail 1.5? Should be 1.4? * [CONTINUUM-1596] - The release perform doesn't work when a scm password is required * [CONTINUUM-1601] - Email address with '+' is not accepted in mail notifier * [CONTINUUM-1610] - Deployment Repository Directory does not work at all * [CONTINUUM-1623] - Checkbox not displaying when validation error in add Instalaction-Tool form * [CONTINUUM-1630] - Error attempting to delete project group * [CONTINUUM-1643] - Perform release page results to a blank page after submitted * [CONTINUUM-1644] - Test failures occur in tagged sources * [CONTINUUM-1646] - Empty recipient is allowed in mail notifier * [CONTINUUM-1647] - Incorrect alt and title text for releaseproject_disabled.gif * [CONTINUUM-1649] - Move Build Definition Template guide to Administrator's Guides * [CONTINUUM-1651] - Unable to delete user-created build definitions * [CONTINUUM-1659] - project admin cannot assign project roles to users * [CONTINUUM-1660] - Download page does not have source archives * [CONTINUUM-1672] - continuum plugin doesn't fails to add maven two projects * [CONTINUUM-1676] - deleting a project or group should cancel any current or scheduled builds, and prevent any from being queued * [CONTINUUM-1679] - Adding Null values for Project's Build Definition directs to a blank page * [CONTINUUM-1688] - Maximum length for name column in object ChangeFile is too small * [CONTINUUM-1693] - Continuum fills our server disk with SNAPSHOTs. * [CONTINUUM-1701] - No field validation when adding Ant and Shell projects * [CONTINUUM-1713] - JDOFatalUserException '.-..column NAME that has maximum length of 255. Please correct your data!' * [CONTINUUM-1715] - no response when adding a project * [CONTINUUM-1725] - Using the Cancel Button without an selected project will produce NPE * [CONTINUUM-1734] - Loop in getProjects methode * [CONTINUUM-1738] - Add schedule page doesn't use its properties file * [CONTINUUM-1739] - Import of Maven2 project fails if 2.0.9 feature depMgm. scopeimport used * [CONTINUUM-1742] - Duplicate installations (environment variables) in Profile are accepted * [CONTINUUM-1746] - Duplicate Profile names are accepted * [CONTINUUM-1748] -
Re: eclipse plugin, resolve dependencies to the projects in the workspace
On Tue, Sep 23, 2008 at 1:09 AM, Eugeny N Dzhurinsky [EMAIL PROTECTED] wrote: Hello, everybody! I have the project A, which depends on the project B, both of the projects are located in the same workspace. When generating the eclipse project files for the project A, the project B reference is being taken from the repository as a JAR file. What I want is to include the project B as a project reference for the project A, so when the project A is opened in the Eclipse, the project B is opened as well as a dependency, and all changes in the project B are reflected in the project A (for example, if some interface contract was changed in the project B, the corresponding files in the project A will contain errors, or changes in the project A with refactoring will be merged to the project B as well). I found there is the property workspace described in http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#workspace, however neither using it as mvn eclipse:eclipse -Dworkspace=/home/user/workspace, nor specifying it in the plugin configuration did not give the desired results, and the project B is still referenced as a JAR file in the local repository. Do I miss something? Thank you! -- Eugene N Dzhurinsky yes, from the command line you use Expression not the configuration valeue, so use eclipse.workspace as in mvn eclipse:eclipse -Declipse.workspace=/home/user/workspace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin, resolve dependencies to the projects in the workspace
Eugeny N Dzhurinsky-2 wrote: I have the project A, which depends on the project B, both of the projects are located in the same workspace. ... I found there is the property workspace described in http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#workspace, however neither using it as mvn eclipse:eclipse -Dworkspace=/home/user/workspace, nor specifying it in the plugin configuration did not give the desired results, and the project B is still referenced as a JAR file in the local repository. Do I miss something? Out of curiosity, why don't you use Maven IDe integration, such as m2eclipse? http://m2eclipse.codehaus.org/ regards, Eugene -- View this message in context: http://www.nabble.com/eclipse-plugin%2C-resolve-dependencies-to-the-projects-in-the-workspace-tp19610981p19616050.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: Antwort: Re: Attaching source zip to jar managed by maven
Olel wrote: sorry for being a little unprecise. It is not that I don't want to have the sources locally, but don't want to manage the attaching on every developer machine as you have guessed. Therefore I tried the m2eclipse feature Download Artifact Sources and give it a try with dbunit-2.2.3 from repo1.maven.org which has Javadoc and sources attached. Unfortunately that doesn't work. Neither are the sources downloaded nor attached to the local jar. Do you have any idea what might be the problem? Can you please submit a bug report to m2eclipse and provide simple test project that would allow to reproduce this issue with dbunit sources. http://jira.codehaus.org/browse/MNGECLIPSE Also note that there is Mave / Download Sources action that could be invoked on Maven projects or individual jars. Olel wrote: The other thing is: most of the jars we use do not have sources in the public repositories. Could you give me a short introduction on how to add these sources manually to our enterprise repository and attach to their jars? With m2eclipse you can attach sources and javadocs locally without deploying them to the Maven repository. You can do that from the jar properies dialog. regards, Eugene -- View this message in context: http://www.nabble.com/Attaching-source-zip-to-jar-managed-by-maven-tp19530862p19616052.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: Excluding empty directories from assembly
You could probably add this functionality without much trouble and make it configurable (boolean includeEmptyDirectories), then donate the code back to Maven for inclusion in a future release of the Assembly plugin. Wayne On Mon, Sep 22, 2008 at 7:00 AM, [EMAIL PROTECTED] wrote: Hi, I'm using the maven assembly plugin to create an assembly of a source tree. My source tree sometimes contains empty directories (they have to be there, don't ask!). Is there a way I can get the assembly plugin to remove all empty directories from the assembly? Here's my descriptor: assembly idjrules-project-assembly/id formats formatzip/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directory / useDefaultExcludestrue/useDefaultExcludes includes include*.xml/include include*.sql/include include*.js/include include**/bom/**/include include**/queries/**/include include**/rules/**/include include**/templates/**/include include**/.ruleproject/include include**/.project/include includejrules-support/**/include /includes excludes exclude**/output/**/exclude exclude**/target/**/exclude exclude**/.rtserver/**/exclude exclude**/.settings/**/exclude /excludes /fileSet /assembly - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: List modules and versions
have a look at versions maven plugin and file an enhancement request if it does not do what you're after Sent from my iPod On 22 Sep 2008, at 20:07, sverhagen [EMAIL PROTECTED] wrote: Is there an easy way to list all modules in a multi-module project and the current version that they are at, possibly their latest release version as well, since that's what I'm ultimately after anyway? -- View this message in context: http://www.nabble.com/List-modules-and-versions-tp19614503p19614503.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help Maven Release to SVN ERROR
So what you will find is that subversion is trying to copy from the working copy thats an older revision than on the server... just do svn up and mvn release:prepare again... the resume will work fine On Tue, 23 Sep 2008 07:51:03 Wendy Smoak wrote: On Mon, Sep 22, 2008 at 12:29 PM, Ryan Wong [EMAIL PROTECTED] wrote: Here is the svn http://dev.ave7.net/svn/java/common/trunk My Issue is when command mvn releaser:prepare There always an error like: ... If it's not just that the tag already exists, then some of the comments in this thread might be helpful: http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does relocation work for plugins?
I have a Maven plugin with an internal groupId that is listed in all our users settings.xml as a valid plugin groupId. I now need to change the groupId to a new value. This new groupId is not listed as a plugin groupId in any of our internal user's settings.xml file. Can I use relocation to avoid the need for users to change their settings but yet get the newest release? Thanks, Justin
Re: Help Maven Release to SVN ERROR
Thanks a lot... I have upgraded to 1.5.2 both server and client. Looking forward for the bug been fixed But It seems all the SVN 1.5 clients performs the same way... Whether it's a protocol change of version 1.5? Michael McCallum wrote: So what you will find is that subversion is trying to copy from the working copy thats an older revision than on the server... just do svn up and mvn release:prepare again... the resume will work fine On Tue, 23 Sep 2008 07:51:03 Wendy Smoak wrote: On Mon, Sep 22, 2008 at 12:29 PM, Ryan Wong [EMAIL PROTECTED] wrote: Here is the svn http://dev.ave7.net/svn/java/common/trunk My Issue is when command mvn releaser:prepare There always an error like: ... If it's not just that the tag already exists, then some of the comments in this thread might be helpful: http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://n2.nabble.com/Help-Maven-Release-to-SVN-ERROR-tp1110454p194.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: Does relocation work for plugins?
You can't relocate the whole group, but you can relocate particular plugin artifacts to achieve this. The same has happened for the Jetty plugin recently on the central repository. - Brett 2008/9/23 Edelson, Justin [EMAIL PROTECTED]: I have a Maven plugin with an internal groupId that is listed in all our users settings.xml as a valid plugin groupId. I now need to change the groupId to a new value. This new groupId is not listed as a plugin groupId in any of our internal user's settings.xml file. Can I use relocation to avoid the need for users to change their settings but yet get the newest release? Thanks, Justin -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring Javadoc and JXR to work together
Staging does tend to have some problems with aligning the paths in the past. Does it work if you generate the full site? - Brett 2008/9/23 [EMAIL PROTECTED]: Hi Folks. I have been trying to get this to work for the last few days and I cannot figure out what configuration will work. I am using Maven 2.0.9 with the following plugins: jxr 2.1 javadoc (default) Here is my major problem: When I generate the site using site:stage, all of the tools seem to run fine and produce a nice reports. The javadoc connection on the jxr report is showing the following url: /V:/common-2.0.0-SNAPSHOT/miscellaneous/common-types/target/site/apidocs/ca/medavie/lang/CallerInfo.html while the javadoc file is located at the following url: /V:/common-2.0.0-SNAPSHOT/target/staging/common/miscellaneous/common-util/xref/ca/medavie/lang/CallerInfo.html Here is the reporting section of my pom file: reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId configuration !--aggregatetrue/aggregate -- /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId version2.1/version configuration !-- aggregatetrue/aggregate -- linkJavadoctrue/linkJavadoc /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version configuration targetJdk1.5/targetJdk rulesets rulesetmedavie_pmd_ruleset.xml/ruleset /rulesets formatxml/format linkXreftrue/linkXref sourceEncodingutf-8/sourceEncoding minimumTokens100/minimumTokens /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration configLocationmedavie_checkstyle_checks.xml/configLocation /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdtaglist-maven-plugin/artifactId configuration tags tagTODO/tag tag@todo/tag tagFIXME/tag tagXXX/tag tagNOPMD/tag tag@SuppressWarnings/tag /tags /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version1.2/version configuration effortMax/effort thresholdLow/threshold xmlOutputtrue/xmlOutput /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.2/version /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjdepend-maven-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0.0-beta-1/version /plugin /plugins /reporting As you can see from the pom file, I have also tried using aggregation (it is currently commented out). When aggregation is used, none of the other (pmd, checkstyle and findbugs) reports can connect to the jxr report and the jxr report cannot connect to the javadoc. Any and all help would be greatly appreciated. Dale Chapman, Corporate Architect, Common Services Medavie 506-867-4430 [EMAIL PROTECTED] Debugging is at least twice as hard as programming. If your code is as clever as you can possibly make it, then by definition, you are not smart enough to debug it. - Brian Kernighan --- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l'entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous
Re: Does relocation work for plugins?
On Mon, Sep 22, 2008 at 6:47 PM, Brett Porter [EMAIL PROTECTED] wrote: You can't relocate the whole group, but you can relocate particular plugin artifacts to achieve this. The same has happened for the Jetty plugin recently on the central repository. Relocation doesn't seem to be working for Jetty-- this came up the other day helping someone on irc. Of course, just specifying version 6.1.11 fixes it, so I didn't go further. If I take the webapp archetype and add: build ... plugins plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId /plugin /plugins I get: imbrium:mywebapp wsmoak$ mvn install [INFO] Scanning for projects... [INFO] [INFO] Building mywebapp Maven Webapp [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 19:02:01 MST 2008 [INFO] Final Memory: 3M/7M [INFO] In case it's relevant: imbrium:mywebapp wsmoak$ mvn -version Maven version: 2.0.9 Java version: 1.5.0_13 OS name: mac os x version: 10.5.4 arch: i386 Family: unix -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does relocation work for plugins?
Yes, I think you need a relocation in the old position for every version of the artifact you intend to relocate - it isn't done at the group or all-versions level. - Brett 2008/9/23 Wendy Smoak [EMAIL PROTECTED]: On Mon, Sep 22, 2008 at 6:47 PM, Brett Porter [EMAIL PROTECTED] wrote: You can't relocate the whole group, but you can relocate particular plugin artifacts to achieve this. The same has happened for the Jetty plugin recently on the central repository. Relocation doesn't seem to be working for Jetty-- this came up the other day helping someone on irc. Of course, just specifying version 6.1.11 fixes it, so I didn't go further. If I take the webapp archetype and add: build ... plugins plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId /plugin /plugins I get: imbrium:mywebapp wsmoak$ mvn install [INFO] Scanning for projects... [INFO] [INFO] Building mywebapp Maven Webapp [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 19:02:01 MST 2008 [INFO] Final Memory: 3M/7M [INFO] In case it's relevant: imbrium:mywebapp wsmoak$ mvn -version Maven version: 2.0.9 Java version: 1.5.0_13 OS name: mac os x version: 10.5.4 arch: i386 Family: unix -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Issues with Maven 2.1.0 resume from feature
This feature is scheduled for M2, which can be built from the maven-2.1.x branch, but was not included in the 2.1.0-M1 release. You can discuss this further on the Maven dev list. If you are interested in using the reactor functionality without upgrading Maven, you can try the reactor plugin which is currently being prepared for release. - Brett 2008/9/23 Henri Tremblay [EMAIL PROTECTED]: Arg.. forget the attachment (which I'm not even sure is going through) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does relocation work for plugins?
Ah. So there's no way to say: version 1.0 through 1.9 have this groupId and 2.0 and above have a different groupId? That might get tricky, but at least I know something is possible. Thanks, Justin - Original Message - From: Brett Porter [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Mon Sep 22 22:16:03 2008 Subject: Re: Does relocation work for plugins? Yes, I think you need a relocation in the old position for every version of the artifact you intend to relocate - it isn't done at the group or all-versions level. - Brett 2008/9/23 Wendy Smoak [EMAIL PROTECTED]: On Mon, Sep 22, 2008 at 6:47 PM, Brett Porter [EMAIL PROTECTED] wrote: You can't relocate the whole group, but you can relocate particular plugin artifacts to achieve this. The same has happened for the Jetty plugin recently on the central repository. Relocation doesn't seem to be working for Jetty-- this came up the other day helping someone on irc. Of course, just specifying version 6.1.11 fixes it, so I didn't go further. If I take the webapp archetype and add: build ... plugins plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId /plugin /plugins I get: imbrium:mywebapp wsmoak$ mvn install [INFO] Scanning for projects... [INFO] [INFO] Building mywebapp Maven Webapp [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.mortbay.jetty -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 19:02:01 MST 2008 [INFO] Final Memory: 3M/7M [INFO] In case it's relevant: imbrium:mywebapp wsmoak$ mvn -version Maven version: 2.0.9 Java version: 1.5.0_13 OS name: mac os x version: 10.5.4 arch: i386 Family: unix -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetty and using src/test/webapp
I think you'd have to copy the files all to one directory and use that
instead, but that would prevent the automatic recompilation.
You might be able to add a profile that adds the test directory as an
additional source directory, but be careful here that it will pollute
target/classes for an eventual build that doesn't run with clean.
If you need an enhancement to the plugin to support multiple class
directories, that would need to be requested of the Jetty developers.
They may have better ideas how to do this, as it seems like an unusual
use case to me.
- Brett
2008/9/23 Andrew Robinson [EMAIL PROTECTED]:
I have a war project that was built that also has a src/test/webapp
directory. The idea was that test pages could be made in this
directory that would not be included in the normal war.
I have got it mostly working except for the classes. I need to have
both target/classes and target/test-classes on the classpath. Here is
what I have been attempting to use:
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.12.rc2/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
webXml${basedir}/src/test/webapp/WEB-INF/web.xml/webXml
webAppSourceDirectory${basedir}/src/test/webapp/webAppSourceDirectory
webAppConfig
contextPath/demo-test/contextPath
baseResource
implementation=org.mortbay.resource.ResourceCollection
resourcesAsCSV
src/test/webapp,src/main/webapp
/resourcesAsCSV
/baseResource
/webAppConfig
/configuration
Looking here:
http://docs.codehaus.org/display/JETTY/Which+files+are+scanned+by+the+Jetty+Maven+Plugin
It says that scanTargets are picked up, but that did not work.
I set classesDirectory to ${basedir}/target/test-classes, but then
the ${basedir}/target/classes were no longer on the classpath.
How can I get jetty to run off of the src/test/webapp and include both
${basedir}/target/test-classes and ${basedir}/target/classes?
Thanks,
Andrew
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: release pluging not workin?
perhaps it is not letting you go backwards... does 3-SNAPSHOT work? - Brett 2008/9/22 nodje [EMAIL PROTECTED]: hum, I need some help here please. The Maven Release plugin is somehow not working as expected. To put the problem simply: mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building commons-xml [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'com.company:company-parent' set to release? (yes/no) yes: : What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1.1-SNAPSHOT What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 2-SNAPSHOT What is the release version for commons-xml? (com.company.commons:commons-xml) 1.0: : In short, it would in this case never accept any values different than the default one. cheers nodje wrote: I'm a newbie with the release plugin and have a hard time already managing dependencies. After much thinking, I end up with this process: - branch first the current trunk version to a branch named 1.0-SNAPSHOT. The trunk version becomes 1.1-SNAPSHOT - release the branch version: the release is the 1.0 version, the branch becomes 1.0.1-SNAPSHOT I need the branch step first in order to be able to fix bug that could appear on the 1.0 version. A tag not being modifiable, I need to be able to rerelease from the 1.0-SNAPSHOT line. And so came the idea of the 1.0.1-SNAPSHOT version. If anyone has another solution for this problem, he is much welcome! Anyways, while trying this I'm confronted to a Maven release-plugin problem: I'm trying to release a component that depends only on the company-parent.pom (that follows the 1-SNAPSHOT - 2-SNAPSHOT release numbering pattern) I want the development version to be updated to depend on the released version 1 or 1.1-SNAPSHOT of the company-parent pom. here's the trace of the command: mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building commons-xml [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'com.company:company-parent' set to release? (yes/no) yes: : What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version?
Re: frustration with testNG tests running twice.
They are probably in the default location so the default configuration runs them in the test phase. - Brett 2008/9/20 Mick Knutson [EMAIL PROTECTED]: I have this declaration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution execution idintegration-tests/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnoretrue/testFailureIgnore suiteXmlFiles suiteXmlFilesrc/test/resources/testng-functional.xml/suiteXmlFile /suiteXmlFiles groupssuite-init,database,functional,selenium/groups excludeGroupsunit/excludeGroups /configuration /execution /executions /plugin Now I even commented out the phasetest/phase to stop unit test from running, but they run anyways. And because there is not a testng.xml for that phase, the tests fail. Can someone please help me get just my functional tests to run in the phaseintegration-test/phase ??? Your help is greatly appreciated! -- --- 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 -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does relocation work for plugins?
I'm not quite sure I understand. There is a relocation pom for 7.0.0pre3. Would you expect it to work if I specify the version? (It doesn't. Same output.) plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version7.0.0pre3/version /plugin -- Wendy On Mon, Sep 22, 2008 at 7:16 PM, Brett Porter [EMAIL PROTECTED] wrote: Yes, I think you need a relocation in the old position for every version of the artifact you intend to relocate - it isn't done at the group or all-versions level. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to config my plugin's life phase before another?
for exapmle, my plugin want to bind to install, but it will replace some file in my war the install it into local responsitory?how to config my plugin to run as the first plugin in the install phase? thx!
Re: Does relocation work for plugins?
Yes, that should work, so there might be something else going on. - Brett 2008/9/23 Wendy Smoak [EMAIL PROTECTED]: I'm not quite sure I understand. There is a relocation pom for 7.0.0pre3. Would you expect it to work if I specify the version? (It doesn't. Same output.) plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version7.0.0pre3/version /plugin -- Wendy On Mon, Sep 22, 2008 at 7:16 PM, Brett Porter [EMAIL PROTECTED] wrote: Yes, I think you need a relocation in the old position for every version of the artifact you intend to relocate - it isn't done at the group or all-versions level. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to config my plugin's life phase before another?
This isn't possible, the defaults get priority. It sounds like you are altering the packaging, therefore your goal should be in the package phase. Cheers, Brett 2008/9/23 陈思淼 [EMAIL PROTECTED]: for exapmle, my plugin want to bind to install, but it will replace some file in my war the install it into local responsitory?how to config my plugin to run as the first plugin in the install phase? thx! -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: Problems using XSD
Thanks Wayne, You correctly mentioned about using Unpack Dependency plugin. I used it it resolved my issue. Thanks for the response. Regards, Ram On 9/22/08, Wayne Fay [EMAIL PROTECTED] wrote: What exactly is your question? I read the email twice, and there's no question in it. If the XMLBeans plugin supports reading XSD files from a Jar and generating the source, this should be pretty simple with a little configuration. If it does not, you will probably need to use the dependency plugin to unpack the XSD jar into Project 2's target folder so the XMLBeans plugin has XSD files to work on so it can generate the source properly. Or you could modify the XMLBeans plugin source code so it supports reading from Jars. Wayne On Mon, Sep 22, 2008 at 1:49 AM, RAM [EMAIL PROTECTED] wrote: Hi All, I have few clarifications using XSD's from multiple Projects using Maven and then generating Java Objects using XMLBeans Plugin. Any help/guidance is appreciated: I have 2 Projects now. *Project 1*: Called as XSD-PROJECT which just holds all the xsd's. This Project builds a jar file which contains all the xsd's. *Project 2: *This Project is a web Project, in which, we have WSDL 1 more XSD under WEB-INF. Our requirement is to use *Project 1* as dependency for *Project 2 *and generate the Java Objects using XMLBeans plugin for the Project 2. The generated classes should include all the Java Object for all the XSD's from both the locations. We are using XMLBeans 2.3.0 Maven 2.0.9. -- Thanks, Ram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Ram
Re: Antwort: Re: Attaching source zip to jar managed by maven
2008/9/22 Eugene Kuleshov [EMAIL PROTECTED] Olel wrote: The other thing is: most of the jars we use do not have sources in the public repositories. Could you give me a short introduction on how to add these sources manually to our enterprise repository and attach to their jars? You can use maven deploy plugin (deploy:deploy-file). Just deploy the sources near the corresponding jar, named something-sources-version.jar for something-version.jar. Cheers. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Problem with Jsp compilation in Maven using jspc
This is best asked at [EMAIL PROTECTED]
You might also look at the alternative JSPC plugin from Jetty.
- Brett
2008/9/17 Nittala [EMAIL PROTECTED]:
Hi,
I have trouble precompiling jsps in our project. I followed the instructions
at http://mojo.codehaus.org/jspc/jspc-maven-plugin/usage.html.
With the settings i have my jsps are not picked up for compilation. It just
prepares the war and thats it.
Here are the entries in my project's pom.xml. I dont completely understand
the jspweb.xml entry. What is it used for and what should be the entry
there? when the Mvn install command gives error about missing jspweb.xml i
gave the path for my existing web.xml. Is this right ? Am i missing
something ? Please help.
Thanks for your help.
plugin
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-maven-plugin/artifactId
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
webappDirectory${pom.basedir}/src/main/webapp/webappDirectory
webXml${pom.basedir}/src/main/webapp/WEB-INF/web.xml/webXml
!-- webXml${pom.basedir}/target/jspweb.xml/webXml
--
/configuration
/plugin
--
View this message in context:
http://www.nabble.com/Problem-with-Jsp-compilation-in-Maven-using-jspc-tp19518483p19518483.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]
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Refactoring Plugin
Hi I need to generate some web service stubs and refactor the code. Is there a Maven Plugin that I can specify refactor package this to that? Regards, Néstor Boscán
Re: release-plugin: execute at generate-sources phase
I think the plugin level configuration would conflict, overriding the section from the build section. - Brett 2008/9/19 Klaus H. [EMAIL PROTECTED]: Hi all, i need to filter a resource file before the generate-sources phase (input file for source-generator). So i bound the maven-resources-plugin to the generate-sources phase. The point is that filtering does not work anymore. Even the filtering in the default lifecycle-phase of the generator plugin does not work anymore. Seem as explicity naming the resource-plugin overwrites some default configuration. Any idea which one this could be? Or any other idea how this could be solved.. Thanks, Klaus --- build plugins plugin artifactIdmaven-resources-plugin/artifactId executions execution idfilterGeneratorInput/id phasegenerate-sources/phase goals goalresources/goal /goals configuration resources resource filteringtrue/filtering directorysrc/main/resources/directory includes includeGeneratorInput.xml/include /includes /resource /resources outputDirectorytarget\klaus/outputDirectory /configuration /execution /executions configuration resources resource filteringtrue/filtering directorysrc/main/resources/META-INF/directory /resource /resources /configuration /plugin !-- (Re-)Generate -- plugin artifactIdmyGeneratorPlugin/artifactId ... -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How define new packaging type and mapping with life cycle?
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590view=markup 2008/9/18 陈思淼 [EMAIL PROTECTED]: In the process of packaging of wars to one ear. we decide to combine all the web project into only one war, and package the only one war into ear package.so we should define a new packaging type called car, and mapping the car to a new life-cycle, can any one tell me how to define a new packaging type and mapping with life cycle? Thank you! -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: Does relocation work for plugins?
I went ahead and reported it, using Jetty as an example. http://jira.codehaus.org/browse/MNG-3762 -- Wendy On Mon, Sep 22, 2008 at 8:25 PM, Brett Porter [EMAIL PROTECTED] wrote: Yes, that should work, so there might be something else going on. - Brett 2008/9/23 Wendy Smoak [EMAIL PROTECTED]: I'm not quite sure I understand. There is a relocation pom for 7.0.0pre3. Would you expect it to work if I specify the version? (It doesn't. Same output.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How define new packaging type and mapping with life cycle?
That's usefull！ thanks 2008/9/23 Brett Porter [EMAIL PROTECTED] http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590view=markup 2008/9/18 陈思淼 [EMAIL PROTECTED]: In the process of packaging of wars to one ear. we decide to combine all the web project into only one war, and package the only one war into ear package.so we should define a new packaging type called car, and mapping the car to a new life-cycle, can any one tell me how to define a new packaging type and mapping with life cycle? Thank you! -- Brett Porter Blog: http://blogs.exist.com/bporter/
