[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Mickael Istria (JIRA)
[ 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21267:
----------------------------------------
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)
10 years, 4 months
[JBoss JIRA] (JBDS-3281) Screencasts: Git
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3281:
--------------------------------
Fix Version/s: 9.1.0.Beta2
(was: 9.1.0.Beta1)
> Screencasts: Git
> ----------------
>
> Key: JBDS-3281
> URL: https://issues.jboss.org/browse/JBDS-3281
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 9.1.0.Beta2
>
>
> As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse.
> Use cases include:
> 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project
> assume a clone, add (or modify), commit, push workflow
> a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly)
> b- navigate/browse an existing repository
> c- git add - for a newly added class or file
> d- git commit -a
> e- git push
> as a new member of the team, just having only installed JBDS, I need to resolve a pull request.
> 2) other scenarios
> - git init a current project that I have in my workspace (and should I move it outside of my workspace first)
> - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3280) Screencasts: Java EE
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3280?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3280:
--------------------------------
Fix Version/s: 9.1.0.Beta2
(was: 9.1.0.Beta1)
> Screencasts: Java EE
> --------------------
>
> Key: JBDS-3280
> URL: https://issues.jboss.org/browse/JBDS-3280
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 9.1.0.Beta2
>
>
> As a new Eclipse+Java EE developer, I need educational screencasts, around 5 minutes each that educate me on a specific Java EE development capabilities of JBDS.
> Use cases include:
> - JPA - how to add one, content-assist, relationships
> - database reverse engineering via DTP vs Forge
> - JAX-RS: creation of new endpoints, content-assist, tester - including the GET/POST/PUT/DELETE with JSON payloads
> - JAX-WS: creation of new endpoints, content-assist, tester
> - CDI special features
> - Servlets
> - JSF
> - deployment to localhost EAP
> - deployment to remove EAP
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3251:
--------------------------------
Fix Version/s: 9.1.0.Beta2
(was: 9.1.0.Beta1)
> Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3251
> URL: https://issues.jboss.org/browse/JBDS-3251
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: documentation, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Martin Malina
> Fix For: 9.1.0.Beta2
>
>
> suggestions from F2F:
> |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes|
> |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc
> HTML5/Hybrid Mobile|
> |OpenShift v3| start, stop, deploy apps
> |eGit Top Use Cases|
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21296.
------------------------------
Fix Version/s: 4.3.1.Beta1
Resolution: Cannot Reproduce Bug
No idea... respin was blue.
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
Closing / cannot reproduce.
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Labels: testfailure
> Fix For: 4.3.1.Beta1
>
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21267:
------------------------------------
I don't think I have permission to approve Nexus releases. Can you email me details on how/where to do that? I've never had to do that before.
> 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21267 at 12/11/15 9:03 AM:
--------------------------------------------------------------
Ok, I was thinking about the CI jobs settings. So yes, they should be released for better consistency.
If you want to take care of it, the process is
# move to a non-SNAPSHOT version, push change
# run the CI job that publishes the SNAPSHOT, or use "mvn deploy" locally
# go to Nexus to approve and release the staging repo.
# Update parent pom to use the new release version
# Bump version to new snapshot
Edit by Nick to add one more:
# Update all the 4.3.mars jobs to use the new version (next week after Beta1 is done)
was (Author: mickael_istria):
Ok, I was thinking about the CI jobs settings. So yes, they should be released for better consistency.
If you want to take care of it, the process is
# move to a non-SNAPSHOT version, push change
# run the CI job that publishes the SNAPSHOT, or use "mvn deploy" locally
# go to Nexus to approve and release the staging repo.
# Update parent pom to use the new release version
# Bump version to new snapshot
Edit by Nick to add one more:
# Update all the 4.3.mars jobs to use the new version
> 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)
10 years, 4 months