[
https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-21267 at 12/11/15 9:18 AM:
------------------------------------------------------------------
Open a request against for permission to stage build and release them to the
ORG/repository.jboss.org component.
Once you're granted the permission, you need to edit your ~/.m2/settings.xml to add a
block such as
{code:xml}
<servers>
<server>
<id>jboss-snapshots-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-staging-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-release-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-releases-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
</servers>
{code}
This will allow you to run "mvn deploy" locally to stage some content (sometimes
useful).
Then once the content is staged, go to
https://repository.jboss.org/nexus/, log in (link
on top right) with your
jboss.org credentials. On the left you'll see a "staging
repositories". Browse the staging repositories until you find the one you want to
release (looking at date/time is the fastest way to find what you want). Click it, verify
content, hit "close" if it's OK, give a dozen of seconds to Nexus to verify
the eligibility of the content as a release, click "Reload" and then
"Release".
was (Author: mickael_istria):
Open a request against the
ORG/repository.jboss.org component.
Once you're granted the permission, you need to edit your ~/.m2/settings.xml to add a
block such as
{code:xml}
<servers>
<server>
<id>jboss-snapshots-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-staging-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-release-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
<server>
<id>jboss-releases-repository</id>
<username>nboldt</username>
<password>yourJBossOrgPassword</password>
</server>
</servers>
{code}
This will allow you to run "mvn deploy" locally to stage some content (sometimes
useful).
Then once the content is staged, go to
https://repository.jboss.org/nexus/, log in (link
on top right) with your
jboss.org credentials. On the left you'll see a "staging
repositories". Browse the staging repositories until you find the one you want to
release (looking at date/time is the fastest way to find what you want). Click it, verify
content, hit "close" if it's OK, give a dozen of seconds to Nexus to verify
the eligibility of the content as a release, click "Reload" and then
"Release".
For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites,
build-ci, maven-plugins,
dl.jb.org, devdoc, versionwatch]
--------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-21267
URL:
https://issues.jboss.org/browse/JBIDE-21267
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Reporter: Nick Boldt
Assignee: Mickael Istria
Priority: Blocker
Labels: task
Fix For: 4.3.1.Beta1
For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins,
dl.jb.org, devdoc,
versionwatch]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final
(eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion =
4.3.1.Beta1
[Unresolved JIRAs with fixVersion = 4.3.1.Beta1,
9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly
upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to
4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta1 (after
4.3.0.Final was released), you do *not* need to do so again.
Please also ensure that the version of your code in the master branch is *greater* than
your code in the 4.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version
-DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform
version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
or
mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new
*{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta1x
git push origin jbosstools-4.3.1.Beta1x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x
branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the
latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your
*{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
* *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your
*{color:orange}jbosstools-4.3.x{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy
JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...]
to do, please complete them next.
[Search for all task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...],
or [Search for build, build-sites, build-ci, maven-plugins,
dl.jb.org, devdoc,
versionwatch task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)