On Thu, Nov 7, 2013 at 4:58 PM, Sergiu Dumitriu <[email protected]> wrote:

> On 11/07/2013 10:29 AM, Vincent Massol wrote:
> > Hi devs,
> >
> > We need to provide a contrib top level POM for extension contributors.
> ATM
> > we recommend to extend the commons top level pom on
> > http://contrib.xwiki.orgbut it's a bad idea because contributors
> > forget to override some pom.xml
> > elements (such as the <developers> section) and thus the published
> > extensions end up with wrong information (such as wrong author: "XWiki
> > Development Team").
> >
> > The reason to put it in commons:
> > * We will have dependencyManagement in it and thus it needs to be in sync
> > with the commons version. It'll have the same version as commons top
> level
> > pom version.
> > * Easy for us since it'll be released at the same time as commons
> > * Easy for extension authors to choose the top level contrib version they
> > need: they'll pick the one corresponding to the xwiki version they want
> to
> > depend on
> >
> > Note that since some extensions may want to depend on versions of XWiki
> > older than 5.3 we can deploy this contrib pom also for older versions
> using
> > mvn deploy:deploy-file
> >
> > WDYT?
>
> +1.
>
> Will this be a copy of xwiki-commons-pom, or an extension that overrides
> a few sections?
>
> Should it include the license check plugin, which currently enforces
> LGPL2.1? Should we make it easier to change the license being enforced?
>
> What do we put instead of the <developers>? Do we make it a generic
> "XWiki community", or leave it empty so that others can fill it in? We
> can use the enforcer's requireProperty rule to check that mandatory
> sections have been filled in.
>

See a first version at
https://github.com/xwiki-contrib/contrib-pom/blob/master/pom.xml


> I'd like to have a single xwiki.version property instead of the current
> commons, rendering, platform.version, so that people don't have to think
> which one should they use for each module.
>

I think that's orthogonal to this discussion.


> Instead of deploy-file, why not actually release older versions? Since
> it's a separate repository, we can do that, we don't have to sync
> releases with the official XWiki releases.
>

It's not a separate repository, that's the point ;) I explained above why I
think it's good to have it in xwiki-commons ;)

Thanks
-Vincent


> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to