Hi Esteban,
(now with reply on list...)
you are right with your guess.
> I am curious as to how well it works with the release plugin,
versions plugin,
> packaging sources, generating sites, eclipse, m2eclipse, other
plugins in general.
For site generation we had a bug that has been fixed in beta2.
I am using it with m2e in Eclipse without problems. Also I use various
deploy profiles including PGP signing what also really works for the
flattened POM.
I am quite unsure how it goes together with the release plugin. However
you could question if you need release plugin anymore if you try what
you want to do as you only have a single property for your version that
you can directly edit, commit and tag.
We are still collection feedback about how well the approach of flatten
plugin works together with the enitre maven ecosystem. I can not give
any guarantees but I would say it is stable enough to give it a try.
However beta3 has not yet been released so be aware of these issues:
https://jira.codehaus.org/browse/MOJO-2039
https://jira.codehaus.org/browse/MOJO-2032
I hope that we can release beta3 this month.
Feedback is very welcome...
Chers
Jörg
Am 21.08.2014 16:06, schrieb Esteban Porcelli:
The reason why I thought the plugin would help is because of the documentation
and examples.
It uses a static parent version that does not change and it uses a property
expression to define the version of the child pom.
The feature I want from Maven is to have child poms that inherit the parent
version, without having to specify that version in each child pom.
If you have 50 children modules and you create a branch, you end up having to
commit changes to 50 poms (the new version for the new branch). (and we have
lots of branches).
When these branches are merged, these pom differences (the version tag) always
results in conflicts.
Maven always displays a warning when using a property expression in the project
version tag
[WARNING] Some problems were encountered while building the effective model for
com.dovetailsys.framework:sharedwebapp:war:1.19.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @
com.dovetailsys.framework:sharedwebapp:${frameworkcore.version}, C:\D
evelopment\frameworkcore2\frameworkcore\shared\webapp\pom.xml, line 11, column
14
What I was most curious about the plugin documentation is how it interacts with other
plugins. For example we use the maven release plugin. It does not like project version to
have a property expression <version>${myproject.version}</version>.
So your plugin does not seem to solve this issue. (Unless I did something wrong
in my testing)
Thanks for your help.
Esteban
-----Original Message-----
From: Robert Scholte [mailto:codeh...@sourcegrounds.com]
Sent: Thursday, August 21, 2014 5:20 AM
To: hohwi...@users.sourceforge.net; Esteban Porcelli
Cc: u...@mojo.codehaus.org
Subject: Re: Flatten maven plugin Question -
http://mojo.codehaus.org/flatten-maven-plugin/
Hi Esteban,
I'm not sure how this plugin could help you in this case. It cleans up the
pom.xml before distributing it to your local and remote repository.
The effect when using the flattened pom.xml should be exactly the same as with
the original pom.xml This is done as part of the build-lifecycle, so it has no
effect on other plugins (which is a good thing).
If http://mojo.codehaus.org/flatten-maven-plugin/ didn't gave you enough info,
let us know how to make it more clear.
Regarding the mailing-lists, archive.codehaus.org is still an infra issue,
waiting to be solved. Markmail is the best option you have. Be aware, that if
you want to post to a certain list, you first need to subscribe for it.
thanks,
Robert
Op Wed, 20 Aug 2014 22:46:17 +0200 schreef Esteban Porcelli
<esteban.porce...@dovetailsystems.com>:
Hi,
By chance I just found this plugin and it will really help my project
if I can use it.
We have several mercurial repositories with a main pom and many many
children poms (20+) that all share the same version.
We also have a lot of branches and having to update all poms on every
merge is a pain (even using the versions plugin), plus it results in a
lot of conflicts that need to be resolved manually.
This appears to be a very recent plugin and I can't find much
documentation on it.
I am curious as to how well it works with the release plugin, versions
plugin, packaging sources, generating sites, eclipse, m2eclipse, other
plugins in general.
I am planning on testing these things but I just wanted to save me
some time if there are already known issues with the plugin.
Thanks a lot,
Esteban
The Mailing Lists:
http://mojo.codehaus.org/flatten-maven-plugin/mail-lists.html
Don't appear to be configured properly
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
