You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by BoD <Bo...@JRAF.org> on 2008/08/25 12:13:44 UTC
SCM dependencies?
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM dependencies?
Posted by BoD <Bo...@JRAF.org>.
Thanks a lot! :)
BoD
Geoffrey Wiseman wrote:
> On Mon, Aug 25, 2008 at 9:16 AM, Glase, Stefan
> <Stefan.Glase@opitz-consulting.de
> <ma...@opitz-consulting.de>> wrote:
>
> Hi,
>
> the free book "Maven - The definitive Guide" published by Sonatype
> has a nice chapter on this topic:
>
> http://www.sonatype.com/book/reference/multimodule.html
>
> Hope to help,
> Stefan
>
>
> Yes, that's what I would recommend as well, reasonable starting point.
> I would have included it in the first email, but was running low on
> time. ;)
>
> - Geoffrey
> --
> Geoffrey Wiseman
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM dependencies?
Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Mon, Aug 25, 2008 at 9:16 AM, Glase, Stefan <
Stefan.Glase@opitz-consulting.de> wrote:
> Hi,
>
> the free book "Maven - The definitive Guide" published by Sonatype has a
> nice chapter on this topic:
>
> http://www.sonatype.com/book/reference/multimodule.html
>
> Hope to help,
> Stefan
>
Yes, that's what I would recommend as well, reasonable starting point. I
would have included it in the first email, but was running low on time. ;)
- Geoffrey
--
Geoffrey Wiseman
AW: SCM dependencies?
Posted by "Glase, Stefan" <St...@opitz-consulting.de>.
Hi,
the free book "Maven - The definitive Guide" published by Sonatype has a nice chapter on this topic:
http://www.sonatype.com/book/reference/multimodule.html
Hope to help,
Stefan
-----Ursprüngliche Nachricht-----
Von: BoD [mailto:BoD@JRAF.org]
Gesendet: Montag, 25. August 2008 14:51
An: Maven Users List
Betreff: Re: SCM dependencies?
Thank you very much for your answer.
Ok let's say I'd like to try the first way (multi-module project,
project dependencies). Where should I start, to make a pom from an
existing project? (Do you know of a simple example, or a tutorial
somewhere for that particular case?)
Thanks!
BoD
Geoffrey Wiseman wrote:
> On Mon, Aug 25, 2008 at 6:13 AM, BoD <BoD@jraf.org
> <ma...@jraf.org>> wrote:
>
> 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?
>
>
> It's a bit of both. If you have a set of related projects that tend to
> have the same lifecycle, it's not uncommon to put them in a multi-module
> project. If you go that route, then it's very easy to check out the
> multi-module project, have Maven build an eclipse workspace, and use
> them such that a change in one module is automatically reflected in the
> other modules within eclipse (project dependencies instead of JAR
> dependencies).
>
> If, on the other hand, these are projects that aren't very tightly
> coupled, then you'd usually stick to JAR-style dependencies, although
> there may still be another way of making what you want happen. It
> sounds like the former case is closer to what you need, though.
>
> - Geoffrey
> --
> Geoffrey Wiseman
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM dependencies?
Posted by BoD <Bo...@JRAF.org>.
Thank you very much for your answer.
Ok let's say I'd like to try the first way (multi-module project,
project dependencies). Where should I start, to make a pom from an
existing project? (Do you know of a simple example, or a tutorial
somewhere for that particular case?)
Thanks!
BoD
Geoffrey Wiseman wrote:
> On Mon, Aug 25, 2008 at 6:13 AM, BoD <BoD@jraf.org
> <ma...@jraf.org>> wrote:
>
> 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?
>
>
> It's a bit of both. If you have a set of related projects that tend to
> have the same lifecycle, it's not uncommon to put them in a multi-module
> project. If you go that route, then it's very easy to check out the
> multi-module project, have Maven build an eclipse workspace, and use
> them such that a change in one module is automatically reflected in the
> other modules within eclipse (project dependencies instead of JAR
> dependencies).
>
> If, on the other hand, these are projects that aren't very tightly
> coupled, then you'd usually stick to JAR-style dependencies, although
> there may still be another way of making what you want happen. It
> sounds like the former case is closer to what you need, though.
>
> - Geoffrey
> --
> Geoffrey Wiseman
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM dependencies?
Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Mon, Aug 25, 2008 at 6:13 AM, BoD <Bo...@jraf.org> wrote:
> 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?
It's a bit of both. If you have a set of related projects that tend to have
the same lifecycle, it's not uncommon to put them in a multi-module
project. If you go that route, then it's very easy to check out the
multi-module project, have Maven build an eclipse workspace, and use them
such that a change in one module is automatically reflected in the other
modules within eclipse (project dependencies instead of JAR dependencies).
If, on the other hand, these are projects that aren't very tightly coupled,
then you'd usually stick to JAR-style dependencies, although there may still
be another way of making what you want happen. It sounds like the former
case is closer to what you need, though.
- Geoffrey
--
Geoffrey Wiseman