+1
On Wed, Sep 30, 2009 at 1:54 PM, Paul Benedict wrote:
> +1 here
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
---
in a lot of cases the invoker plugin is simpler
Sent from my [rhymes with tryPod] ;-)
On 30 Sep 2009, at 21:53, Donszelmann Mark
wrote:
Hi
is the Maven Plugin Harness the thing to use to write plugin tests,
or is there something
newer / better around nowadays.
I looked in the Maven ma
+1 here
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi
is the Maven Plugin Harness the thing to use to write plugin tests, or
is there something
newer / better around nowadays.
I looked in the Maven manual which has a chapter on writing Plugins,
but not on writing tests
for it.
Regards
Mark Donszelmann
---
I wired up the staging repo to my Nexus group and built trunk so it's
good from here.
On 2009-09-30, at 10:31 AM, John Casey wrote:
Hi everyone,
This release is meant to fix a couple of the biggest bugs introduced
in 2.4.
We fixed 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.js
+1
Arnaud
On Sep 30, 2009, at 7:40 PM, John Casey wrote:
Hi everyone,
We fixed 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&styleName=Text&version=15560
There are no issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pi
+1
arnaud
On Sep 30, 2009, at 7:40 PM, John Casey wrote:
Sorry, here's my +1.
John Casey wrote:
Hi everyone,
This release is meant to fix a couple of the biggest bugs
introduced in 2.4.
We fixed 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Text&vers
Sorry, here's my +1.
John Casey wrote:
Hi everyone,
This release is meant to fix a couple of the biggest bugs introduced in
2.4.
We fixed 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Text&version=15760
There are still plenty of issues left in JIRA
Hi everyone,
We fixed 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11250&styleName=Text&version=15560
There are no issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11250&resolution=-1
Staging repo:
https://repository.apa
Hi everyone,
This release is meant to fix a couple of the biggest bugs introduced in 2.4.
We fixed 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Text&version=15760
There are still plenty of issues left in JIRA for 2.5 and beyond:
http://jira.codehaus.org
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.2.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant to
I agree with Brett, Gilles, Daniel.
Gilles, thanks for that reference, I think we should all learn from that!
On Wed, Sep 30, 2009 at 7:49 AM, Daniel Kulp wrote:
>
> I agree with Brett. Strongly recommend, but not require.
>
> Dan
>
>
> On Wed September 30 2009 12:57:34 am Brett Porter wrote:
I agree with Brett.Strongly recommend, but not require.
Dan
On Wed September 30 2009 12:57:34 am Brett Porter wrote:
> I think any rule needs to be enforced on the server side as much as in
> the repository plugin too.
>
> For mine, I think strongly recommending SCM is a good idea, but we
> 1) defined rules for what an "acceptable" artifact is
> 2) gating central with those rules
Any time when I referred to
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
as a requirement, I always had a bad feeling.
Why? Requirement is what you can verify against, but this m
There is no requirements for open sources project to offer access to a
repository : http://www.opensource.org/docs/osd
So recommending it is good, but make it mandatory would be excessive.
Gilles Scokart
15 matches
Mail list logo
