-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
On Thu, Oct 21, 2010 at 3:17 PM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
uh, oh. We depend on being able to specify that as empty too. I hope
this gets fixed before it starts affecting my builds.
However,
On Thu, Oct 21, 2010 at 1:40 PM, Phillip Hellewell ssh...@gmail.com wrote:
I just found out the hard way that the latest version of the assembly
plugin requires an id tag in the descriptor file, which is used as
the classifier appended to the zip.
I don't want to specify an id here because
-Original Message-
From: Wendy Smoak [mailto:wsm...@gmail.com]
On Thu, Oct 21, 2010 at 1:40 PM, Phillip Hellewell ssh...@gmail.com
wrote:
I just found out the hard way that the latest version of the assembly
plugin requires an id tag in the descriptor file, which is used as
the
On Mon, Oct 25, 2010 at 11:07 AM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
I was finally able to test this with the 2.2 release version, and it
fails for me too, so I created a issue in Jira: MASSEMBLY-517.
Thanks Eric. Now I don't have to create it :)
Phillip
I'll add comments but I don't think this is a bug.
On Mon, Oct 25, 2010 at 4:23 PM, Phillip Hellewell ssh...@gmail.com wrote:
On Mon, Oct 25, 2010 at 11:07 AM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
I was finally able to test this with the 2.2 release version, and it
fails for me
On Mon, Oct 25, 2010 at 1:07 PM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
-Original Message-
From: Wendy Smoak [mailto:wsm...@gmail.com]
Have you tried setting appendAssemblyId to false?
No, that doesn't help, but thanks for the suggestion.
How so? If id is required (and this
A simple scan of the release notes reveals this was introduced
intentionally by MASSEMBLY-464
On Mon, Oct 25, 2010 at 4:58 PM, Wendy Smoak wsm...@gmail.com wrote:
On Mon, Oct 25, 2010 at 1:07 PM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
-Original Message-
From: Wendy Smoak
Just to be clear, it's been a long-standing bug that the assembly id was
NOT required. It's always been the intention to require that element.
That's why we provided the appendAssemblyId/ configuration element, to
give the user control over whether that id is used to form the
coordinate for
do not alter or disrupt this transmission. thank you
Date: Mon, 25 Oct 2010 17:24:01 -0400
From: jdca...@commonjava.org
To: users@maven.apache.org
Subject: Re: Classifier now required by assembly plugin
Just to be clear, it's been a long-standing bug that the assembly id was
NOT required
I just found out the hard way that the latest version of the assembly
plugin requires an id tag in the descriptor file, which is used as
the classifier appended to the zip.
I don't want to specify an id here because then means I have to
specify a classifier in the dependency section of my other
On Thu, Oct 21, 2010 at 11:40 AM, Phillip Hellewell ssh...@gmail.com wrote:
I just found out the hard way that the latest version of the assembly
plugin requires an id tag in the descriptor file, which is used as
the classifier appended to the zip.
I don't want to specify an id here because
-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
On Thu, Oct 21, 2010 at 11:40 AM, Phillip Hellewell ssh...@gmail.com
wrote:
I just found out the hard way that the latest version of the assembly
plugin requires an id tag in the descriptor file, which is used as
the
On Thu, Oct 21, 2010 at 3:17 PM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
uh, oh. We depend on being able to specify that as empty too. I hope this
gets fixed before it starts affecting my builds.
However, are you sure this is really an issue? I just tried one of my builds
which
13 matches
Mail list logo
