Details

      Description

      An interesting functionality for the Maven2 CARGO plug-in would be the following:

      1. The user enters all server information (connector URLs, user names, passwords, ...) in its settings.xml file
      2. When calling that server, it would only give the server name to CARGO and all options would be deduced automatically.

      An example:

      The Maven settings.xml file contains:

      ...
      <servers>
      <server>
      <id>jonas1</id>
      <configuration>
      <cargo.remote.uri>jmx://jonas1</cargo.remote.uri>
      <cargo.jonas.domain.name>jonas</cargo.jonas.domain.name>
      <cargo.remote.username>jonas</cargo.remote.username>
      <cargo.remote.password>jonas</cargo.remote.password>
      </configuration>
      </server>
      <server>
      <id>jonas2</id>
      <configuration>
      <cargo.remote.uri>jmx://jonas2</cargo.remote.uri>
      <cargo.jonas.domain.name>jonas</cargo.jonas.domain.name>
      <cargo.remote.username>jonas</cargo.remote.username>
      <cargo.remote.password>jonas</cargo.remote.password>
      </configuration>
      </server>
      <servers>
      ...

      In this case, the following configuration in a pom.xml file:

      ...
      <plugin>
      <groupId>org.codehaus.cargo</groupId>
      <artifactId>cargo-maven2-plugin</artifactId>
      <version>1.0-SNAPSHOT</version>
      <configuration>
      <container>
      <containerId>jonas4x</containerId>
      <type>remote</type>
      </container>
      <configuration>
      <type>runtime</type>
      <properties>
      <cargo.jonas.server.name>jonas1</cargo.jonas.server.name>
      <cargo.jonas.domain.name>jonas</cargo.jonas.domain.name>
      </properties>
      </configuration>
      </configuration>
      </plugin>
      ...

      would automatically be "expanded" into:

      ...
      <plugin>
      <groupId>org.codehaus.cargo</groupId>
      <artifactId>cargo-maven2-plugin</artifactId>
      <version>1.0-SNAPSHOT</version>
      <configuration>
      <container>
      <containerId>jonas4x</containerId>
      <type>remote</type>
      </container>
      <configuration>
      <type>runtime</type>
      <properties>
      <cargo.remote.uri>jmx://jonas1</cargo.remote.uri>
      <cargo.remote.username>jonas</cargo.remote.username>
      <cargo.remote.password>jonas</cargo.remote.password>
      <cargo.jonas.server.name>jonas1</cargo.jonas.server.name>
      <cargo.jonas.domain.name>jonas</cargo.jonas.domain.name>
      </properties>
      </configuration>
      </configuration>
      </plugin>
      ...

      I'm attaching the patch to the Maven plug-in to achieve the functionality

        Gliffy Diagrams

          Attachments

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                savasalitokmen Savas Ali Tokmen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: