Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

@Enrico What "--add-modules ALL-SYSTEM" really does ? For me it would be maybe a handy hack but for you it would be just a hack anyway as it first seems. Strong encapsulation in Java9 can be openly passed by. For instance in Surefire we extend UrlClassLoader and I need to access entire Java API

Re: Closing issues in JIRA

I had a look and it seems roles assignments in MASSEMBLY were broken: I just changed them to match classical pattern please check and confirm MASSEMBLY works now as other Maven Jira projects Regards, Hervé Le samedi 17 juin 2017, 14:17:16 CEST Karl Heinz Marbaise a écrit : > Hi, > > created

Re: Migration of remaining plugins to Git

Good thought. We could ask about a timeline. On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > They are now adding user grouping... I wonder how long before repo grouping > too > > On Sun 18 Jun 2017 at 17:12, Paul Hammant wrote: > >

Re: Migration of remaining plugins to Git

They're always very polite for things that I ask for, but I can't claim to have suggested anything that got implemented. I've a better hit-rate with JetBrains and their IDEs. - Paul On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Liable to get an

Re: Migration of remaining plugins to Git

Polite, yes, just non commital ;-) On Sun 18 Jun 2017 at 23:10, Paul Hammant wrote: > They're always very polite for things that I ask for, but I can't claim to > have suggested anything that got implemented. I've a better hit-rate with > JetBrains and their IDEs. > > - Paul >

Re: Migration of remaining plugins to Git

I met Chris Wanstrath at a meetup in Cincinatti about four years ago, and bent his ear about how fantastic Github-Pages (and Jekyll) was as a CMS. I suggested that if they could add themes for "high school", "community group", etc they could pull in another category of user of the platform, and

Re: Migration of remaining plugins to Git

Choose one to start with, is what I would do. git svn clone of a trunk only, then make that master. branch/tag history can be retained in Subversion but also up on MavenCentral as foo-x.y-sources.jar files. Unless you optimize that git-svn-clone operation by specifying the first Svn commit for

Re: Migration of remaining plugins to Git

I updated the page to mark in green the repos that are ready to migrate: just need the job to be done (with the help of infra, I suppose) with immediate one to one migration We can in parallel work on organizing more complex 1 to many migration plan Thank you for your help on this tedious work

Re: Migration of remaining plugins to Git

yes, git is really ubiquitous now and nowadays could perhaps help some contributions here is our tracking of git migration [1] there are a few entries that we could move if someone takes the job: Doxia core, Doxia Site Tools, Enforcer, Jxr, Plugin Tools, Release there are issues to fix when

Re: Migration of remaining plugins to Git

They are now adding user grouping... I wonder how long before repo grouping too On Sun 18 Jun 2017 at 17:12, Paul Hammant wrote: > Choose one to start with, is what I would do. > > git svn clone of a trunk only, then make that master. branch/tag history > can be retained in

Re: Migration of remaining plugins to Git

Hi, I am currently migrating many projects from sv to git, all of them are on the same svn repo. I am using tools like svn2git https://github.com/nirvdrum/svn2git These tools retain the full history, authors, branches and tags. I can give more info if needed Hope that helps Enrico Il dom 18

Re: Migration of remaining plugins to Git

Liable to get an answer like: > We don't comment our roadmap publicly I'm afraid (I've gotten that a couple of times for different things... you'd think given that I'm the maintainer of the GitHub Branch Source plugin for Jenkins they might - you know - want to help... but alas) On 18 June 2017

Releasing maven-reporting-impl 3.0

Hi, currently there are 13 issues solved and I would like to start with a release of no one objects on Tuesday... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

Il dom 18 giu 2017, 09:38 Tibor Digana ha scritto: > @Enrico > What "--add-modules ALL-SYSTEM" really does ? > For me it would be maybe a handy hack but for you it would be just a hack > anyway as it first seems. Strong encapsulation in Java9 can be openly > passed

Migration of remaining plugins to Git

In order to be able to build a composite 'trunk' for all components of maven (that are org.apache.*) can we move the remaining things left in Subversion to Git, and mirror them to Github? `git submodule` (etc) would be how we'd recreate a developer experience that felt like a single trunk that

Re: Migration of remaining plugins to Git

Am 2017-06-18 um 15:45 schrieb Paul Hammant: In order to be able to build a composite 'trunk' for all components of maven (that are org.apache.*) can we move the remaining things left in Subversion to Git, and mirror them to Github? `git submodule` (etc) would be how we'd recreate a developer

Re: New Branch (report real sys props of forked JVM) SUREFIRE-1360

Tibor, I have left a few comments on GitHub. Check the out. I'll run the ITs too here. Michael Am 2017-06-18 um 02:15 schrieb Tibor Digana: I have fixed https://issues.apache.org/jira/browse/SUREFIRE-1302 in branch