June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-19500. ------------------------------------ Resolution: Done Pushed in master. > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19500: ----------------------------------- Labels: new_and_noteworthy (was: ) > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19569: ------------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Unable to switch pages shown in visual preview when editing mobile html5 > ------------------------------------------------------------------------ > > Key: JBIDE-19569 > URL: https://issues.jboss.org/browse/JBIDE-19569 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta2 > > > I'm not sure if my use case is valid or not. > But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one. > So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview. > Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button? > But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :) > [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19922) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19922?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19922. ---------------------------------- Resolution: Done > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JST] > ------------------------------------------------- > > Key: JBIDE-19922 > URL: https://issues.jboss.org/browse/JBIDE-19922 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19700) Support @BatchProperty qualifiers for injected beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19700?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19700: ----------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Support @BatchProperty qualifiers for injected beans > ---------------------------------------------------- > > Key: JBIDE-19700 > URL: https://issues.jboss.org/browse/JBIDE-19700 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch, cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > You can find an example of such beans here: > https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... > 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project > 2. Open batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/RecordsReader.java > 3. There should not be warning messages about no eligible beans for *separatorRegex* and *fileName* properties. > 4. OpenOns for these properties should open import-file.xml and select the corresponding properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19505: ----------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Angular Code Assist doesn't work for jboss-kitchensink-angularjs app > -------------------------------------------------------------------- > > Key: JBIDE-19505 > URL: https://issues.jboss.org/browse/JBIDE-19505 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > 1. Import jboss-kitchensink-angularjs from JBoss Central > 2. Open partials/home.html page > 3. Open Angular Explorer and lind modules > MemberService > MembersCtrl to controler > 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m > ERROR: Code Assist doesn't contain proposal for message variable -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19781) Open 'Properties' view together with the Batch diagram editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19781?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19781: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta1) > Open 'Properties' view together with the Batch diagram editor > ------------------------------------------------------------- > > Key: JBIDE-19781 > URL: https://issues.jboss.org/browse/JBIDE-19781 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.x > > > Users have problems to find where to edit properties like item readers or batchlet refs. > If the Properties view is not open when editor is started, they do not have the idea to use it. > So I suggest to open it always when diagram is opened or changes its inner model element. Or do you have a better idea? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19937) Finish button in v3 New OpenShift Application does not do anything

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19937?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19937: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > Finish button in v3 New OpenShift Application does not do anything > ------------------------------------------------------------------ > > Key: JBIDE-19937 > URL: https://issues.jboss.org/browse/JBIDE-19937 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Blocker > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta1 > > > In New OpenShift Application wizard If I choose to create a new application from template available on https://console.stg.openshift.com/ I can proceed through wizard and select various settings for an application but after hitting Finish button on any wizard page, nothing happens. There is not even any error in error log. Finish button just go to disabled stay for a while (up to 2 second) and then it is active again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3451) For JBDS 9.0.0.Beta1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3451?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3451. ---------------------------- Assignee: Nick Boldt Resolution: Done > For JBDS 9.0.0.Beta1: Code Freeze + Branch > ------------------------------------------ > > Key: JBDS-3451 > URL: https://issues.jboss.org/browse/JBDS-3451 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 9.0.0.Beta1 > > > For JBDS 9.0.0.Beta1: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19759: ------------------------------------------ The users can for now launch the v3 new application wizard via context menu. We went out of time for the proper fix in 4.3.0.Beta1 > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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