you need to define your scm url to a parent directory of your modules and add a
pom in this directory.
Hilco Wijbenga a écrit :
Our project consists of two modules (say, A and B) in CVS. Both are
necessary for the build and until we move to Subversion I don't have
the option of changing this
On 2/16/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
you need to define your scm url to a parent directory of your modules and add a
pom
in this directory.
Ah yes, module is a bit overloaded. :-) I was talking about *CVS*
modules. There is no parent directory...
I think you are stucked!!!
Can you refactor your build?
-D
On 2/16/07, Hilco Wijbenga [EMAIL PROTECTED] wrote:
On 2/16/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
you need to define your scm url to a parent directory of your modules
and add a pom
in this directory.
Ah yes, module is a
On 2/16/07, Dan Tran [EMAIL PROTECTED] wrote:
Can you refactor your build?
We've already been doing that for the last 3 months or so. It's not my
full time job, more a labour of love. :-) So it doesn't progress very
quickly (although we've managed to pull off some major improvements).
This 2
I got a very dirty solution for your. but I will be slow ;-)
create a dumy sub project in one of your sub module that know how too pull
the source of other module using maven-scm-plugin.
I did that a lot when during my migration of merging CVS and starteam into
SVN
-D
On 2/16/07, Hilco
Our project consists of two modules (say, A and B) in CVS. Both are
necessary for the build and until we move to Subversion I don't have
the option of changing this setup.
I don't see how I can check out both modules in Continuum. Or would
that be possible with a special SCM URL?
Obviously, I
