Re: Proposal for new git-workspace-plugin

[Baptiste MATHUS]

Maybe a look would be interesting at the "Repo" tool created by Google for
Android. And I'm sure I read that the tool was created with the idea of
having no adherence towards Android itself.

Not sure that's usable for Maven use-cases as-is, and I like the idea of
having a Maven plugin that would do the magic Maven-style. But there might
be ideas in repo we want to look at.

My 2 cents.
Cheers
Le 18 sept. 2012 02:42, "Mark Derricutt"  a écrit :

> Different style of beast.
>
> This is more downloading sources of defined modules that are related to a
> project and automatically generating a maven reactor build for them all (
> afaict ).
>
> Essentially working around the brain-dead git-submodules system which
> seems very geared towards source dependencies vs binary-artifacts of maven.
>
> On 18/09/2012, at 11:45 AM, Chris Graham  wrote:
>
> > Does the m2e plugin already do this? I've seen it download sources of
> deps.
> > Or are we talking about something different here?
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Proposal for new git-workspace-plugin

[Mark Derricutt]

Different style of beast.

This is more downloading sources of defined modules that are related to a 
project and automatically generating a maven reactor build for them all ( 
afaict ).

Essentially working around the brain-dead git-submodules system which seems 
very geared towards source dependencies vs binary-artifacts of maven.

On 18/09/2012, at 11:45 AM, Chris Graham  wrote:

> Does the m2e plugin already do this? I've seen it download sources of deps.
> Or are we talking about something different here?


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Chris Graham]

Does the m2e plugin already do this? I've seen it download sources of deps.
Or are we talking about something different here?

-Chris

On Tue, Sep 18, 2012 at 4:23 AM, Jesse Glick  wrote:

> On 09/13/2012 10:16 AM, Kristian Rosenvold wrote:
>
>> https://cwiki.apache.org/**confluence/display/MAVEN/git-**
>> workspace-plugin
>>
>
> Interesting. I had a thought a while ago for an IDE to help you with
> similar tasks [1] but having it as a Maven plugin would arguably be better,
> especially if user interaction can be kept to a minimum.
>
> [1] 
> http://netbeans.org/bugzilla/**show_bug.cgi?id=198781
>
>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Proposal for new git-workspace-plugin

[Jesse Glick]

On 09/13/2012 10:16 AM, Kristian Rosenvold wrote:

https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin


Interesting. I had a thought a while ago for an IDE to help you with similar tasks [1] but having it as a Maven plugin would arguably be better, especially if user 
interaction can be kept to a minimum.


[1] http://netbeans.org/bugzilla/show_bug.cgi?id=198781


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Kristian Rosenvold]

That would be the idea, yes (not sure if we need to fork lifecycles
though). Get the "trunk" of any given plugin and have all dependencies
checked out and compiled at trunk too seems to be the default mode of
operation.

As for source, there is none, we're still cooking the ideas. But I
expect to start coding something soon ;)

Kristian



2012/9/16 Mark Derricutt :
> A thought...
>
> If I run "mvn clean install" from the top-level pom containing the 
> git-workspace-plugin, are we intending to fork each of those lifecycles in 
> reactor-resolved-order for all the modules in the git-workspace?
>
> That would be uber-awesome.
>
> On 14/09/2012, at 2:16 AM, Kristian Rosenvold  
> wrote:
>
>> I have just added wiki document to discuss the design of a totally new
>> plugin I have dubbed the "git-workspace-plugin".
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Mark Derricutt]

A thought...

If I run "mvn clean install" from the top-level pom containing the 
git-workspace-plugin, are we intending to fork each of those lifecycles in 
reactor-resolved-order for all the modules in the git-workspace?

That would be uber-awesome.

On 14/09/2012, at 2:16 AM, Kristian Rosenvold  
wrote:

> I have just added wiki document to discuss the design of a totally new
> plugin I have dubbed the "git-workspace-plugin".
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Mark Derricutt]

Kristian,

I'm liking where you're heading with this plugin - is there any working code 
one can play with currently at all?

I'm currently going thru the process of breaking up our large git-multi-module 
repository to smaller repos, and this looks to be a godsend already.  ( we also 
use git-flow for our branching setup, so would be good to give it a bash with 
that...



On 14/09/2012, at 2:16 AM, Kristian Rosenvold  
wrote:

> I have just added wiki document to discuss the design of a totally new
> plugin I have dubbed the "git-workspace-plugin".
> 
> The idea is to change the way we work with layered multi-module
> projects in git that will make it a whole lot easier for anyone
> wishing to make a change to do so.
> 
> The page is at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> and I would really appreciate any kind of feedback on this.
> 
> Feel free to edit the page, I will also keep it up to date ;)
> 
> Kristian
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Kristian Rosenvold]

