Hi All,
I am member of the MXNet(incubating) project and I am working to publish our
Scala packages to Maven(have been done in previous releases). On OSX I am
encountering a weird problem, when I maven release-perform, it seem to create 2
different repos in the Staging library and there by
ns, it's a failure in the pgp key server ring and despite
> the fact that the ring is meant to distribute load, they all seem to go
> down at the same time. There isn't actually anything we can do on the rao
> side to make this work besides drop the staging rule that checks the ke
When this happens, it's a failure in the pgp key server ring and despite
the fact that the ring is meant to distribute load, they all seem to go
down at the same time. There isn't actually anything we can do on the rao
side to make this work besides drop the staging rule that checks
The log of the server shows a lot of connection problems to the key servers.
2016-05-26 09:33:06 INFO [ool-1-thread-10] -
com.sonatype.mercury.plexus.pgp.DefaultPgpVerifier - Had some errors during key
retrieval:
843ddb767188601c@http://gpg-keyserver.de/ : Failed (HTTP response code=404,
exce
On Thu, May 26, 2016 at 5:35 PM, Manfred Moser wrote:
> Seems like a performance/networking glitch. I am talking to Sonatype ops and
> support to get more info/help.
Could you please forward the conversation to me, Manfred?
Thanks,
Jochen
--
The next time you hear: "Don't reinvent the wheel!
On Thu, May 26, 2016 at 3:30 PM, Karl Heinz Marbaise wrote:
> Can you check in Nexus the tab "Activity" (at the bottom of the page) there
> you should see what has failed...
That is where I found the few details that I can give.
Thanks,
Jochen
--
The next time you hear: "Don't reinvent the
Apache Rat 0.12 on repository.apache.org. The
staging repository is orgapachecreadur-1002. Now, when I tried to
close it, I igot an error message "1 rule failed: Apache rules". As I
don't have any more information, thus not the slightest idea what the
problem might be, I am unable t
t; Gary
> On May 26, 2016 6:30 AM, "Karl Heinz Marbaise" wrote:
>
>> Hi,
>>
>> On 5/26/16 11:39 AM, Jochen Wiedmann wrote:
>>
>>> Hi,
>>>
>>> I hope that someone can help me with the following:
>>>
>>&
gt; I hope that someone can help me with the following:
>>
>> I staged a release of Apache Rat 0.12 on repository.apache.org. The
>> staging repository is orgapachecreadur-1002. Now, when I tried to
>> close it, I igot an error message "1 rule failed: Apache rules".
Hi,
On 5/26/16 11:39 AM, Jochen Wiedmann wrote:
Hi,
I hope that someone can help me with the following:
I staged a release of Apache Rat 0.12 on repository.apache.org. The
staging repository is orgapachecreadur-1002. Now, when I tried to
close it, I igot an error message "1 rule f
Hi,
I hope that someone can help me with the following:
I staged a release of Apache Rat 0.12 on repository.apache.org. The
staging repository is orgapachecreadur-1002. Now, when I tried to
close it, I igot an error message "1 rule failed: Apache rules". As I
don't have any m
Hi Karl-Heinz,
Karl Heinz Marbaise wrote:
> Hi,
>
> does someone know where to look cause currently the site staging job
> seemed to blocked and waiting for 11 hours
>
>
> http://ci.apache.org/builders/maven-site-staging
Maybe it waits for manual input on std
Hi,
does someone know where to look cause currently the site staging job
seemed to blocked and waiting for 11 hours
http://ci.apache.org/builders/maven-site-staging
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e
of the
components (maven-shared-utils, maven-jar-signer) are currently voted
on, so are not available in Central.
1) I see there is a staging-group at
https://repository.apache.org/content/repositories/maven-staging-group/
Should this group maybe be included in settings or a profile so stuff
in a vot
Hi Mirko,
>
Both the Maven 3[0] and Maven 2[1] build fail because two of the
components (maven-shared-utils, maven-jar-signer) are currently voted
on, so are not available in Central.
1) I see there is a staging-group at
https://repository.apache.org/content/repositories/maven-stag
currently voted
on, so are not available in Central.
1) I see there is a staging-group at
https://repository.apache.org/content/repositories/maven-staging-group/
Should this group maybe be included in settings or a profile so stuff
in a vote may already be used?
2) Maven2 is (finally
; On 11 February 2014 11:26, Jason van Zyl wrote:
>> So the current setup of the RAT plugin let me tag everything and then it
>> blew up while trying to build the binaries for staging. Less than ideal,
>> surprised me, and moderately annoying. It is never a good idea to only
&
n/java/org/apache/maven/SessionModule.java
which was in the report too.
On 11 February 2014 11:26, Jason van Zyl wrote:
> So the current setup of the RAT plugin let me tag everything and then it blew
> up while trying to build the binaries for staging. Less than ideal, surprised
>
If you can wait til tomorrow I'll sort it out...
On Tuesday, 11 February 2014, Jason van Zyl wrote:
> So the current setup of the RAT plugin let me tag everything and then it
> blew up while trying to build the binaries for staging. Less than ideal,
> surprised me, and moderatel
So the current setup of the RAT plugin let me tag everything and then it blew
up while trying to build the binaries for staging. Less than ideal, surprised
me, and moderately annoying. It is never a good idea to only execute something
during a release. Absolutely guaranteed to only blow while
;
> > maven-compiler-plugin-3.2 uses the new maven-shared-incremental-1.1 and
> > these are in two staging repositories, both have to be included as
> > repositories,
> >
> > Regards
> > Mirko
> >
> > Regards Mirko
> > --
> > http://illegals
Hi Alex,
I wrote that advice. The reasons is that depending on your package
structure and number of different team needing different staging profiles
I can become hard to maintain all the repository targets and profiles
matching correctly. We have certainly found that to be the case with OSSRH
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 Ne
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/
Hi,
I'd like to stage the Maven Help Plugin somewhere next week.
So if you want to have something as part of this release, then now is the
time to fix it.
Robert
https://jira.codehaus.org/browse/MPH
-
To unsubscribe, e-mail
Hi Hervé,
I'm sorry for the late reply
> introducing new status, with pseudo-pom property and so on seems irrealistic,
> at least to me: the concept is interesting, but I doubt it can fit into the
> actual code
Do you think it is feasible to add such status info as some plugin config?
> Perhap
uld prefer not to be
> >> >> >> locked
> >> >> >> to a specific vendor. I built an ant/ivy build pipeline
> >> >> >> implementing
> >> >> >> promotion with the help of my team mates. My primary motivation is
&g
lement standard build
> promotion/staging mechanism?
> From: the.ga...@gmail.com
> To: dev@maven.apache.org
>
> Hi Martin,
>
>As far as I understand our approach is fundamentally different than
> what "mvn release:prepare" does. We treat all build as a pot
everything).
I don't know whether it is better or not, but it suites better for
us (it is huge code base in which several modules released together as
a single product).
Regards, Gabor
On Sun, Jan 6, 2013 at 2:59 PM, Martin Gainty wrote:
>
> Gabor How is Ivy better suited to spe
Gabor How is Ivy better suited to specifying promotion/staging tags than
implementing with mvn
release:prepare?http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html
Martin
__
Jogi és Bizalmassági kinyilatkoztatás Ez az
üzenet
f my team mates. My primary motivation is to
>> >> >> enable the mixing of artifacts from ant and maven builds through a
>> >> >> central maven repository.
>> >> >>
>> >> >> I have two main issues with the current
ique id (build number);
> >> >> - no standard way to reference to staged/promoted artifact in the
> >> >> dynamic version number i.e. I can't specify in a standard way that I
> >> >> want the latest artifact which passed the integration test and has
>
gt; dynamic version number i.e. I can't specify in a standard way that I
>> >> want the latest artifact which passed the integration test and has
>> >> version from a specific branch.
>> >>
>> >> Proposal for promotion model:
>> >> -
t; dynamic version number i.e. I can't specify in a standard way that I
> >> want the latest artifact which passed the integration test and has
> >> version from a specific branch.
> >>
> >> Proposal for promotion model:
> >> - store status informatio
passed the integration test and has
>> version from a specific branch.
>>
>> Proposal for promotion model:
>> - store status information in a POM property (introducing standard
>> meta data in the POM would be much nicer) e.g. integration, milestone
>> - wr
nch.
>
> Proposal for promotion model:
> - store status information in a POM property (introducing standard
> meta data in the POM would be much nicer) e.g. integration, milestone
> - write an extension which can interpret and resolve "3.3.?
> latest.milestone" like no
on in a POM property (introducing standard
meta data in the POM would be much nicer) e.g. integration, milestone
- write an extension which can interpret and resolve "3.3.?
latest.milestone" like notation in the version number
Proposal for staging model:
- status information is identified by
It appears that the attachments got snipped somewhere, so making the images
available via normal browsing:
*Problem:* I essentially want to know how to inject a site stage structure
parser in doxia for use with maven-site-plugin, since the
maven-site-plugin's usage of Doxia for running site:stage
Lennart,
Your attachments are missing.
/Anders
On Thu, Dec 6, 2012 at 11:49 PM, Lennart Jörelid
wrote:
> Hello all,
>
> I have a few reactors where two separate parent poms exist; one parent is
> used exclusively for reactor projects [with pom] and
> the other parent is exclusively used for al
Hello all,
I have a few reactors where two separate parent poms exist; one parent is
used exclusively for reactor projects [with pom] and
the other parent is exclusively used for all other projects [with
... something not pom ...].
The build itself works as expected - but the *mvn site:stage* bui
I didn't check if it is needed or not, I just did what was not obvious
you can either test and do the upgrade if you have the problem, or just
upgrade to be sure since it is easy
Regards,
Hervé
Le mercredi 11 juillet 2012 08:17:33 Barrie Treloar a écrit :
> On Wed, Jul 11, 2012 at 7:48 AM, Herv
On Wed, Jul 11, 2012 at 7:48 AM, Hervé BOUTEMY wrote:
> I did the work on the plugin in r1359931 and prepared the htaccess in r1359934
Thanks.
I take it the "upgrade m-site-p to 3.1" wasn't needed?
I can't see it being specifically being defined so we are just
inheriting from maven-parent:21
--
seful to upgrade m-site-p to 3.1 in enforcer parent pom
> to benefit from MSITE-602 fix (wrong staging directory...)
>
> Regards,
>
> Hervé
>
> [1] http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered-
> resources/.htaccess?revision=1345430&view=markup
>
&
rule simply helps
people used to find plugins in /plugins/maven-xxx-plugin
Notice it could be useful to upgrade m-site-p to 3.1 in enforcer parent pom to
benefit from MSITE-602 fix (wrong staging directory...)
Regards,
Hervé
[1] http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered-
reso
On Tue, Jul 10, 2012 at 9:51 AM, Hervé BOUTEMY wrote:
> ah ok, I got it
> it's a specific configuration written in maven-enforcer-plugin
[del]
> IMHO, enforcer should switch. Tell me if you need help.
Ahh, my itch was to fix the bug and push a release.
I'm not sure if it stretches to upgrading :)
ah ok, I got it
it's a specific configuration written in maven-enforcer-plugin
IIUC, it's a try to handle the case where a project (defining its top level
directory) contains a plugin (published in /plugins/), with the question of
the staging directory.
This is a question common with
On Tue, Jul 10, 2012 at 6:24 AM, Hervé BOUTEMY wrote:
>> From what I can tell the automated steps now put things at
>> /www/maven.apache.org/staging
> no, there is no "staging" directory.
> Where did you get this info?
>From the command logs..
> mvn site site
d steps now put things at
> /www/maven.apache.org/staging
no, there is no "staging" directory.
Where did you get this info?
> But the manual steps say
> /www/maven.apache.org/plugins/
yes, that's what's actually used, either with site:stage-deploy or manual scp
Regards,
Hervé
Can someone have a look at the web page
http://maven.apache.org/developers/release/maven-plugin-release.html
and compare that automated results with the recommended manual steps.
>From what I can tell the automated steps now put things at
/www/maven.apache.org/staging
But the manual steps
2012/7/6 Barrie Treloar :
> Just following
> http://maven.apache.org/developers/release/maven-plugin-release.html
> and Staging the latest documentation.
>
> The stage completed successfully and its been a few hours since but
> the staging documentation is still not avail
Just following
http://maven.apache.org/developers/release/maven-plugin-release.html
and Staging the latest documentation.
The stage completed successfully and its been a few hours since but
the staging documentation is still not available.
I have not verified the folder permissions to 0775 and
l me
> please what's the policy to publish staging sites?
> I would avoid to override the current site :P
>
> Many thanks in advance, have a nice day!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
>
Hi all guys! :)
I intend to publish a [fluido] RC in a short while - can you tell me
please what's the policy to publish staging sites?
I would avoid to override the current site :P
Many thanks in advance, have a nice day!
-Simo
http://people.apache.org/~simonetripodi/
To purge the local repo we have a jenkins plugin that can be used :
https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repo+Cleaner+Plugin
(note that these days I have a doubt that it doesn't have a bug thus if we
are using it at Apache too it could help us to stabilize it :-) )
For real HTTP proxy
purge local repo and any caching proxies in between that is
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 30 Nov 2011 05:16, "Stephen Connolly"
wrote:
> yep... now all w
yep... now all we need is a way to easily purge if the vote is cancelled
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 30 Nov 2011 00:24, "Barrie Treloar" wrote:
> On We
On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies wrote:
>> Are you able to give an overview or point me at the docs I haven't read yet.
>
> So, whenever we stage a release, Nexus creates a private repository
> just for that one release of that one item. That's the URL sent around
> in release vot
On Tue, Nov 29, 2011 at 5:37 PM, Barrie Treloar wrote:
> On Wed, Nov 30, 2011 at 3:34 AM, Benson Margulies
> wrote:
>> https://issues.apache.org/jira/browse/INFRA-4163
>
> I read that issue, but I don't understand how its meant to be used.
> And I suspect its my lack of understanding of Nexus.
>
On Wed, Nov 30, 2011 at 3:34 AM, Benson Margulies wrote:
> https://issues.apache.org/jira/browse/INFRA-4163
I read that issue, but I don't understand how its meant to be used.
And I suspect its my lack of understanding of Nexus.
Are you able to give an overview or point me at the docs I haven't
https://issues.apache.org/jira/browse/INFRA-4163
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Oh, good, I don't need to do anything.
On Tue, Nov 29, 2011 at 10:17 AM, Dennis Lundberg
wrote:
> Hi
>
> Yes, it's a bug in the site plugin. It's fixed in the next version.
>
> On Tuesday, November 29, 2011, Benson Margulies
> wrote:
>>
> http://maven.apache.org/shared/maven-common-artifact-filt
Hi
Yes, it's a bug in the site plugin. It's fixed in the next version.
On Tuesday, November 29, 2011, Benson Margulies
wrote:
>
http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/
>
> Is this on purpose or by accident? There seem to be two extra
http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/
Is this on purpose or by accident? There seem to be two extra directories to me.
-
To unsubscribe, e-mail: dev-unsubscr...@mav
Hi guys!
@Stephen: sorry I didn't already do, going to do it right now! :)
@Olivier: the idea of a context, is wonderful, +1!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Wed, Nov 16, 2011 at 4
2011/11/16 Simone Tripodi :
> Hi all again!
>
> @Olivier: sorry for the latency but looks like this is a week I don't
> have a lot of time for OSS :(
> Anyway, I just published a new version of maven site, applying the
> fluido-skin[1]
>
> What I honestly think, is we need fresh new logos for the s
On 16 November 2011 14:53, Simone Tripodi wrote:
> @Steve: I'm going to send a message just for asking if there are no
> objections, no votes :)
>
Seriously, just move it out of sandbox... no need to ask... if there
was any body who felt strong enough to object and who has a binding
veto, they'd
Hi all again!
@Olivier: sorry for the latency but looks like this is a week I don't
have a lot of time for OSS :(
Anyway, I just published a new version of maven site, applying the
fluido-skin[1]
What I honestly think, is we need fresh new logos for the site, if we
agree applying this new skin to
no problem. last time i was promoting something from sandbox, i was told
just commit it, don't bother with a vote. too many votes can be a bad
thing, however as olamy did a vote for scripting, do what ever you want...
all i am saying is no vote required to promote from sandbox
- Stephen
---
Sent
Cool.
Did you manage to have a sample of m.a.o working fine ?
2011/11/15 Simone Tripodi :
> Hi all guys,
> I just deployed a new version of the sites skin on my personal ASF space[1].
>
> What's new:
>
> * css/js scripts are now minified in one single css/jss;
> * the code prettifier now works a
Good morning Steven!
I think I will follow the more polite ASF way calling for a vote,
thanks for the feedback!
Have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Nov 15, 2011 at 11
Hi Ivan!!!
I definitively have to check the banner right, looks like an issue!
Thanks for reporting!
About the missing images references, I think, they miss because it is
expected that the sites should be deployed under the right location,
I'll ask Hervé to make sure.
Thanks for your contribution
call a vote to promote from sandbox if you want, but we are commit then
review... just move out of sandbox and prey nobody vetos ;-)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
sc
Few small issues:
You have a broken right banner on the main page:
Also the topbar version links to banner images which do not exist:
../../../images/apache-maven-project-2.png
../../../images/maven-logo-2.gif
Can you check it out? I would but I'm not doing so well with free time atm...
Hi all guys,
I just deployed a new version of the sites skin on my personal ASF space[1].
What's new:
* css/js scripts are now minified in one single css/jss;
* the code prettifier now works also offline (removed the ugly script loader);
* if bannerLeft is not provided, text is now rendered us
Hi,
somehow I managed to accidentally deploy a maven-ant-plugin artifact to
the staging repository,
that is
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/maven/plugins/maven-ant-plugin/2.3-ic/maven-ant-plugin-2.3-ic.jar
.
Can someone delete that, please
Since they aren't linked anywhere, they are essentially invisible and
really only helpful to those few devs around here who know they exist.
(Those who really need them least)
2010/3/23 Barrie Treloar :
> On Wed, Mar 24, 2010 at 10:41 AM, Wendy Smoak wrote:
>>
>> On Tue, Mar 23, 2010 at 6:45 PM,
On Wed, Mar 24, 2010 at 10:41 AM, Wendy Smoak wrote:
>
> On Tue, Mar 23, 2010 at 6:45 PM, Brett Porter wrote:
> > In what instances do you find you need to use them? I thought for plugins,
> > with the use of @since and similar descriptive text it wasn't needed.
>
> Count me -0 on removing them.
On Tue, Mar 23, 2010 at 6:45 PM, Brett Porter wrote:
> In what instances do you find you need to use them? I thought for plugins,
> with the use of @since and similar descriptive text it wasn't needed.
Count me -0 on removing them. We keep versioned docs around for a lot
of things and I think t
They are official
> docs IMO, not really "staged" (even though that's how they get there,
> I subverted the staging url to avoid changing the config that was
> already in the poms.)
In what instances do you find you need to use them? I thought for plugins, with
the us
ing this, but we never decided how to do it.
I was hesitant to add another task to the RM's already long list. :(
I use those docs, but I "just know" where they are. They are official
docs IMO, not really "staged" (even though that's how they get there,
I subverted the stagi
removed?
+1
> Perhaps it would be better if the staging was done to
> /www/people.apache.org/builds/maven/sites instead?
+1
>
> - Brett
>
> --
> Brett Porter
> br...@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
>
> -
t;
> Perhaps it would be better if the staging was done to
> /www/people.apache.org/builds/maven/sites instead?
+1 (cleanup will be easier)
>
> - Brett
>
> --
> Brett Porter
> br...@apache
In the release docs [1], there is nothing about removing the staged
documentation directory after it is completed. This means we have a lot of
versioned directories of plugin sites, but they are never linked to. Should
they be removed?
Perhaps it would be better if the staging was done to
the maven-staging-001
(u:brianf, a:98.229.140.52)
<https://repository.apache.org/content/repositories/maven-staging-001>
repository.
test-1.pom
<https://repository.apache.org/content/repositories/maven-staging-001/org/apache/maven/test/1/test-1.pom>
repository-metadata
t; right click on my staging profile to "finish" it, the app complains that
> "The server did not finish staging the profile"
>
> Now what?
>
> S.
>
>
> On Sun, Mar 1, 2009 at 8:52 PM, Brian E. Fox wrote:
>
>> Maybe it's waiti
Right :)
Ok, I've staged the release. I am trying to perform step 5 from (
http://maven.apache.org/developers/release/releasing.html) and when I right
click on my staging profile to "finish" it, the app complains that "The
server did not finish staging the profile"
Now
Maybe it's waiting for the password?
-Original Message-
From: Stephane Nicoll [mailto:stephane.nic...@gmail.com]
Sent: Sunday, March 01, 2009 10:57 AM
To: Maven Developers List
Subject: stuck on gpg:sign while staging ear plugin
Hey guys,
I am trying to stage EAR plugin 2.3.2 b
Hey guys,
I am trying to stage EAR plugin 2.3.2 before calling for a vote. I've
followed everything as described on[1] but the mvn process is stuck on the
gpg sign goal
[INFO] [INFO] [gpg:sign {execution: default}]
I have MacOS 10.5.6 with maven 2.0.9 and gpg 1.4.9
snic...@cobra:~$ gpg --versio
Best to wait, I just fixed the issues you found, if you change your
vote, we can release them, it's been 72hrs.
-Original Message-
From: Dennis Lundberg [mailto:denn...@apache.org]
Sent: Friday, February 20, 2009 6:49 PM
To: Maven Developers List
Subject: Release/staging questio
g/service/local/staging/deploy/maven2/
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks for reminding me. We'll implement a custom plugin to validate
the sigs and send a notification. If the sigs don't match, we can stop
the promotion.
--Brian (mobile)
On Feb 8, 2009, at 12:32 PM, Wendy Smoak wrote:
On Thu, Feb 5, 2009 at 10:19 PM, Brett Porter
wrote:
You also n
On Thu, Feb 5, 2009 at 10:19 PM, Brett Porter wrote:
> You also need another step - either rsync to people so that one is kept up
> to date, or provide a replacement for Henk's scripts (or just block
> deploy/promotion with messed up sigs).
Any news on this bit?
The reposit...@a.o list needs so
steps.
--Brian
-Original Message-
From: Brian E. Fox [mailto:bri...@reply.infinity.nu]
Sent: Thursday, February 05, 2009 3:32 PM
To: Maven Developers List
Subject: [vote] use repository.zones.apache.org as the new
staging/releasing location for Maven artifacts
As proposed in separate
al Message-
> From: Jesse McConnell [mailto:jesse.mcconn...@gmail.com]
> Sent: Friday, February 06, 2009 10:29 AM
> To: Maven Developers List
> Subject: Re: [vote] use repository.zones.apache.org as the new
> staging/releasing location for Maven artifacts
>
> well might be a
jesse.mcconn...@gmail.com]
Sent: Friday, February 06, 2009 10:29 AM
To: Maven Developers List
Subject: Re: [vote] use repository.zones.apache.org as the new
staging/releasing location for Maven artifacts
well might be a bit belated but I am +1 for this as well, bringing a
bit of order to the stagin
well might be a bit belated but I am +1 for this as well, bringing a
bit of order to the staging process is a good thing..
my only concern which I have written a number of responses to only to
just delete and not send is something that has been brought up a
number of times on the infra list
his was mentioned on this list several days ago. I realize you may
not want to seem like you are forcing this on anyone, but it seemed
to me this was a done deal when infra told Brian to set it up in a
zone.
But if you want a +1 instead, consider this it.
It would be possible to support the
On Feb 5, 2009, at 10:34 PM, Jason van Zyl wrote:
On 5-Feb-09, at 9:53 PM, Ralph Goers wrote:
I'm not sure why this needs a vote. Just do it.
This requires pulling all of the org.apache.maven.* artifacts into
Nexus and that's where they stay for this project because we can't
keep parti
So lets vote:
+1 Yes, lets lead the way at ASF with a better staging and releasing
process
+0 shrug
-1 No, I like managing my artifacts by hand.
--
Brian Fox
Apache Maven PMC
http://blogs.sonatype.com/brian/
---
1 - 100 of 181 matches
Mail list logo
