Re: Jenkins and Maven 3.0.5 or JDK 7

+1 On Sun, Oct 8, 2017 at 12:02 AM, Tibor Digana wrote: > I don't think the devs would work on all artifacts(projects) a time. > If the naming convention of repo for a plugin would be artifactId, like > /maven-clean-plugin, then even easy to figure out which one to

Re: migrating some code to Git

+1 to create INFRA jira issue to switch following 6 components from svn to the current git mirror: - Doxia core - Doxia Sitetools - Enforcer - Jxr - Plugin Tools - Release On Sat, Oct 7, 2017 at 10:35 PM, Arnaud Héritier wrote: > +1 > > Can you share the script ? > > On

Re: Jenkins and Maven 3.0.5 or JDK 7

Is it usual to need all dozen repositories or is a single repository (or a handful) more likely? Chas > On Oct 7, 2017, at 1:32 PM, Arnaud Héritier wrote: > > AFAIR the main concern was for developers to have to clone several dozen of > repositories > I don't think it is

Re: Jenkins and Maven 3.0.5 or JDK 7

TLDR; = Perhaps we can start with 2 proofs of concept: 1. full git clone + Jenkins jobs for the 7 existing git repos (with 6 additional ones in 2 days) 2. git split of one of the aggregator svn trunk: skins or doxia-tools can be easy choices since they are light, where plugins or shared are

Re: migrating some code to Git

trying as attachment: hope this will be kept by the ML usually, only the first variable "MAVEN_REPO=xxx" has to be changed, but Doxia components required a little tweak on the next 2 variables "SVNBASE=" and "GITREPO=" Regards, Hervé Le samedi 7 octobre 2017, 22:35:07 CEST Arnaud Héritier a

Re: Jenkins and Maven 3.0.5 or JDK 7

I don't think the devs would work on all artifacts(projects) a time. If the naming convention of repo for a plugin would be artifactId, like /maven-clean-plugin, then even easy to figure out which one to clone. The most likely the dev would just clone one repo she/he is interested in at the

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.0

Hi Hervé, On 07/10/17 13:50, Hervé BOUTEMY wrote: IIUC, Mikail Osipov (mosi...@gmx.de) is the usual Michael Osipov on the PMC :) I wasn't aware of that nor have I found any evidence of that... Thanks for clearing up...That's fine... Kind regards Karl Heinz Marbaise then with you and me,

[RESULT] [VOTE] Release Apache Maven WAR Plugin version 3.2.0

Hi, The vote has passed with the following result: +1 : Mikail Osipov (Michael Osipov), Dejan Stojadinović, Baptiste Mathus, Hervé Boutemy, Karl-Heinz Marbaise PMC quorum: reached I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise

Re: Jenkins and Maven 3.0.5 or JDK 7

thanks for your interest and feedback Le samedi 7 octobre 2017, 12:00:32 CEST Tibor Digana a écrit : > 78 is too much. notice that there would also be a question on the git repos naming convention, to avoid flat 78 names but keep at least 3 meaningful groups (plugins, shared, resources: I think

Re: Jenkins and Maven 3.0.5 or JDK 7

In my company I have such situation in SVN. Making a tag from subfolder. Git always makes the tag from the root, right? Let's google something... On Sat, Oct 7, 2017 at 2:47 PM, Tibor Digana wrote: > In my company I have such situation. > Making a tag from

Re: Jenkins and Maven 3.0.5 or JDK 7

In my company I have such situation. Making a tag from subfolder. Git always makes the tag from the root, right? Let's google something... On Sat, Oct 7, 2017 at 2:05 PM, Hervé BOUTEMY wrote: > thanks for your interest and feedback > > Le samedi 7 octobre 2017, 12:00:32

Re: Jenkins and Maven 3.0.5 or JDK 7

Herve, I think making the tag as I wanted would not be possible in git. Let's make it with all 78 projects. In 2016 I migrated my svn project "audit" located in sub-folder behind trunk (trunk/libs/audit) to git which is exactly what we need to do in ASF. In our case the commands would be 99% the

Re: Jenkins and Maven 3.0.5 or JDK 7

Herve, I think, first of all, we should write a list with exact names of git repositories for which INFRA will crate them in git1-us-west.apache.org/repos/asf and mirror in github.com/apache And then the authors.txt. In my case I did not migrate tags and branches which is my problem given in my

Re: Jenkins and Maven 3.0.5 or JDK 7

78 is too much. There is no problem to trigger release over sub-folders and tag it with prefix which is already done in SVN. The CI build can always trigger the root and Jenkinsfile would have 41 stages for plugins, 26 stages for Shared, etc. It can be done in Jenkinsfile and so the shell would

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.0

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 30/09/17 17:55, Karl Heinz Marbaise wrote: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12341372 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.0

IIUC, Mikail Osipov (mosi...@gmx.de) is the usual Michael Osipov on the PMC :) then with you and me, we have the 3 PMC votes, isn't it? Regards, Hervé Le samedi 7 octobre 2017, 13:07:09 CEST Karl Heinz Marbaise a écrit : > Hi, > > there is missing one PMC vote ? > > Kind regards > Karl Heinz

