i see, i had a similar issue. projects are independent and should not
'reach into' each other.
to use common stuff, jar them up in one project, install them into
your repo, then in the other projects you can add as a dependency or
use the unpack goal of the dependency plugin to explode them into
This variable is set for several different modules to use the same common
base for tests files. So '.' would assume that I am copying them over to
each module in my tree. When there is actually only one copy.
On Dec 14, 2007 7:30 AM, Tomislav Stojcevich <[EMAIL PROTECTED]> wrote:
> Can't you jus
Can't you just use . for "current directory" instead of a variable?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No one can help me out here?
On Dec 13, 2007 5:56 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> In my normal Manen build, I have a variable called MyProject_HOME set to *
> C:\opt\MyProject* and I use that throughout my build. Now I want to
> understand where to set that in order to still run Con
In my normal Manen build, I have a variable called MyProject_HOME set to *
C:\opt\MyProject* and I use that throughout my build. Now I want to
understand where to set that in order to still run Continuum?
Am I going to set a another system variable to *
/opt/contiuum/workingDirectory/*
--
Tha
