Got it.

My suggestion would be to create a plugin that uses the attachment mechanism for a set of JARs. build-helper might already do that.

eg..
<configuration>
  <artifacts>
    <artifact>
     <g/> <a/> <v/> <file />
    </artifact>
    ...
  </artifacts>
</configuration>

And in the plugin:

for ( Artifact a : artifacts ) { projectHelper.attachArtifact( a ); }

And then run:
mvn install
or
mvn deploy

All the attached artifacts will be shipped with it.

- Brett

On 11/08/2006 12:44 AM, Edelson, Justin wrote:
Let me start over...

The problem seems to be that there's no "good" way of installing or
deploying multiple 3rd party jars using a pom and, at least in the
current release of M2, the install:install-file goal doesn't work
properly within a pom.

I was perfectly content with using a shell script to do the deploy, but
that didn't seem to work for Dave Syer (he does a better job than I of
explaining his problem with this solution). As I said below, it did get
me thinking if there wasn't a need for a new packaging type. Even when
the install plugin is released with the fix to make install:install-file
usable within a pom, deploying multiple 3rd party jars using a pom will
still be extremely verbose. Unless I'm missing something, it requires a
new <execution> block for each jar. Twice in fact if you want to use
install as well as deploy.

As far as I know, this isn't something you can use assembly:unpack to
do.

Justin

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 11:38 PM
To: Maven Developers List
Subject: Re: Thread about automating install/deploy

Not quite sure which direction you are going here, but I'd recommend using the assembly plugin + its unpack goal to do this (shipping just the one big artifact around, and it can retain internal directory structure).

- Brett

On 10/08/2006 9:40 AM, Edelson, Justin wrote:
http://www.nabble.com/Automating-install%3Ainstall-file-t2071058.html

________________________________

From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wed 8/9/2006 6:35 PM
To: Maven Developers List
Subject: Re: Thread about automating install/deploy



What messages are you referring to?

On 10/08/2006 6:55 AM, Edelson, Justin wrote:
So hopefully I didn't turn off Mr. Syer entirely... but it did get me
thinking. Does Maven need a new packaging type to do what he's
talking
about?

Something like this...


<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0";
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
      <modelVersion>4.0.0</modelVersion>
      <groupId>com.mycompany.maven</groupId>
      <artifactId>3rdparty</artifactId>
      <packaging>3rdparty</packaging>
      <name>My Company's 3rdparty Jars</name>
      <version>1.0-SNAPSHOT</version>
      <build>
              <plugins>
                      <plugin>
<groupId>org.apache.maven.plugins</groupId> <artifactId>maven-3rdparty-plugin</artifactId>
                                      <configuration>
                                              <basedir>lib</basedir>
                                              <jarFiles>
                                                      <jarFile>
<generatePom>true</generatePom> <artifactId>jconnect</artifactId> <groupId>com.sybase</groupId> <version>5.5.EBF11656</version> <fileName>jConnect5.5.EBF11656.jar</fileName>
                                                      </jarFile>
                                                      <jarFile>
<generatePom>true</generatePom> <artifactId>jai-core</artifactId> <groupId>javax.media</groupId> <version>1.1.2</version> <fileName>jai-1.1.2/jai_core.jar</fileName>
                                                      </jarFile>
                                              </jarFiles>
                                      </configuration>
                                      <extensions>true</extensions>
                      </plugin>
              </plugins>
      </build>
</project>

This new packaging type is only configured for deploy and install
phases
(maybe verify as well).

Thoughts?

Although I'm perfectly happy with my shell scripts, I can see the
virtue
in doing this with a pom.

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


--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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







--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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

Reply via email to