September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23072) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central Discovery]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23072?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23072. ---------------------------------- Resolution: Done > For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central Discovery] > ------------------------------------------------------------------------------ > > Key: JBIDE-23072 > URL: https://issues.jboss.org/browse/JBIDE-23072 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.1.Final > > > For JBIDE 4.4.1.Final [Central Discovery]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA > [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.4.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch: > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.1.x > git push origin jbosstools-4.4.1.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too. > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Discovery 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in commit messages so JIRAs are closed automatically

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23091: ---------------------------------- Summary: use #close smart tag in commit messages so JIRAs are closed automatically Key: JBIDE-23091 URL: https://issues.jboss.org/browse/JBIDE-23091 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Nick Boldt Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23090) instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23090: ---------------------------------- Summary: instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email Key: JBIDE-23090 URL: https://issues.jboss.org/browse/JBIDE-23090 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Nick Boldt instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email so that Alexey or Jeff can run it locally in their /tmp folder 1. script how to fetch jbosstools-build-ci 2. script how to then run getProjectRootPomParents.sh -w1 /tmp/some-folder/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23075) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23075?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23075: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23075 > URL: https://issues.jboss.org/browse/JBIDE-23075 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Final > > > For JBIDE 4.4.1.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA > [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.4.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch: > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.1.x > git push origin jbosstools-4.4.1.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too. > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23061) Integration tests: have warning when scaling to 0 asserted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23061?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23061: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.1.Final) > Integration tests: have warning when scaling to 0 asserted > ---------------------------------------------------------- > > Key: JBIDE-23061 > URL: https://issues.jboss.org/browse/JBIDE-23061 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.1.Final) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23016: ---------------------------------------- {quote}So this scenario would only apply if the user installs all the components manually, not using devsuite installer. But that's still a supported scenario I believe. And still believe it would actually work.{quote} Can you please verify it? > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Final > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23045: ---------------------------------------- For clarification. The XML source editor comes from Eclipse. [~jludvice] your suggestions make sense IMO but they should be addressed to upstream Eclipse. > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23089) when central tests crash job breaks due to dirty workspace

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23089: ---------------------------------- Summary: when central tests crash job breaks due to dirty workspace Key: JBIDE-23089 URL: https://issues.jboss.org/browse/JBIDE-23089 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, central Affects Versions: 4.4.1.Final, 4.4.2.AM1 Reporter: Nick Boldt {code} 15:00:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.central.test: Working tree is dirty. 15:00:03 [ERROR] git status central/tests/org.jboss.tools.central.test: 15:00:03 [ERROR] 15:00:03 [ERROR] Untracked files: 15:00:03 [ERROR] central/tests/org.jboss.tools.central.test/hs_err_pid29878.log 15:00:03 [ERROR] 15:00:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above). 15:00:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring 15:00:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin{code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Workaround: wipe workspace, try again Solution: add hs_err_pid*.log to .gitignore -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23085) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23085?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-23085. --------------------------------- Resolution: Done > For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Arquillian] > ----------------------------------------------------------------------- > > Key: JBIDE-23085 > URL: https://issues.jboss.org/browse/JBIDE-23085 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.1.Final > > > For JBIDE 4.4.1.Final [Arquillian]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA > [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.4.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch: > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.1.x > git push origin jbosstools-4.4.1.x > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too. > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Arquillian 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)

9 years, 7 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