September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13963) Improve the port-forwarding wizard UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13963?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13963: ------------------------------------- Priority: Minor (was: Major) > Improve the port-forwarding wizard UI > ------------------------------------- > > Key: JBIDE-13963 > URL: https://issues.jboss.org/browse/JBIDE-13963 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: OpenShift_portforward.png > > > the wizard buttons are a bit misleading: clicking on "Ok" at the bottom of the wizard closes the wizard but does not start or stop the port-forwarding (I got that problem a few times when I was preparing a demo). > I think the wizard buttons should rather be "Start"/"Cancel" or "Stop/Cancel". > The "Start all" and "stop all" buttons on the side of the tables should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15469) {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15469?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15469: ------------------------------------- A new patch from Teiid TEIIDDES-1857 has added api to foundation, so, we'll bump to 1.1.0 and give up on that 1.0.100 idea ;) > {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15469 > URL: https://issues.jboss.org/browse/JBIDE-15469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > > jbosstools-base/foundation submodule had changes since 4.1.0.Final is released: > {code}$ git diff --name-only jbosstools-4.1.0.Final -- foundation > foundation/plugins/org.jboss.tools.foundation.core/.options > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/Trace.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/InternalURLTransport.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/URLTransportCache.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierProgressWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/InterruptableJoinJob.java > foundation/pom.xml{code} > No changes in Public API so far and hat means only service version should be incremented: > 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15429) openshift-java-client: add support for downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15429?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15429: ------------------------------------- Labels: openshift-java-client (was: ) > openshift-java-client: add support for downloadable cartridges > -------------------------------------------------------------- > > Key: JBIDE-15429 > URL: https://issues.jboss.org/browse/JBIDE-15429 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.0.Alpha1 > > > OpenShift added support for downloadable cartridges lately. This allows you to provide your very own cartridge by providing a git-url where it may be checked out. > Fusesource provided a PR on github that we should merge in: https://github.com/openshift/openshift-java-client/pull/68 > The PR seems perfectly functional but it has a few shortcomings though that we have to fix though (see comments in the PR) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13248: ------------------------------------------ We're still missing: * license (+ license-url) * tags * website > openshift-java-client: provide nice names, versions and descriptions for cartridges > ----------------------------------------------------------------------------------- > > Key: JBIDE-13248 > URL: https://issues.jboss.org/browse/JBIDE-13248 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift-java-client > Fix For: 4.2.x > > > The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers > * <display-name /> > * <version /> > * <description /> > eventually > * <website /> > * <help-topics /> > We should add at least these 3 in the ICartridge. > There are also further interesting informations: > * <tag /> > * <scales-from /> & <scales-to /> > * <scales-with /> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13248: ------------------------------------- Labels: openshift-java-client (was: ) > openshift-java-client: provide nice names, versions and descriptions for cartridges > ----------------------------------------------------------------------------------- > > Key: JBIDE-13248 > URL: https://issues.jboss.org/browse/JBIDE-13248 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift-java-client > Fix For: 4.2.x > > > The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers > * <display-name /> > * <version /> > * <description /> > eventually > * <website /> > * <help-topics /> > We should add at least these 3 in the ICartridge. > There are also further interesting informations: > * <tag /> > * <scales-from /> & <scales-to /> > * <scales-with /> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15058) Application Wizard: Embed Wizard: wizard jobs should not get cancelled autom. if a given time is exceeded.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15058?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15058: ------------------------------------- Summary: Application Wizard: Embed Wizard: wizard jobs should not get cancelled autom. if a given time is exceeded. (was: Application Wizard: Embed Wizard: Turn wizard jobs not toget cancelled if a given time is exceeded.) > Application Wizard: Embed Wizard: wizard jobs should not get cancelled autom. if a given time is exceeded. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15058 > URL: https://issues.jboss.org/browse/JBIDE-15058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > The current implementation of WizardUtils#runInWizard will always cancel the job it is running if it exceeds a given timeout. If the caller is not providing a timeout a default timeout of 2 minutes is applied: > {code:title=org.jboss.tools.common.ui.WizardUtils#runInWizard} > public static IStatus runInWizard(final Job job, final DelegatingProgressMonitor delegatingMonitor, > final IWizardContainer container) throws InvocationTargetException, InterruptedException { > return runInWizard(job, delegatingMonitor, container, DEFAULT_TIMEOUT); > } > {code} > All Jobs in OpenShiftApplicationWizard are thus using timeouts. Once the timeouts are reached the WizardUtils#runInWizard will cancel them. We should offer #runInWizard that never timeouts and cancels and use these in the OpenShiftApplicationWizard and all other jobs that use this facility: > {code:EmbedCartridgeWizardPage} > EmbedCartridgesJob job = new EmbedCartridgesJob( > new ArrayList<IEmbeddableCartridge>(pageModel.getSelectedEmbeddableCartridges()), > pageModel.getApplication()); > IStatus result = WizardUtils.runInWizard(job, job.getDelegatingProgressMonitor(), getContainer(), EMBED_CARTRIDGES_TIMEOUT); > {code} > {code:OpenShiftApplicationWizard} > private IStatus createApplication() { > try { > CreateApplicationJob job = new CreateApplicationJob( > model.getApplicationName() > , model.getApplicationCartridge() > , model.getApplicationScale() > , model.getApplicationGearProfile() > , model.getInitialGitUrl() > , model.getConnection().getDefaultDomain()); > IStatus status = WizardUtils.runInWizard( > job, job.getDelegatingProgressMonitor(), getContainer(), APP_CREATE_TIMEOUT); > IApplication application = job.getApplication(); > model.setApplication(application); > if (status.isOK()) { > openLogDialog(application, job.isTimeouted(status)); > } > return status; > } catch (Exception e) { > return OpenShiftUIActivator.createErrorStatus( > NLS.bind("Could not create application {0}", model.getApplicationName()), e); > } > } > private IStatus addCartridges(final IApplication application, final Set<IEmbeddableCartridge> selectedCartridges) { > try { > EmbedCartridgesJob job = new EmbedCartridgesJob( > new ArrayList<IEmbeddableCartridge>(model.getSelectedEmbeddableCartridges()), > true, // dont remove cartridges > model.getApplication()); > IStatus result = WizardUtils.runInWizard( > job, job.getDelegatingProgressMonitor(), getContainer(), EMBED_CARTRIDGES_TIMEOUT); > if (result.isOK()) { > openLogDialog(job.getAddedCartridges(), job.isTimeouted(result)); > } > return result; > } catch (Exception e) { > return OpenShiftUIActivator.createErrorStatus( > NLS.bind("Could not add/remove cartridges for application {0}", application.getName()), e); > } > } > private IStatus waitForApplication(IApplication application) { > try { > AbstractDelegatingMonitorJob job = new WaitForApplicationJob(application, getShell()); > IStatus status = WizardUtils.runInWizard( > job, job.getDelegatingProgressMonitor(), getContainer(), APP_WAIT_TIMEOUT); > return status; > } catch (Exception e) { > return OpenShiftUIActivator.createErrorStatus( > NLS.bind("Could not wait for application {0} to become reachable", application.getName()), e); > } > } > private boolean importProject() { > try { > final DelegatingProgressMonitor delegatingMonitor = new DelegatingProgressMonitor(); > IStatus jobResult = WizardUtils.runInWizard( > new ImportJob(delegatingMonitor), delegatingMonitor, getContainer(), IMPORT_TIMEOUT); > return JobUtils.isOk(jobResult); > } catch (Exception e) { > ErrorDialog.openError(getShell(), "Error", "Could not create local git repository.", OpenShiftUIActivator > .createErrorStatus("An exception occurred while creating local git repository.", e)); > return false; > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2471) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2471?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBDS-2471: ------------------------------------ Affects Version/s: 7.0.0.GA > JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2471 > URL: https://issues.jboss.org/browse/JBDS-2471 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration-platform > Affects Versions: 5.0.2.GA, 7.0.0.GA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Fix For: 5.0.6.GA-SOA, 6.0.2.GA > > > JBDS6: > "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime" > -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true > -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed" > SOA 5.3.1 run.conf: > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning > =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true" > fi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2471) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2471?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-2471: ----------------------------------------- This bug is still present in JBDS 7.0.0.GA and for all SOA 5.x platforms > JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2471 > URL: https://issues.jboss.org/browse/JBDS-2471 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration-platform > Affects Versions: 5.0.2.GA, 7.0.0.GA > Environment: Version: 5.0.2.GA > Build id: v20130119-0035-H249-GA > Build date: 20130119-0035 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Fix For: 5.0.6.GA-SOA, 6.0.2.GA > > > JBDS6: > "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime" > -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true > -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed" > SOA 5.3.1 run.conf: > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning > =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true" > fi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14933) Consider hiding of 'Disable automatic maven build' in OpenShift application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14933?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14933: ------------------------------------- Priority: Minor (was: Major) > Consider hiding of 'Disable automatic maven build' in OpenShift application wizard > ---------------------------------------------------------------------------------- > > Key: JBIDE-14933 > URL: https://issues.jboss.org/browse/JBIDE-14933 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > > 'Disable automatic maven build' doesn't make much sense according to applications which don't use maven (like python, php, etc.). We can either hide this option or display a hint that it affects only java applications. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15389) User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15389: ------------------------------------- Priority: Minor (was: Major) > User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15389 > URL: https://issues.jboss.org/browse/JBIDE-15389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.Alpha2 > > Attachments: tail-files.png > > > When doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. > !tail-files.png! > Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013