I reported this to Mevenide and should be fixed in future versions. A work
around is to lock down the assembly version you are using:
...
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.1</version>
<executions>
...
Maven does not require all artifact-specifying attributes for plugins like
it does with normal dependencies. Whether the beta version of the assembly
plugin is a bug or not, remains to be seen. It could simply be a side
effect of configuration changes. And by not providing it with its required
configuration, it does this.
I hope they will fix automatic plugin resolution to exclude beta editions
somehow.
Ravi
[EMAIL PROTECTED] wrote on 05/11/2007 11:47:50 AM:
> On 5/5/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
> > <snip/>
> > However, if the same XML is used with Maven 2.0.6, an "extra"
directory
> > is created having the name of the packed "zip" source:
> >
> > root / eclipsePlugins / uimaj-ep-debug-2.1.0-incubating.zip /
> > org.apache.uima.debug.2.1.0.incubating / etc.
> > <******** extra directory **********>
> >
> >
> > Is this a bug, or do we need to change something when moving to 2.0.6?
> > Did the version of "assembly" plugin change when moving from Maven
2.0.4
> > to 2.0.6?
> >
>
> I think I may have traced this problem back to version 2.2-beta1 of
> the Maven assembly plugin. It appears to create these extra
> directories when unpacking zip files from dependencySets, whereas
> version 2.1 did not.
>
> Does anyone know if this is an expected change in behavior of the
> assembly plugin, or a bug?
>
> -Adam
>
> ---------------------------------------------------------------------
> 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]
