Re: can release-plugin check preconditions?
Hi Stephen, the issue is: http://jira.codehaus.org/browse/MRELEASE-690 Cheers, Christopher Am 04.07.2011 23:55, schrieb Stephen Connolly: Please create an issue for it. ping me back with the issue id and I'll add it to the Backlog On 4 July 2011 22:48, Christopher Cudennec wrote: Thanks Stephen, that was a quick answer :) Checking if the tag exists seems to be described by: http://jira.codehaus.org/browse/MRELEASE-572 and http://jira.codehaus.org/browse/MRELEASE-165. I'd vote for these! Unfortunately I could not find an issue for checking the release repository. Do you know anything about that? Is it worth creating a new issue? Cheers, Christopher Am 04.07.2011 23:22, schrieb Stephen Connolly: correct. See MRELEASE-166 and other open issues in the release plugin On 4 July 2011 22:07, Christopher Cudennecwrote: Hi everyone! I'd like to have some advice for using the Maven release plugin. As far as I understand the plugin does not check the SCM or the Maven repository before performing a release. It will result in a failure if either the tag already exists in the SCM or the version has already been deployed to the repository. In that case you have to clean up the mess yourself by performing a rollback or removing the SCM tag. Can someone confirm that behaviour? Is there any provided way to check preconditions for performing the release *before* actually executing it? Thanks, Christopher - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: can release-plugin check preconditions?
Thanks Stephen, that was a quick answer :) Checking if the tag exists seems to be described by: http://jira.codehaus.org/browse/MRELEASE-572 and http://jira.codehaus.org/browse/MRELEASE-165. I'd vote for these! Unfortunately I could not find an issue for checking the release repository. Do you know anything about that? Is it worth creating a new issue? Cheers, Christopher Am 04.07.2011 23:22, schrieb Stephen Connolly: correct. See MRELEASE-166 and other open issues in the release plugin On 4 July 2011 22:07, Christopher Cudennec wrote: Hi everyone! I'd like to have some advice for using the Maven release plugin. As far as I understand the plugin does not check the SCM or the Maven repository before performing a release. It will result in a failure if either the tag already exists in the SCM or the version has already been deployed to the repository. In that case you have to clean up the mess yourself by performing a rollback or removing the SCM tag. Can someone confirm that behaviour? Is there any provided way to check preconditions for performing the release *before* actually executing it? Thanks, Christopher - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
can release-plugin check preconditions?
Hi everyone! I'd like to have some advice for using the Maven release plugin. As far as I understand the plugin does not check the SCM or the Maven repository before performing a release. It will result in a failure if either the tag already exists in the SCM or the version has already been deployed to the repository. In that case you have to clean up the mess yourself by performing a rollback or removing the SCM tag. Can someone confirm that behaviour? Is there any provided way to check preconditions for performing the release *before* actually executing it? Thanks, Christopher - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multi modules/different pom/more than one source dir
Hey everyone, as far as I know it is not possible to set the name of the pom-file when using a multi module project. The xml schema states this: 4.0.0 The modules to build in addition to the current project maxOccurs="unbounded" type="xs:string"/> So my pom.xml for the project looks something like ... one two I guess the default file name (i.e. pom.xml) is assumed. I can build my projects by commandline using something like "mvn -f myproject.xml" so why not adding an attribute to set the name of the pom file? The reason why I need this is that I have to cope with a multi source folder problem. I already know that this is regarded as being "evil" but I would like to introduce maven to an existing project without (much) changing the directory structure... I can solve my problem in each subproject by creating a new pom.xml and packaging this project before my "real" project. Any comments or suggestions? Thanks, Christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archetypes
Hey, thanks for the answer. I got to it by thinking and reading the documentation in the meantime as well ;). Archetypes are not what I was really looking for to tell the truth. I prefer copying my pom.xml in my existing projects. It's really poor that you need to define any kind of file for a folder to be created. Just giving a folder name for "source" does nothing... Using "allowPartial" didn't work out as well, so I'm quite annoyed by the archetype. The main stuff (packaging, ...) worked fine nevertheless... Thanks, Christopher Napoleon Esmundo Ramirez schrieb: Hello, The archetype plugin gives you a kick to start on projects immediately. It creates the template of your project as far as sources and resources are concerned. The target is defined in the project's pom.xml and it doesn't need to be in the archetype as it frequently gets cleaned in the file system. :) Cheers! Nap On 4/5/06, Christopher Cudennec <[EMAIL PROTECTED]> wrote: Hello everyone, I try to get to know what I can do by the archetype plugin. The guide to creating archetypes is alright for the basics but I would like to know how to set more variables by the archetype.xml. The documentation talks about setting the source and test-source-directory. But what about the target directory? In order to be able to adjust my own archetype to my existing project structure I would like to be able to set this one as well. I would appreciate any comments or a DTD ;). Thanks, Christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 05.04.2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Archetypes
Hello everyone, I try to get to know what I can do by the archetype plugin. The guide to creating archetypes is alright for the basics but I would like to know how to set more variables by the archetype.xml. The documentation talks about setting the source and test-source-directory. But what about the target directory? In order to be able to adjust my own archetype to my existing project structure I would like to be able to set this one as well. I would appreciate any comments or a DTD ;). Thanks, Christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
