done https://issues.apache.org/jira/browse/COMMONSSITE-79
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-12-13 19:13 GMT+01:00 sebb <seb...@gmail.com>: > File a JIRA with exact details. > > On 13 December 2014 at 18:03, Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: >> @Sebb: when trying to release jcs I had a lot of trouble just because >> [commons] parent pom doesn't follow asf rules (remote resource plugin >> is deactivated where it is correct in apache pom for instance) >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >> >> >> 2014-12-13 18:56 GMT+01:00 sebb <seb...@gmail.com>: >>> On 13 December 2014 at 17:51, Romain Manni-Bucau <rmannibu...@gmail.com> >>> wrote: >>>> At least some skip should be removed since it breaks apache parent >>>> behavior. >>> >>> No idea what you mean here - if you think there is a bug, file a JIRA issue. >>> >>>> Le 13 déc. 2014 18:42, "sebb" <seb...@gmail.com> a écrit : >>>> >>>>> On 13 December 2014 at 12:26, Mark Struberg <strub...@yahoo.de> wrote: >>>>> > Hi! >>>>> > >>>>> > I've never seen any other ASF project where it is such a torture to >>>>> release. >>>>> > This is partly because the quality level is really high, but a big part >>>>> of it is that we don't have a mature parent pom. >>>>> >>>>> Sorry, but I don't think that is at all relevant. >>>>> Releasing is tedious because Maven does not really support non-Maven >>>>> release directories (i.e. www.apache.org/dist/commons) so work-rounds >>>>> are needed. >>>>> This is true whatever the parent pom is used. >>>>> >>>>> It's partly also that Maven does some things well, but when >>>>> adjustments are needed, it can be all but impossible to work out how >>>>> to coax it to do what's needed. >>>>> >>>>> > >>>>> > I have no clue why we don't just use the common apache parent pom. I've >>>>> NEVER experienced such issues like missing NOTICE and LICENSE with it. >>>>> It's >>>>> really much more solid than our own one. >>>>> >>>>> Until very recently the ASF parent pom was broken, and with no sign of >>>>> any fixes. >>>>> For example, it did not allow override of the compiler plugin version, >>>>> and there were a few other issues with it. >>>>> >>>>> There are stil issues with LICENSE and NOTICE, because the >>>>> automatically created ones are not always correct. >>>>> I'm not sure it creates the appropriate source and javadoc jars either. >>>>> >>>>> And it does not create decent manifests. >>>>> >>>>> The Commons Pom includes a lot of common setup that would otherwise >>>>> have to be added to each component's parent pom. >>>>> That is not an efficient way of proceeding. >>>>> >>>>> There are various other additional optional features in the Commons >>>>> pom which are useful for testing. >>>>> >>>>> I think the CP pom works fine for single module projects. >>>>> I'm not sure about multimodule projects, but is the ASF pom any better? >>>>> >>>>> Rather than raise unsubstantiated criticisms of the CP pom, file bugs >>>>> for any problems and/or try fixing them. >>>>> >>>>> > LieGrue, >>>>> > strub >>>>> > >>>>> > --------------------------------------------------------------------- >>>>> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> > For additional commands, e-mail: dev-h...@commons.apache.org >>>>> > >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
