Hi,
I have a general question about maven.
I've used maven in the past at a company where I used to work. The way
we used it was I think pretty typical, we had a few libraries the
project depended on, and we generated a few reports, etc.
In my current company, we use a custom (internal) tool, which has, I
think, a lot in common with maven, the problem being of course that it
is *not* maven :) Ie, there is no documentation, no maintenance, etc.
There are also a few problems with it, that's why I was wondering if we
could entirely replace this tool with maven, and I have a few questions
I hope you guys can help me with.
The main difference I see is that our custom tool handles "scm"
dependencies. What I mean by that is that we have our project which is
split in several "modules" and they all have their own life on
subversion, and we say for example that the project is on
svn://svn/project1/trunk and it depends on svn://svn/module1/trunk and
on svn://svn/module2/branches/v2.
Then when we "bootstrap" the project, the tool will checkout these two
modules, and generate an eclipse workspace, with one project by module,
and the "team" plugin setup as needed for the project and its dependencies.
So a developer can work on the project itself, but if he finds a problem
on a dependency he can also work on it! He has the sources and can
commit, etc.
When I used to work with maven, we only had "jar" dependencies, ie, the
project depended on "built" versions of some module (external or
internal), which is a bit different.
So my question is, is this kind of "scm" dependency possible with maven?
Thank you very much.
BoD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
