Re: Release plugin: release project from within subdirectory
Maven is about doing things the right way, no hacks. Hacks impede understanding of a project by others (or yourself 6 months later) and are an antipattern What happens when 6 months down the line you need a new feature and decide to upgrade the release plugin? You have relied on the hack, and the hack works no more... Far better to reorg the project processes so the hack is no longer required up front. You will have a simpler project and you can just concentrate on writing code Time spent hacking the build is time not coding On Friday, 20 July 2012, Kalle Korhonen wrote: Thanks Werdex. Using the release plugin version 2.3.2 and it's still exactly the same, only goalsdeploy -f Sources/pom.xml/goals works when the pom.xml is not in the root, regardless of pomFileName setting. Stephen, isn't that exactly why you want to lock down the plugin versions? I'll take a well-working hack any day over proper but broken. Kalle On Thu, Apr 21, 2011 at 12:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com javascript:; wrote: fyi that is a hack and may not work in future versions when the bug is fixed - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 20 Apr 2011 15:36, werdex werde...@yahoo.com javascript:; wrote: Hi, The following did trick for me: configuration goalsdeploy -f Sources/pom.xml/goals /configuration -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6290891.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.orgjavascript:; For additional commands, e-mail: users-h...@maven.apache.orgjavascript:; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: users-h...@maven.apache.orgjavascript:;
Re: Release plugin: release project from within subdirectory
On Fri, Jul 20, 2012 at 1:20 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Maven is about doing things the right way, no hacks. Says the purist :P Hacks impede understanding of a project by others (or yourself 6 months later) and are an antipattern What happens when 6 months down the line you need a new feature and decide to upgrade the release plugin? You have relied on the hack, and the hack What happens when you are trying to deliver code but cannot because the tool of the righteous doesn't work for you? Pragmatism always wins. Anyway, to me it looks like a pretty valid use case that you'd have a git repo with associated documentation to go with the code. The canonical example many others before me have mentioned is that you have folders such as documentation/ and development/ at the root your of your git repo. The pomFileName option is there but just doesn't seem to work. Kalle On Friday, 20 July 2012, Kalle Korhonen wrote: Thanks Werdex. Using the release plugin version 2.3.2 and it's still exactly the same, only goalsdeploy -f Sources/pom.xml/goals works when the pom.xml is not in the root, regardless of pomFileName setting. Stephen, isn't that exactly why you want to lock down the plugin versions? I'll take a well-working hack any day over proper but broken. Kalle On Thu, Apr 21, 2011 at 12:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com javascript:; wrote: fyi that is a hack and may not work in future versions when the bug is fixed - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 20 Apr 2011 15:36, werdex werde...@yahoo.com javascript:; wrote: Hi, The following did trick for me: configuration goalsdeploy -f Sources/pom.xml/goals /configuration -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6290891.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.orgjavascript:; For additional commands, e-mail: users-h...@maven.apache.orgjavascript:; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: users-h...@maven.apache.orgjavascript:; - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin: release project from within subdirectory
On 20 Jul 2012, at 6:10 PM, Kalle Korhonen wrote: Maven is about doing things the right way, no hacks. Says the purist :P This isn't purist, this is being disciplined. Hacks impede understanding of a project by others (or yourself 6 months later) and are an antipattern What happens when 6 months down the line you need a new feature and decide to upgrade the release plugin? You have relied on the hack, and the hack What happens when you are trying to deliver code but cannot because the tool of the righteous doesn't work for you? Then you stop, you fix the bug, submit the fix upstream, and move on. I did that a few weeks ago with a problem I was having with the maven-resources-plugin (among others), I discovered my problem had been reported 5 years ago my more than one person, but nobody had spent the hour or so that it took to fix it. Pragmatism always wins. Lack of discipline always wins. It drives me up the wall when I have to pick apart and undo some ugly hack that was put in place because someone wasn't willing to get the original job done properly, and I'm left forced having to debug the hack they put in place instead. When you encounter a problem that seems to need a hack, picture yourself in six months time, arms crossed glaring at yourself today, going you could have fixed it and didn't, and now look at how I am suffering Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
Re: Release plugin: release project from within subdirectory
Thanks Werdex. Using the release plugin version 2.3.2 and it's still exactly the same, only goalsdeploy -f Sources/pom.xml/goals works when the pom.xml is not in the root, regardless of pomFileName setting. Stephen, isn't that exactly why you want to lock down the plugin versions? I'll take a well-working hack any day over proper but broken. Kalle On Thu, Apr 21, 2011 at 12:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: fyi that is a hack and may not work in future versions when the bug is fixed - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 20 Apr 2011 15:36, werdex werde...@yahoo.com wrote: Hi, The following did trick for me: configuration goalsdeploy -f Sources/pom.xml/goals /configuration -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6290891.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin: release project from within subdirectory
fyi that is a hack and may not work in future versions when the bug is fixed - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 20 Apr 2011 15:36, werdex werde...@yahoo.com wrote: Hi, The following did trick for me: configuration goalsdeploy -f Sources/pom.xml/goals /configuration -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6290891.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin: release project from within subdirectory
Hi, The following did trick for me: configuration goalsdeploy -f Sources/pom.xml/goals /configuration -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6290891.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin: release project from within subdirectory
Got stuck with the same problem. Is there a solution to this? -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-release-project-from-within-subdirectory-tp5057222p6207546.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release plugin: release project from within subdirectory
Hello,
I'm trying to set up release plugin for a project that lives in the
subdirectory of the repo;
That is, given the layout like this:
repo root
|- pom.xml
|
|- [module1]
| |- pom.xml
|
|- [module2]
| |- pom.xml
|
|- [tools]
|- [mytool]
|- pom.xml
I'd like to release mytool, which is completely standalone module.
mvn release:clean release:prepare release:perform -f tools/mytool/pom.xml
Initial configuration was like this:
configuration
preparationGoalsclean/preparationGoals
goalsdeploy/goals
/configuration
release:clean and release:prepare went as expected, i.e. against
tools/mytool. But release:perform checked out whole codebase under
tools/mytool/target/checkout, and invoked mvn deploy against root pom of
the checkout folder. Which is basically another project
With no luck I tried number of options:
*
pomFileName${project.build.directory}/checkout/tools/mytool/pom.xml/pomFileName
* pomFileNametools/mytool/pom.xml/pomFileName
* arguments-f tools/mytool/pom.xml/arguments
* arguments-f
${project.build.directory}/checkout/tools/mytool/pom.xml/arguments
Still deploy is invoked against root pom. Generally, is it possible to
release project located in a repo subdirectory?
- maven 2.2.1
- release plugin 2.0
Thanks,
Pavel
