clean scm:update|deploy on a parent POM, modules?

[Michael Hüttermann <mi...@huettermann.net>]

Hello,

I have the following structure

/root/moduleA/
/root/moduleB/
/root/moduleC/

and the following CruiseControl snippet (I skipped the "time" and
"mvnhome"-attributes here):

<maven2 pomfile="/root/moduleB/pom.xml" goal="clean scm:update|deploy/>
(the issue is not depending on CruiseControl though)

The addressed /root/moduleB/pom.xml is of package type POM referencing a
bunch of other modules especially
/root/moduleA/ and
/root/moduleC/

/root/moduleB/pom.xml also contains the elements
<scm><connection>...</connection><developerConnection>...</developerConnection><url>...</url>.
The connection references the /root/ in my Subversion. I checked out the
/root/ from Subversion to my build machine including ./moduleA, ./moduleB,
./moduleC to do a "mvn deploy" after updating the sources there.

So with other words, before running a "mvn deploy" I want to update my
whole root level /root/* on the build machine with all its modules.

Unfortunately it looks like the modules are not updated accordingly. With
my setting, obviously only the /root/moduleB/ is updated. Is this
possible? How can I customize the setting that /root/ is updated
completely ?

Thanks for your time!

Best regards
Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: clean scm:update|deploy on a parent POM, modules?

[Michael Hüttermann <mi...@huettermann.net>]

or with other words: how can I update a checked out folder completely
before calling a "mvn deploy" on a single module inside the whole
structure? Alternatively: how can I checkout a complete folder before?
Doing an update or a checkout is not a difference here. What is the
recommended way? As explained below .. there are some pitfalls ..

Thanks !!

Michael


> Hello,
>
> I have the following structure
>
> /root/moduleA/
> /root/moduleB/
> /root/moduleC/
>
> and the following CruiseControl snippet (I skipped the "time" and
> "mvnhome"-attributes here):
>
> <maven2 pomfile="/root/moduleB/pom.xml" goal="clean scm:update|deploy/>
> (the issue is not depending on CruiseControl though)
>
> The addressed /root/moduleB/pom.xml is of package type POM referencing a
> bunch of other modules especially
> /root/moduleA/ and
> /root/moduleC/
>
> /root/moduleB/pom.xml also contains the elements
> <scm><connection>...</connection><developerConnection>...</developerConnection><url>...</url>.
> The connection references the /root/ in my Subversion. I checked out the
> /root/ from Subversion to my build machine including ./moduleA, ./moduleB,
> ./moduleC to do a "mvn deploy" after updating the sources there.
>
> So with other words, before running a "mvn deploy" I want to update my
> whole root level /root/* on the build machine with all its modules.
>
> Unfortunately it looks like the modules are not updated accordingly. With
> my setting, obviously only the /root/moduleB/ is updated. Is this
> possible? How can I customize the setting that /root/ is updated
> completely ?
>
> Thanks for your time!
>
> Best regards
> Michael
>
>
> ---------------------------------------------------------------------
> 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