Re: gitflow releases with maven?
2011/7/29 Mark Struberg : > > 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: users-h...@maven.apache.org
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 : > > Do you have activated? > You might try disabling it, maybe there is a bug with that on windows. > is meant to spare bandwith in huge projects by doing a > git-clone file:// from the local git repo instead of cloning the upstream > repo in release:perform. Yes, localCheckout=true and pushChanges=false are used, because the maven-release-plugin should perform only local changes. Gitflow has to do additional branching / merging, which has to be pushed outside the maven-release-plugin. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
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: 'd:devprojectsmaven.mastersourcemaven.master' does not appear to be a > git > repository > fatal: The remote end hung up unexpectedly > > > When using a different path with slashes > "git clone file:///d:/dev/projects/maven.master/source/maven.master/" > everything works fine. Looks like I hit this issue: http://jira.codehaus.org/browse/MRELEASE-624 Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
2011/7/29 Mark Derricutt : > > 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 being the version number. If I > checked out master and > did a maven install, I'd expect to get a SNAPSHOT and not something that's > going to overwrite existing > released artifacts. > >> It must not match the maven repo, but there should not be a SNAPSHOT-pom on >> HEAD > > As above I beg to differ. Hmm, this is what I understand from the gitflow documentation and what results, when performing a manual release without the maven-release-plugin. But you are right, ignoring this restriction is no real problem. >> [...] >> [INFO] --- maven-release-plugin:2.2:perform (default-cli) @ master --- >> [INFO] Checking out the project to perform the release ... >> [INFO] Performing a LOCAL checkout from >> scm:git:file://D:\dev\projects\maven.master\source\maven.master >> [INFO] Executing: cmd.exe /X /C "git clone >> file://D\dev\projects\maven.master\source\maven.master >> D:\dev\projects\maven.master\source\maven.master\target\checkout" > > Interesting - I see you have maven.master mentioned twice in the path - > what do you have in your SCM settings element? scm:git:ssh://git@myserver:22/maven.master.git scm:git:ssh://git@myserver:22/maven.master.git > And what is the root path of the git repo The file path to the local clone is: D:\dev\projects\maven.master\source\maven.master There are two "maven.master", because I organize my projects in subfolders with eclipse workspace folders parallel to the source folders (e.g. D:\dev\projects\maven.master\workspace). > and are you releasing from that directory? Both, the git and mvn commands are executed from "D:\dev\projects\maven.master\source\maven.master" 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: 'd:devprojectsmaven.mastersourcemaven.master' does not appear to be a git repository fatal: The remote end hung up unexpectedly When using a different path with slashes "git clone file:///d:/dev/projects/maven.master/source/maven.master/" everything works fine. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
2011/7/26 Mark Derricutt : > 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 > $ git push && git push --tags > > At least thats my work flow. There may be one or two fix up patches before I > finish the release branch, if I need to roll back the release and tweak > something ( I'll git tag -d the maven made tag if things for that far ). > > After the git flow release is finnished, both master and develop sit at the > next -SNAPSHOT version, > this actually works out nice as it means you can then at some point do a "git > flow hotfix start..." > if need be to patch the last release ( which branches from master ). This breaks the gitflow master definition: "We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state." But without this restriction, your process should work. > Master will always be the code at the time the git flow release branch > finished, > it's not necessarily a direct match to your maven repo. It must not match the maven repo, but there should not be a SNAPSHOT-pom on HEAD Also, if I configure the maven-release-plugin with > false > true the maven release fails with: [...] [INFO] --- maven-release-plugin:2.2:perform (default-cli) @ master --- [INFO] Checking out the project to perform the release ... [INFO] Performing a LOCAL checkout from scm:git:file://D:\dev\projects\maven.master\source\maven.master [INFO] Executing: cmd.exe /X /C "git clone file://D\dev\projects\maven.master\source\maven.master D:\dev\projects\maven.master\source\maven.master\target\checkout" [INFO] Working directory: D:\dev\projects\maven.master\source\maven.master\target [ERROR] The git-clone command failed. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 58.157s [INFO] Finished at: Wed Jul 27 16:17:26 CEST 2011 [INFO] Final Memory: 5M/247M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2:perform (default-cli) on project master: Unable to checkout from SCM [ERROR] Provider message: [ERROR] The git-clone command failed. [ERROR] Command output: [ERROR] fatal: 'D\dev\projects\maven.master\source\maven.master' does not appear to be a git repository [ERROR] fatal: The remote end hung up unexpectedly [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException Do I have to make a special configuration on SCM? Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
Hello Mark, 2011/7/25 Mark Derricutt > > We're using gitflow/maven quite nicely, I use for my release plugin: > > > org.apache.maven.plugins > maven-release-plugin > 2.1 > > deploy > false > true > > > In this configuration maven does a local checkout, and doesn't require a git > push during release. > This means after a maven release, I do my git-flow release, THEN push the > master/develop branch to my origin. I'm sorry, I don't understand. You first run the maven-release-plugin? On which gitflow-branch (develop, feature, release)? I think the maven release results in a NON-SNAPSHOT tag and finaly creates a new SNAPSHOT-pom on head. If you now do finish the gitflow release, this SNAPSHOT-pom will go on the master branch. But gitflow defines master as the stable production branch. There should no SNAPSHOT-pom exist on the master branch. Am I mistaken? Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
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 with hacks and results in confusing or not correct tags. Is there a kind of "lightweight" release-plugin, which does only perform - version-checks and updates (remove SNAPSHOTs) - build and test the changed project - commit the changes into the current branch if everything is correct It should NOT create a tag or push changes. [1] http://nvie.com/posts/a-successful-git-branching-model/ http://yakiloo.com/getting-started-git-flow/ Regards, Lars
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:
org.apache.maven.plugins
maven-release-plugin
${project.groupId}.${project.artifactId}-${releaseVersion}
Unfortunately, there is no ${releaseVersion} property.
${project.version} is computed with the old -SNAPSHOT value.
Is there a way, how I can configure the maven-release-plugin to work this way?
Regards,
Lars
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [m3] version-property in pluginManagement causes a warning
2010/11/23 Lars Fischer > > 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] 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 placed in a third master-parent pom. Using the property defined in the master-parent as value inside the pluginManagement of the inherited parents, I get a warning, that the plugin-version has to be set. The property works fine, when used in a pure plug-in configuration. Is it not possible to use a property inside the pluginManagement section? Kind regards, Lars
Re: Fwd: Problem M2_HOME variabla
2010/11/22 Blanca Hernández > > > 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 a little hint, although I'm sure you already know this: changes to system properties require to restart the programms referencing them. You need to open a new shell directly from the windows startmenu to use changed properties. 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 null. Defining the same parameter inside my NewMojo the values are injected. Searching for the reason, I found that extending other plug-ins is no good idea when using Maven2. I use Maven3 and have no need to run my plug-in with Maven2. Is there a way to enable the inheritance from other Mojos to pretend duplicating the code? 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
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
Hello Maxime,
2010/11/17 Maxime Gréau
>
> 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}.
This is the output after calling "mvn help:effective-pom install" using
"${project.build.directory}"
[...]
org.codehaus.mojo
exec-maven-plugin
1.1
test2
install
exec
echo
D:\development\projects\test\target
[...]
[INFO] --- exec-maven-plugin:1.1:exec (test2) @ test ---
[INFO] D:developmentprojectstesttarget
I changed my configuration and used the correct Windows-path directly:
D:\development\projects\test\target
And the output is still wrong.
Next I changed "\" to "/":
D:/development/projects/test/target
And now I get the complete path:
"[INFO] D:/development/projects/test/target"
Looks like a bug inside the exec-maven-plugin, which filters all "\"
characters.
Kind regards,
Lars
[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:
org.codehaus.mojo
exec-maven-plugin
1.1
test
exec
install
echo
${project.build.directory}
As result the path to the target folder of the build project is printed.
But there is a major problem: the path does not contain any "/" or "\". It
looks like
"D:developmentprojectstesttarget" but should be
"D:\development\projects\test\target"
Where is my mistake?
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
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 :
> Hello
>
> i would like to deploy a mvn-site using scp with user/password.
>
> This is contained the settings.xml:
>
> site
> aUser
> myPassword
>
>
>
> The pom.xml looks like this:
>
> [...]
>
> org.apache.maven.plugins
> maven-site-plugin
> 2.1.1
>
> [...]
>
> [...]
>
> site
> scp://${scm.host}/srv/www/htdocs/maven/${project.artifactId}
>
>
>
>
> Running site-deploy, maven asks for the password:
>
> [INFO] [site:deploy {execution: default-deploy}]
> Keyboard interactive required, supplied password is ignored
> Password:
>
>
> Why is the configured password ignored?
> Where is my mistake?
>
> Regards,
> Lars
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
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:
site
aUser
myPassword
The pom.xml looks like this:
[...]
org.apache.maven.plugins
maven-site-plugin
2.1.1
[...]
[...]
site
scp://${scm.host}/srv/www/htdocs/maven/${project.artifactId}
Running site-deploy, maven asks for the password:
[INFO] [site:deploy {execution: default-deploy}]
Keyboard interactive required, supplied password is ignored
Password:
Why is the configured password ignored?
Where is my mistake?
Regards,
Lars
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
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 -Dtag=R_reporting_1.1.1 -DreleaseVersion=1.1.1 -DdevelopmentVersion=1.1.2-SNAPSHOT release:prepare results in a log: [...] [INFO] Tagging release with the label svn://svnrepository/tags/components/rt/R_reporting_1.1.1... [INFO] Executing: cmd.exe /X /C "svn --username jondoe --password * --non-interactive copy --file C:\DOKUME~1\lfischer\LOKAL E~1\Temp\maven-scm-571333557.commit --revision 5815 svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/repo rting svn://svnrepository/tags/components/rt/R_reporting_1.1.1" [...] [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/reporting' does not exist in revision 5815 I thought the tagging has to perform a copy from the local temp folder to the new tag place in the svn. But the execution shows a 2nd source "--revision 5815 svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/reporting" The error states right, that this is not a valid source. But why is it generated into the copy statement? My environment: - maven 2.2.1 - maven-release-plugin 2.0-beta-9 - svn 1.6.6 (SlikSvn:tag/1@40358) WIN32 regards Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[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 -DdevelopmentVersion=1.1.2-SNAPSHOT release:prepare results in a log: [...] [INFO] Tagging release with the label svn://svnrepository/tags/components/rt/R_reporting_1.1.1... [INFO] Executing: cmd.exe /X /C "svn --username jondoe --password * --non-interactive copy --file C:\DOKUME~1\lfischer\LOKAL E~1\Temp\maven-scm-571333557.commit --revision 5815 svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/repo rting svn://svnrepository/tags/components/rt/R_reporting_1.1.1" [...] [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/reporting' does not exist in revision 5815 I thought the tagging has to perform a copy from the local temp folder to the new tag place in the svn. But the execution shows a 2nd source "--revision 5815 svn://svnrepository/tags/components/rt/R_poms_1.1.0/parent.standard/reporting" The error states right, that this is not a valid source. But why is it generated into the copy statement? My environment: - maven 2.2.1 - maven-release-plugin 2.0-beta-9 - svn 1.6.6 (SlikSvn:tag/1@40358) WIN32 Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
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 the same renaming rules like the > > binary-jars? I tried to integrate a MANIFEST.MF with the needed "Eclipse-SourceBundle"- header into the source-jar. But I found no way to do this. The maven-source- plugin generates a small new MANIFEST.MF and has no option to configure an other file for it. regards, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 into > this platform-folder following the same renaming rules like the > binary-jars? Am I the only one who needs the sources of the used bundles? Is there a plan for extending the plugin for such a goal? regards, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
