Cargo

Run Cargo on a Parent POM

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.0.3
  • Component/s: Maven2
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Would it be possible to enable support for running cargo goal on a parent pom and then running the goal on each of the child modules. At the moment it fails as the parent does not have a cargo plugin definition.

The new module should be able to silently ignore any modules without a cargo configuration.

The goal would succeed if there was at least one module which succeeeded.

Paul

Issue Links

relates to

New Feature - A new feature of the product, which has yet to be developed. CARGO-481 Add a <skip> configuration element that allows you to skip plugin's execution

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Savas Ali Tokmen added a comment -

Can you please elaborate how this would work?

Show
Savas Ali Tokmen added a comment - Can you please elaborate how this would work?
Hide
Permalink
Paul Austin added a comment - - edited

I have found a solution.

In the parent pom.xml I add the following property to the configuration of the cargo plugin.

 <skip>${skipWebDeploy}</skip>

The I add the following property to the same pom.

<properties>
  <skipWebDeploy>true</skipWebDeploy>
</properties>

I each module that I want to deploy I add the following property.

<properties>
  <skipWebDeploy>false</skipWebDeploy>
</properties>

Then I can run the cargo redeploy mojo on the top level project and it will ignore any modules that don't set the skip to false.

Show
Paul Austin added a comment - - edited I have found a solution. In the parent pom.xml I add the following property to the configuration of the cargo plugin. <skip>${skipWebDeploy}</skip> The I add the following property to the same pom. <properties> <skipWebDeploy>true</skipWebDeploy> </properties> I each module that I want to deploy I add the following property. <properties> <skipWebDeploy>false</skipWebDeploy> </properties> Then I can run the cargo redeploy mojo on the top level project and it will ignore any modules that don't set the skip to false.
Hide
Permalink
Savas Ali Tokmen added a comment -

Nice workaround Closing this issue, then.

Show
Savas Ali Tokmen added a comment - Nice workaround Closing this issue, then.
Hide
Permalink
Anders Hammar added a comment -

Well, I'd say it's not a very nice Maven solution IMO although it works. A much better solution would be to configure the cargo plugin in pluginManagement in the parent pom with skip true. Then in those projects you actually want to use cargo you configure the cargo plugin in the pluginManagement but with skip false. And you could also add any appropriate configuration (any generic configuration should go in the parent pom).
Using properties is a little bit too much developer style than Maven style.
Yet another solution would be to have a separate module (or even possibly a profile in the top project), where cargo is configured to deploy the artifacts that you want to deploy. You would then execute cargo in that module (or that profile) after all projects have been built. A separate module would be similar the approach for setting up an automated integration test of your apps.

Show
Anders Hammar added a comment - Well, I'd say it's not a very nice Maven solution IMO although it works. A much better solution would be to configure the cargo plugin in pluginManagement in the parent pom with skip true. Then in those projects you actually want to use cargo you configure the cargo plugin in the pluginManagement but with skip false. And you could also add any appropriate configuration (any generic configuration should go in the parent pom). Using properties is a little bit too much developer style than Maven style. Yet another solution would be to have a separate module (or even possibly a profile in the top project), where cargo is configured to deploy the artifacts that you want to deploy. You would then execute cargo in that module (or that profile) after all projects have been built. A separate module would be similar the approach for setting up an automated integration test of your apps.
Hide
Permalink
Paul Austin added a comment -

I actually define the plugin with a profilem which has an execution on it so it runs with install

So I can build and deploy my whole site with a single command.

mvn -P tomcat7Deploy,localhost clean install

or just to deploy

mvn -P tomcat7Deploy,localhost cargo:deployer-redeploy

With this you can create "virtual" parent poms (that aren't the actual parent) that have all the modules you want to deploy.

With the other approach it would be a lot more verbose and complex for others to use (I have this available for other related modules to use that wouldn't be smart enough not to screw things up).

Show
Paul Austin added a comment - I actually define the plugin with a profilem which has an execution on it so it runs with install So I can build and deploy my whole site with a single command. mvn -P tomcat7Deploy,localhost clean install or just to deploy mvn -P tomcat7Deploy,localhost cargo:deployer-redeploy With this you can create "virtual" parent poms (that aren't the actual parent) that have all the modules you want to deploy. With the other approach it would be a lot more verbose and complex for others to use (I have this available for other related modules to use that wouldn't be smart enough not to screw things up).

People

  • Assignee:
    Anders Hammar
    Reporter:
    Paul Austin
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: