December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21233: --------------------------------------------- Since we in the past have found/had several issues including the TP as composite in past I'm curious to grok what this suggestion actually does and if those past issues are not relevant anymore. a) is this just about the *final* form on the GA site to users ? i.e. Integration stack and other builds would not want the TP included in the composite when depending on this. b) in past we had TP in associated site to avoid it got listed either in categorized or uncategorized content - is that not an issue anymore ? c) "we now always co-release JBT with its TP in the same URL" i'm not following as good reason to do this since my assumption is we would be interested in being able to release *smaller* parts rather than bigger parts together ? sorry if seem like dumb questions but I just remember all the issues that occurred when TP was part of the sites in the past, so just educate me on what changed. > remove need for a targetplatforms/jbosstoolstarget/neon site > ------------------------------------------------------------ > > Key: JBIDE-21233 > URL: https://issues.jboss.org/browse/JBIDE-21233 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ > But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain. > Therefore I propose we stop linking to this site. > We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-357) Create a new JBDSIS-based independent installer bundle

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-357?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-357. ---------------------------- Resolution: Rejected Ref: https://issues.jboss.org/browse/JBDS-3276 Retaining the ability to build a JBDSIS independent installer but not moving forward with releasing one at this time. > Create a new JBDSIS-based independent installer bundle > ------------------------------------------------------ > > Key: JBTIS-357 > URL: https://issues.jboss.org/browse/JBTIS-357 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Paul Leacu > Assignee: Nick Boldt > > a: Check for the existance of an inserted zip > b: if found, present user with the option to install one or more of the 3 feature groupings (based on product definitions). These are the same groupings seen in Central. > So the logic for this "if found do..." should be built into the installer by default (and ignored for Core); should IS need to respin the logic after we GA, they'll need to rebuild from our repo. Not ideal but better than having to fork the installer entirely. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21272) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21272?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-21272. ---------------------------------- > For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Playground] > -------------------------------------------------------- > > Key: JBIDE-21272 > URL: https://issues.jboss.org/browse/JBIDE-21272 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. 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, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Playground 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21152) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21152?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21152. --------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 Resolution: Partially Completed I made the error message more explicit : "A remote Git repository using the HTTP(S) protocol must be defined on project {0}" > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21152 > URL: https://issues.jboss.org/browse/JBIDE-21152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20550) New Project Example: Tooltip missing for requirement with a warning triangle

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20550?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20550. --------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) Resolution: Done Fixed in 4.3.x and master See http://screencast.com/t/lXdjzlcFzh > New Project Example: Tooltip missing for requirement with a warning triangle > ---------------------------------------------------------------------------- > > Key: JBIDE-20550 > URL: https://issues.jboss.org/browse/JBIDE-20550 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > Attachments: empty-tooltip.png > > > When you open a new project example wizard and there is a requirement which is not really met, a yellow warning triangle may be shown. > I wanted to know what this means so I pointed my mouse at it a an empty tooltip was shown. We should put some text into the tooltip explaining what's going on. > The screenshot below already shows the empty tooltip when you hover over the triangle: > !empty-tooltip.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21261) Fix ECMA5 content assist JUnit test

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21261?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21261: ----------------------------------- Fix Version/s: 4.3.1.Beta2 > Fix ECMA5 content assist JUnit test > ----------------------------------- > > Key: JBIDE-21261 > URL: https://issues.jboss.org/browse/JBIDE-21261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript > Affects Versions: 4.3.1.Beta1 > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > During CI build on jenkins JUnit I test fails. Filing test checks for ECMA5 related proposals in content assist for .js file in JavaScript project. With manually created project and .js file everything works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-21297: ---------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21297 > URL: https://issues.jboss.org/browse/JBIDE-21297 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-21297. ----------------------------------- Resolution: Duplicate Issue > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21297 > URL: https://issues.jboss.org/browse/JBIDE-21297 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.3.1.Beta1, 4.3.1.Beta2, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21305) Include Docker tooling 1.2.0.Final in TP

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21305?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21305: ---------------------------------- Description: Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download) Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. was:Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download at eclipse.org) in TP 4.50.x and 4.51.x (since consumed by OpenShift tooling) for both JBoss Tools and JBoss Developer Studio > Include Docker tooling 1.2.0.Final in TP > ---------------------------------------- > > Key: JBIDE-21305 > URL: https://issues.jboss.org/browse/JBIDE-21305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download) > Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21306) "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21306?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21306. --------------------------------- Resolution: Done Switched to "Do you accept the following untrusted SSL certificate?" !http://content.screencast.com/users/fbricon/folders/Jing/media/e582b7c0-9779-46f7-81b2-beeeda98f0d2/00000257.png|width=525! Fixed in master/4.3.x. > "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes > ----------------------------------------------------------------------------------- > > Key: JBIDE-21306 > URL: https://issues.jboss.org/browse/JBIDE-21306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > when connecting to CDK I get dialog stating: > Please Accept or Deny the following untrusted SSL certificate" > but the buttons say No Yes. > Either make the title into a question or change the buttons to say Accept / Deny -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015