I don't worry much about git. I don't care if a tag includes the entire repo with all the projects. What gives me s head ache is maven release plugin building a project which is not in the root dir of the git workspace.
Am 13. April 2015 12:18:57 MESZ, schrieb nino martinez wael <nino.martinez.w...@gmail.com>: >Yes currently we are for one of our projects. > >We do not currently have a "feature" design where you pull in branches >(from subprojects) to make a release for necessary releases. > >I see what you mean by releasing single projects within one git repo.. >I guess one of the problems also are that git repo revisions are being >messed with.. I think it would be alot better and more GIT clean using >a seperate repo per project.. > >WYDT? I am also quite busy currently. But as you, I can also read mails >:) > >regards > >On Mon, Apr 13, 2015 at 11:57 AM, Stephan Classen <sclas...@apache.org> >wrote: >> are you also managing multiple projects in a single git repo like we >do in >> onami? >> this was the major discussion point the last time. >> >> how can we release a single project (like lifecycle) and not release >all >> onami projects at once. >> >> I'm currently quite busy but if you want to discuss possible >approaches I >> should find enough time to read my mails >> >> Stephan >> >> >> >> >> On 04/12/2015 04:42 PM, nino martinez wael wrote: >>> >>> Hi Guys we've now setup and are using git together with maven, also >>> for release process at my company and are working just fine... >>> >>> So should we try do move just one subproject first or what do you >say? >>> >>> regards Nino >> >> > > > >-- >Best regards / Med venlig hilsen >Nino Martinez
