June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22556) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22556?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-22556: ------------------------------------- Assignee: Martin Malina > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Integration Tests] > -------------------------------------------------------------------- > > Key: JBIDE-22556 > URL: https://issues.jboss.org/browse/JBIDE-22556 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.4.1.S116 > > > For JBIDE 4.4.1.Alpha1 [Integration Tests]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22518) Create New and Noteworthy for 4.4.0.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22518?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22518. --------------------------------- All sub-tasks are closed. Closing this. > Create New and Noteworthy for 4.4.0.Final > ----------------------------------------- > > Key: JBIDE-22518 > URL: https://issues.jboss.org/browse/JBIDE-22518 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.4.0.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22538) Core/General New and Noteworthy for 4.4.0.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22538?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22538. --------------------------------- There were no issues to document in this component's query. Closing. > Core/General New and Noteworthy for 4.4.0.Final > ----------------------------------------------- > > Key: JBIDE-22538 > URL: https://issues.jboss.org/browse/JBIDE-22538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.0.Final > > > If no news for 4.4.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3739. ------------------------------- Verified in devstudio 10.0.0.GA B33. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22449) Better parse qualifiers for versions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22449?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22449: --------------------------------------- [~fbricon], do you want to test this somehow? More importantly, is the test passing? I can't find it here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Better parse qualifiers for versions > ------------------------------------ > > Key: JBIDE-22449 > URL: https://issues.jboss.org/browse/JBIDE-22449 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Final > > > Currently, in ide-config.properties, if no 1.2.3.GA-123456-23455 version is found, we fall back to 1.2.3.GA. > We need to be able to have a more fined-grained fallback on qualifiers: > .dev-115-maxisstupid-v12323 then > .dev-115-maxisstupid then > .dev-115 then > .dev-115 then > .dev -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22627) Docker image tag is ignored in Deploy Image to OpenShift wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22627?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22627: ---------------------------------- Labels: docker openshift_v3 (was: ) > Docker image tag is ignored in Deploy Image to OpenShift wizard > --------------------------------------------------------------- > > Key: JBIDE-22627 > URL: https://issues.jboss.org/browse/JBIDE-22627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > When deploying a docker image from docker explorer by selecting context menu item Deploy to OpenShift..., image name in opened Deploy Image to OpenShift wizard does not contain tag of the image. This requires manual addition of image tag, otherwise latest tag is presumed by default, what does not have to be desired at some scenarios. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22627) Docker image tag is ignored in Deploy Image to OpenShift wizard

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22627: ------------------------------------- Summary: Docker image tag is ignored in Deploy Image to OpenShift wizard Key: JBIDE-22627 URL: https://issues.jboss.org/browse/JBIDE-22627 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Marián Labuda When deploying a docker image from docker explorer by selecting context menu item Deploy to OpenShift..., image name in opened Deploy Image to OpenShift wizard does not contain tag of the image. This requires manual addition of image tag, otherwise latest tag is presumed by default, what does not have to be desired at some scenarios. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22038) Errors on startup with Java 9

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22038?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22038. ------------------------------- [~mmalina] I believe you are right in believing this is done. And I shall close this issue. > Errors on startup with Java 9 > ----------------------------- > > Key: JBIDE-22038 > URL: https://issues.jboss.org/browse/JBIDE-22038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Martin Malina > Labels: java9 > Fix For: 4.4.0.Final > > > Starting fresh JBT/JBDS with Java 9 results in an error dialog popping up with these two errors: > {noformat}An internal error occurred during: "Update project wizard list". > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38) > at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31) > at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1064) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:282) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:273) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 6 more{noformat} > {noformat}An internal error occurred during: "Download quickstarts list". > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263) > at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28) > at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 7 more{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22468) If host is unreachable, credentials ui fails to load favicon over and over

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22468?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22468: ---------------------------------- Attachment: credentials-domain.png [~rob.stryker], where exactly should the favicon be? I don't have any for jboss.org or redhat.com either: !credentials-domain.png! > If host is unreachable, credentials ui fails to load favicon over and over > -------------------------------------------------------------------------- > > Key: JBIDE-22468 > URL: https://issues.jboss.org/browse/JBIDE-22468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > Attachments: credentials-domain.png > > > Make a new credential domain such as "myhost". This should fail quickly and should no longer make repeated attempts to load a favicon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22626: ---------------------------------- Labels: docker openshift_v3 (was: ) > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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