September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-880) Update known issues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-880?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-880: ------------------------------ Fix Version/s: 10.0.0.Alpha1 > Update known issues > ------------------- > > Key: JBTIS-880 > URL: https://issues.jboss.org/browse/JBTIS-880 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 10.0.0.Alpha1, 9.0.2.CR1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 10.0.0.Alpha1, 9.0.2.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23127: ---------------------------------------- [~jeffmaury] I believe so, however we're not involved in it at all so far. > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23127: ------------------------------------ Oxygen: will Java9 support be available > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23159: ------------------------------------ Correction. You have to wrap lists of projects passed to getProjectRootPomParents.sh with quotes: Thus: {code} ./util/getProjectRootPomParents.sh -updateRootPom -b master -b2 master \ -pv 4.4.2.AM1-SNAPSHOT -w1 /tmp/jbt.github -p1 "aerogear arquillian base browsersim central \ discovery forge freemarker hibernate javaee jst livereload openshift server vpe webservices \ integration-tests" -p2 "build build-sites devdoc download.jboss.org maven-plugins versionwatch" \ -p3 "artwork ci devdoc product qa website"{code} > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23159 at 9/19/16 10:06 PM: -------------------------------------------------------------- Correction. You have to wrap lists of projects passed to getProjectRootPomParents.sh with quotes: Thus: {code} ./util/getProjectRootPomParents.sh -updateRootPom -b master -b2 master \ -pv 4.4.2.AM1-SNAPSHOT -w1 /tmp/jbt.github -p1 "aerogear arquillian base browsersim central \ discovery forge freemarker hibernate javaee jst livereload openshift server vpe webservices \ integration-tests" -p2 "build build-sites devdoc download.jboss.org maven-plugins versionwatch" \ -p3 "artwork ci devdoc product qa website"{code} I fixed the jobs to hopefully pass in the escaped quotes correctly next time. was (Author: nickboldt): Correction. You have to wrap lists of projects passed to getProjectRootPomParents.sh with quotes: Thus: {code} ./util/getProjectRootPomParents.sh -updateRootPom -b master -b2 master \ -pv 4.4.2.AM1-SNAPSHOT -w1 /tmp/jbt.github -p1 "aerogear arquillian base browsersim central \ discovery forge freemarker hibernate javaee jst livereload openshift server vpe webservices \ integration-tests" -p2 "build build-sites devdoc download.jboss.org maven-plugins versionwatch" \ -p3 "artwork ci devdoc product qa website"{code} > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23159: ------------------------------------ No, it does NOT do the upversioning because every project is different. Some keep all the plugins/features aligned, some use a mix of 1.x, 2.x, 3.x, and 4.x plugins. Also, we don't blindly upversion just because we've branched. We only upversion where it makes sense. Sometimes we upversion from x.y.z to x.y.z+1. Sometimes we upversion to x.y.z+99 (eg., to move to 4.3.100 while 4.3.1 is in the maintenance branch). And sometimes, we move to x.y+1.0 (eg., from 1.1.1 to 1.2.0) because bigger changes are planned as we move to a new version of Eclipse. I would expect this to be true of Openshift as it depends on Docker Tools, and Docker Tools will be moving up to a x.y+1 version in Neon.1. I can't script all those rules since they vary by project (and sometimes by subproject too) so I leave it to the component leads to know when/how to upversion correctly, using the script noted in the generated JIRAs: {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} There's also the baseline comparison check that will fail when devs forget to upversion. But it won't tell them HOW to upversion, only that the version needs to be greater than the baseline, which is currently set to jbosstools 4.4.1.Final. So if a project like Openshift forgets to bump from 3.3.0 to 3.3.1, and ends up trying to build 3.3.0.AM1 when 3.3.0.Final is in the baseline, it'll complain: {code} [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.openshift.client: Version have moved backwards for (org.jboss.tools.openshift.client/3.3.0.AM1-v20160917-1037-B1568). Baseline has 3.3.0.Final-v20160902-1639-B14) with delta: 0.0.0 -> [Help 1] {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4032: ------------------------------------- Rob, were you able to solve this problem? > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > Fix For: 10.2.0.AM1 > > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23158) Update parent pom in main branch after codefreeze branching

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23158?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23158: ------------------------------------ Sure, but one of the projects for which a JIRA was generated in JBIDE-23159 should have been jbosstools-build, including bumping that project's pom to a new version (jbosstools-build/parent/pom.xml that is). > Update parent pom in main branch after codefreeze branching > ----------------------------------------------------------- > > Key: JBIDE-23158 > URL: https://issues.jboss.org/browse/JBIDE-23158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a release when codefreezing and also update parent poms in those branches should also update parent pom in the main (master or maintenance) branch. > For example if we update pom in just created 4.4.1.x branch to 4.4.1.Final then we also need to update the parent pom in master to 4.4.2.AM1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23158) Update parent pom in main branch after codefreeze branching

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23158?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23158: ---------------------------------------- This issue is about updating the parent pom in pom.xml's. JBIDE-23159 is about upversioning component versions. > Update parent pom in main branch after codefreeze branching > ----------------------------------------------------------- > > Key: JBIDE-23158 > URL: https://issues.jboss.org/browse/JBIDE-23158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a release when codefreezing and also update parent poms in those branches should also update parent pom in the main (master or maintenance) branch. > For example if we update pom in just created 4.4.1.x branch to 4.4.1.Final then we also need to update the parent pom in master to 4.4.2.AM1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23159: ---------------------------------------- Does this script also upversioning the component versions? It looks like it only updates the parent pom? > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016