November 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2715 at 11/7/13 11:20 AM: ------------------------------------------------------------ PR applied: https://github.com/jbdevstudio/jbdevstudio-website/pull/50 New layout for scripted install page: !JBDS2823.png! Also fixed references to "EAP" -> "JBoss EAP" on download/* pages. Pages to review: https://devstudio.jboss.com/updates/7.0-staging/ https://devstudio.jboss.com/updates/7.0-development/ https://devstudio.jboss.com/updates/7.0/ https://devstudio.jboss.com/download/7.x.html https://devstudio.jboss.com/download/6.x.html https://devstudio.jboss.com/download/5.x.html https://devstudio.jboss.com/download/4.x.html https://devstudio.jboss.com/download/scripted-install/ was (Author: nickboldt): PR applied: https://github.com/jbdevstudio/jbdevstudio-website/pull/50 New layout for scripted install page: !JBDS2823.png! Also fixed references to "EAP" -> "JBoss EAP" on download/* pages. > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2715: ----------------------------- Attachment: JBDS2823.png PR applied: https://github.com/jbdevstudio/jbdevstudio-website/pull/50 New layout for scripted install page: !JBDS2823.png! Also fixed references to "EAP" -> "JBoss EAP" on download/* pages. > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: JBDS2823.png > > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13869: ---------------------------------------- Are you sure it's using the parent pom from PR, that you should have "mvn clean install"ed ? > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15860) Show a warning when enterprise maven repo is missing for enterprise quickstarts

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15860?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15860: --------------------------------------------- +1 looks good to me! > Show a warning when enterprise maven repo is missing for enterprise quickstarts > ------------------------------------------------------------------------------- > > Key: JBIDE-15860 > URL: https://issues.jboss.org/browse/JBIDE-15860 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.CR1 > > > Since the newest quickstarts now require the maven eap and/or wfk repos, generated projects won't build OOTB if these repos are not defined in the user's settings.xml. > Maven archetype based wizards show a warning is essential dependencies can't be resolved. We need to add the same thing for zipped quickstarts. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14544: ------------------------------------- Yes, we will need to bring in a few extra people with their own machines (ideally Windows & Mac), ideally with brand new XCode and Android SDK installations as well as with previous (older) XCode and Android installations. We will also need to document what specific versions of XCode/iOS Simulator and Android SDKs we expect to be available on the end-user's machine and make sure our error messages are user-friendly. > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12646) web.xml servlet-name validation is not case-sensitive

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12646?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-12646: --------------------------------------- Hello [~scabanovich] ! The test failed on the following assertion: {code} Assert.assertFalse(new File("./A.txt").isFile()); {code} > web.xml servlet-name validation is not case-sensitive > ----------------------------------------------------- > > Key: JBIDE-12646 > URL: https://issues.jboss.org/browse/JBIDE-12646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.0.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > Attachments: JBIDE-12646 - Wi-Fi.m4v, ServletNameValidation.png > > > [Using the HTML5 sample project generated from Central] > I'm adding a servlet declaration in the web.xml file but the web.xml editor does not report a warning when the servlet name case is wrong: > {code} > <servlet-mapping> > <servlet-name>org.jboss.tools.example.html5.rest.JaxrsActivator</servlet-name> > <url-pattern>/hello/*</url-pattern> > </servlet-mapping> > {code} > In the example above, the class name should be JaxRsActivator, not JaxrsActivator. > On the other hand, it properly reports a warning when a letter is missing in the classname. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15825?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15825: --------------------------------------- Postponing to 4.2.0.Alpha1 since the expected validation problem appear as soon as a Project>Clean is executed. Some thoughts on how to fix that: the change listeners should not respond to classpath changes (as it's already the case), but it could accept changes on some classes, as the log show that this happened after the target runtime was set: {code} 16:42:08.627 [Worker-15] TRACE **ignored** Delta /test2/build/classes/MyAnnotation.class [Changed] ... 16:42:08.629 [Worker-15] DEBUG JAX-RS Metamodel for project 'test2' now has 0 Applications, 6 HttpMethods, 0 Resources and 0 Endpoints. ... 16:42:08.955 [Worker-11] DEBUG *** Validating project test2 after files [L/test2/.settings/org.eclipse.wst.common.project.facet.core.xml] changed... *** ... {code} In that case, if JDT can provide us with the associated Java source file, the JAX-RS builder could look at this source file, instanciate a custom JAX-RS HTTP Method element from it (which is not the case ATM). This element would be part of the validation (even if only org.eclipse.wst.common.project.facet.core.xml is marked as a changed file). > JAX-RS problems don't show up after target runtime is set > --------------------------------------------------------- > > Key: JBIDE-15825 > URL: https://issues.jboss.org/browse/JBIDE-15825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > JAX-RS problems don't show up after target runtime is set on project that was created with target runtime set to <None>. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-13869: ------------------------------------ The integration-test plugin I tried with has eclipse-test-plugin packaging. And I can see tests running on a very limited eclipse instance (basically just the dependency features I specified in pom), but I don't see any tests running against the JBDS bundle. > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15880) openshift-java-client: provide its own lib specific timeout that may be set via system properties

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15880?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15880: ------------------------------------------ I introduced 2 new client-lib specific timeouts {code} public static final String SYSPROP_OPENSHIFT_CONNECT_TIMEOUT = "com.openshift.httpclient.connect.timeout"; public static final String SYSPROP_OPENSHIFT_READ_TIMEOUT = "com.openshift.httpclient.read.timeout"; {code} there are now 4 timeouts which override one each other: 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {code:title=UrlConnectionHttpClient} 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} > openshift-java-client: provide its own lib specific timeout that may be set via system properties > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-15880 > URL: https://issues.jboss.org/browse/JBIDE-15880 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.CR1 > > > client timeouts when talking to OpenShift are unfortunaltey still a topic and cause errors (JBIDE-15835, JBIDE-15831) when OpenShift is installed on systems with poor performance. We should thus provide a client-lib specific default timeout that a user may override by setting it in the system properties. > The timeout-setting order would thus then be: > 1) specific operation timeout (ex. JBT is currently using a specific creation timeout) > 2) client-lib default timeout (which may be set by a system property) > 3) HttpUrlConnection default timeout (jdk timeout: -Dsun.net.client.defaultConnectTimeout=600000) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15877) In Run Configurations, Android label should be more descriptive

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15877?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15877: -------------------------------------- PR Applied to master and will be targeted to 4.1.1CR1 > In Run Configurations, Android label should be more descriptive > --------------------------------------------------------------- > > Key: JBIDE-15877 > URL: https://issues.jboss.org/browse/JBIDE-15877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Fix For: 4.1.1.CR1 > > Attachments: HybridMobile_runconfig_icons.png, LunchConfigurationTypes.png > > > In Run Configurations, labels are "Android", "CordovaSim" and "iOS Simulator". > The "Android" label should be renamed to emphasis Android what? How about "Android Simulator/Device"? - since I assume run configs will work with simulator and device. Otherwise just "Android Simulator"? > !HybridMobile_runconfig_icons.png! -- 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, 5 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 November 2013