September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25074) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25074: ---------------------------------- Summary: For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central] Key: JBIDE-25074 URL: https://issues.jboss.org/browse/JBIDE-25074 Project: Tools (JBoss Tools) Issue Type: Task Components: central Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.1.AM3 For JBIDE 4.5.1.AM3 [central]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.1.AM3-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25074) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25074?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25074: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central] > ----------------------------------------------------------------- > > Key: JBIDE-25074 > URL: https://issues.jboss.org/browse/JBIDE-25074 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [central]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25075) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [forge]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25075: ---------------------------------- Summary: For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [forge] Key: JBIDE-25075 URL: https://issues.jboss.org/browse/JBIDE-25075 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.1.AM3 For JBIDE 4.5.1.AM3 [forge]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.1.AM3-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25070) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [aerogear-hybrid]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25070: ---------------------------------- Summary: For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [aerogear-hybrid] Key: JBIDE-25070 URL: https://issues.jboss.org/browse/JBIDE-25070 Project: Tools (JBoss Tools) Issue Type: Task Components: aerogear-hybrid Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.1.AM3 For JBIDE 4.5.1.AM3 [aerogear-hybrid]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.1.AM3-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-24773: ------------------------------------------- I'm a fan of having the .target file be regenerated via Jenkins, since that way we know we're consistent between our local one and the upstream one. My worry with having to regenerate it locally every 3 weeks is that we diverge somehow with the dependencies we're all using on different platforms. (Linux, Mac, Windows) so would be better to have "one .target to rule them all" provided during the build process instead. That said, if the .target file is generated during the build and announced somehow, we'd be able to keep in sync locally through a more manual download and update. I would hope that this thing wouldn't change that often though. > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4160) Closing terminal opened during Container Development Environment start terminates vagrant process

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4160?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-4160. ------------------------------- Closing as this will not be fixed. > Closing terminal opened during Container Development Environment start terminates vagrant process > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4160 > URL: https://issues.jboss.org/browse/JBDS-4160 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 10.1.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 11.1.0.AM2 > > > Closing terminal with running vagrant up command terminates startup process without any warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24996) Script for configuring Cygwin on windows images are not working properly

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24996?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-24996. --------------------------------- > Script for configuring Cygwin on windows images are not working properly > ------------------------------------------------------------------------ > > Key: JBIDE-24996 > URL: https://issues.jboss.org/browse/JBIDE-24996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Jan Richter > Labels: central-ci > Fix For: 4.5.1.AM2 > > > C:\cygwin64\bin folder is empty on image win10-jbds-x64. > Add curl command, please. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22544. --------------------------------- Closing as issue was resolved some time ago in upstream and is not reproducible for a couple of devstudio releases. > Redudant error report in Devstudio's Problems View > -------------------------------------------------- > > Key: JBIDE-22544 > URL: https://issues.jboss.org/browse/JBIDE-22544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Reporter: Ondrej Dockal > Assignee: Victor Rubezhny > Fix For: 4.5.1.AM1 > > Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png > > > Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25069) Add User Access Control permissions for default browser used by central for Windwos snapshots

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25069?page=com.atlassian.jira.plugi... ] Vojtech Prusa updated JBIDE-25069: ---------------------------------- Parent: (was: JBIDE-25063) Issue Type: Feature Request (was: Sub-task) > Add User Access Control permissions for default browser used by central for Windwos snapshots > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25069 > URL: https://issues.jboss.org/browse/JBIDE-25069 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, maven > Environment: Windows 7,8.1, 10 > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > > Job is failing for Windows 7, 8.1 & 10 most likely because lack of User Access Control permissions for default browser used by central component. > My suggestion is: > * change privileges for default browser (edge?) > * change default browser > * in worst case exclude these tests for windows > Now blocked by https://redhat.service-now.com/surl.do?n=PNT0065275 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25013) Refactor integration tests for use with RedDeer 2.0

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25013?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-25013: ------------------------------------- Assignee: Rastislav Wagner (was: Josef Kopriva) > Refactor integration tests for use with RedDeer 2.0 > --------------------------------------------------- > > Key: JBIDE-25013 > URL: https://issues.jboss.org/browse/JBIDE-25013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.5.1.AM3 > > > A number of integration-tests plugins require reddeer 1.2 and need to be migrated to use 2.0. > {code}** [1] ./plugins/org.jboss.tools.seam.reddeer/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [2] ./tests/org.jboss.tools.central.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [3] ./tests/org.jboss.tools.dummy.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [4] ./tests/org.jboss.tools.eclipsecs.ui.test/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [5] ./tests/org.jboss.tools.examples.ui.bot.test/META-INF/MANIFEST.MF ** > 9:Require-Bundle: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [6] ./tests/org.jboss.tools.freemarker.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [7] ./tests/org.jboss.tools.jsf.ui.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [8] ./tests/org.jboss.tools.maven.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [9] ./tests/org.jboss.tools.openshift.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017