December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16170?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-16170 at 12/4/13 4:41 AM: -------------------------------------------------------------- Please review https://github.com/jbosstools/jbosstools-central/pull/190 if https://github.com/jboss-jdf/jdf-stack/pull/30 has not been applied, then start JBT/JBDS with -Dorg.jboss.tools.stacks.url_stacks=https://raw.github.com/fbricon/jdf-stack/patch-2/stacks.yaml in *.ini to test was (Author: fbricon): Please review https://github.com/jbosstools/jbosstools-central/pull/190 if https://github.com/jboss-jdf/jdf-stack/pull/30 has not be applied, then start JBT/JBDS with -Dorg.jboss.tools.stacks.url_stacks=https://raw.github.com/fbricon/jdf-stack/patch-2/stacks.yaml in *.ini to test > Latest HTML5 archetype doesn't show unavailable maven repo in wizard > -------------------------------------------------------------------- > > Key: JBIDE-16170 > URL: https://issues.jboss.org/browse/JBIDE-16170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.1.Final > > > The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore) > Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes. > So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16105) openshift-java-client: offer access to express.conf/timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16105?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16105: ------------------------------------- Labels: help_wanted openshift-java-client (was: ) > openshift-java-client: offer access to express.conf/timeout > ----------------------------------------------------------- > > Key: JBIDE-16105 > URL: https://issues.jboss.org/browse/JBIDE-16105 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift-java-client > Fix For: 4.2.x > > > express.conf now offers a setting for timeouts: > {code} > # The default timeout for network operations > #timeout=<integer> > {code} > we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout). > This should replace or be aliased by the system property we already use: -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16110) openshift-java-client: correct IHttpClient.NO_TIMEOUT = 0 by = -1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16110?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16110: ------------------------------------- Labels: help_wanted openshift-java-client (was: openshift-java-client) > openshift-java-client: correct IHttpClient.NO_TIMEOUT = 0 by = -1 > ----------------------------------------------------------------- > > Key: JBIDE-16110 > URL: https://issues.jboss.org/browse/JBIDE-16110 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift-java-client > Fix For: 4.2.x > > > IHttpClient#NO_TIMEOUT currently == 0, it should be -1 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16112) openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16112?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16112: ------------------------------------- Labels: openshift-java-client (was: ) > openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout > -------------------------------------------------------------------------------------------- > > Key: JBIDE-16112 > URL: https://issues.jboss.org/browse/JBIDE-16112 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.x > > > The current code to set timeouts in openshift-java-client is: > {code} > private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { > if (timeout == NO_TIMEOUT) { > timeout = openShiftTimeout; > if (timeout == NO_TIMEOUT) { > timeout = systemPropertyTimeout; > if (timeout == NO_TIMEOUT) { > timeout = defaultTimeout; > } > } > } > return timeout; > } > {code} > calling it looks like this: > {code} > private void setReadTimeout(int timeout, URLConnection connection) { > connection.setReadTimeout( > getTimeout( > timeout, > getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), > getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), > DEFAULT_READ_TIMEOUT)); > } > {code} > DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16112) openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16112?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16112: ------------------------------------- Labels: help_wanted openshift-java-client (was: openshift-java-client) > openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout > -------------------------------------------------------------------------------------------- > > Key: JBIDE-16112 > URL: https://issues.jboss.org/browse/JBIDE-16112 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift-java-client > Fix For: 4.2.x > > > The current code to set timeouts in openshift-java-client is: > {code} > private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { > if (timeout == NO_TIMEOUT) { > timeout = openShiftTimeout; > if (timeout == NO_TIMEOUT) { > timeout = systemPropertyTimeout; > if (timeout == NO_TIMEOUT) { > timeout = defaultTimeout; > } > } > } > return timeout; > } > {code} > calling it looks like this: > {code} > private void setReadTimeout(int timeout, URLConnection connection) { > connection.setReadTimeout( > getTimeout( > timeout, > getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), > getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), > DEFAULT_READ_TIMEOUT)); > } > {code} > DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15744) openshift-java-client: add support for List<IEnvironmentVariable> and refactor methods that reference "List" in their names, however are operating on "Map<String, IEnvironmentVariable>", to reference "Map"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15744?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15744: ------------------------------------- Labels: openshift-java-client (was: ) > openshift-java-client: add support for List<IEnvironmentVariable> and refactor methods that reference "List" in their names, however are operating on "Map<String,IEnvironmentVariable>", to reference "Map" > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15744 > URL: https://issues.jboss.org/browse/JBIDE-15744 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.x, 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.x > > > This enhancement to the interface will remove the requirement that users of the interface implementation instances to do extra processing to pull the list of variables from the provided immutable Map<String,IEnvirontmentVariable> instance. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15822) Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15822?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15822: ------------------------------------- Summary: Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them (was: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them) > Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15822 > URL: https://issues.jboss.org/browse/JBIDE-15822 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > We currently only check the validity of embedded cartridges when you check/uncheck them. Since there are cartridges which are not valid in scaled apps (ex. phpmyadmin), we should also check the embedded cartridges when one hits the "Enable Scaling" checkbox. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15822) Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15822?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15822: ------------------------------------- Priority: Minor (was: Major) > Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15822 > URL: https://issues.jboss.org/browse/JBIDE-15822 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > We currently only check the validity of embedded cartridges when you check/uncheck them. Since there are cartridges which are not valid in scaled apps (ex. phpmyadmin), we should also check the embedded cartridges when one hits the "Enable Scaling" checkbox. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2840) Java 8

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2840?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2840: ----------------------------------- Links to upstream issue/doc : - Upstream bug : https://bugs.eclipse.org/bugs/show_bug.cgi?id=380190 - Status page http://wiki.eclipse.org/JDT_Core/Java8 - Early access announcement : http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg09679.html - p2 update site for early access : http://dist.springsource.com/snapshot/TOOLS/java8/e43 > Java 8 > ------ > > Key: JBDS-2840 > URL: https://issues.jboss.org/browse/JBDS-2840 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > Fix For: 8.0.0.GA > > > Support for Java 8 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2840) Java 8

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2840?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2840: ------------------------------ Component/s: upstream > Java 8 > ------ > > Key: JBDS-2840 > URL: https://issues.jboss.org/browse/JBDS-2840 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: upstream > Reporter: Burr Sutter > Fix For: 8.0.0.GA > > > Support for Java 8 -- 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, 4 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 2013