Oh I missed to answer the question on scm-publish and not inherited
configuration.
The configuration for mono module trigger the plugin execution on
phase post-site
If you apply same for multi modules that will trigger svn commit for
each module.
That can be long as it will include a checkout of the path too. (and
btw you will have to define scm url for each plugin: no inheritence as
for the site deployment which add the ${artifactId} at the end.
So IMHO will be a pain to deploy multi modules sites.Makes sense ? 2012/12/7 Olivier Lamy <[email protected]>: > no sure of that in fact as I can deploy manually :-) > BTW that's a better pattern IMHO. > I changed it for logging to test that. > If it doesn't work we have to create a jira entry. > > 2012/12/7 Simone Tripodi <[email protected]>: >> Salut Olivier, >> >> +1 indeed at Any23, Amber, ... we applied the pattern you suggested. >> My fault this time, I applied the wrong versioning pattern while >> migrating components ;( >> >> I am taking care of that update, thanks! >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> On Fri, Dec 7, 2012 at 2:51 PM, Olivier Lamy <[email protected]> wrote: >>> no idea neither >>> I don't manage the nexus instance. >>> But the isssue is probably the version number which end with >>> SNAPSHOT-incubating >>> That's not very standard. IMHO that must be incubating-SNAPSHOT >>> >>> >>> 2012/12/7 Christian Grobmeier <[email protected]>: >>>> oh wow. it seems jenkins runs with ldap. Cool. >>>> thanks for letting me know >>>> >>>> >>>> On Fri, Dec 7, 2012 at 2:32 PM, Simone Tripodi >>>> <[email protected]>wrote: >>>> >>>>> every member should have the access - you included - indeed was me on >>>>> setting up all initial jobs, unfortunately I have no clue about the >>>>> deploy issue :( >>>>> >>>>> best, >>>>> -Simo >>>>> >>>>> http://people.apache.org/~simonetripodi/ >>>>> http://simonetripodi.livejournal.com/ >>>>> http://twitter.com/simonetripodi >>>>> http://www.99soft.org/ >>>>> >>>>> >>>>> On Fri, Dec 7, 2012 at 1:30 PM, Christian Grobmeier <[email protected]> >>>>> wrote: >>>>> > On Fri, Dec 7, 2012 at 1:28 PM, Simone Tripodi <[email protected] >>>>> >wrote: >>>>> > >>>>> >> No clue as well, hopefully Olivier knows how to set the jobs in order >>>>> >> to allow jenkins deploying our artifacts,,, >>>>> >> >>>>> >> Who - besides Olivier - does have access to Jenkins? >>>>> > I mean, just in case something wents wrong and our Guru is not >>>>> > available? >>>>> > >>>>> > >>>>> >> -Simo >>>>> >> >>>>> >> http://people.apache.org/~simonetripodi/ >>>>> >> http://simonetripodi.livejournal.com/ >>>>> >> http://twitter.com/simonetripodi >>>>> >> http://www.99soft.org/ >>>>> >> >>>>> >> >>>>> >> On Fri, Dec 7, 2012 at 12:55 PM, Christian Grobmeier >>>>> >> <[email protected]> wrote: >>>>> >> > On Fri, Dec 7, 2012 at 12:50 PM, Daniel Manzke < >>>>> >> [email protected] >>>>> >> >> wrote: >>>>> >> > >>>>> >> >> hey guys, >>>>> >> >> >>>>> >> >> is still not able to be build on jenkins, through the relative path >>>>> to >>>>> >> the >>>>> >> >> parent. locally everything is fine. >>>>> >> >> >>>>> >> >> >>>>> >> > sure it is the relative path? >>>>> >> > For me it looks like the deployment to snapshots does not work: >>>>> >> > https://builds.apache.org/job/Onami-Logging/20/console >>>>> >> > >>>>> >> > Its a 401, which means not authorization. >>>>> >> > >>>>> >> > Not sure about how to fix it further :-) >>>>> >> > >>>>> >> > Cheers >>>>> >> > >>>>> >> > >>>>> >> > >>>>> >> >> I'm not the maven guru to know what to do. :) >>>>> >> >> >>>>> >> >> -- >>>>> >> >> Viele Grüße/Best Regards >>>>> >> >> >>>>> >> >> Daniel Manzke >>>>> >> >> >>>>> >> > >>>>> >> > >>>>> >> > >>>>> >> > -- >>>>> >> > http://www.grobmeier.de >>>>> >> > https://www.timeandbill.de >>>>> >> >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > http://www.grobmeier.de >>>>> > https://www.timeandbill.de >>>>> >>>> >>>> >>>> >>>> -- >>>> http://www.grobmeier.de >>>> https://www.timeandbill.de >>> >>> >>> >>> -- >>> Olivier Lamy >>> Talend: http://coders.talend.com >>> http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
