Re: gitflow releases with maven?

2011/7/29 Mark Derricutt m...@talios.com: Hrm - I still believe that master would be production-ready-state even with the -SNAPSHOT version, the code is in a state that ready for production release.  If I did a maven release from there I'd get the same code built, with the only difference

Re: gitflow releases with maven?

Could this be a Windows problem? I tried to perfom a second clone from the local file path with the generated maven path: git clone file://D:\dev\projects\maven.master\source\maven.master This results in: Cloning into devprojectsmaven.mastersourcemaven.master... fatal:

Re: gitflow releases with maven?

Hello Mark, I see, that you assigned MRELEASE-624. Thank you for the quick reaction! 2011/7/29 Mark Struberg strub...@yahoo.de: Do you have localCheckout activated? You might try disabling it, maybe there is a bug with that on windows. localCheckout is meant to spare bandwith in huge

Re: gitflow releases with maven?

2011/7/29 Mark Struberg strub...@yahoo.de: Oki, I understand. Will try to look at it the next week. Great. Thank you, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: gitflow releases with maven?

2011/7/26 Mark Derricutt m...@talios.com: Before cutting the release, I start a new release branch, do the maven release, then when I'm happy, finish the release branch, THEN push to origin $ git flow release start 3.4.5 $ mvn release:prepare release:perform $ git flow release finish 3.4.5

Re: gitflow releases with maven?

Hello Mark, 2011/7/25 Mark Derricutt m...@talios.com We're using gitflow/maven quite nicely, I use for my release plugin:              plugin                    groupIdorg.apache.maven.plugins/groupId                    artifactIdmaven-release-plugin/artifactId                    

gitflow releases with maven?

Hello, I use git together with gitflow(1) and would like to release projects the gitflow way. Gitflow itself creates branches, a release tag and merges changes back into other branches. The maven-release-plugin performs similar things an other way. I tried to use both together, but it works only

maven-release-plugin: computed releaseVersion used as property?

Hello, I would like to use the maven-release-plugin and set a different release tag without the need of interacting. Additional I need to use the computed release version as part of the tag. I tried to configure it like this: plugin groupIdorg.apache.maven.plugins/groupId

Re: Fwd: Problem M2_HOME variabla

2010/11/22 Blanca Hernández blancahdezni...@gmail.com I think this is not the problem, because, I also tryed something like M2_HOME = C:\apache-maven-2.2.1 With the same error, just changing the path. Somebody told me the could be maybe Windows7 incompatibilities, do you think so?? Just

[m3] version-property in pluginManagement causes a warning

Hello, I would like to define a group of plug-ins inside the pluginManagement section of a parent pom. Most of the plugins use the same version, but they also have to be in sync with other configurations in an second parent pom. I decided to use a property defining the version. This property is

Re: [m3] version-property in pluginManagement causes a warning

2010/11/23 Lars Fischer lfisc...@fastmail.fm Is it not possible to use a property inside the pluginManagement section? Sorry, the reason was an another wrong configuration. Everything works fine. Kind regards, Lars

[m3] extending an existing Mojo from another plug-in

Hello, I would like to create a new maven plug-in to extend another plug-in (P_O) to solve some very special requirements. I defined a dependency to P_O and created a NewMojo by extending an existing BaseMojo from P_O. But parameters defined in the BaseMojo are not injected. They are always

[m3] property ${project.build.directory} returns defect path

Hello, I use Maven v3.0.0 and would like to use the property ${project.build.directory} inside commandlineArgs of the exec-maven-plugin. My configuration looks like this: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.1/version executions

Re: [m3] property ${project.build.directory} returns defect path

Hello Maxime, 2010/11/17 Maxime Gréau greaumax...@gmail.com I tested your configuration and it works fine for me (Apache Maven 3.0 and exec-maven-plugin-1.0) First, you can execute : mvn help:effective-pom You will see the real path returned by the property ${project.build.directory}.

Re: [m3] property ${project.build.directory} returns defect path

I switched to exec-maven-plugin version 1.2. But now I get an error: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:exec (test2) on project test.test: Command execution failed. Cannot run program echo (in directory D:\development\projects\test) Kind regards, Lars

Re: [m3] property ${project.build.directory} returns defect path

The windows path bug is fixed in 1.2: http://jira.codehaus.org/browse/MEXEC-81 Kind regards, Lars

maven-release-plugin 2.1 bugfix not working

Hello, the bug entry at http://jira.codehaus.org/browse/MRELEASE-128 was closed with the release of version 2.1. But the described effect still happens. Could someone please check this and maybe reopen the entry? Kind regards, Lars

Re: [ANN] Maven Release Plugin 2.1 Released

[MRELEASE-128] - SCM properties being replaced during release:perform This is still not working for me: http://jira.codehaus.org/browse/MRELEASE-128 Regards, Lars

site-deploy: configured password is ignored

Hello i would like to deploy a mvn-site using scp with user/password. This is contained the settings.xml: server idsite/id usernameaUser/username passwordmyPassword/password /server The pom.xml looks like this: [...] plugin groupIdorg.apache.maven.plugins/groupId

Re: site-deploy: configured password is ignored

I found the reason: the sshd on the server used PasswordAuthentication no. After switching to yes my maven config works fine. Regards, Lars 2010/6/10 Lars Fischer lfisc...@fastmail.fm: Hello i would like to deploy a mvn-site using scp with user/password. This is contained the settings.xml

Re: [maven-release-plugin] problem with wrong source on tagging

Hello, could someone please tell my, where is my mistake: I have problems releasing a project using the maven-release-plugin: A call like: mvn --batch-mode -DautoVersionSubmodules=true -Dresume=false -Dusername=jondoe -Dpassword=jondoe -DtagBase=svn://svnrepository/tags/components/rt

[maven-release-plugin] problem with wrong source on tagging

Hello, I have problems releasing a project using the maven-release-plugin: A call like: mvn --batch-mode -DautoVersionSubmodules=true -Dresume=false -Dusername=jondoe -Dpassword=jondoe -DtagBase=svn://svnrepository/tags/components/rt -Dtag=R_reporting_1.1.1 -DreleaseVersion=1.1.1

Re: maven-eclipse-plugin install-plugins and source-jars

Hello, On Wed, 17 Sep 2008 15:13:31 +0200, Lars Fischer [EMAIL PROTECTED] mail.org said: I use the maven-eclipse-plugin with the goal install-plugins to create an eclipse target-platform containing my bundle-dependencies. Is is also possible to get the sources of these dependencies

Re: maven-eclipse-plugin install-plugins and source-jars

Hello, On Fri, 19 Sep 2008 08:24:09 +0200, Lars Fischer I use the maven-eclipse-plugin with the goal install-plugins to create an eclipse target-platform containing my bundle-dependencies. Is is also possible to get the sources of these dependencies into this platform-folder following

maven-eclipse-plugin install-plugins and source-jars

Hello, I use the maven-eclipse-plugin with the goal install-plugins to create an eclipse target-platform containing my bundle-dependencies. Is is also possible to get the sources of these dependencies into this platform-folder following the same renaming rules like the binary-jars? regards,