Well it depends on the three libs....

I was just suggesting a more *maven* way of getting the pom's and the jars
into the repo.

if you add the dependencies to the other jars to the poms that you are
pushing, then depending on one will pull in its dependents

for example if jviewsall depends on both sdmgui and svgdom, all you need is
three poms like I had, e.g.

%basedir%/sdmgui/pom.xml

<project  xmlns="http://maven.apache.org/POM/4.0.0";>
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.ilog.jviews</groupId>
    <artifactId>sdmgui</artifactId>
    <version>5.5-SNAPSHOT</version>
    <description>JViews sdmgui library</description>
    <build>
      <plugins>
        <plugin>
          <artifactId>maven-jar-plugin</artifactId>
          <configuration>
            <forceCreation>true</forceCreation>
          </configuration>
        </plugin>
        <plugin>
          <artifactId>maven-antrun-plugin</artifactId>
          <executions>
            <execution>
              <phase>package</phase>
              <goals>
                <goal>run</goal>
              </goals>
              <configuration>
                <tasks>
                  <copy file="${basedir}/src/jar/${project.artifactId}"

tofile="${project.build.directory}/${project.build.finalName}"
                     overwrite="true"/>
                </tasks>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
</project>

%basedir%/svgdom/pom.xml

<project  xmlns="http://maven.apache.org/POM/4.0.0";>
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.ilog.jviews</groupId>
    <artifactId>svgdom</artifactId>
    <version>5.5-SNAPSHOT</version>
    <description>JViews svgdomlibrary</description>
    <build>
      <plugins>
        <plugin>
          <artifactId>maven-jar-plugin</artifactId>
          <configuration>
            <forceCreation>true</forceCreation>
          </configuration>
        </plugin>
        <plugin>
          <artifactId>maven-antrun-plugin</artifactId>
          <executions>
            <execution>
              <phase>package</phase>
              <goals>
                <goal>run</goal>
              </goals>
              <configuration>
                <tasks>
                  <copy file="${basedir}/src/jar/${project.artifactId}"

tofile="${project.build.directory}/${project.build.finalName}"
                     overwrite="true"/>
                </tasks>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
</project>


%basedir%/jviewsall/pom.xml

<project  xmlns="http://maven.apache.org/POM/4.0.0";>
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.ilog.jviews</groupId>
    <artifactId>jviewsall</artifactId>
    <version>5.5-SNAPSHOT</version>
    <dependencies>
      <dependency>
        <groupId>${project.groupId}</groupId>
        <artifactId>sdmgui</groupId>
        <version>${project.version}</version>
      </dependency>
      <dependency>
        <groupId>${project.groupId}</groupId>
        <artifactId>svgdom</groupId>
        <version>${project.version}</version>
      </dependency>
    </dependencies>

    <description>JViews sdmgui library</description>
    <build>
      <plugins>
        <plugin>
          <artifactId>maven-jar-plugin</artifactId>
          <configuration>
            <forceCreation>true</forceCreation>
          </configuration>
        </plugin>
        <plugin>
          <artifactId>maven-antrun-plugin</artifactId>
          <executions>
            <execution>
              <phase>package</phase>
              <goals>
                <goal>run</goal>
              </goals>
              <configuration>
                <tasks>
                  <copy file="${basedir}/src/jar/${project.artifactId}"

tofile="${project.build.directory}/${project.build.finalName}"
                     overwrite="true"/>
                </tasks>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
</project>

The aggregator pom would just be to help release all of them (as you would a
normal maven project)

i.e.

<project>
 ...
 <modules>
  <module>jviewsall</module>
  <module>svgdom</module>
  <module>sdmgui</module>
 </modules>
...
</project>

You would not depend on the aggregator
2008/11/6 jgarrison <[EMAIL PROTECTED]>

>
> Now I'm really confused.
>
> I have a lot of development experience (20+ years) but am a rank newbie
> when
> it comes to Maven, and I guess I don't understand your response.
>
> The original issue was with the aggregate POM, not sdmgui (or the other two
> libraries).  These are static 3rd party libraries that are always used
> together. I wanted to express this in a POM-packaging POM so that the
> client
> could state a dependency on a single POM and get all three libraries.  This
> may not sound like much of a benefit, but I have several other identical
> situations where there are dozens of libraries that form a dependency
> "set".
>
> --
> View this message in context:
> http://www.nabble.com/Aggregate-POM-for-thirdparty-package---dependencies-not-downloaded-tp20330421p20368015.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to