On Mon, Nov 2, 2015 at 9:55 AM, Pierre De Rop <pierre.de...@gmail.com> wrote: > Hello Benson; > > Currently only DependencyManager is using bndtools and gradle (and IIUC, > SCR will jump to bndtools soon). > > So, I propose that you first do a prototype with only all maven based sub > project and make also a jira issue that describes all the impacts, > including any impacts regarding the release process. Then I will look into > it and will help to see how to adapt DM.
OK. I am to some extent inclined to ask the PMC to reach a consensus, formally, on whether to do this at all. If the decision is to do it, then the prototype would be the first task. > > However, I think it would be worth to first read the new release process > used by DM in [1] (we are not using maven or the nexus staging repository > anymore, we are only simply using svn from the gradle script). > > FYI, the gradle script used to generate DM binaries is the one that is > generated by bndtools. The only specific gradle script we have done is: [2] > and is only used to make releases. The readme from [3] describes how to > make DM releases and how to use the script. > > [1] https://issues.apache.org/jira/browse/FELIX-4818 > [2] > http://svn.apache.org/viewvc/felix/trunk/dependencymanager/release/build.gradle > [3] > http://svn.apache.org/viewvc/felix/trunk/dependencymanager/release/README.release?view=log > > > cheers; > /Pierre > > On Mon, Nov 2, 2015 at 1:41 PM, Benson Margulies <bimargul...@gmail.com> > wrote: > >> I am a gradle idiot. Is someone else willing to help or at least give me >> some pointers? >> On Nov 2, 2015 7:24 AM, "Marcel Offermans" <marcel.offerm...@luminis.nl> >> wrote: >> >> > I would be more comfortable if we first had someone volunteer to adapt >> all >> > (Maven and Ant/Gradle based builds) to work with Git and otherwise ensure >> > that all projects keep working. Then demonstrate all of that (with a copy >> > of our repository), and update our documentation to reflect the new >> > processes before we decide on making such a move. I have a feeling this >> is >> > going to be a lot of work and it could break quite a few processes that >> we >> > currently have which is why I don’t think we should “just switch” and >> then >> > try to pick up the broken pieces. >> > >> > Greetings, Marcel >> > >> > On 31 October 2015 at 22:01:01 , Oliver Lietz (apa...@oliverlietz.de) >> > wrote: >> > >> > On Friday 30 October 2015 06:41:09 Benson Margulies wrote: >> > > On Fri, Oct 30, 2015 at 2:36 AM, Carsten Ziegeler < >> cziege...@apache.org> >> > wrote: >> > > > Am 30.10.15 um 01:48 schrieb Benson Margulies: >> > > >> Is this a consensus to proceed yet? It's been a few days since the >> > > >> last contribution. >> > > > >> > > > We clearly have different opinions, they range from "why change?", >> > > > "let's get moving" to "let's do more than a simple conversion". >> > > > I don't see a clear consensus/agreement on any of the three. For each >> > > > opinion there are imho good/valid arguments. I have the feeling that >> a >> > > > formal vote does not lead us anywhere. >> > > > >> > > > Maybe someone can clearly identify/list the benefits for everyone if >> we >> > > > move from svn to a single git repo - compared to using the already >> > > > existing git proxy. I think this should give everyone a clear view of >> > > > why the migration makes sense. And if there are no compelling reasons >> > > > then we have a decision as well. >> > > >> > > I think I can state some advantages: >> > > >> > > >> > > 1: Make it significantly easier to apply patches from people who >> > > provide them via github. >> > > >> > > 2: Make it significantly easier to create branches in the main repo >> > > for collaborative changes. >> > > >> > > 3: Take a first step towards subdividing into multiple repos where >> > > that makes sense. >> > >> > some more: >> > >> > https://issues.apache.org/jira/browse/SLING-3987 >> > >> > >> https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git >> > >> > Is there already a project at Apache which moved from Subversion to Git >> > setting up multiple repos or even a repo per release artifact? >> > >> > Regards, >> > O. >> > >> > > My sense of the email thread is that we have some enthusiastic >> > > supporters of moving to git, and some '+0' weak objectors. So, in some >> > > models of consensus process, that would be a reason to go ahead. Do >> > > you want to recast this as a VOTE as a way of clarifying views? >> > > >> > > > Carsten >> > > > -- >> > > > Carsten Ziegeler >> > > > Adobe Research Switzerland >> > > > cziege...@apache.org >> > >> > >>
