May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- Comments in the tm mailing list indicate the view will stay, but the string "Terminal (old)" shouldn't be visible to any users upon release. I've asked for clarification to verify to verify that the two views won't have visibly similar names that may be confusing to a user. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- So I will note that the method in the trace (waitFor) is simply a busy-loop basically. We're just verifying the monitor isn't canceled, and the future object that jboss client jars returns me isn't "complete" yet. The busy-loop also increments the progress monitor slightly in what's called an infinite-progress-monitor style... ie, the monitor keeps moving forward, but slower and slower. The reason it seems to stop at 72% is because the last 30% or so is done in publish.performFinish(), so its basically sitting at 99%, which means the infinite progress monitor is just sitting at 99% and has nowhere else to go. As for why it's freezing at all, I have absolutely no idea. The stack traces on both client and server indicate that the threads are all still active and actual transfering should still be occurring as far as I can tell. I'll ask on wf-dev > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-19711 at 5/28/15 11:24 PM: --------------------------------------------------------------- I have no idea. [~maxandersen] ? What's your thoughts here? My understanding is we're not looking for JBDS *or* Central initially, so I imagine it's for jbt core only (?) was (Author: rob.stryker): I have no idea. [~maxandersen] ? What's your thoughts here? > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-642) JBDS Articles: draft intro text about why to do a certain thing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-642?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-642: ------------------------------------ Feedback: 1. For FH: This is a bit better but it should probably be edited so that it flows better. My suggestion: Red Hat JBoss Developer Studio includes an Import wizard to allow users to quickly and easily import previously created FeedHenry applications. Once the application is imported, you can change or enhance the application, test the changes, and then push it back to the FeedHenry server. Sentence one tells you why and sentence two tells you what you can do. Lots of room for improvement but I would keep it simple and specific. I'd encourage you to work on the second one based on the feedback above to make it more concise and specific, as well as to cut down on unnecessary words. > JBDS Articles: draft intro text about why to do a certain thing > --------------------------------------------------------------- > > Key: TOOLSDOC-642 > URL: https://issues.jboss.org/browse/TOOLSDOC-642 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > Need intro text about why a user would want to do the thing the article describes. > For example, why would the user want to import a FH app, or why create a HTML5 web app, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Jeff Bride (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Jeff Bride commented on JBIDE-19463: ------------------------------------ ouch. this does sound complex. Well, in any case, thanks for giving it some thought and the clear explanation, Rob. jeff > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19463: ------------------------------------- Honestly, I think it's very unlikely we'd get a usecase like this up and running in any reasonable time. The reality of it is that we'd probably need to add at least a dozen new plugins depending on how far back we wanted to extend this support, each with a copy of the jboss client-all jar. These client jars are as small as 400k (back in jboss 4.2) up to 7 meg (for wf 8.1). Even averaging this out, it could add 30 to 50 megs to the distribution easily. It would also add a huge amount of complexity, and a testing nightmare for QE to accurately verify. The reason it'd require so many plugins is because the jar being added is the client-all jar. At least some classes of the client-all jar change in almost every release, and so it'd be a huge investigative task to figure out the full set of classes that are needed for the jmx requests, whether those specific class files have changed in any micro / minor changes, whether they've changed in a breaking manner, etc etc, for all releases in the past. Splitting the jar would be an option, putting jars only with those classes needed for JMX requests, but this is pretty much rejected out-of-hand because we are not in the business of modifying or customizing app-server jars (even client jars distributed with the app server). If I had to imagine a solution, the closest I could come is to being able to add some UI so that you can set the location of a client-all jar from somewhere on your disk for your runtime-less server, and it would be up to you to ensure its the proper jar. But even that comes with its own UI perils (where to put such a UI? Server editor? How to make it hidden enough to not distract users who don't need it without also making it invisible to people looking for it?) In short, I think it's highly unlikely we'll be able to get this feature going in any meaningful fashion. [~maxandersen] Any thoughts? > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19808: ------------------------------------ Here's another version of the mirror including packed artifacts & regenerating the site's metadata.... http://download.jboss.org/jbosstools/updates/requirements/apache-director... And another using latestversiononly="true", but no regeneration of metadata: http://download.jboss.org/jbosstools/updates/requirements/apache-director... but I suspect you'll have the same problem because the upstream site is a pre-p2 site. > Teiid Designer would like to depend on org.apache.directory.studio plugins > -------------------------------------------------------------------------- > > Key: JBIDE-19808 > URL: https://issues.jboss.org/browse/JBIDE-19808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, teiid > Affects Versions: 4.2.3.Final > Reporter: Paul Richardson > Assignee: Barry LaFond > Attachments: p2.diff > > > *Reason:* > Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478]. > The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense. > The current working implementation of Teiid with this widget can be found here: > https://github.com/phantomjinx/teiid-designer/tree/ldap-studio > The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits. > *Project page/sources:* > * [directory.apache.org|https://directory.apache.org] > * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] > * [udpate site | http://directory.apache.org/studio/update/2.x/] > *Version:* 2.0.0 > *License and owner:* Apache licence and Foundation > *Original p2 repo:* http://directory.apache.org/studio/update/2.x/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director... > *Include Sources:* Not available from existing update site but may well be in the next release. > *Affected projects:* Teiid Designer > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > * org.apache.directory.api.ldap.model > * org.apache.directory.studio.common.core > * org.apache.directory.studio.common.ui > * org.apache.directory.studio.connection.core > * org.apache.directory.studio.connection.ui > * org.apache.directory.studio.ldapbrowser.common > * org.apache.directory.studio.ldapbrowser.core > * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency > {code} >  > <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> > <repository location="http://directory.apache.org/studio/update/2.x/"/> > <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/> > </location> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19711: ------------------------------------- I have no idea. [~maxandersen] ? What's your thoughts here? > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18772 at 5/28/15 8:03 PM: ------------------------------------------------------------- The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA, and is published to two places -- once for JBT and again for JBDS. Because JBDS content has to live on a different server, even if it's the identical bits. So, the deploy step performs 4 rsync.sh calls, requiring both sets of rsync_path values. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... was (Author: nickboldt): The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA are published to two places -- once for JBT and again for JBDS. Because JBDS content has to live on a different server, even if it's the identical bits. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA are published to two places -- once for JBT and again for JBDS. Because JBDS content has to live on a different server, even if it's the identical bits. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 May 2015