Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Arnaud Heritier, Olivier Lamy
+1 (non binding): Nicolas Deloof, Barrie Treloar
I will promote the artifacts to the central repo.
-
To unsubscri
+1
--
Olivier
2009/6/13 Barrie Treloar :
> The vote is still missing some binding numbers, currently there are:
>
> +1 (binding): Benjamin Bentmann, Arnaud Heritier
> +1 (non binding): Nicolas Deloof, Barrie Treloar
>
> -
> To uns
The vote is still missing some binding numbers, currently there are:
+1 (binding): Benjamin Bentmann, Arnaud Heritier
+1 (non binding): Nicolas Deloof, Barrie Treloar
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
On Wed, Jun 10, 2009 at 8:31 PM, Vincent
Siveton wrote:
> 2009/6/9, nicolas de loof :
>> +1
>> Could we move the assembly plugin configuration to the plugins parent /
>> apache-release profile for future plugin releases to conform ASF rules ?
>
> I tried to add it on Doxia, and I think we need to
2009/6/9, nicolas de loof :
> +1
> Could we move the assembly plugin configuration to the plugins parent /
> apache-release profile for future plugin releases to conform ASF rules ?
I tried to add it on Doxia, and I think we need to add this stuff in
the release profile.
The more important thin
+1
Could we move the assembly plugin configuration to the plugins parent /
apache-release profile for future plugin releases to conform ASF rules ?
2009/6/8 Arnaud HERITIER
> +1Thanks a lot for your help
>
> Arnaud
>
> On Mon, Jun 8, 2009 at 10:30 PM, Benjamin Bentmann <
> benjamin.bentm...@udo.
On Tue, Jun 9, 2009 at 6:00 AM, Benjamin
Bentmann wrote:
> Barrie Treloar wrote:
>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-008/
>
> +1
>
>> Staging site:
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7/
>
> The staging site refers to plugin v
+1Thanks a lot for your help
Arnaud
On Mon, Jun 8, 2009 at 10:30 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Barrie Treloar wrote:
>
> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-008/
>>
>
> +1
>
> Staging site:
>> http://maven.apache.org/p
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-008/
+1
Staging site:
http://maven.apache.org/plugins/maven-eclipse-plugin-2.7/
The staging site refers to plugin version 2.8-SNAPSHOT. Just keep in
mind to deploy the final site from the
(source-release should be correct now)
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11133&resolu
On Sun, Jun 7, 2009 at 10:15 PM, Benjamin
Bentmann wrote:
> Barrie Treloar wrote:
>
>> * Added source-release assembly
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-006/
>
> It appears the source-release packages are missing the LICENSE and NOTICE
> files [
Barrie Treloar wrote:
* Added source-release assembly
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-006/
It appears the source-release packages are missing the LICENSE and
NOTICE files [0].
The descriptor you copied isn't fully worked out yet. For a plugin,
Ok here are the steps I took:
Copied
https://svn.apache.org/repos/asf/maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml
to src/assemble/
Modified pom to include
maven-assembly-plugin
Note:
* Changed wording of index.html as per Arnaud suggestion.
* Added source-release assembly
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/
If you need an example, you can look at what I did for the ant tasks [1]. The
same assembly should work fine for the eclipse plugin. You probably just want
to make minor changes for any files that do/don't exist.
[1]http://svn.apache.org/repos/asf/maven/ant-tasks/tags/maven-ant-tasks-2.0.10/s
My understanding of the problems that are being had with the assembly stuff
is around releasing multi-module projects (e.g. surefire, enforcer). If all
you are releasing is a single module (e.g. maven-eclipse-plugin), then
assembly does exactly what you want right now.
The issue that John and Bri
Seriously just use the assembly plugin to zip up the source folder,
excluding target. There are several examples in the related threads.
On Thu, Jun 4, 2009 at 5:04 PM, Arnaud HERITIER wrote:
> I thought we needed to have a fix in the assembly plugin to be able to
> release with ASF rules.If we
I thought we needed to have a fix in the assembly plugin to be able to
release with ASF rules.If we can do it with just some local changes in our
pom, we have to do it.
However I agree with Barry and we cannot loose too many time to do the
release.
Is there someone who can help us to setup the ecl
On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox wrote:
> On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
> benjamin.bentm...@udo.edu> wrote:
>
>> Arnaud HERITIER wrote:
>>
>> I think there's no value to block all releases, waiting for this fix.I
>>> agree, support this change, but it won't help ou
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Arnaud HERITIER wrote:
>
> I think there's no value to block all releases, waiting for this fix.I
>> agree, support this change, but it won't help our users to have them
>> waiting
>> all our releases for sev
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them waiting
all our releases for several weeks.
I don't really understand why fixing a project to produce a proper
source bundle (e.g.
I believe adding the previous assembly plugin release with:
src
is sufficient for our plugins. The purpose of the updated plugin is to
make it possible to put that in a parent POM without generating
unwanted assemblies and ensuring the content is correct rather than
duplicating the abo
On Jun 3, 2009, at 4:36 PM, Barrie Treloar wrote:
On Thu, Jun 4, 2009 at 8:54 AM, David Jencks
wrote:
On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
To be conform with ASF requirements, I understand that we have to
wait the
new assembly plugin to be able to produce the new sources di
On Thu, Jun 4, 2009 at 8:54 AM, David Jencks wrote:
>
> On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
>
>> To be conform with ASF requirements, I understand that we have to wait the
>> new assembly plugin to be able to produce the new sources distro. There
>> are
>> already 3 or 4 attempts to
On Jun 3, 2009, at 3:55 PM, Arnaud HERITIER wrote:
To be conform with ASF requirements, I understand that we have to
wait the
new assembly plugin to be able to produce the new sources distro.
There are
already 3 or 4 attempts to vote the release and it's not yet ended.
I think also that oth
To be conform with ASF requirements, I understand that we have to wait the
new assembly plugin to be able to produce the new sources distro. There are
already 3 or 4 attempts to vote the release and it's not yet ended.
I think also that others ASF projects using Maven won't wait for this fix if
the
On Thu, Jun 4, 2009 at 7:18 AM, Benjamin Bentmann
wrote:
> Barrie Treloar wrote:
>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-staging-005/
>
> -1
>
> As far as I understand the recent discussions about proper releases [0] and
> the current docs [1], we are require
The new assembly plugin makes it trivially easy to have the release
profile build the source distro, which is really amazingly nice.
However you can easily have a separate profile to run an earlier
assembly plugin to construct just the required source distro and run
it with -N so it only r
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them waiting
all our releases for several weeks.
We are doing it like that (yes badly) for a long time now. Thus I don't
think that one or two releases will change
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-005/
-1
As far as I understand the recent discussions about proper releases [0]
and the current docs [1], we are required to provide "a source package,
which must be sufficient for a user to
+1
Just a remark about the note on the home page. I think it's better to say
that "Starting at version 2.6, *by default,* the generated .classpath now
includes "... And you can add a link on the page which explains how to
change it.
Arnaud
Cheers,
Arnaud
# Arnaud Héritier
# http://blog.aheriti
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&styleName=Html&version=15130
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11133&resolution=-1&sorter/field=updated&sorter/orde
32 matches
Mail list logo
