RE: order of the unpacking from \"unpack-dependencys\"

[David Bräutigam <da...@googlemail.com>]

Hi I have the following unpack goal:

<execution>
                <id>unpack-modules</id>
                <phase>verify</phase>
                <goals>
                  <goal>unpack-dependencies</goal>
                </goals>
                <configuration>

<outputDirectory>${basedir}/target/dist_tmp/classes</outputDirectory>
                  <includeGroupIds>${project.groupId}</includeGroupIds>
                  <includeClassifiers>classes</includeClassifiers>
                  <includeTypes>jar</includeTypes>
                  <includeScope>runtime</includeScope>
                  <excludeTransitive>true</excludeTransitive>
                  <includes>**/*.class</includes>
                  <excludes>META-INF/**,com/atomikos/**</excludes>
                </configuration>
</execution>

The identification works with the group id. The solution with a separate
unpack per module would be possible.

But I would prefer that the "unpack-dependencies" uses the order in which i
define the dependency's. This would prevent further problems as mentioned by
Michael.

But what puzzles me is that the unpack order seams arbitrary but fixed.
Maybe i should as in the developer mailing list for an deeper insight of the
matter.

Regards David