Restricting release deployment
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Restricting release deployment
by Stephen Chamberlain
::
Rate this Message:
Hi All,
We have just started using Nexus and have a question. If we deploy a release version of a project, we would like to get an error message if that release version depends on a SNAPSHOT version of another project (this is to ensure that we cannot have release artifacts depending on SNAPSHOTs). Is it possible to configure Nexus to check the dependencies of a release deployment? Best Regards, Steve Chamberlain. |
|
|
Re: Re[nexus-user] stricting release deployment
by MALICE
::
Rate this Message:
I presume you are using maven? In maven it is not possible to release an
artifact if it has dependencies on SNAPSHOTS, so imo this is not something Nexus should check... On Thursday 10 September 2009 14:24, Stephen Chamberlain wrote: > Hi All, > > We have just started using Nexus and have a question. If we deploy a > release version of a project, we would like to get an error message if that > release version depends on a SNAPSHOT version of another project (this is > to ensure that we cannot have release artifacts depending on SNAPSHOTs). > > Is it possible to configure Nexus to check the dependencies of a release > deployment? > > Best Regards, > Steve Chamberlain. -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: Roland.Asmann@... Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Re[nexus-user] stricting release deployment
by Anders Hammar
::
Rate this Message:
No, not in the OSS version at least (might be a Pro feature, I don't know). However, it shouldn't be too hard to develop such as plugin (or has someone already developed one?).
If you use Maven and maven-release-plugin it will do this check for you. But this is on the client side though. /Anders On Thu, Sep 10, 2009 at 14:24, Stephen Chamberlain <chamberlain@...> wrote:
|
|
|
Re: Re[nexus-user] stricting release deployment
by Stephen Chamberlain
::
Rate this Message:
"In maven it is not possible"
I am not sure this is true. If I use the deploy plugin to deploy an artifact to the Nexus repository, there is no such check performed. This check is performed if I use the release plugin. However, the choice to use the deploy or release plugin is made by the maven client, not the central repository server.
|
|
|
Re: Re: Re[nexus-user] stricting release deployment
by MALICE
::
Rate this Message:
True. The deploy-plugin doesn't check this. But because you wrote "If we
deploy a release version of a project", I presumed you released the project using maven. If this is the case, then it doesn't matter if you deploy the artifact during the release or afterwards: the released version cannot contain references to SNAPSHOTS. On Thursday 10 September 2009 14:57, Stephen Chamberlain wrote: > "In maven it is not possible" > > I am not sure this is true. If I use the deploy plugin to deploy an > artifact to the Nexus repository, there is no such check performed. This > check is performed if I use the release plugin. > > However, the choice to use the deploy or release plugin is made by the > maven client, not the central repository server. > > MALICE wrote: > > I presume you are using maven? In maven it is not possible to release an > > artifact if it has dependencies on SNAPSHOTS, so imo this is not > > something Nexus should check... > > > > On Thursday 10 September 2009 14:24, Stephen Chamberlain wrote: > >> Hi All, > >> > >> We have just started using Nexus and have a question. If we deploy a > >> release version of a project, we would like to get an error message if > >> that > >> release version depends on a SNAPSHOT version of another project (this > >> is to ensure that we cannot have release artifacts depending on > >> SNAPSHOTs). > >> > >> Is it possible to configure Nexus to check the dependencies of a release > >> deployment? > >> > >> Best Regards, > >> Steve Chamberlain. > > > > -- > > Roland Asmann > > > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > > Bäckerstrasse 1/2/7 > > A-1010 Wien > > FN 266155f, Handelsgericht Wien > > > > Tel.: +43/1/513 88 77 - 27 > > Fax.: +43/1/513 88 62 > > Email: Roland.Asmann@... > > Web: www.cfc.at > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: nexus-user-unsubscribe@... > > For additional commands, e-mail: nexus-user-help@... -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: Roland.Asmann@... Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
|
|
Re: Re: Re[nexus-user] stricting release deployment
by Juven Xu
::
Rate this Message:
The staging feature of nexus pro could be useful in this case, deploy release artifacts into staging repository, analysis the dependencies before closing or promotion.
But still, currently in Nexus, there's no utilities we can use to analysis dependencies, but I'm sure we can borrow some from Maven world. :P On Thu, Sep 10, 2009 at 9:17 PM, Roland Asmann <Roland.Asmann@...> wrote: True. The deploy-plugin doesn't check this. But because you wrote "If we -- - juven |
|
|
RE: Re: Re[nexus-user] stricting release deployment
by justinedelson
::
Rate this Message:
My understanding from prior threads is that this type of analysis is dependent upon the release of Maven 3. From: Juven Xu [mailto:juven@...] Sent: Thu 9/10/2009 9:39 AM To: nexus-user@... Subject: Re: [nexus-user] Re: Re[nexus-user] stricting release deployment The staging feature of nexus pro could be useful in this case, deploy release artifacts into staging repository, analysis the dependencies before closing or promotion. But still, currently in Nexus, there's no utilities we can use to analysis dependencies, but I'm sure we can borrow some from Maven world. :P On Thu, Sep 10, 2009 at 9:17 PM, Roland Asmann <Roland.Asmann@...> wrote: True. The deploy-plugin doesn't check this. But because you wrote "If we -- - juven |
|
|
Re: Re: Re[nexus-user] stricting release deployment
by Brian Fox
::
Rate this Message:
On Thu, Sep 10, 2009 at 11:14 AM, Edelson, Justin
<Justin.Edelson@...> wrote: > My understanding from prior threads is that this type of analysis is > dependent upon the release of Maven 3. Not entirely. Using some pieces of M3 code in a Staging rule plugin would make it easier, but it's possible to analyze the dependencies without it. The key in Nexus would be to use the staging functionality and set rules to validate this criteria. The rules and extensions are part of Nexus 1.4. --------------------------------------------------------------------- To unsubscribe, e-mail: nexus-user-unsubscribe@... For additional commands, e-mail: nexus-user-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
