Add staging configuration (BUILD-151)

[BUILD-167] Enable the staging profile by default Created: 20/Oct/14  Updated: 04/Nov/14  Resolved: 04/Nov/14

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: POMs 30

Type: Sub-task Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:

 Description   

To avoid "forgetting" to do -P staging; make sure we know how to disable it (for "emergencies" and simply for cases where we don't want or can't stage, e.g for now for anything not-community and not-enterprise)

Unfortunately, we can't just have our staging profile be activated by default, since we only want to activate it during releases.



 Comments   
Comment by Magnolia International [ 20/Oct/14 ]

Tried the "dummy profile" trick, doesn't seem to work

Comment by Magnolia International [ 21/Oct/14 ]

So it works now by using <arguments>-P staging</arguments> on the release-plugin, and introducing 2 extra properties to control the profile itself: disableNexusStaging and enableNexusStaging. Additionally, we've introduced additionalReleaseArguments to allow folks to still pass stuff to the release plugin manually.

Comment by Magnolia International [ 04/Nov/14 ]

While the "fixes" for this have been committed and release, it turns out it doesn't work as expected. One still HAS TO explicitly mention the -Pstaging profile; if not, Maven can't even validate the POM, since it refers to dependencies it can't know about. The fixes above only apply once the release plugin is in effect.

Generated at Sun Feb 11 23:39:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.