December 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-542) contents of http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/earlyaccess/ differ from github sources and contains invalid child site pointer

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-542: -------------------------------- Summary: contents of http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... differ from github sources and contains invalid child site pointer Key: JBTIS-542 URL: https://issues.jboss.org/browse/JBTIS-542 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 4.3.0.Alpha2 Reporter: Nick Boldt Assignee: Paul Leacu Fix For: 4.3.0.Alpha2 Error logged in Eclipse when loading JBT update site: {code}!MESSAGE No repository found at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... Reason: I'm looking at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... because the composite*.xml files attempt to reference the p2.index file instead of being an empty repo. This is what causes the error above. But when I look at the sources in github [1], I see a completely different site. Which is correct? Should the site be empty (no child sites), or should it ref 4.3.0.Alpha2 ? [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... Also, how did this site get corrupted? Was it some automatic generation step? Or...? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21377: ------------------------------- Summary: Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category (was: Incliude Yaml editor) > Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Incliude Yaml editor

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21377: ---------------------------------------- Unless this editor has major flaws on performance or UX (adding useless menus here and there), I think it's better to have it mandatory. > Incliude Yaml editor > -------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Incliude Yaml editor

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21377: ------------------------------------ Alternatives to creating an install-time dependency from one of our JBT/JBDS features, eg., Central Community, JSDT, com.jboss.devstudio.core.feature: * we could include this as a new Central connector for both JBT and JBDS, making it visible but optional after JBT/JBDS install * we could add it to the "Abridged JBoss Tools / JBDS" categories on the update sites, so it's available from Marketplace installs, making it highly encouraged when doing an initial install, but still optional > Incliude Yaml editor > -------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Incliude Yaml editor

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-21377: -------------------------------------- Summary: Incliude Yaml editor Key: JBIDE-21377 URL: https://issues.jboss.org/browse/JBIDE-21377 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: updatesite Affects Versions: 4.3.1.Beta1 Reporter: Mickael Istria There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. This would require adding it to the TP and adding a dependency from a JBT feature to it. On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21376: ---------------------------------- Attachment: Screenshot 2015-12-21 18.06.40.png [~mlabuda], can you clarify on where to look for exactly ? Here I can't see those entries in the "Image Stream" node in the OpenShift Explorer. To be honest, I would have expected to see all proposals in the same wizard, maybe categorized in the same manner as in the Web Console (if categories are provided in the returned data). > Different application proposals on Eclipse tooling vs Web Console > ----------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21376: --------------------------------------- The first 3 entries you see in web console on the right side are images/image streams, not templates. So you should be able to already see them under Image Streams resource in OpenShift explorer view. > Different application proposals on Eclipse tooling vs Web Console > ----------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png > > > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: automatically create a server for new apps

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21372: -------------------------------- Summary: Server Adapter: automatically create a server for new apps (was: Server Adapter: implement automatic publishing) > Server Adapter: automatically create a server for new apps > ---------------------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: implement automatic publishing

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21372: ----------------------------------- Assignee: Andre Dietisheim > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-21376: ------------------------------------- Summary: Different application proposals on Eclipse tooling vs Web Console Key: JBIDE-21376 URL: https://issues.jboss.org/browse/JBIDE-21376 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Xavier Coulon Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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