+1. I had infra set up a staging group for us some time ago to make this easier; you can stage all of them and test by using the repo URL for the staging group.
On Sun, Nov 1, 2015 at 8:00 AM, Karl Heinz Marbaise <[email protected]> wrote: > Hi, > > +1 for releasing them in one go... > > > On 11/1/15 10:03 AM, Hervé BOUTEMY wrote: >> >> Currently, we have 5 Maven parent POMs [1] (not counting Doxia), each with >> its >> own release cycle. >> Releasing each separately is a pain. And knowing which pom is at which >> version >> is a pain also. > > Unfortunately true... > > >> >> What would you think of: >> >> 1. setting the same version to every Maven parent POM: next would be >> version >> 29, since the maximum currently is plugins parent at 28 > > > To make a clear step start with version 30.... > > Kind regards > Karl Heinz Marbaise > >> >> 2. releasing the 5 POMs in only one release >> >> This would mean putting all the poms in pom svn [2] (currently plugins >> parent >> is in plugins, shared in shared, skins in skin...). >> I still don't know if the best bet is to make Maven parent the release >> root: >> maven >> |-- plugins >> |-- shared >> |-- skins >> |-- archetypes >> >> or if we should create a new parent that is only used as reactor >> >> any opinion? >> >> Regards, >> >> Hervé >> >> [1] http://maven.apache.org/pom/index.html >> >> [2] http://svn.apache.org/repos/asf/maven/pom/trunk/maven/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
