June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17501) EAP runtime download cannot be finished

by Martin Malina (JIRA)

Martin Malina created JBIDE-17501: ------------------------------------- Summary: EAP runtime download cannot be finished Key: JBIDE-17501 URL: https://issues.jboss.org/browse/JBIDE-17501 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection, server Affects Versions: 4.2.0.Beta2 Environment: JBDS 8.0.0.Beta2a B106 Reporter: Martin Malina Attachments: runtime-download-no-finish.png I tried download EAP 6.1 using the runtime download feature. I hit an issue when I go the path through Server -> New server (it works find if I go through Preferences -> JBoss Tools runtime detection). I chose EAP 6.1 as server type, then defaults (local, file operations), new runtime. There I clicked Download. I followed through - the runtime was downloaded, the fields pre-filled. But now the Finish button is grey and I cannot finish the dialog: -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17107) Visual Preview: CSS and images very often don't show up after refresh / editing

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17107?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17107: ------------------------------------- [~vpakan], in the original this bug was created for visual preview and wasn't coupled with vpe. So, probably it's better to close this one and create duplicate with VPE prefix? > Visual Preview: CSS and images very often don't show up after refresh / editing > -------------------------------------------------------------------------------- > > Key: JBIDE-17107 > URL: https://issues.jboss.org/browse/JBIDE-17107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17497) Servertools plugin heirarchy has large problem

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17497?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17497: ------------------------------------- After reviewing the chart, it seems the biggest problem is the plugin org.jboss.ide.eclipse.archives.webtools. This is the plugin that integrates project archives with ASTools. This plugin needs to be split into a core and a UI, and it needs to move further down the stack to below as.core / as.ui. If this can be done, it'd present a very logical place to put all archives integration code, one which webservices / esb / bpel would not need to use, but which as.core or fuseide could depend on. I previously thought as.runtimes.integration was above as.core, but it seems it must have been moved down, and so this is no longer an issue. Any runtime integration code can live there without dragging in as.core. This is a good thing. > Servertools plugin heirarchy has large problem > ---------------------------------------------- > > Key: JBIDE-17497 > URL: https://issues.jboss.org/browse/JBIDE-17497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Priority: Critical > Attachments: 2014-06-02 19.07.bmml, 2014-06-02 19.07.png > > > The plugin heirarchy of ASTools is better than it used to be, but not good enough for what current consumers of ASTools need it for. > The problem is simple. There are 3 types of clients using ASTools API: > 1) Those who need all of ASTools installed (including server adapter) > 2) Those who only want access to interfaces, to use *if* server adapters is installed (do NOT want as.core force installed) > 3) Those who create their own server adapters, want to use interfaces and some impl classes, but do not want as.core (server adapters) installed. > Those of group 1 are no problem. > Those of group 2 want as.wtp.core and as.wtp.ui to be minimal implementations with very few (near-zero) dependencies > Those of group 3 want as.wtp.core and as.wtp.ui to provide as much functionality as possible, including things like zipping archives, or integration with download runtimes. > An example of group 1 is jbosstools-central. > An example of group 2 is ESB / BPEL > An example of group 3 is FuseIDE > Currently, there are classes in plugins positioned above as.core (ie, depend on as.core) that would be useful to FuseIDE (integration with stacks / runtimes / archives), but pushing these classes down into as.wtp.core / as.wtp.ui would mean the as.wtp.* plugins now require archives / stacks / yaml, and then so does bpel / esb. > There needs to be another set of core/ui plugins for extenders or implementers that do NOT bring in the server adapters. > Alternatively, we could move the server adapters out of as.core / as.ui and into two new higher-level plugins, as.serveradapter.core / as.serveradapter.ui, leaving as.core/as.ui as the new plugins to be extended by fuse-ide. > There are of course other possible solutions, but all possible solutions basically require new plugins with substantial class movement. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17418) Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17418?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17418: --------------------------------------- @fbricon, Right, the classes in "target/generated-sources" folder would not be part of the displayed list, so I'll fix that to include all sources in the project (and related projects, btw). Now, talking about "entities", sdo you have an example of such a behaviour ? what kind of annotations should be looked for ? JPA {{@Entity}}, Hibernate {{@Entity}}, other ? This is now getting more or less related JBIDE-17367 > Browsing for entities dialog shouldn't be empty by default in new JAX-RS Resource wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17418 > URL: https://issues.jboss.org/browse/JBIDE-17418 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > Attachments: JBIDE-17418.png > > > When a project contains JPA entities and you try to create a new JAX-RS Resource, browsing for "Target Entity" displays a blank viewer by default. I expected all entities from the project to be displayed, similar to how other wizards work. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17500) Review EAP runtimes available for download

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17500?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17500: ------------------------------------- Great stuff, martin. Glad you've got my back. I'll work on it. > Review EAP runtimes available for download > ------------------------------------------ > > Key: JBIDE-17500 > URL: https://issues.jboss.org/browse/JBIDE-17500 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > The Download runtime UI offers many versions of EAP, but it seems that not all of them are valid. > I'm not sure if all of this is taken from stacks, if so, a JIRA with JDF will be required as well. > When you open Preferences -> JBoss Tools -> JBoss Runtime Detection > and click Download..., you're offered JBoss runtimes for download. > In the list, there are these EAP versions: > JBoss EAP 6.0.0 > JBoss EAP 6.0.1 > JBoss EAP 6.1.0 > JBoss EAP 6.2.0 > 6.0.0 and 6.0.1 are listed as manual downloads and if I want to download them, I am offered this link: > http://www.jboss.org/products/ > From there, I can get to https://www.jboss.org/products/eap/download/ > The oldest version of EAP this contains is 6.1.0. > Probably the only place to get older EAP is access.redhat.com. > So we should either remove these older versions from the list (I would prefer that) or link to access.redhat.com. > Then there is 6.1.0 and 6.2.0, both available through the Download Manager, which is fine. But the site also contains 6.3.0.Beta so we might offer that, too? > The same applies to Portal - we list JPP 6.0.0 and point users to jboss.org/products. But that only offers JPP 6.1.0. So I would vote for removing the JPP 6.0.0 entry. > And last, WildFly 8.1.0.Final is available, so we should add that. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17499) OpenShift Explorer: Context menu contains item Domain without selected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17499: ------------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > OpenShift Explorer: Context menu contains item Domain without selected connection > --------------------------------------------------------------------------------- > > Key: JBIDE-17499 > URL: https://issues.jboss.org/browse/JBIDE-17499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta3 > > Attachments: contextmenu.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens). > !contextmenu.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17499) OpenShift Explorer: Context menu contains item Domain without selected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17499: ------------------------------------- Summary: OpenShift Explorer: Context menu contains item Domain without selected connection (was: Context menu in a OpenShift Explorer contains item Domain without selected connection) Labels: explorer (was: ) > OpenShift Explorer: Context menu contains item Domain without selected connection > --------------------------------------------------------------------------------- > > Key: JBIDE-17499 > URL: https://issues.jboss.org/browse/JBIDE-17499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta3 > > Attachments: contextmenu.png > > > In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens). > !contextmenu.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17499) OpenShift Explorer: Context menu contains item Domain without selected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17499: ------------------------------------- Estimated Difficulty: Low > OpenShift Explorer: Context menu contains item Domain without selected connection > --------------------------------------------------------------------------------- > > Key: JBIDE-17499 > URL: https://issues.jboss.org/browse/JBIDE-17499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta3 > > Attachments: contextmenu.png > > > In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens). > !contextmenu.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17499) Context menu in a OpenShift Explorer contains item Domain without selected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17499: ------------------------------------- Fix Version/s: 4.2.0.Beta3 > Context menu in a OpenShift Explorer contains item Domain without selected connection > ------------------------------------------------------------------------------------- > > Key: JBIDE-17499 > URL: https://issues.jboss.org/browse/JBIDE-17499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta3 > > Attachments: contextmenu.png > > > In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens). > !contextmenu.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17083) JBIDE-16919 Visual Preview: Navigation from source to view works poorly

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17083?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17083. ------------------------------- Verified with JBDS Beta2-v20140601-0744-B106 > JBIDE-16919 Visual Preview: Navigation from source to view works poorly > ----------------------------------------------------------------------- > > Key: JBIDE-17083 > URL: https://issues.jboss.org/browse/JBIDE-17083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta2 > > > Navigation from source to view works really poorly: > - selection & scrolling on the visual part very often doesn't work at all; > - selection & scrolling requires double click (need single click). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 2014