Apache nexus repository
|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
 |
Apache nexus repository
by Martijn Dashorst
::
Rate this Message:
We've been releasing to people.apache.org, and that is/was painful for
the maven repository artifacts: we loose metadata with each release. Some of the maven guys work for sonatype and have donated the Nexus enterprise repository to the ASF for our releases. I'd like to propose that we release all future releases through the nexus repository instead of people.apache.org. (I expect this to become policy somewhere in the future). Here is what the Maven Project is using if you want to understand what you would need to do as a project: http://maven.apache.org/developers/release/releasing.html http://maven.apache.org/developers/committer-settings.html There is also the staging documentation in the Nexus book: http://www.sonatype.com/books/nexus-book/reference/staging.html Also know that using Nexus requires us to take your artifacts off people.apache.org and place them under the management of Nexus. But once this is done, staging and promoting is painless and we will fully manage the repository (including snapshot management) and the sync artifacts to central for you. [ ] yes, use nexus deployment from now [ ] no, ... Martijn |
|
|
Re: Apache nexus repository
by Martijn Dashorst
::
Rate this Message:
+1
On Sat, Jun 27, 2009 at 9:24 PM, Martijn Dashorst<martijn.dashorst@...> wrote: > We've been releasing to people.apache.org, and that is/was painful for > the maven repository artifacts: we loose metadata with each release. > Some of the maven guys work for sonatype and have donated the Nexus > enterprise repository to the ASF for our releases. I'd like to propose > that we release all future releases through the nexus repository > instead of people.apache.org. (I expect this to become policy > somewhere in the future). > > Here is what the Maven Project is using if you want to understand what > you would need to do as a project: > > http://maven.apache.org/developers/release/releasing.html > > http://maven.apache.org/developers/committer-settings.html > > There is also the staging documentation in the Nexus book: > > http://www.sonatype.com/books/nexus-book/reference/staging.html > > Also know that using Nexus requires us to take your artifacts off > people.apache.org and place them under the management of Nexus. But > once this is done, staging and promoting is painless and we will fully > manage the repository (including snapshot management) and the sync > artifacts to central for you. > > [ ] yes, use nexus deployment from now > [ ] no, ... > > Martijn > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. |
|
|
Re: Apache nexus repository
by igor.vaynberg
::
Rate this Message:
+1
we release to nexus at my work and it is as simple as mvn release:deploy to get all the artifacts into the repo. -igor On Sat, Jun 27, 2009 at 12:43 PM, Martijn Dashorst<martijn.dashorst@...> wrote: > +1 > > On Sat, Jun 27, 2009 at 9:24 PM, Martijn > Dashorst<martijn.dashorst@...> wrote: >> We've been releasing to people.apache.org, and that is/was painful for >> the maven repository artifacts: we loose metadata with each release. >> Some of the maven guys work for sonatype and have donated the Nexus >> enterprise repository to the ASF for our releases. I'd like to propose >> that we release all future releases through the nexus repository >> instead of people.apache.org. (I expect this to become policy >> somewhere in the future). >> >> Here is what the Maven Project is using if you want to understand what >> you would need to do as a project: >> >> http://maven.apache.org/developers/release/releasing.html >> >> http://maven.apache.org/developers/committer-settings.html >> >> There is also the staging documentation in the Nexus book: >> >> http://www.sonatype.com/books/nexus-book/reference/staging.html >> >> Also know that using Nexus requires us to take your artifacts off >> people.apache.org and place them under the management of Nexus. But >> once this is done, staging and promoting is painless and we will fully >> manage the repository (including snapshot management) and the sync >> artifacts to central for you. >> >> [ ] yes, use nexus deployment from now >> [ ] no, ... >> >> Martijn >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > |
|
|
Re: Apache nexus repository
by jthomerson
::
Rate this Message:
+1 - we need a better solution! Can we import old releases (at least
the 1.3.X and the 1.4-RCX releases)? -- Jeremy Thomerson http://www.wickettraining.com On Sat, Jun 27, 2009 at 6:46 PM, Igor Vaynberg<igor.vaynberg@...> wrote: > +1 > > we release to nexus at my work and it is as simple as mvn > release:deploy to get all the artifacts into the repo. > > -igor > > On Sat, Jun 27, 2009 at 12:43 PM, Martijn > Dashorst<martijn.dashorst@...> wrote: >> +1 >> >> On Sat, Jun 27, 2009 at 9:24 PM, Martijn >> Dashorst<martijn.dashorst@...> wrote: >>> We've been releasing to people.apache.org, and that is/was painful for >>> the maven repository artifacts: we loose metadata with each release. >>> Some of the maven guys work for sonatype and have donated the Nexus >>> enterprise repository to the ASF for our releases. I'd like to propose >>> that we release all future releases through the nexus repository >>> instead of people.apache.org. (I expect this to become policy >>> somewhere in the future). >>> >>> Here is what the Maven Project is using if you want to understand what >>> you would need to do as a project: >>> >>> http://maven.apache.org/developers/release/releasing.html >>> >>> http://maven.apache.org/developers/committer-settings.html >>> >>> There is also the staging documentation in the Nexus book: >>> >>> http://www.sonatype.com/books/nexus-book/reference/staging.html >>> >>> Also know that using Nexus requires us to take your artifacts off >>> people.apache.org and place them under the management of Nexus. But >>> once this is done, staging and promoting is painless and we will fully >>> manage the repository (including snapshot management) and the sync >>> artifacts to central for you. >>> >>> [ ] yes, use nexus deployment from now >>> [ ] no, ... >>> >>> Martijn >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.5 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> > |
|
|
RedirectRequestTarget SC_MOVED_PERMANENTLY
by michael mosmann
::
Rate this Message:
Hi,
can we extends RedirectRequestTarget somehow, so that setting response status code to SC_MOVED_PERMANENTLY is done in an easy way? michael |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by Martijn Dashorst
::
Rate this Message:
A patch is welcome :)
I don't see why we shouldn't extend redirectrequesttarget to also take the status code. But there might be a better place to set it, and I'd rather not have more ways to skin a cat (not that I'd like to skin cats though... I love my two cats!) Martijn On Sun, Jun 28, 2009 at 1:40 PM, Michael Mosmann<michael@...> wrote: > Hi, > > can we extends RedirectRequestTarget somehow, so that setting response > status code to SC_MOVED_PERMANENTLY is done in an easy way? > > michael > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by martin-g
::
Rate this Message:
See WebErrorCodeResponseTarget
@devs: why the name of this class is *Response*Target while actually it is an implementation of I*Request*Target ? It is a bit confusing/inconsistent. El dom, 28-06-2009 a las 13:40 +0200, Michael Mosmann escribió: > Hi, > > can we extends RedirectRequestTarget somehow, so that setting response > status code to SC_MOVED_PERMANENTLY is done in an easy way? > > michael > > > |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by michael mosmann
::
Rate this Message:
Am Sonntag, den 28.06.2009, 13:53 +0200 schrieb Martijn Dashorst:
> A patch is welcome :) as jira-ticket or as email with some files? mm:) |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by jthomerson
::
Rate this Message:
JIRA - always.
-- Jeremy Thomerson http://www.wickettraining.com On Sun, Jun 28, 2009 at 7:01 AM, Michael Mosmann<michael@...> wrote: > Am Sonntag, den 28.06.2009, 13:53 +0200 schrieb Martijn Dashorst: >> A patch is welcome :) > > as jira-ticket or as email with some files? > > mm:) > > > |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by Martijn Dashorst
::
Rate this Message:
Well, it is always a response, superimposed upon an existing request
target, and never an incoming request. Which makes it consistent with english language. Martijn On Sun, Jun 28, 2009 at 1:58 PM, Martin Grigorov<mcgregory@...> wrote: > See WebErrorCodeResponseTarget > > @devs: why the name of this class is *Response*Target while actually it > is an implementation of I*Request*Target ? > It is a bit confusing/inconsistent. > > El dom, 28-06-2009 a las 13:40 +0200, Michael Mosmann escribió: >> Hi, >> >> can we extends RedirectRequestTarget somehow, so that setting response >> status code to SC_MOVED_PERMANENTLY is done in an easy way? >> >> michael >> >> >> > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by michael mosmann
::
Rate this Message:
Am Sonntag, den 28.06.2009, 07:43 -0500 schrieb Jeremy Thomerson:
> JIRA - always. will do.. as quickstart-app? mm:) |
|
|
Re: RedirectRequestTarget SC_MOVED_PERMANENTLY
by Martijn Dashorst
::
Rate this Message:
Nope, just a patch to the existing class (unified diff)
Martijn On Sun, Jun 28, 2009 at 3:43 PM, Michael Mosmann<michael@...> wrote: > Am Sonntag, den 28.06.2009, 07:43 -0500 schrieb Jeremy Thomerson: >> JIRA - always. > > will do.. > as quickstart-app? > > mm:) > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. |
| Free embeddable forum powered by Nabble | Forum Help |
