Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cf-dev] Deploy RC1 to eclipse releases repo 
Well, the noRelease file has the same problem. It cannot be used to prevent the Maven "deploy" stage from being executed altogether. It can only be used to prevent a profile from being activated. However, if we use a "release" profile for changing the <distributionManagement> section's repository definition, then preventing the profile from being active in a module, the deploy stage is still executed (e.g. using the standard Maven Deploy plugin) using the original repository location from the parent POM's <distributionManagement> section. This, again, would lead to deploying the same artifacts twice to Eclipse Releases :-(
So, I am afraid the problem remains that we are not able to selectively disable execution of the deploy phase for just some modules in a reactor project. Another option would be to group all modules that should not be deployed at all to one or more separate "Examples" project(s) for which we do not invoke mvn deploy at all ...

Kai


> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kovatsch Matthias
> Sent: Monday, November 02, 2015 11:45 AM
> To: Californium (Cf) developer discussions
> Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> 
> Hmm, I thought we deploy the examples to neither?
> Would that be possible?
> We had this noRelease file and then you found a better way to exclude
> them. Was there a problem with that?
> 
> Ciao
> Matthias
> 
> > -----Original Message-----
> > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of Hudalla Kai (INST/ESY)
> > Sent: Montag, 2. November 2015 08:45
> > To: Californium (Cf) developer discussions
> > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> >
> > I did, Matthias, and ran into the next problem (as expected) ;-)
> >
> > Basically, our build jobs work pretty well :-) At least they worked
> > well for Californium (parent) and Element Connector. When building
> > Scandium I ran into a problem with the Examples module:
> >
> > The build job tries to deploy the built artifacts to two different
> repositories:
> > a) Eclipse Releases and b) Maven Central's staging repository. I have
> > configured the Californium (parent) POM to use the Nexus Staging
> Maven
> > Plugin as a replacement for the standard Maven Deploy plugin for its
> > capability of doing both deploy to the repository indicated by the
> > POM's <distributionManagement> section as well as deploy to Maven
> > Central's staging repository. The particular repo to deploy to is
> > determined by two
> > factors: the version identifier (either a SNAPSHOT or a release
> > version) and the value of the "skipStaging" Maven property.
> >
> > This works pretty well when deploying all artifacts as a whole to
> > either one of these repositories but unfortunately does not support
> > our intention to only "selectively" deploy some of the artifacts to
> > Maven Central. IN the case of Scandium, I marked the "Examples"
> module
> > to not be deployed to Maven Central by means of setting the
> > "skipStaging" property to true within the Exmaples module's POM file.
> > However, when the Nexus Staging Maven Plugin processes this module it
> correctly recognizes the "skipStaging"
> > property being true und thus falls back to deploy the artifacts to
> the
> > repo found in the <distributionManagement> section which is the
> > Eclipse Releases repo :-( The problem is that our build job first
> > deploys to the Eclipse Releases repo (simply by setting the
> > skipStaging property to true at the Maven command line) and
> afterwards
> > tries to deploy to Maven Central's staging repo (by omitting the
> > skipStaging property). However, because the "Examples" submodule sets
> > this property itsel  f (to "true"), the Nexus Staging Maven Plugin
> > tries to (again) deploy the Examples artifact to Eclipse Releases -
> and fails because it already exists in there.
> >
> > So, the overall problem is that we cannot selectively "turn off" the
> > deploy step altogether. At least, I do not know how to do that. May
> be
> > we can try to bind the Nexus Staging Maven Plugin to a different
> > (later) stage in the POM of those modules that we do not want to be
> deployed.
> > However, a much simpler solution would be if we could agree to deploy
> > ALL artifacts to both Eclipse Releases and Maven Central as well.
> >
> > Thoughts?
> >
> > Kai
> >
> > > -----Original Message-----
> > > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-
> bounces@xxxxxxxxxxx]
> > > On Behalf Of Kovatsch Matthias
> > > Sent: Friday, October 30, 2015 5:23 PM
> > > To: Californium (Cf) developer discussions
> > > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> > >
> > > Feel free to continue with RC2 and so on to test the release
> process
> > > from the current head. We had some updates since RC1 already (while
> > > not modifying any relevant stuff---Wayne said that is fine for the
> > > release process). Thanks for taking care of this!
> > >
> > > I think it is also fine to trigger each sub-release on its own,
> that
> > > is, parent, element-connector, scandium, etc.
> > >
> > > Ciao
> > > Matthias
> > >
> > >
> > > > -----Original Message-----
> > > > From: cf-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > > > On Behalf Of Hudalla Kai (INST/ESY)
> > > > Sent: Freitag, 30. Oktober 2015 10:23
> > > > To: Californium (Cf) developer discussions
> > > > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> > > >
> > > > Hi Matthias,
> > > >
> > > > thanks for asking but it seems to be easier to run through this
> > > > process alone for now. As a matter of fact I cannot use the fully
> > > > automated release builds we have defined because they are
> designed
> > > > to check out master's HEAD and create a release from that
> revision
> > > > in
> > > one
> > > > step as opposed to what we did with RC1, i.e. manually creating
> > > > the TAG and then later build and release that revision.
> > > >
> > > > From my point of view it is still desirable to be able to do the
> > > > tagging and releasing in one automated build and I think we are
> on
> > > > a good way of getting there. The only remaining concern I
> > > > currently
> > > have
> > > > is how to orchestrate the multiple (release) build jobs for
> > > > releasing all Californium components together. But maybe that can
> > > > be done using
> > > the Promoted Build plugin...
> > > >
> > > > For now, I have created additional build jobs that check out a
> > > > particular TAG and release the artifacts. But we will do this
> only
> > > for
> > > > RC1 I hope. Thus, if we want to test our automated release
> > > > process,
> > > we
> > > > will need to create RC2 some time soon ;-)
> > > >
> > > > Regards,
> > > > Kai
> > > >
> > > > > -----Original Message-----
> > > > > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-
> > > bounces@xxxxxxxxxxx]
> > > > > On Behalf Of Kovatsch Matthias
> > > > > Sent: Thursday, October 29, 2015 5:13 PM
> > > > > To: Californium (Cf) developer discussions
> > > > > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> > > > >
> > > > > Hi Kai
> > > > >
> > > > > We should definitely start testing the release process. The
> > > > > release review is ongoing and I think it looks good---Nov 4 we
> > > > > should
> > > release.
> > > > >
> > > > > Anything I can/should do? Change or check the *-release jobs on
> > > Hudson?
> > > > >
> > > > > Ciao
> > > > > Matthias
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: cf-dev-bounces@xxxxxxxxxxx
> > > > > > [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > > > > > On Behalf Of Hudalla Kai (INST/ESY)
> > > > > > Sent: Donnerstag, 29. Oktober 2015 13:30
> > > > > > To: Californium (Cf) developer discussions
> > > > > > Subject: Re: [cf-dev] Deploy RC1 to eclipse releases repo
> > > > > >
> > > > > > Oh, I totally forgot that we cannot deploy to Eclipse's
> > > > > > Release Repo using a manual build on private machines but
> only
> > > > > > from out HIPP
> > > > > infrastructure.
> > > > > > Anyways, I would dare try to do this using our HIPP instance
> > > > > > as well
> > > > > > :-)
> > > > > >
> > > > > > Regards,
> > > > > > Kai
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-
> > > > > bounces@xxxxxxxxxxx]
> > > > > > > On Behalf Of Hudalla Kai (INST/ESY)
> > > > > > > Sent: Thursday, October 29, 2015 1:25 PM
> > > > > > > To: Californium (Cf) developer discussions
> > > > > > > Subject: [cf-dev] Deploy RC1 to eclipse releases repo
> > > > > > >
> > > > > > > Dear fellow committers,
> > > > > > >
> > > > > > > since people are already starting to complain why RC1 is
> not
> > > > > > > available yet via Maven [1] ;-), I would like to (manually)
> > > > > > > create
> > > > > a
> > > > > > > release build of RC1 and deploy it to Eclipse's release
> repo
> > > [2]
> > > > > > > using my personal GPG key (hopefully for the last time ;-
> )).
> > > > > > > We can then later decide if we also want to make it
> > > > > > > available on Maven
> > > > > Central ...
> > > > > > >
> > > > > > > Any objections?
> > > > > > >
> > > > > > > [1]
> > > > > > > https://github.com/eclipse/californium.scandium/issues/58
> > > > > > > [2]
> > > > > > > https://repo.eclipse.org/content/repositories/californium-
> > > releas
> > > > > > > es
> > > > > > >
> > > > > > > Regards,
> > > > > > > Kai
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > cf-dev mailing list
> > > > > > > cf-dev@xxxxxxxxxxx
> > > > > > > To change your delivery options, retrieve your password, or
> > > > > > > unsubscribe from this list, visit
> > > > > > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > > > > > _______________________________________________
> > > > > > cf-dev mailing list
> > > > > > cf-dev@xxxxxxxxxxx
> > > > > > To change your delivery options, retrieve your password, or
> > > > > > unsubscribe from this list, visit
> > > > > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > > > > _______________________________________________
> > > > > cf-dev mailing list
> > > > > cf-dev@xxxxxxxxxxx
> > > > > To change your delivery options, retrieve your password, or
> > > > > unsubscribe from this list, visit
> > > > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > > > _______________________________________________
> > > > cf-dev mailing list
> > > > cf-dev@xxxxxxxxxxx
> > > > To change your delivery options, retrieve your password, or
> > > > unsubscribe from this list, visit
> > > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > > _______________________________________________
> > > cf-dev mailing list
> > > cf-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or
> > > unsubscribe from this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/cf-dev
> > _______________________________________________
> > cf-dev mailing list
> > cf-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or
> > unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cf-dev
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev

Back to the top