Hi all - I'm using maven-assembly-plugin to create zip distributions of
our web application. It takes in the Apache Tomcat zip artifact, and the
war artifact for the app, and creates an assembly.
There are a couple of file operations I haven't figured out how to do yet.
For example, Tomcat unzips
here is current state:
- using github link does fix web access in modules problems: see actual
3.1.1staging [1]
- with MPIR-291, branches and tags are supported: "git clone --branch "
instructions are generated
- with MPIR-290, I did a hack to remove module path from git clone
instructions
with
What do you think happened? Is this a change in the remote resources plugin?
On Sep 10, 2013, at 11:33 AM, Daniel Kulp wrote:
>
> -1
>
> The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE
> files. This is a regression from 3.1.0 (and 3.0.5). That definitely need
The Apache Maven team is pleased to announce the release of the Apache
Maven Install Plugin, version 2.5
The Install Plugin is used during the install phase to add artifact(s) to
the local repository.
http://maven.apache.org/plugins/maven-install-plugin/
You should specify the version in y
On 10 September 2013 17:16, sebb wrote:
> On 10 September 2013 16:33, Daniel Kulp wrote:
> >
> > -1
> >
> > The src.tar.gz and src.zip files have lost their top level NOTICE and
> LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That
> definitely needs to be fixed. I don't have t
On Sep 10, 2013, at 12:16 PM, sebb wrote:
> On 10 September 2013 16:33, Daniel Kulp wrote:
>>
>> -1
>>
>> The src.tar.gz and src.zip files have lost their top level NOTICE and
>> LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That
>> definitely needs to be fixed. I don't h
On Sep 10, 2013, at 12:04 PM, Jason van Zyl wrote:
> What do you think happened? Is this a change in the remote resources plugin?
No…. in the old releases, they were named LICENSE.txt and NOTICE.txt (txt
extension) which is not how the RR plugin would have ever generated them. This
is a sour
On Sun, 8 Sep 2013 09:07:33 -0400
Jason van Zyl wrote:
+1 (none-binding)
works fine for some mojo projects + nuiton.org and chorem.org projects.
thanks,
tony.
> Hi,
>
> Here is a link to Jira with 6 issues resolved:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version
-1
The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE
files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs
to be fixed. I don't have time today to look into that, but might tomorrow if
someone doesn't beat me to it.
Ran a couple builds with
On 10 September 2013 16:33, Daniel Kulp wrote:
>
> -1
>
> The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE
> files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs
> to be fixed. I don't have time today to look into that, but might tomorrow
>
On Sep 10, 2013, at 10:11 AM, Jason van Zyl wrote:
>
> On Sep 10, 2013, at 9:58 AM, sebb wrote:
>
>> Which as I have argued all along is insufficient.
>> - the vote email does not have vital information "for the record"
>> - indeed in the case of this vote, neither the vote e-mail nor the
>>
On 10 September 2013 15:11, Jason van Zyl wrote:
>
> On Sep 10, 2013, at 9:58 AM, sebb wrote:
>
>> On 10 September 2013 14:23, Jason van Zyl wrote:
>>>
>>> On Sep 10, 2013, at 7:53 AM, sebb wrote:
>>>
I've just realised that you said the hash is in the maven core jar.
That is a binary
On Sep 10, 2013, at 9:58 AM, sebb wrote:
> On 10 September 2013 14:23, Jason van Zyl wrote:
>>
>> On Sep 10, 2013, at 7:53 AM, sebb wrote:
>>
>>> I've just realised that you said the hash is in the maven core jar.
>>> That is a binary artifact, and has no direct relationship with the
>>> sou
Hi,
Here is a link to Jira with 6 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968
Staging repo:
https://repository.apache.org/content/repositories/maven-016/
https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven
Let's continue with the vote, the binaries are still good. I will send another
message with a new email template for posterity.
On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote:
> Hi,
>
> Here is a link to Jira with 6 issues resolved:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectI
On 10 September 2013 14:23, Jason van Zyl wrote:
>
> On Sep 10, 2013, at 7:53 AM, sebb wrote:
>
>> I've just realised that you said the hash is in the maven core jar.
>> That is a binary artifact, and has no direct relationship with the
>> source artifact on which people are supposed to be voting
On Sep 10, 2013, at 7:53 AM, sebb wrote:
> I've just realised that you said the hash is in the maven core jar.
> That is a binary artifact, and has no direct relationship with the
> source artifact on which people are supposed to be voting.
>
It is supposed to be the SHA1 of the release from w
Sure, I can remake the email, but the binaries are fine. I made a little tool
for myself and I'll just use the template from the website.
The SHA1 I took was for the release which is the value that's interpolated into
the build.properties.
On Sep 9, 2013, at 3:56 PM, Stephen Connolly
wrote:
+1
Den 8. sep. 2013 15:08 skrev "Jason van Zyl" følgende:
> Hi,
>
> Here is a link to Jira with 6 issues resolved:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-016/
>
> The distribu
I've just realised that you said the hash is in the maven core jar.
That is a binary artifact, and has no direct relationship with the
source artifact on which people are supposed to be voting.
I don't think it's possible to tie the SCM tag to this vote thread
"for the record" without the hash (an
Hi,
>
whereas in Maven 3.1 the following two integration tests fail:
this must be Maven 3.1.1 ...sorry...;-)
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177
Hi,
in relationship with the Maven 3.1.1 vote
I have found an interessting thing:
* maven-dependency-plugin (trunk: r1521365):
Maven 3.0.5:
The following integration tests have been skipped:
[INFO] Building: purge-local-repository-reresolve/pom.xml
[INFO] ..SKIPPED
[INFO] Building: purge-local-
+1 [non-binding]
Tested with
* appassembler-maven-plugin (trunk: r18705)
* maven-invoker-plugin (trunk: r1521365),
* iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e
https://github.com/khmarbaise/iterator-maven-plugin),
* several of my own projects worked like a charm.
On
23 matches
Mail list logo
