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
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
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
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 jgl...@cloudbees.com wrote:
On 09/13/2012 10:16 AM, Kristian Rosenvold wrote:
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
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
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
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
Hi,
2012/9/14 Kristian Rosenvold kristian.rosenv...@gmail.com:
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
2012/9/14 Olivier Lamy ol...@apache.org:
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
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
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
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
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.
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
15 matches
Mail list logo
