October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20693) Add new features for tools.jboss.org/features/

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20693?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20693: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add new features for tools.jboss.org/features/ > ---------------------------------------------- > > Key: JBIDE-20693 > URL: https://issues.jboss.org/browse/JBIDE-20693 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20991) support automatic setup of CDK start/stop server

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20991?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20991: ----------------------------------- Fix Version/s: 4.3.1.Beta1 > support automatic setup of CDK start/stop server > ------------------------------------------------ > > Key: JBIDE-20991 > URL: https://issues.jboss.org/browse/JBIDE-20991 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.Beta1 > > > related to JBIDE-20990 it should be possible to automatically setup the CDK server based on what Installer have installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Added non-version composites to the integration stack snapshots sites for JBT: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/894e2a... > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20993: ------------------------------------ Note that without symlinks we need additional configuration in scripts such as: https://github.com/jbosstools/jbosstools-build-ci/commit/a88ca95a61e3ad71... https://github.com/jbosstools/jbosstools-build-ci/commit/07e67973c00ad3fa... > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20976: ------------------------------- Attachment: plugins_Mars.0-vs.1.vs.NeonM2.png features_Mars.0-vs.1.vs.NeonM2.png.png After updating TP to M2, we now have a much smaller set of IUs w/ Neon.M2 versions older than Mars.1: {code} org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 org.eclipse.jetty.webapp 9.2.13.v20150730 org.eclipse.jetty.xml 9.2.13.v20150730 org.eclipse.pde.doc.user 3.11.1.v20150903-1352 org.eclipse.platform.doc.user 4.5.1.v20150819-1130 org.eclipse.swt 3.104.1.v20150825-0743 org.eclipse.swt.gtk.linux.x86_64 3.104.1.v20150825-0743 org.eclipse.wst.server.core 1.7.0.v201508271522 org.eclipse.wst.server.discovery 1.1.0.v201508271522 org.eclipse.wst.server.ui 1.5.201.v201509022125 org.eclipse.wst.server_core.feature 3.3.600.v201508271522 org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 {code} -- https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... -- https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... !features_Mars.0-vs.1.vs.NeonM2.png.png! !plugins_Mars.0-vs.1.vs.NeonM2.png! > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21003: ------------------------------------ Should I pull a new mirror from http://download.eclipse.org/linuxtools/updates-docker-nightly/features/?d or wait for an actual release? Currently, the latest versions of the docker tooling feature are: * http://download.eclipse.org/linuxtools/updates-docker-nightly/features/or... * http://download.eclipse.org/linuxtools/update-neon-docker-m2/features/org... * http://download.eclipse.org/linuxtools/update-mars-1-docker-rc4/features/... Do we want a different version pulled for 4.3.1.Beta1 / Mars vs. 4.4.0.Alpha1 / Neon? > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20947. ------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21001: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/544, https://github.com/jbosstools/jbosstools-jst/pull/545, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315 (was: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21011) Фильм Врата тьмы смотреть онлайн в хорошем HD 720 качестве на русском BDRip 22.10.2015

by ecorezgg ecorezgg (JIRA)

ecorezgg ecorezgg created JBIDE-21011: ----------------------------------------- Summary: Фильм Врата тьмы смотреть онлайн в хорошем HD 720 качестве на русском BDRip 22.10.2015 Key: JBIDE-21011 URL: https://issues.jboss.org/browse/JBIDE-21011 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: ecorezgg ecorezgg Смотреть "Врата тьмы" здесь - http://bit.ly/1QSp5pK Смотреть "Врата тьмы" здесь - http://bit.ly/1QSp5pK Смотреть "Врата тьмы" здесь - http://bit.ly/1QSp5pK --- --- --- Врата тьмы смотреть онлайн в отличном качестве hdrip 720 07.10.2015 смотреть онлайн full free movie фильм Врата тьмы 2015 07.10.2015 Врата тьмы сериал триллер комедия семейный боевик фантастика пoлнaя верcия смотреть онлайн 07.10.2015 Врата тьмы смотреть видеo 07.10.2015 Врата тьмы yжacы 2015 смотреть онлайн 07.10.2015 Врата тьмы смотреть скачать 07.10.2015 смотреть yжacы Врата тьмы 07.10.2015 Врата тьмы тoррент смотреть 07.10.2015 yбрaть з дрyзей смотреть 07.10.2015 Врата тьмы 2015 смотреть онлайн кинoгo 07.10.2015 Врата тьмы смотреть онлайн нa телефoне 07.10.2015 кинo смотреть онлайн беcплaтнo Врата тьмы 07.10.2015 Врата тьмы смотреть kinogo 07.10.2015 смотреть трейлер фильмa Врата тьмы 07.10.2015 смотреть Врата тьмы 2 07.10.2015 смотреть в oтличнoм кaчеcтве Врата тьмы 07.10.2015 Врата тьмы смотреть онлайн вк 07.10.2015 смотреть фильм Врата тьмы кинoгo 07.10.2015 смотреть Врата тьмы через 07.10.2015 смотреть фильм 2015 гoдa Врата тьмы 07.10.2015 смотреть фильм Врата тьмы бoбфильм 07.10.2015 Врата тьмы 2015 смотреть онлайн трейлер 07.10.2015 Врата тьмы смотреть онлайн видеo 07.10.2015 смотреть онлайн yжacтик Врата тьмы 07.10.2015 смотреть yжacтик Врата тьмы 2015 07.10.2015 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-20948. -------------------------------- > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear] > ---------------------------------------------------------- > > Key: JBIDE-20948 > URL: https://issues.jboss.org/browse/JBIDE-20948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Aerogear]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear 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, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015