July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19990: ------------------------------------- JSF support enabled it's working HTML5 support enabled it's working > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3463: -------------------------------- Story Points: 5 Sprint: Sprint #6 July 2015 > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: InstallConfigRecord.xml > > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-19990 at 7/7/15 1:09 AM: ------------------------------------------------------------- * JSF support enabled it's working * HTML5 support enabled it's working was (Author: vpakan): JSF support enabled it's working HTML5 support enabled it's working > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding'

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3453: -------------------------------- Fix Version/s: 9.0.0.Beta2 > Launch after installation results in 'not responding' > ----------------------------------------------------- > > Key: JBDS-3453 > URL: https://issues.jboss.org/browse/JBDS-3453 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, 64-bit > installer run with OpenJDK 1.7.0_79 > devstudio run with OpenJDK 1.8.0_45 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: .log, jstacks > > > When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning). > Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding'

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3453: -------------------------------- Sprint: Sprint #6 July 2015 > Launch after installation results in 'not responding' > ----------------------------------------------------- > > Key: JBDS-3453 > URL: https://issues.jboss.org/browse/JBDS-3453 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, 64-bit > installer run with OpenJDK 1.7.0_79 > devstudio run with OpenJDK 1.8.0_45 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: .log, jstacks > > > When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning). > Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20191) Locus plug-ins have errors after importing into workspace

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20191: ------------------------------------- Summary: Locus plug-ins have errors after importing into workspace Key: JBIDE-20191 URL: https://issues.jboss.org/browse/JBIDE-20191 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Affects Versions: 4.3.0.Beta1 Reporter: Denis Golovin Assignee: Denis Golovin There are several problems with locus plrojects after importing them into workspace as maven projects: 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-39) Consider using Eclipse Bundle Recipes (EBR)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/LOCUS-39?page=com.atlassian.jira.plugin.s... ] Denis Golovin commented on LOCUS-39: ------------------------------------ [~mickael_istria] I believe it is actually possible to "aggregate" any amount of maven call in one using maven-invoker plugin. Basically it lets you to invoke maven from maven, but from user perspective it looks like single maven call. That would first call EBR builds for required bundles, install them into local repo and then call maven again to build p2repository. I am also curious why we don't use inclusion of actual jar inside bundle and then expose it through OSGi, for examle like that https://github.com/jbosstools/jbosstools-locus/compare/jbosstools:master..... Are there any class loading related problems? > Consider using Eclipse Bundle Recipes (EBR) > ------------------------------------------- > > Key: LOCUS-39 > URL: https://issues.jboss.org/browse/LOCUS-39 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > > I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I have the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. > More background about EBR: > * http://www.eclipse.org/ebr > * http://de.slideshare.net/guw/tasty-recipes-for-osgi-bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20136) Batch diagram generates references in <next> element

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20136?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20136 at 7/6/15 6:37 PM: ----------------------------------------------------------------------- For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. Of course, it makes no sense. The attached pull request prohibits drawing connection to a flow element with id attribute not set. was (Author: scabanovich): For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. Of course, it makes no sense. I still cannot find if we can prevent it. > Batch diagram generates references in <next> element > ---------------------------------------------------- > > Key: JBIDE-20136 > URL: https://issues.jboss.org/browse/JBIDE-20136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > Attachments: diagram.png, editor.png > > > I created two steps in batch diagram editor without the ID specified and connected them with "Next on" element. In source view, the "to" values contained some unusual values like "StepNode#0" (see attachmets). > For "Next" element is the behaviour different - editor would not allow me to create connection at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20190) parent pom needs to reference http://maven.repository.redhat.com/ga/

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20190?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20190: ------------------------------------- Patch seems to work for me. > parent pom needs to reference http://maven.repository.redhat.com/ga/ > -------------------------------------------------------------------- > > Key: JBIDE-20190 > URL: https://issues.jboss.org/browse/JBIDE-20190 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > > The small refactor that took place in https://issues.jboss.org/browse/JBIDE-19641 requires access to the redhat maven repository, which is not currently in parent pom. > Current build is failing due to being unable to locate jboss runtime jars. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20087) Automatically integrate the app with FeedHenry

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20087?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-20087: ------------------------------------ Assignee: Gorkem Ercan > Automatically integrate the app with FeedHenry > ---------------------------------------------- > > Key: JBIDE-20087 > URL: https://issues.jboss.org/browse/JBIDE-20087 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta2 > > > There is almost anything I can do in FH cloud with the newly pushed app until I integrate the app with FeedHenry (creating fhconfig.json, downloading feedhenry.js ..) Even the FeedHenry editor doesn't work. > It would be super cool if the tooling could integrate the app with FH automatically, however I'm not familiar with FH API if that is even possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015