Op Thu, 13 Mar 2014 01:40:23 +0100 schreef Jörg Hohwiller
<jo...@j-hohwiller.de>:
Hi there,
I added site documentation and some other missing infos. Further I fixed
some JavaDoc issues.
For clarification I found the following questions:
* Why do we copy <repositories> section of <profile> when we strip
<repositories> from <project>? This appears inconsistent to me.
I think repositories should stay, pluginRepositories not
* Shall we prevent creating "useless" profiles (those that have no
dependencies) in flattened POM?
Sounds reasonable
* Shall we consider more complex logic to figure out if properties are
influenced by profiles and used in dependencies so we do not resolve
such properties?
I know there's a JIRA issue which suggest that dependencies shouldn't
contain properties. At build-time I would like to use properties to keep a
set of artifacts like Spring at the same version. But at deploy-time it's
probably better to have them resolved.
* Is there a way to prevent maven from deploying the parent POMs when a
top-level build is triggered? See some of my examples...
there are different types of parent: aggregator, release-root, sub-parent,
standalone. The latter should be deployed, since this will be the parent
for other projects (e.g. mojo-parent) . The rest is probably less
interesting when using a flatten pom. This feature is just as dangerous as
the embedBuildPRofileDependencies.
FYI: my eclipse temporary lost the maven formatter settings. Sorry for
the intermediate mess in DIFFs.
time to sleep now...
Regards
Jörg
Am 10.03.2014 21:09, schrieb Robert Scholte:
http://mojo.codehaus.org/development/process.html#Versioning_and_Release_Strategy
In this case beta might be right (feature complete). There are already
a good number of ITs, there's a lot of javadoc.
http://mojo.codehaus.org/development/performing-a-release.html#Graduating_from_the_Sandbox
for getting it out of the sandbox
Robert
Op Mon, 10 Mar 2014 16:55:24 +0100 schreef Baptiste Mathus
<bmat...@batmat.net>:
Hi, just a quick thought about a detail. I saw you named it 1.0-beta-x.
Maybe first releasing an alpha-x for the very first version would be
better.
Anyway, about voting, IIRC there's a vote to go out of sandbox before a
vote to release.
My 2 cents.
2014-03-09 23:16 GMT+01:00 Jörg Hohwiller <jo...@j-hohwiller.de>:
Hi there,
I hope renaming of consumer-maven-plugin to flatten-maven-plugin was
perfectly correct.
We should have another SNAPSHOT version released for testers.
Then I will update the related JIRA issues with that.
I still have to add some documentation for the site...
If there is anything else (beside starting the vote one day) let me
know.
Regards
Jörg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
