Result 3 +1 (including mine)
will proceed with the release
On Mon, Jul 21, 2008 at 8:53 AM, John Casey [EMAIL PROTECTED] wrote:
+1
Carlos Sanchez wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
Couldn't we setup a custom profile for QA checks (pmd, checkstyle, clirr
...) that we activate in a separate project in the CI server ?
It's what I begin to do at work. The advantage is to keep the integration
build fast and we can have a look at the QA builds to improve them.
Arnaud
On Mon, Jul
Hi,
I agree too.
IMHO we don't have to block a release because they are checkstyle
errors : releasing something must not be nightmare (we are here to
help users and fix issues).
Ok except for missing license headers in source files.
We will find some exceptions which will prevent automatisation of
On 21/07/2008, at 4:56 PM, Arnaud HERITIER wrote:
Couldn't we setup a custom profile for QA checks (pmd, checkstyle,
clirr
...) that we activate in a separate project in the CI server ?
It's what I begin to do at work. The advantage is to keep the
integration
build fast and we can have a
It is maybe a stupid question, but I think it's still using ant 1.6.5. I
know that switching to 1.7 (I did locally) issue a weird path with space
problem on Windows. Ant 1.7.1 is out but I don't know if the problem is
fixed and I am lazy to search in BugSuperZilla.
To me, the biggest limitation
http://jira.codehaus.org/browse/MANTRUN-68
is scheduled for version 1.3.
I think Carlos wanted to get a version of the plugin out with all the
fixes, before upgrading Ant.
Yes, the spaces in a Windows path was fixed in 1.7.1.
Stephane Nicoll wrote:
It is maybe a stupid question, but I think
Olivier Lamy wrote:
Hi,
I agree too.
IMHO we don't have to block a release because they are checkstyle
errors : releasing something must not be nightmare (we are here to
help users and fix issues).
Right, I totally agree with that. I just wrote down things that are
worth looking at during
points that we need to reduce Checkstyle errors, checking
Clirr
report and licenses.
Any others ideas?
Cheers,
Vincent
-- Forwarded message --
From: Dennis Lundberg [EMAIL PROTECTED]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven
Makes sense.
Thanks for the info.
S.
On Mon, Jul 21, 2008 at 11:54 AM, Dennis Lundberg [EMAIL PROTECTED]
wrote:
http://jira.codehaus.org/browse/MANTRUN-68
is scheduled for version 1.3.
I think Carlos wanted to get a version of the plugin out with all the
fixes, before upgrading Ant.
Yes,
+1
On Sun, Jul 20, 2008 at 4:16 PM, Carlos Sanchez [EMAIL PROTECTED] wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
+1
Carlos Sanchez wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
+1
Carlos Sanchez wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
: Dennis Lundberg [EMAIL PROTECTED]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven Developers List dev@maven.apache.org
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed
before we
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
Staging site:
On 19/07/2008, at 11:26 PM, Dennis Lundberg wrote:
I went and harvested the mojo-dev list for release vote comments,
most of the from Benjamin. Some are specific to plugins, but many
are general. Here's the list:
Thanks Dennis! (and Benjamin :)
Inherit from the latest released parent
Lundberg [EMAIL PROTECTED]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven Developers List dev@maven.apache.org
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed
before we can release 1.2
] Release Maven antrun plugin version 1.2
To: Maven Developers List dev@maven.apache.org
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed
before we can release 1.2, for which I have to vote -1 to the current
release candidate.
- The POM is missing
Hi,
Following the recent Dennis's comments on MPIR and Antrun, I asked
myself how to improve our QA review and specially how to handle Maven
reports in the release process.
Does release manager need to justify failing reports for a given
release? If so, how.
How to improve the Maven report conf
Hi,
9 issues fixed. Last release was 2.5 years ago
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
Staging site:
http://maven.apache.org/plugins/maven-antrun-plugin-1.2/
Guide to testing
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed before
we can release 1.2, for which I have to vote -1 to the current release
candidate.
- The POM is missing the license header (I fixed this in svn)
- The Source files have the old
Thanks Dennis to fix them.
BTW Carlos, could you also include a release notes link on the jira
report? We discussed about it recently.
Cheers,
Vincent
2008/7/16, Dennis Lundberg [EMAIL PROTECTED]:
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that
]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven Developers List dev@maven.apache.org
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed
before we can release 1.2, for which I have to vote
Checkstyle errors, checking Clirr
report and licenses.
Any others ideas?
Cheers,
Vincent
-- Forwarded message --
From: Dennis Lundberg [EMAIL PROTECTED]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven Developers List dev
PROTECTED]
Date: 16 juil. 2008 15:48
Subject: Re: [VOTE] Release Maven antrun plugin version 1.2
To: Maven Developers List dev@maven.apache.org
Thanks for pushing for this release Carlos!
Unfortunately there are a couple of things that needs to be fixed
before we can release
Vincent Siveton wrote:
What are the minimalist things that we need to check for a good Maven release?
[...]
Any others ideas?
Cross-compiling against the intended minimum JDK to catch accidental
usage of newer types/methods.
Checking for properly declared dependencies with the help of
25 matches
Mail list logo