Re: migrating some code to Git

I wrote a little shell script to check differences between tags in svn and git checkout the only differences I found for the 6 git repos are: 1. empty dirs (which exist in svn but are pruned in git) 2. one strage case in enforcer-1.2 where a few files seem to have newlines issues to me, this

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.0

Hi, there is missing one PMC vote ? Kind regards Karl Heinz Marbaise On 30/09/17 17:55, Karl Heinz Marbaise wrote: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12341372 There are still a couple of issues left in JIRA:

Re: Jenkins and Maven 3.0.5 or JDK 7

Le samedi 7 octobre 2017, 14:48:32 CEST Tibor Digana a écrit : > In my company I have such situation in SVN. Making a tag from subfolder. > Git always makes the tag from the root, right? it looks like git can tag a subfolder: https://github.com/apache/maven-plugins/tree/maven-war-plugin-3.2.0

Re: Jenkins and Maven 3.0.5 or JDK 7

we can start with naming the future git repos: I suppose adding a table at the end of the Git migration Wiki page can give a good view of the result (with 78 new repos + existing 7 repos + the 6 in migration if nobody objects = 91 repos) once we're all convinced of the target, we'll see how to

Re: Jenkins and Maven 3.0.5 or JDK 7

On Fri, Oct 6, 2017 at 10:52 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On Fri 6 Oct 2017 at 16:47, Arnaud Héritier wrote: > > > I agree that we should use pipeline nowdays > > perhaps a shared lib if we want to standardize some stuffs and a set of > >

Re: Jenkins and Maven 3.0.5 or JDK 7

On Sat, Oct 7, 2017 at 4:17 AM, Hervé BOUTEMY wrote: > There are 6 svn locations without any special complexity that are waiting > for > a volunteer for git migration for a few years but nobody does anything > about: > I started 3 days ago to ask for help about it and got

Re: Jenkins and Maven 3.0.5 or JDK 7

Nothing avoids to have a big git repo with many independent projects but yes it will tag everything in the repo (not really a problem). Same thing when we create a branch. Tibor I did a script similar to yours in the past: https://gist.github.com/aheritier/8824148 (ok it is a bit complex :-) ) I

Re: Jenkins and Maven 3.0.5 or JDK 7

+1 On Sat, Oct 7, 2017 at 7:11 PM, Hervé BOUTEMY wrote: > we can start with naming the future git repos: I suppose adding a table at > the > end of the Git migration Wiki page can give a good view of the result > (with 78 > new repos + existing 7 repos + the 6 in

Re: Jenkins and Maven 3.0.5 or JDK 7

What are the concerns with separate git repository per artifact? Is it the monolithic build? Chas > On Oct 7, 2017, at 1:20 PM, Arnaud Héritier wrote: > > +1 > >> On Sat, Oct 7, 2017 at 7:11 PM, Hervé BOUTEMY wrote: >> >> we can start with

Re: Jenkins and Maven 3.0.5 or JDK 7

AFAIR the main concern was for developers to have to clone several dozen of repositories I don't think it is a real issue. We can share a script to do it easily On Sat, Oct 7, 2017 at 10:26 PM, Chas Honton wrote: > What are the concerns with separate git repository per

Re: migrating some code to Git

+1 Can you share the script ? On Sat, Oct 7, 2017 at 12:32 PM, Hervé BOUTEMY wrote: > I wrote a little shell script to check differences between tags in svn and > git > checkout > the only differences I found for the 6 git repos are: > 1. empty dirs (which exist in svn