help with moving cargo settings to profiles.xml or ~/.m2/settings.xml

[Julian Dunn-2]

I'm a release manager and have Cargo working with M2 with a profile
within my POM, like this:

  <profiles>
    <profile>
      <id>jcdtest</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <configuration>
              <configuration>
                <type>runtime</type>
                <properties>
                 
<cargo.tomcat.manager.url>http://www.dev.nm.cbc.ca:6041/manager/</cargo.tomcat.manager.url>
                 
<cargo.remote.username>manager</cargo.remote.username>
                 
<cargo.remote.password>XXXXXXXDELETED</cargo.remote.password>
                </properties>
              </configuration>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

If I try to move this to my settings.xml (so that developers don't get
to see the passwords), Maven explodes with this:

Error reading settings.xml: Unrecognised tag: 'build' (position:
START_TAG seen ...</id>\n      <build>... @59:14)
  Line:   59
  Column: 14

Seems that Maven can understand <build> as a child of <profile> within
the POM only. Does this make any sense? How can I fix this?

- Julian

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Adrian Cole]

try this...

replace the following:

    <cargo.remote.password>XXXXXXXDELETED</cargo.remote.password>

with

    <cargo.remote.password>${cargo.password}</cargo.remote.password>

and set this in your settings.xml

   <properties>
      <cargo.password>msdadsad</cargo.password>
   </properties>

On Wed, Apr 15, 2009 at 5:11 PM, Julian Dunn <Julian.Dunn@...> wrote:

>
> I'm a release manager and have Cargo working with M2 with a profile
> within my POM, like this:
>
>  <profiles>
>    <profile>
>      <id>jcdtest</id>
>      <build>
>        <plugins>
>          <plugin>
>            <groupId>org.codehaus.cargo</groupId>
>            <artifactId>cargo-maven2-plugin</artifactId>
>            <configuration>
>              <configuration>
>                <type>runtime</type>
>                <properties>
>
> <cargo.tomcat.manager.url>http://www.dev.nm.cbc.ca:6041/manager/</cargo.tomcat.manager.url>
>
> <cargo.remote.username>manager</cargo.remote.username>
>
> <cargo.remote.password>XXXXXXXDELETED</cargo.remote.password>
>                </properties>
>              </configuration>
>            </configuration>
>          </plugin>
>        </plugins>
>      </build>
>    </profile>
>  </profiles>
>
> If I try to move this to my settings.xml (so that developers don't get
> to see the passwords), Maven explodes with this:
>
> Error reading settings.xml: Unrecognised tag: 'build' (position:
> START_TAG seen ...</id>\n      <build>... @59:14)
>  Line:   59
>  Column: 14
>
> Seems that Maven can understand <build> as a child of <profile> within
> the POM only. Does this make any sense? How can I fix this?
>
> - Julian
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Julian Dunn-2]

Thanks -- that (or a variation of that) worked.

I wonder why the Maven developers removed this functionality. Looks
like my newly-purchased Maven book (the Sonatype one) needs a rewrite of
Chapter 11...

- Julian
 
>>> Adrian Cole <ferncam1@...> 04/15/09 11:16 AM >>>
try this...

replace the following:

    <cargo.remote.password>XXXXXXXDELETED</cargo.remote.password>

with

    <cargo.remote.password>${cargo.password}</cargo.remote.password>

and set this in your settings.xml

   <properties>
      <cargo.password>msdadsad</cargo.password>
   </properties>

On Wed, Apr 15, 2009 at 5:11 PM, Julian Dunn <Julian.Dunn@...>
wrote:

>
> I'm a release manager and have Cargo working with M2 with a profile
> within my POM, like this:
>
>  <profiles>
>    <profile>
>      <id>jcdtest</id>
>      <build>
>        <plugins>
>          <plugin>
>            <groupId>org.codehaus.cargo</groupId>
>            <artifactId>cargo-maven2-plugin</artifactId>
>            <configuration>
>              <configuration>
>                <type>runtime</type>
>                <properties>
>
>

<cargo.tomcat.manager.url>http://www.dev.nm.cbc.ca:6041/manager/</cargo.tomcat.manager.url>

>
> <cargo.remote.username>manager</cargo.remote.username>
>
> <cargo.remote.password>XXXXXXXDELETED</cargo.remote.password>
>                </properties>
>              </configuration>
>            </configuration>
>          </plugin>
>        </plugins>
>      </build>
>    </profile>
>  </profiles>
>
> If I try to move this to my settings.xml (so that developers don't

get
> to see the passwords), Maven explodes with this:
>
> Error reading settings.xml: Unrecognised tag: 'build' (position:
> START_TAG seen ...</id>\n      <build>... @59:14)
>  Line:   59
>  Column: 14
>
> Seems that Maven can understand <build> as a child of <profile>
within
> the POM only. Does this make any sense? How can I fix this?
>
> - Julian
>
>
---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email