2012/9/14 Olivier Lamy :
> As far I can see most git beginners use git as they use svn. (hey do
> you remember when you started git and fully break your local clone
> trying to merge some local branches: don't say to me it never happened
> :-) )

I crashed and burned. Badly. Multiple times.

> So our maven tooling must be accessible for the mass (sure extra
> options for geek/nerds is always welcome :-) ) and be operational for
> basic/daily stuff of majority of dev folks.
>>
>> As can be seen from the wiki, I am somewhat at loss for a good
>> branchless solution. I think the best solution is probably to support
>> "trunk only" when running branchless, effectively
>> just move all the checked out dependencies to SNAPSHOT and use trunk
>> for everything. I think we can call it svn mode ;)
> Yup again we must try to build the most generic plugin for most used
> scm (sure better to concentrate efforts on most populars: svn and
> git).

I think it's really ok to default to "trunk" mode (maybe unless you're
checking out a tag of the main project) it's the one feature I
remember very clearly I would've enjoyed the first time I (ever) tried
to change something in maven.

I remember the first time I checked out maven source code quite
clearly, I was checking out repositories like crazy and building just
more and more dependencies until I finally managed to find the one
thing I was interested in. At the time it felt like I had built half
the known universe of components before I reached my goal ;)
(And they all have similar-sounding names; hey; didn't I check out
archiver-archiver just 10 minutes ago ???)

Of course, workspace-plugin would keep the pom changes in the
top-level project as a separate commit, so it doesn't mess up the
actual changeset in the end. (We could support a "patch" command too)

Just my 50 Øre (0.5 Norwegian kroner, recently deprecated).

Kristian

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Olivier Lamy]

Hi,

2012/9/14 Kristian Rosenvold :
> I updated the docs at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> to include a branch/branchless strategy.
>
> A branch based strategy is real badass if you're comfortable with
> branches. Arguably most git n00bs are not used to a version control
> system with a well functioning branch concept, so a branchless mode of
> operation is required.
Yup that's cool and IMHO could be the default option.
My personnal opinion on that.
As far I can see most git beginners use git as they use svn. (hey do
you remember when you started git and fully break your local clone
trying to merge some local branches: don't say to me it never happened
:-) )
So our maven tooling must be accessible for the mass (sure extra
options for geek/nerds is always welcome :-) ) and be operational for
basic/daily stuff of majority of dev folks.
>
> As can be seen from the wiki, I am somewhat at loss for a good
> branchless solution. I think the best solution is probably to support
> "trunk only" when running branchless, effectively
> just move all the checked out dependencies to SNAPSHOT and use trunk
> for everything. I think we can call it svn mode ;)
Yup again we must try to build the most generic plugin for most used
scm (sure better to concentrate efforts on most populars: svn and
git).

IMHO we have a generic tool for building daily operations which must
not be focused only on the current "à la mode" scm.

And btw some maven projects (I don't want to be focused on tools only
for Apache Maven sources) will continue to use for long dependencies
with some mix of scm.

My 0.02 euros.

>
> Kristian
>
> 2012/9/13 Kristian Rosenvold :
>> IntelliJ would work very happily with just a pom file aggregating pom;
>> which in this case would be just a modules list. The only problem
>> reaIly is that  I have to put it in a subfolder, since "there can be
>> only one" (Highlander).
>>
>> I'm sure we could generate multiple output formats for the aggregating
>> project, does not eclipse have native pom support too ?
>>
>> Kristian  (Only touches eclipse with pitcfork)
>>
>> 2012/9/13 Jason van Zyl :
>>> You may want to look at PSF files in Eclipse if you want to leverage an 
>>> existing format.
>>>
>>> http://wiki.eclipse.org/PSF
>>>
>>> On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:
>>>
 Hi,
 This idea looks nice :-).
 I imagine you will retrieve scm locations of dependencies from their poms.
 In such case dependencies can be a mix of scm (git, svn, hg etc..)
 So I would prefer we try to do something more generic to provide such
 features for all scms we support with maven scm (hey we have a very
 generic scm api :-) ).
 Maybe it's the case and just the plugin name confuse me :-).

 2012/9/13 Kristian Rosenvold :
> I have just added wiki document to discuss the design of a totally new
> plugin I have dubbed the "git-workspace-plugin".
>
> The idea is to change the way we work with layered multi-module
> projects in git that will make it a whole lot easier for anyone
> wishing to make a change to do so.
>
> The page is at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> and I would really appreciate any kind of feedback on this.
>
> Feel free to edit the page, I will also keep it up to date ;)
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



 --
 Olivier Lamy
 Talend: http://coders.talend.com
 http://twitter.com/olamy | http://linkedin.com/in/olamy

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>>
>>> Simplex sigillum veri. (Simplicity is the seal of truth.)
>>>
>>>
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Kristian Rosenvold]

I updated the docs at
https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
to include a branch/branchless strategy.

A branch based strategy is real badass if you're comfortable with
branches. Arguably most git n00bs are not used to a version control
system with a well functioning branch concept, so a branchless mode of
operation is required.

As can be seen from the wiki, I am somewhat at loss for a good
branchless solution. I think the best solution is probably to support
"trunk only" when running branchless, effectively
just move all the checked out dependencies to SNAPSHOT and use trunk
for everything. I think we can call it svn mode ;)

Kristian

2012/9/13 Kristian Rosenvold :
> IntelliJ would work very happily with just a pom file aggregating pom;
> which in this case would be just a modules list. The only problem
> reaIly is that  I have to put it in a subfolder, since "there can be
> only one" (Highlander).
>
> I'm sure we could generate multiple output formats for the aggregating
> project, does not eclipse have native pom support too ?
>
> Kristian  (Only touches eclipse with pitcfork)
>
> 2012/9/13 Jason van Zyl :
>> You may want to look at PSF files in Eclipse if you want to leverage an 
>> existing format.
>>
>> http://wiki.eclipse.org/PSF
>>
>> On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:
>>
>>> Hi,
>>> This idea looks nice :-).
>>> I imagine you will retrieve scm locations of dependencies from their poms.
>>> In such case dependencies can be a mix of scm (git, svn, hg etc..)
>>> So I would prefer we try to do something more generic to provide such
>>> features for all scms we support with maven scm (hey we have a very
>>> generic scm api :-) ).
>>> Maybe it's the case and just the plugin name confuse me :-).
>>>
>>> 2012/9/13 Kristian Rosenvold :
 I have just added wiki document to discuss the design of a totally new
 plugin I have dubbed the "git-workspace-plugin".

 The idea is to change the way we work with layered multi-module
 projects in git that will make it a whole lot easier for anyone
 wishing to make a change to do so.

 The page is at
 https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
 and I would really appreciate any kind of feedback on this.

 Feel free to edit the page, I will also keep it up to date ;)

 Kristian

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> --
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>>
>> Simplex sigillum veri. (Simplicity is the seal of truth.)
>>
>>
>>
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Kristian Rosenvold]

IntelliJ would work very happily with just a pom file aggregating pom;
which in this case would be just a modules list. The only problem
reaIly is that  I have to put it in a subfolder, since "there can be
only one" (Highlander).

I'm sure we could generate multiple output formats for the aggregating
project, does not eclipse have native pom support too ?

Kristian  (Only touches eclipse with pitcfork)

2012/9/13 Jason van Zyl :
> You may want to look at PSF files in Eclipse if you want to leverage an 
> existing format.
>
> http://wiki.eclipse.org/PSF
>
> On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:
>
>> Hi,
>> This idea looks nice :-).
>> I imagine you will retrieve scm locations of dependencies from their poms.
>> In such case dependencies can be a mix of scm (git, svn, hg etc..)
>> So I would prefer we try to do something more generic to provide such
>> features for all scms we support with maven scm (hey we have a very
>> generic scm api :-) ).
>> Maybe it's the case and just the plugin name confuse me :-).
>>
>> 2012/9/13 Kristian Rosenvold :
>>> I have just added wiki document to discuss the design of a totally new
>>> plugin I have dubbed the "git-workspace-plugin".
>>>
>>> The idea is to change the way we work with layered multi-module
>>> projects in git that will make it a whole lot easier for anyone
>>> wishing to make a change to do so.
>>>
>>> The page is at
>>> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
>>> and I would really appreciate any kind of feedback on this.
>>>
>>> Feel free to edit the page, I will also keep it up to date ;)
>>>
>>> Kristian
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> Simplex sigillum veri. (Simplicity is the seal of truth.)
>
>
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Kristian Rosenvold]

We will definitely be using the scm locations from the POM, combined
with some dark magics on resolving where the project is located (think
maven-plugins with multiple projects sharing the same root). Mark has
tried explaining this algorithm on irc several times, but my eyes go
watery every time. This time I suppose I'll have to find out ;=)

The problem I see with supporting multiple different SCMs is that at
some point their model breaks down, and at some point quite
fundamentally. Let me get into a very subtle detail:

When you have multiple top-level project sharing "plexus-utils" and
you run a command like "mvn git-snapshot plexus-utils" (inside
surefire) I think what really needs to be done is "git checkout -tb
surefire-snapshot origin/master"; in other words we create a branch
that represents the changes done in context of surefire. When you run
the corresponding "mvn git-snapshot plexus-utils" inside the
"maven-jar-plugin", you probably create a branch for the changes in
context of jar-plugin. If you do that, you can basically be in a
position to ALWAYS be able to switch contexts (I can resume working on
my jar-plugin changes while being in mid-progress on the surefire
changes). You can just auto-commit and change branch

The clue here is that this is the "plexus-utils" clone will have one
branch tracking head for each top-level project, as well as the master
branch from asf. Now this is the stuff git is built for; I can pick
changes between the branches like cherries from an autumn tree.

The only way I can map this onto subversion involves making a number
of distinct checkouts of the same project (tags, trunk and feature
branches); I think this is a receipe for disaster. So while I should
be able to check out svn projects, I'm afraid the feature set of the
plugin I want to make is not very adaptable/valuable in svn.

We *will* of course use maven-scm; and I'm sure the smart people here
will come up with some models that allow this plugin to be useful for
svn too ;)  I'm sure we'd work well with  hg.

Since no code has been written yet, we're free to call it what we want ;)

I added a section on GITHUB support to the end of the wiki page

Kristian


2012/9/13 Olivier Lamy :
> Hi,
> This idea looks nice :-).
> I imagine you will retrieve scm locations of dependencies from their poms.
> In such case dependencies can be a mix of scm (git, svn, hg etc..)
> So I would prefer we try to do something more generic to provide such
> features for all scms we support with maven scm (hey we have a very
> generic scm api :-) ).
> Maybe it's the case and just the plugin name confuse me :-).
>
> 2012/9/13 Kristian Rosenvold :
>> I have just added wiki document to discuss the design of a totally new
>> plugin I have dubbed the "git-workspace-plugin".
>>
>> The idea is to change the way we work with layered multi-module
>> projects in git that will make it a whole lot easier for anyone
>> wishing to make a change to do so.
>>
>> The page is at
>> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
>> and I would really appreciate any kind of feedback on this.
>>
>> Feel free to edit the page, I will also keep it up to date ;)
>>
>> Kristian
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

[Jason van Zyl]

You may want to look at PSF files in Eclipse if you want to leverage an 
existing format.

http://wiki.eclipse.org/PSF

On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:

> Hi,
> This idea looks nice :-).
> I imagine you will retrieve scm locations of dependencies from their poms.
> In such case dependencies can be a mix of scm (git, svn, hg etc..)
> So I would prefer we try to do something more generic to provide such
> features for all scms we support with maven scm (hey we have a very
> generic scm api :-) ).
> Maybe it's the case and just the plugin name confuse me :-).
> 
> 2012/9/13 Kristian Rosenvold :
>> I have just added wiki document to discuss the design of a totally new
>> plugin I have dubbed the "git-workspace-plugin".
>> 
>> The idea is to change the way we work with layered multi-module
>> projects in git that will make it a whole lot easier for anyone
>> wishing to make a change to do so.
>> 
>> The page is at
>> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
>> and I would really appreciate any kind of feedback on this.
>> 
>> Feel free to edit the page, I will also keep it up to date ;)
>> 
>> Kristian
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
> 
> 
> 
> -- 
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

Simplex sigillum veri. (Simplicity is the seal of truth.)

Re: Proposal for new git-workspace-plugin

[Olivier Lamy]

Hi,
This idea looks nice :-).
I imagine you will retrieve scm locations of dependencies from their poms.
In such case dependencies can be a mix of scm (git, svn, hg etc..)
So I would prefer we try to do something more generic to provide such
features for all scms we support with maven scm (hey we have a very
generic scm api :-) ).
Maybe it's the case and just the plugin name confuse me :-).

2012/9/13 Kristian Rosenvold :
> I have just added wiki document to discuss the design of a totally new
> plugin I have dubbed the "git-workspace-plugin".
>
> The idea is to change the way we work with layered multi-module
> projects in git that will make it a whole lot easier for anyone
> wishing to make a change to do so.
>
> The page is at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> and I would really appreciate any kind of feedback on this.
>
> Feel free to edit the page, I will also keep it up to date ;)
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Proposal for new git-workspace-plugin

[Kristian Rosenvold]

I have just added wiki document to discuss the design of a totally new
plugin I have dubbed the "git-workspace-plugin".

The idea is to change the way we work with layered multi-module
projects in git that will make it a whole lot easier for anyone
wishing to make a change to do so.

The page is at
https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
and I would really appreciate any kind of feedback on this.

Feel free to edit the page, I will also keep it up to date ;)

Kristian

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org