Hi Brett,
I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning
after downloading the m2-beta-3. It seems to be working fine except for
the fact that it is not including the jars for the modules nor their
dependencies. Maybe I am missing something here:
At first it was complaining about not being able to find the bin.xml
file in the modules. I put a bin.xml just into each one of them
containing the dependecySets with the output directory set exactly as it
is in the bin.xml that I am pasting below and it started to work but, as
I said, without anything from the modules.
Here is my root pom symplified:
<?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.carosys</groupId>
<artifactId>jeeves</artifactId>
<packaging>pom</packaging>
<version>1.0</version>
<name>Jeeves Care</name>
<organization>
<name>Caro Sys</name>
<url>http://www.carosys.com</url>
</organization>
<description>A system that is able to produce behaivoral trends as
well as point out certain health conditions out of the regular
activities of daily living of a person.</description>
<developers>
<!-- removed for simplicity -->
</developers>
<issueManagement>
<!-- removed for simplicity -->
</issueManagement>
<ciManagement>
<!-- removed for simplicity -->
</ciManagement>
<scm>
<!-- removed for simplicity -->
</scm>
<modules>
<module>jeeves-common</module>
<module>jeeves-hub</module>
</modules>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.0-beta-2-SNAPSHOT</version>
<configuration>
<descriptor>bin.xml</descriptor>
<finalName>jeeves-1.0-beta-1</finalName>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.8</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.4</version>
<type>jar</type>
<exclusions>
<!-- removed for simplicity -->
</exclusions>
</dependency>
</dependencies>
<repositories>
<!-- removed for simplicity -->
</repositories>
</project>
Here is the assembly descriptor.
<assembly>
<id>bin</id>
<formats>
<format>zip</format>
</formats>
<fileSets>
<fileSet>
<includes>
<include>README*</include>
<include>LICENSE*</include>
<include>NOTICE*</include>
</includes>
</fileSet>
<fileSet>
<!-- Resources from jeeves-hub-->
<directory>jeeves-hub/src/main/resources</directory>
<outputDirectory>resources</outputDirectory>
</fileSet>
<fileSet>
<!-- service-wrapper from jeeves-hub-->
<directory>jeeves-hub/service-wrapper</directory>
<outputDirectory>service-wrapper</outputDirectory>
</fileSet>
<fileSet>
<!-- bat files from jeeves-hub-->
<directory>jeeves-hub</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>*.bat</include>
</includes>
</fileSet>
<fileSet>
<!-- readme files from jeeves-hub-->
<directory>jeeves-hub</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>readme.*</include>
</includes>
</fileSet>
<fileSet>
<!-- xml files from jeeves-common-->
<directory>jeeves-common/src/main/resources</directory>
<outputDirectory>resources</outputDirectory>
<includes>
<include>common.properties</include>
<include>AlarmConfig.xml</include>
<include>NewAlarmConfig.xml</include>
</includes>
</fileSet>
</fileSets>
<dependencySets>
<dependencySet>
<outputDirectory>lib</outputDirectory>
</dependencySet>
</dependencySets>
</assembly>
Brett Porter wrote:
Tomorrow.
On 10/4/05, Erick Dovale <[EMAIL PROTECTED]> wrote:
When is the beta-3 goint to be realeased??
cheers,
erick.
Brett Porter wrote:
.. fixed in SVN for the beta-3 release.
On 10/3/05, Brett Porter <[EMAIL PROTECTED]> wrote:
It's a bug. The aggregator isn't forking the "package" goal first as it should.
I will fix it shortly.
- Brett
On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote:
Hi Brett,
I checked out the assembly plugin and was able to build it and deploy it
to my local repo. I also updated the version of the pluging in my root
pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built
plugin.
When I run the assembly plugin on my root pom it is behaiving
differently becasue before it was generating the zip for the root pom
first and then iterating over the rest of the modules; now its building
the zip last but it is not including the dependencies for the modules
nor it is including the modules them selves.
I am positive that I am missing something however, can figure it out my
self. Any hints??
cheers,
Erick.
Brett Porter wrote:
On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote:
What is this tag?
It indicates the plugin should not run over subprojects, but has
access to the reactor to perform an aggregating task.
How do I get my hands on the latest commited code?
See the instructions on the site for building frmo source for how to
obtain it. You can build the plugin itself with "m2 install" on that
plugin.
Is
it already deployed to the repo??
No.
I've been searching all over the place
looking for a class called:
org.apache.maven.plugins.assembly.model.Assembly which is te one that
gets instantiated out of the assembly descriptor but have been unable to
find it so far. Can you point me to it?
It is generated from assembly.mdo. If you do the build step above, it
will be in target/generated-sources.
I also took a look at
AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and
found no significant change since 2 days a go when I last looked at it.
It was not a signifcant change, just the addition of @aggregator.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
