February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18703) Browsersim: Need to add javaFx web engine support for standalone mode

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18703?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18703: ------------------------------------------- Labels: new_and_noteworthy (was: ) > Browsersim: Need to add javaFx web engine support for standalone mode > --------------------------------------------------------------------- > > Key: JBIDE-18703 > URL: https://issues.jboss.org/browse/JBIDE-18703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.2.0.Final > Reporter: Ilya Buziuk > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > What need to be done here: > 1. add all required jetty dependencies to build > 2. Change Browsersim code a bit > 3. Add javafx mocks only in case if javafx is not available(openjdk case) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19181: ---------------------------------------- Summary: correct naming of internal packages so that they're consistent across all openshift plugins Key: JBIDE-19181 URL: https://issues.jboss.org/browse/JBIDE-19181 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Andre Dietisheim Fix For: 4.3.0.Alpha1 Internal packages across the openshift plugins are non-consistent: ex. org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins. For reference, here's the official Eclipse: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages {quote} org.eclipse.jdt.internal.core.compiler - Correct usage org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name. org.eclipse.core.internal.resources - Correct usage org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse. org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name. {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19176) Fixup Openshift v3 Eclipse Log Appenders to be useable be either v2 or v3 clients

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19176?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19176: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 > Fixup Openshift v3 Eclipse Log Appenders to be useable be either v2 or v3 clients > --------------------------------------------------------------------------------- > > Key: JBIDE-19176 > URL: https://issues.jboss.org/browse/JBIDE-19176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Make logging usable by both v2 and v3 clients -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-386) Target Platform is missing some source plugins when generating with sources

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBTIS-386?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBTIS-386: ----------------------------------- Lars has attempted the build. THe results are pasted here: https://gist.github.com/lhein/19aa5a1c6d8d37d97490 In short, didn't quite work very well. [~pleacu] Can you make this a priority please? > Target Platform is missing some source plugins when generating with sources > --------------------------------------------------------------------------- > > Key: JBTIS-386 > URL: https://issues.jboss.org/browse/JBTIS-386 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Lars Heinemann > Assignee: Paul Leacu > Priority: Critical > > when mirroring the TP locally with sources some of the source plugins are missing. for instance org.eclipse.wst.server.ui.source. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19174) Create and use Mars M5 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19174?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19174: ----------------------------------- Description: Update current target-platform snapshot to use Mars M5. p2diff with https://github.com/jbosstools/jbosstools-target-platforms/pull/125 {code} mistria@mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff -mode=ignoreVersions file:/home/mistria/git/jbossto ols-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... < org.eclipse.jgit.java7.feature.jar [3.7.0.201502031740-rc1] < org.eclipse.jgit.java7 [3.7.0.201502031740-rc1] < org.eclipse.jgit.java7.feature.group [3.7.0.201502031740-rc1] > org.eclipse.birt.chart [4.3.2.v201405191524] === Summary === file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 3 unique IUs http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains 1 unique IUs {code} was:Update current target-platform snapshot to use Mars M5. > Create and use Mars M5 target-platform > -------------------------------------- > > Key: JBIDE-19174 > URL: https://issues.jboss.org/browse/JBIDE-19174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Update current target-platform snapshot to use Mars M5. > p2diff with https://github.com/jbosstools/jbosstools-target-platforms/pull/125 > {code} > mistria@mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff -mode=ignoreVersions file:/home/mistria/git/jbossto > ols-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > < org.eclipse.jgit.java7.feature.jar [3.7.0.201502031740-rc1] > < org.eclipse.jgit.java7 [3.7.0.201502031740-rc1] > < org.eclipse.jgit.java7.feature.group [3.7.0.201502031740-rc1] > > org.eclipse.birt.chart [4.3.2.v201405191524] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 3 unique IUs > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains 1 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-18900: ------------------------------------- Both FeedHenry launch configuraions works fine with Oracle Java 1.8 and JBT 2015-02-06_00-45-13-B9487 > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, FHshortcuts.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-18900 at 2/6/15 8:03 AM: ------------------------------------------------------------- Both FeedHenry launch configurations works fine with Oracle Java 1.8 and JBT 2015-02-06_00-45-13-B9487 was (Author: vpakan): Both FeedHenry launch configuraions works fine with Oracle Java 1.8 and JBT 2015-02-06_00-45-13-B9487 > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, FHshortcuts.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-386) Target Platform is missing some source plugins when generating with sources

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBTIS-386?page=com.atlassian.jira.plugin.... ] Mickael Istria edited comment on JBTIS-386 at 2/6/15 7:53 AM: -------------------------------------------------------------- So the issue seems to be that JBT-IS TP uses JBT Unified TP whereas it should use JBT Multiple TP (same content, but reference sites that includeSources, so you get sources as an addition) To try that: * Locally, change https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... to jbosstools-multiple, and change artifact version to 4.2.1.CR2-SNAPSHOT (it has to be a SNAPSHOT) * mvn install this new TP * Then go to fuseide/targetplatform * Replace TP version by 4.2.1.CR2-SNAPSHOT (which is the one you just tweaked and installed locally) * Build it with "mvn -Pmultiple2repo -Dmirror-target-to-repo.includeSources=true" * Check for availability of sources. was (Author: mickael_istria): So the issue seems to be that JBT-IS TP uses JBT Unified TP whereas it should use JBT Multiple TP (same content, but reference sites that includeSources, so you get sources as an addition) To try that: * Locally, change https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... to jbosstools-multiple, and change artifact version to 4.2.1.CR2-SNAPSHOT (it has to be a SNAPSHOT) * mvn install this new TP * Then go to fuseide/targetplatform * Replace TP version by 4.2.1.CR2-SNAPSHOT (which is the one you just tweaked and installed locally) * Check for availability of sources. > Target Platform is missing some source plugins when generating with sources > --------------------------------------------------------------------------- > > Key: JBTIS-386 > URL: https://issues.jboss.org/browse/JBTIS-386 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Lars Heinemann > Assignee: Paul Leacu > Priority: Critical > > when mirroring the TP locally with sources some of the source plugins are missing. for instance org.eclipse.wst.server.ui.source. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18709?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18709: ------------------------------------- I've tested our current tools with the following URLs: http://www.jboss.org/download-manager/file/jboss-eap-6.4.0.Alpha.zip http://www.jboss.org/download-manager/jdf/file/jboss-eap-6.4.0.Alpha.zip I had to add the following to a local stacks.yaml: {code} ##################### # E A P 6.4 # ##################### - &jbosseap640runtime id: jbosseap640runtime name: JBoss EAP 6.4.0 version: 6.4.0 license: *lgpl21 url: http://www.jboss.org/products downloadUrl: http://www.jboss.org/download-manager/jdf/file/jboss-eap-6.4.0.Alpha.zip # deleted bom stuff labels: { requiresCredentials: true, runtime-category: SERVER, runtime-type: EAP, runtime-size: 158177216, wtp-runtime-type: org.jboss.ide.eclipse.as.runtime.eap.61 } {code} The non-jdf request failed and only downloaded an html page. The jdf URL worked. Our tools still required credentials, even though technically we don't need them. But if you note above, we still have requiresCredentials=true. This is to ensure that our tools make a request with the proper JDF request parameters, like an xml / json request header, etc. If we simply changed requiresCredentials to false, it would attempt a standard wget / curl / http request, and the result of that (even to the JDF url) is that it simply fetches an html page, which doesn't work. This means the current stacks.yaml label of "requiresCredentials" would be more accurately named something like "requiresWorkflow", but we can't change this because it'd break previous versions of JBT / JBDS. Leaving it, however, would mean that the label says requiresCredentials=true even when an alpha release for example doesn't require credentials. I'm not sure how much of an issue this is, since at the moment the stacks.yaml file doesn't list any alpha releases at all. And, from what I can tell, beta releases all require credentials. So this only really becomes an issue if somehow an alpha release makes it into stacks.yaml, and even then it's only an issue if someone objects to the "requiresCredentials=true" flag. We may be forced to simply keep the requiresCredentials=true for alpha releases even though it's not technically true. > EAP alpha releases not require credentials; verify downloadRuntimes works > ------------------------------------------------------------------------- > > Key: JBIDE-18709 > URL: https://issues.jboss.org/browse/JBIDE-18709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Rob Stryker > > A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release. > We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18709?page=com.atlassian.jira.plugi... ] David Hladky edited comment on JBIDE-18709 at 2/6/15 7:20 AM: -------------------------------------------------------------- Hi Rob, in order to test it on staging, you need to set Terms and Conditions model of some product version to Anonymous Download and use its links for testing. Feel free to choose any product and any product version, because the data on staging are just for testing purposes and no one does any other research on it. was (Author: dhladky): Hi Rob, in order to test it on staging, you need to set Terms and Conditions model of some product version to Anonymous Download and use its links for testing. > EAP alpha releases not require credentials; verify downloadRuntimes works > ------------------------------------------------------------------------- > > Key: JBIDE-18709 > URL: https://issues.jboss.org/browse/JBIDE-18709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Rob Stryker > > A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release. > We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015