Mmmm, this solution would deploy all the artifacts to the same repository (the one that is "active" at the moment). I'd actually need to deploy the various _classes_ of artifacts (sources, javadoc, etc.) to different repositories...

Thanks for the moment,
 L

Giancarlo Degani ha scritto:
Maybe you can try with a specific profile for each type of artifact/repository.
Something like this :

<project...
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.mycompany</groupId>
  <artifactId>multirepo</artifactId>
  <packaging>jar</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>multirepo</name>
      <distributionManagement>
            <repository>
            <id>archiva.internal</id>
            <name>Internal Release Repository</name>
            ...
        </repository>
        <snapshotRepository>
            <id>archiva.snapshots</id>
            <name>Internal Snapshot Repository</name>
           ...
        </snapshotRepository>
    </distributionManagement

  <profiles>
      <profile>
          <id>repo1</id>
      <distributionManagement>
            <repository>
            <id>archiva.internal2</id>
            <name>Internal Release Repository</name>
            ...
        </repository>
        <snapshotRepository>
            <id>archiva.snapshots2</id>
            <name>Internal Snapshot Repository</name>
            ...
        </snapshotRepository>
    </distributionManagement>

      </profile>
  </profiles>
</project>

When the repo1 profile is enabled the default repository  (
archiva.internal ) will be replaced by archiva.internal2 as you can
see using mvn help:effective-pom.

Hope this can help.

Best regards

Giancarlo


2008/7/17 Ing. Lorenzo Bigagli <[EMAIL PROTECTED]>:
Dear all,

our policy requires different artifacts (jars, sources, javadocs, etc.) to
be deployed to possibly different repos.
I guess this is possible through deploy:deploy-file, but I would actually
like to encode such policy in profiles, so that everything is more
streamlined and easy for the programmers.

For example, I'd like to have a profile that deploy:
- the jar to repo A, along with the javadocs
- the sources to repo B

Anybody can provide me with an example of how such a profile would look
like?
Would such an arrangement be compatible with using the release plugin for
deployment?

Hope you can help, thanks,
 LB

--
Ing. Lorenzo Bigagli
Ordine degli Ingegneri della Provincia di Prato
Sez. A, n.552

i: Via Enrico Mayer 5, 59100 Prato (PO), Italia
c: +39 335 8078555
f: +39 0574 602524
m: [EMAIL PROTECTED]



--
Dott. Lorenzo Bigagli
PIN - Polo Universitario di Prato
dell'Università di Firenze

i: Piazza dell'Università
  59100 Prato (PO), Italia
t: +39 0574 602535
f: +39 0574 602524
m: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to