maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: RE: How to have release management incremental (or release) builds publish to Nexus, but not user builds?
Date Wed, 08 Dec 2010 15:42:19 GMT
Right, and the answer is adding different permissions in your repo manager
for your build server and your devs. Only the build server, and maybe some
trusted devs, will be authz to deploy.

/Anders (mobile)
Den 8 dec 2010 15.56 skrev "KARR, DAVID (ATTSI)" <dk068x@att.com>:
>> -----Original Message-----
>> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
>> Behalf Of Anders Hammar
>> Sent: Tuesday, December 07, 2010 11:54 PM
>> To: Maven Users List
>> Subject: Re: How to have release management incremental (or release)
>> builds publish to Nexus, but not user builds?
>>
>> I'm arguing as I think you're sending the questioner off into the
>> wilderness
>> by suggesting something you call "common practice, which I do not see
>> as
>> common practice. I'm just trying to stop someone not being a Maven
>> expert
>> from going down a difficult path where he/she would run into all kinds
>> of
>> strange behavior.
>
> Anders, thank you for protecting my interests. :)
>
> However, I'm much more interested in solving the problem I had with my
> "releaseIncremental" profile that I reported in this chain yesterday.
>
>> I've checked both the apache parent and the codehaus parent I can't
>> find
>> what you're talking about.
>> http://repo2.maven.org/maven2/org/apache/apache/8/apache-8.pom
>> http://repo2.maven.org/maven2/org/codehaus/codehaus-parent/3/codehaus-
>> parent-3.pom
>>
>> /Anders
>>
>> On Wed, Dec 8, 2010 at 08:45, Kalle Korhonen
>> <kalle.o.korhonen@gmail.com>wrote:
>>
>> > The "commonness" of the practice is hardly the point of this thread
>> so
>> > it baffles me why you'd want to start arguing about it, but there is
>> a
>> > specific distributionManagement section in the release profiles of
>> > Apaches', Codehaus' parent poms and in the parent pom I linked to so
>> I
>> > offered a tried and widely used solution to the questioner. There's
>> > nothing difficult for users in it.
>> >
>> > Kalle
>> >
>> >
>> > On Tue, Dec 7, 2010 at 9:49 PM, Anders Hammar <anders@hammar.net>
>> wrote:
>> > > Commonly used practice? Really? I don't think so. Are the users
>> supposed
>> > to
>> > > enable different snapshot repos depending on what "type" of
>> snapshot
>> > > artifacts the want to use? Seems very complicated and error prone
>> to me
>> > and
>> > > simply just to difficult for the users to get right.
>> > >
>> > > /Anders
>> > >
>> > > On Tue, Dec 7, 2010 at 19:10, Kalle Korhonen
>> <kalle.o.korhonen@gmail.com
>> > >wrote:
>> > >
>> > >> Of course, developers never need to run "deploy" goal in the
> first
>> > >> place. Anyhow, it's a commonly used practice to deploy to
>> different
>> > >> locations. Create a release profile and override the
>> > >> distributionManagement section as needed, for example see
>> > >> http://svn.codehaus.org/tynamo/trunk/tynamo-parent/pom.xml.
>> > >>
>> > >> Kalle
>> > >>
>> > >>
>> > >> On Tue, Dec 7, 2010 at 10:00 AM, KARR, DAVID (ATTSI)
>> <dk068x@att.com>
>> > >> wrote:
>> > >> > I'm working on strategies to convert a large and complex Ant
>> build
>> > >> > system to use Maven.
>> > >> >
>> > >> > I'm assuming that developers who are working on individual
>> modules
>> > will
>> > >> > do a build that pulls the artifacts of other modules (that
>> they're not
>> > >> > working on) from the Nexus repository we have running on an
>> intranet
>> > >> > server. These will be both release artifacts and snapshot
>> artifacts.
>> > >> >
>> > >> > I also assume that incremental builds performed by the release
>> > >> > management team will publish snapshot artifacts to the Nexus
>> > repository,
>> > >> > but builds performed by developers will not publish to the
> Nexus
>> > >> > repository.
>> > >> >
>> > >> > Is this reasonable? If so, what mechanisms do I have to have
> in
>> place
>> > >> > to make release management builds publish artifacts to Nexus,
>> but not
>> > >> > developer builds?
>> > >> >
>> > >> >
> ----------------------------------------------------------------
>> -----
>> > >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > >> > For additional commands, e-mail: users-help@maven.apache.org
>> > >> >
>> > >> >
>> > >>
>> > >>
> ------------------------------------------------------------------
>> ---
>> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > >> For additional commands, e-mail: users-help@maven.apache.org
>> > >>
>> > >>
>> > >
>> >
>> >
> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message