January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15107) JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15107?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15107: ---------------------------------------- Fix Version/s: 4.1.2.Final 4.2.0.Alpha2 (was: 4.1.x) > JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7 > ------------------------------------------------------------------- > > Key: JBIDE-15107 > URL: https://issues.jboss.org/browse/JBIDE-15107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Environment: 64-bit Windows 7 > 32-bit JDK 7u25 > Reporter: Yahor Radtsevich > Assignee: Rob Stryker > Priority: Critical > Labels: jbds711 > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: screenshot.png > > > I cannot run JBoss EAP 6.1 with its default launch configuration. > The default launch configuration has {{-Xms1303m}} and {{-Xmx1303m}} in its parameters, which is obviously the reason of this bug. > *Steps to reproduce:* > # Install JBDS 7.0.0.Beta2 bundled with JBoss EAP 6.1 Server > # Open JBoss Central and create new HTML5 Project > # Try to run this project on the server > *Actual result:* > Server cannot be started. The following message is shown in the console: > {code:title=console output} > Error occurred during initialization of VM > Could not reserve enough space for object heap > {code} > And this pop-up appears: > !screenshot.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

[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ] Catherine Robson commented on JBIDE-14744: ------------------------------------------ I added a new mockup for the first screen for discussion. I wanted to focus the first screen around the decision to pick an existing application or choose to create a new application - I think this is the way that users are probably approaching this wizard. If they decide to create a new application, then we can show the different types of categories (and we should use the OpenShift terminology here I think of "QuickStarts, Cartridges, etc".) We should try to keep everything in a category, even the basic cartridges in my opinion. > Allow users to choose from quickstarts/templates when creatingApplication wizard: new application > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14744 > URL: https://issues.jboss.org/browse/JBIDE-14744 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.0.Beta1 > > Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, openshift-quickstart.png > > > The web ui offers a large set of quickstarts/templates: > !openshift-quickstart.png! > in a mail from clayton on the 4th of june: > {quote} > For QuickStarts, brokers may choose to > a) enable community quickstarts > (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf) > b) enable their own list of quickstarts > (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json) > c) disable the quickstarts link > (delete /etc/openshift/quickstarts.json) > To correctly fetch the quickstarts for a server, retrieve the API document > /broker/rest/api > and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts. > Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific: > * API versioning is not supported > * Only JSON is supported > * The body of the response is slightly different than standard REST API feed results > * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not) > The format of the JSON response (in either a) or b) above) is: > {quote} > {code} > { > data: [ > quickstart: { > id: "<string id>", > href: "<absolute URL to a display URL for the quickstart>", > name: "<name>", > updated: "<last update date in seconds from the epoch>", > summary: "<brief HTML body of the item>", > body: "<full HTML body of the item>", > cartridges: "<cartridge spec>", > website: "<URL of metadata about the source of the quickstart or the technology>", > tags: "<comma delimited list of tags>", > language: "<display name of the type of quickstart>", > initial_git_url: "<absolute URL or Git reference to source>", > provider: "openshift|reviewed|partner|community", # default is community > }, > ] > } > {code} > {quote} > You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time. > Cartridge spec: > The cartridge spec is defined as either: > a) a comma delimited list of cartridge name search conditions > b) a string containing a JSON array > If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field. > Otherwise, > 1) split the string by "," into "segments" > 2) trim whitespace from each segment > 3) split each segment by "|" into "matches" - these represent logical ORs > 4) strip leading and trailing "*" characters > 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select. > See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > {quote} -- 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-16405) Engines switcher in BrowserSim does not work on java7u51

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16405?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov edited comment on JBIDE-16405 at 1/28/14 1:55 PM: ------------------------------------------------------------------------- To make BrowserSim switcher work we need to load both javafx Webkit and SWT Webkit. For java 7u45 and earlier we need to load SWT webkit before javafx webkit, for java 7u51 we need to load javafx webkit before swt webkit. For java8b124(latest from ea) everything is fine for both ways of loading. >From the conversation with Steve Northover from javafx this will not be fixed in java 7. In the worst case we will check the java version and after that load webkits in appropriate order. was (Author: kmarmaliykov): To make BrowserSim switcher work we need to load both javafx Webkit and SWT Webkit. For java 7u45 and earlier we need to load SWT webkit before javafx webkit, for java 7u51 we need to load javafx webkit before swt webkit. For java8b124(latest from ea) everything is fine. >From the conversation with Steve Northover from javafx this will not be fixed in java 7. In the worst case we will check the java version and after that load webkits in appropriate order. > Engines switcher in BrowserSim does not work on java7u51 > -------------------------------------------------------- > > Key: JBIDE-16405 > URL: https://issues.jboss.org/browse/JBIDE-16405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Alpha1 > Environment: Windows 7, java7u51 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries > Upstream issue: https://javafx-jira.kenai.com/browse/RT-35480 -- 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-16405) Engines switcher in BrowserSim does not work on java7u51

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16405?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16405: ------------------------------------------------ To make BrowserSim switcher work we need to load both javafx Webkit and SWT Webkit. For java 7u45 and earlier we need to load SWT webkit before javafx webkit, for java 7u51 we need to load javafx webkit before swt webkit. For java8b124(latest from ea) everything is fine. >From the conversation with Steve Northover from javafx this will not be fixed in java 7. In the worst case we will check the java version and after that load webkits in appropriate order. > Engines switcher in BrowserSim does not work on java7u51 > -------------------------------------------------------- > > Key: JBIDE-16405 > URL: https://issues.jboss.org/browse/JBIDE-16405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Alpha1 > Environment: Windows 7, java7u51 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries > Upstream issue: https://javafx-jira.kenai.com/browse/RT-35480 -- 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-16405) Engines switcher in BrowserSim does not work on java7u51

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16405?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-16405: ------------------------------------------- Description: java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries Upstream issue: https://javafx-jira.kenai.com/browse/RT-35480 was: java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries Upstream issue: (https://javafx-jira.kenai.com/browse/RT-35480 > Engines switcher in BrowserSim does not work on java7u51 > -------------------------------------------------------- > > Key: JBIDE-16405 > URL: https://issues.jboss.org/browse/JBIDE-16405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Alpha1 > Environment: Windows 7, java7u51 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries > Upstream issue: https://javafx-jira.kenai.com/browse/RT-35480 -- 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-16405) Engines switcher in BrowserSim does not work on java7u51

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-16405: ---------------------------------------------- Summary: Engines switcher in BrowserSim does not work on java7u51 Key: JBIDE-16405 URL: https://issues.jboss.org/browse/JBIDE-16405 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.2.0.Alpha1 Environment: Windows 7, java7u51 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Priority: Critical Fix For: 4.2.0.Alpha2 java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Java\jdk1.7.0_51\jre\bin\jfxwebkit.dll: Can't find dependent libraries Upstream issue: (https://javafx-jira.kenai.com/browse/RT-35480 -- 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-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2669: ------------------------------------- I verified on installed downloaded from hudson. See Steps to reproduce. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: build1667.png, update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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-15932) CordovaSim needs to display console logs especially during startup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15932: --------------------------------------------- I've updated the title/description to more clearly indicate the primary concern is startup/bootup issues which result in nothing working and users has zero ideas. The suggestion/middleroad is to investigate if this can be done by overriding the console.log function for the swt browser and thus have it show up as normal console output from where browsersim is started. > CordovaSim needs to display console logs especially during startup > ------------------------------------------------------------------ > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Priority: Blocker > Labels: jbds711 > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on. > Just using firebug or similar would not solve this issue since it is not started early enough. -- 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-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2669: -------------------------------- Steps to Reproduce: Steps to Verify: 1. EXECUTE: Install/Start JBDS 2. ASSERT: Welcome screen is present 3. ASSERT: Help -> About JBoss Developer Studio menu is presen 4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text 5. ASSERT: JBDS Icon present in installed features icons list was: Steps To Verify: 1. EXECUTE: Install/Start JBDS 2. ASSERT: Welcome screen is present 3. ASSERT: Help -> About JBoss Developer Studio menu is presen 4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text 5. ASSERT: JBDS Icon present in installed features icons list > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: build1667.png, update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2669: -------------------------------- Steps to Reproduce: Steps To Verify: 1. EXECUTE: Install/Start JBDS 2. ASSERT: Welcome screen is present 3. ASSERT: Help -> About JBoss Developer Studio menu is presen 4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text 5. ASSERT: JBDS Icon present in installed features icons list > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: build1667.png, update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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 January 2014