Jason van Zyl wrote:
You probably want to post on the Nexus list as this plugin already exists.
If I read his email right, I believe he means to say he's implementing
that existing plugin on his projects - aka adding it to the poms, not
re-implementing the plugin.
Either way, the nexus list (
You probably want to post on the Nexus list as this plugin already exists.
On Feb 27, 2013, at 11:57 AM, alex.price wrote:
> Hi,
>
> I am currently implementing the "Nexus Staging Maven Plug-in" for many of
> our releases, which aims to place artifacts in the Nexus Staging area in an
> automate
Hi,
I am currently implementing the "Nexus Staging Maven Plug-in" for many of
our releases, which aims to place artifacts in the Nexus Staging area in an
automated "closed" state.
I am currently reading the Sonatype article on the plug-in:
http://www.sonatype.com/books/nexus-book/reference/stagin
> On 27 Feb 2013, at 19:34, Benson Margulies wrote:
>
>> I think it's long overtime for us to officially disclaim support for
>> Maven 1.
I completely agree. In fact .. while I would suggest to do this asap and
then make the same call for Maven 2. I wonder who would actually be
actively stepping
Yep. The code's there if anyone wants to contribute, but unless someone here
speaks up, I don't think anyone intends to do further work on it.
It would be super-helpful to fold all the JIRA projects related to it, too,
since occasionally people get confused between the versions.
- Brett
On 28/
Yes, I think we need to look at
http://jira.codehaus.org/browse/MCHANGES-299
before releasing.
Can someone else confirm my findings in that issue?
I have some time to work on it this weekend.
On Wed, Feb 27, 2013 at 7:35 PM, Benson Margulies wrote:
> The changes to support the current versions o
On Wed, Feb 27, 2013 at 7:52 PM, Gary Gregory wrote:
> We've had similar discussion @Commons about a topic like this one. My view
> is that you'll never know who will step up on volunteer, or who is in
> enough pain to stand up and do the work.
>
I think the question is less of a prediction what
2013/2/27 Benson Margulies :
> On Wed, Feb 27, 2013 at 10:52 AM, Gary Gregory wrote:
>> We've had similar discussion @Commons about a topic like this one. My view
>> is that you'll never know who will step up on volunteer, or who is in
>> enough pain to stand up and do the work.
>
> As a matter of
+1
Sent from my iPhone
On 27 Feb 2013, at 19:34, Benson Margulies wrote:
> I think it's long overtime for us to officially disclaim support for Maven 1.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For add
On Wed, Feb 27, 2013 at 11:01 AM, Brian Fox wrote:
> On Wed, Feb 27, 2013 at 10:56 AM, Benson Margulies
> wrote:
>
>> If someone else
>> wants to support it, they are welcome to do so elsewhere.
>>
>
> Or here through active participation. But while we don't have active
> committers supporting it
On Wed, Feb 27, 2013 at 10:56 AM, Benson Margulies wrote:
> If someone else
> wants to support it, they are welcome to do so elsewhere.
>
Or here through active participation. But while we don't have active
committers supporting it, we should say so. Nothing stops us from doing
more than the offi
On Wed, Feb 27, 2013 at 10:52 AM, Gary Gregory wrote:
> We've had similar discussion @Commons about a topic like this one. My view
> is that you'll never know who will step up on volunteer, or who is in
> enough pain to stand up and do the work.
As a matter of Foundation culture, we, as a project
+1 and take if off the dist site.
On Wed, Feb 27, 2013 at 10:42 AM, Benson Margulies wrote:
> Are there any readers on this list who are prepared to respond to any
> issues on Maven 1.x, especially, for example, security issues? Does
> anyone know how to make a release? Unless that set is non-em
We've had similar discussion @Commons about a topic like this one. My view
is that you'll never know who will step up on volunteer, or who is in
enough pain to stand up and do the work.
I think what is helpful is to list for each branch what the expectations
should be, like version 1 is inactive b
Are there any readers on this list who are prepared to respond to any
issues on Maven 1.x, especially, for example, security issues? Does
anyone know how to make a release? Unless that set is non-empty, we
really need to 'retire' it, I claim.
On Wed, Feb 27, 2013 at 10:37 AM, Anders Hammar wrote:
Yes, this line is not really true:
"Note that *no further development* is planned for the Maven-1.0 branch,
and Maven-1.1 is in maintenance mode, i.e. development is restricted to
support and bug fixes."
/Anders
On Wed, Feb 27, 2013 at 7:33 PM, Benson Margulies wrote:
> I think it's long overti
+1
On Wednesday, 27 February 2013, Benson Margulies wrote:
> I think it's long overtime for us to officially disclaim support for Maven
> 1.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional comma
The changes to support the current versions of JIRA are still pending;
could I please make a release? I seem to remember that someone had
wanted to do something before we made a release.
-
To unsubscribe, e-mail: dev-unsubscr...@m
I think it's long overtime for us to officially disclaim support for Maven 1.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi Jason,
I can help in the analysis. I recently written some annotation
checking tool in japa (javaparser) and ASM :) Do you want to analyze
the source code or the class files?
Regards,
g
On Wed, Feb 27, 2013 at 1:56 AM, Hervé BOUTEMY wrote:
> Did you finally tried "full graph analysis on C
+1 on giving people one week from the Jason's initial mail in this thread.
Will the release be a RC or the real deal? We've had this discussion before
and I honestly don't remember what we decided, but I think cutting a RC
first for core is good. So maybe cut a RC now and have us/people test that
21 matches
Mail list logo
