[#RIO-278] Rio Mojos should avoid being executed if they are not the root project

Rio

Rio Mojos should avoid being executed if they are not the root project

Created: 30/Jul/10 09:20 PM Updated: 02/Aug/10 04:03 PM

Component/s:

Maven Plugin

Affects Version/s:

4.0

Fix Version/s:

4.1

Time Tracking:

Not Specified

Description

« Hide

In the case of a multi-module project, the Rio mojos (oar, deploy, undeploy, start, stop, ui, cybernode and monitor) should first check to see if the project being executed is the execution root. This will avoid cascading executions.

The classdepandjar mojo will not check, this will allow modules within a multi-module project to use the classdepandjar mojo when being built by it's parent(s)

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Dennis Reedy added a comment - 30/Jul/10 10:03 PM

The oar mojo will not check to see if the project being executed is the execution root, this will allow modules within a multi-module project to use the oar mojo when being built by it's parent(s).

The Oar mojo will check if the configured opstring file exists, if not log a debug message and return