May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- [~maxandersen], that's what I wanted to try before, but couldn't find out how to disable Oomph. So trying as suggested by Mickael: [~mickael_istria], you mean true, no? Like -Dorg.eclipse.oomph.setup.skip=true under -vmargs in eclipse.ini, right? I did that and I can still see all the preferences of Oomph. And the config was there right away (org.jboss.tools.runtime.ui.prefs), just after first start of clean Eclipse (previously I thought it only appeared during JBT installation, but it gets there right after the startup of Eclipse). So no luck here. Perhaps the "Skip automatic task execution at startup time" checkbox under Preferences -> Oomph -> Setup could help, but I can only check it after it's too late :) > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19704: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.0.Beta1 > > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18556: -------------------------------- Sprint: (was: Sprint #3 May 2015) > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18583) pong index.html no longer works on cordovasim (Mac OS specific)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18583?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18583: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > pong index.html no longer works on cordovasim (Mac OS specific) > --------------------------------------------------------------- > > Key: JBIDE-18583 > URL: https://issues.jboss.org/browse/JBIDE-18583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR2 > Environment: Mac Os > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: index.html.zip > > > This works in previous versions. > replace the index.html into a hybrid app - it works when using ios simulator but not with cordovasim. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18672: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > cannot run ionic tabs (the default) app with cordovasim > ------------------------------------------------------- > > Key: JBIDE-18672 > URL: https://issues.jboss.org/browse/JBIDE-18672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.Final > Environment: Mac OS X, JavaFX > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.3.0.Beta1 > > > run: > ionic start ionic-demo > import ionic-demo > run as > cordova sim > try use the app, click back. > Two issues: > 1) cordova sim complains about app.appexit not being supported > 2) when trying to click do not show again I get the following in the cordovasim error log: > Outstanding resource locks detected: > ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total > 84 total resources being managed > average resource age is 15.1 frames > 0 resources at maximum supported age (0.0%) > 16 resources marked permanent (19.0%) > 17 resources have had mismatched locks (20.2%) > 17 resources locked (20.2%) > 30 resources contain interesting data (35.7%) > 0 resources disappeared (0.0%) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18583) pong index.html no longer works on cordovasim (Mac OS specific)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18583?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18583: ------------------------------------- hmm.. my "great expectations" that the issue will be fixed in jdk8u60 and jdk9 were confounded. The pong sample does not work against JavaFx even with updated WebKit. Seems to be some javafx canvas bug. Keep digging... > pong index.html no longer works on cordovasim (Mac OS specific) > --------------------------------------------------------------- > > Key: JBIDE-18583 > URL: https://issues.jboss.org/browse/JBIDE-18583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR2 > Environment: Mac Os > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: index.html.zip > > > This works in previous versions. > replace the index.html into a hybrid app - it works when using ios simulator but not with cordovasim. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19757: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Consider using main JBT site for server discovery > ------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19757: -------------------------------------- Summary: Consider using main JBT site for server discovery Key: JBIDE-19757 URL: https://issues.jboss.org/browse/JBIDE-19757 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build, server Reporter: Mickael Istria With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing {code} !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". {code} because we are lines specifying bundle but no version in the site.xml. [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-19687: -------------------------------- Attachment: errorMessage Attached the error info > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19741: --------------------------------------------- It is actually a very significant part. This visualizes it a bit better for me: {code} $ du -sk * | sed -e 's/_.*//g' | distribution -g --color jbosstools-javaee|246112 (51.05%) ----------------------------------------- jbosstools-server| 53056 (11.00%) --------- jbosstools-hibernate| 47888 (9.93%) -------- jbosstools-base| 40000 (8.30%) ------- jbosstools-webservices| 22424 (4.65%) ---- jbosstools-jst| 20128 (4.17%) ---- jbosstools-central| 14108 (2.93%) --- jbosstools-browsersim| 11044 (2.29%) -- jbosstools-vpe| 10764 (2.23%) -- jbosstools-openshift| 4092 (0.85%) - jbosstools-birt| 2396 (0.50%) - jbosstools-portlet| 2328 (0.48%) - jbosstools-freemarker| 2276 (0.47%) - jbosstools-forge| 1716 (0.36%) - jbosstools-arquillian| 1664 (0.35%) - {code} in javaee: {code} Key|Ct (Pct) Histogram seam|103688 (42.13%) ------------------------------------------------------ jsf| 90180 (36.64%) ----------------------------------------------- cdi| 50992 (20.72%) --------------------------- batch| 1224 (0.50%) - site| 12 (0.00%) - all-tests| 4 (0.00%) - pom.xml| 4 (0.00%) - README.md| 4 (0.00%) - {code} > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015