February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3579: ----------------------------------- Not really, I borked the m2e contribution for Mars.2 so will have to release it / install it separetely > Fuse archetype catalog cannot be added with JBDS 9 > -------------------------------------------------- > > Key: JBDS-3579 > URL: https://issues.jboss.org/browse/JBDS-3579 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: maven > Affects Versions: 9.0.0.GA > Reporter: Keith Babo > Assignee: Fred Bricon > Fix For: 9.1.0.CR1 > > > When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally). > Archetype catalog in question: > https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... > Steps to reproduce: > - Preferences -> Maven -> Archetypes -> Add Remote Catalog > - Add URL above for Catalog File > - Click Verify ... and you get the message "Remote catalog is empty" > - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog." > Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21066 at 2/19/16 1:47 PM: ------------------------------------------------------------- Once again, Mars.2 has been updated and the version of org.eclipse.tm.terminal.view.ui remains at 4.0.0.201506031417. Same for Neon.0.M5: !tm.term.view.png! But there are newer nightlies we can use in our TP. Just need +1 from [~akazakov] and/or [~maxandersen] that we're OK to include random nightly 4.0.0.20151107 bits in our soon-to-be Final release. And need to know if I should pull just the one plugin, or all the tm.terminal stuff. was (Author: nickboldt): Once again, Mars.2 has been updated and the version of org.eclipse.tm.terminal.view.ui remains at 4.0.0.201506031417. Same for Neon.0.M5: !tm.term.view.png! But there are newer nightlies we can use in our TP. Just need +1 from [~akazakov] and/or [~maxandersen] that we're OK to include random nightly bits in our soon-to-be Final release. > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21066: ------------------------------- Attachment: tm.term.view.png Once again, Mars.2 has been updated and the version of org.eclipse.tm.terminal.view.ui remains at 4.0.0.201506031417. Same for Neon.0.M5: !tm.term.view.png! But there are newer nightlies we can use in our TP. Just need +1 from [~akazakov] and/or [~maxandersen] that we're OK to include random nightly bits in our soon-to-be Final release. > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21367) Include nightly build of Docker tooling in CR1 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21367?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-21367. -------------------------------- Resolution: Done Pulled bits from http://download.eclipse.org/linuxtools/update-mars-2-docker-rc4/ into http://download.jboss.org/jbosstools/updates/requirements/docker/1.2.1.20... and then into the 4.50.x and 4.52.x TPs: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.2.CR1... https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1... > Include nightly build of Docker tooling in CR1 TP > ------------------------------------------------- > > Key: JBIDE-21367 > URL: https://issues.jboss.org/browse/JBIDE-21367 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.0.CR1, 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > Attachments: docker121rc4.png > > > Please include the 1.2.1.RC4 build of the Docker tooling once the TP for JBoss Tools 4.3.1.CR1 needs to be built. > Bits should be available from http://download.eclipse.org/linuxtools/updates-docker-nightly-mars/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21367) Include nightly build of Docker tooling in CR1 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21367?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21367: ------------------------------- Attachment: docker121rc4.png !docker121rc4.png! > Include nightly build of Docker tooling in CR1 TP > ------------------------------------------------- > > Key: JBIDE-21367 > URL: https://issues.jboss.org/browse/JBIDE-21367 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.0.CR1, 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > Attachments: docker121rc4.png > > > Please include the 1.2.1.RC4 build of the Docker tooling once the TP for JBoss Tools 4.3.1.CR1 needs to be built. > Bits should be available from http://download.eclipse.org/linuxtools/updates-docker-nightly-mars/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3590: ------------------------------------------- I could do the jira clean up in about 10 seconds - reviewing that PR will take a few hours to actually grok and verify it. Thus no, I don't think that would be faster. Please work with [~dgolovin] to get the PR reviewed. > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21724) when clicking cancel on "configure automated error reporting" it disables all

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21724: ------------------------------------------- Summary: when clicking cancel on "configure automated error reporting" it disables all Key: JBIDE-21724 URL: https://issues.jboss.org/browse/JBIDE-21724 Project: Tools (JBoss Tools) Issue Type: Bug Components: aeri Reporter: Max Rydahl Andersen Priority: Critical When you click configure in aeri preferences the dialog only have Disable and Enable buttons. Clicking "close" in upper left (i.e. Cancel as in = don't do anything) result in all reporting disabled. I would expect closing the dialog with the close buton or escape would change nothing. - but i globally disables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21719: --------------------------------------------- moving this to specific fixversion so it does not get marked to be looked at after GA. We need to solve/agree on this before GA anyways. [~apodhrad] "Moreover, whenever you open a new view (e,g, Error Log) it is opened in the narrow space next the the Properties view." That is not good. I'm not seeing that - does it happen for any new view ? If anything it should open in same tab area. > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.1.CR1 > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21719: ---------------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.1.CR1 > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21723) debug/warning errors from aeri in logs

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21723: ------------------------------------------- Summary: debug/warning errors from aeri in logs Key: JBIDE-21723 URL: https://issues.jboss.org/browse/JBIDE-21723 Project: Tools (JBoss Tools) Issue Type: Bug Components: aeri Reporter: Max Rydahl Andersen seeing a info and warning message when errors occurs. {code} eclipse.buildId=4.6.0.I20151209-2300 java.version=1.8.0_20 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring org.eclipse.epp.logging.aeri.ide Info Fri Feb 19 18:56:42 CET 2016 Added ‘Unknown category 'org.jboss.to…8.jar_5289305038018513896.jar’ under ‘b2c2e18436026b0d358c3d135c923fc4’ to local history at /Users/max/workspaces/eclipsee…org.jboss.tools/local-history. ; version: 1.100.0.v20160203-1727 org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.doRemember(LocalReportsHistory.java:137) at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.remember(LocalReportsHistory.java:119) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:190) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} and {code} eclipse.buildId=4.6.0.I20151209-2300 java.version=1.8.0_20 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring org.eclipse.epp.logging.aeri.ide Warning Fri Feb 19 18:56:42 CET 2016 Unexpected response : UNKNOWN ‐ UNKNOWN ; version: 1.100.0.v20160203-1727 org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.tryParse(IO.java:237) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.upload(IO.java:116) at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:189) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016