July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17010) Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17010?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-17010: --------------------------------------- See also JBIDE-16717 and JBIDE-16022. > Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1 > ----------------------------------------------------------------------- > > Key: JBIDE-17010 > URL: https://issues.jboss.org/browse/JBIDE-17010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Beta1 > Environment: JPP 6.1.1, Seam 2.3.2, Portlet Bridge 3.2.1, Database: HSQL (DefaultDS) > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > Attachments: jpp611.log > > > There is an error in console output when seam portlet is deployed to JPP 6.1.1. > {code} > ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 84) HHH000299: Could not complete schema update: java.lang.NullPointerException > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17832) Add JVM name and architecture info collected by usage plug-in to Usage Preferences page

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-17832: -------------------------------------- Summary: Add JVM name and architecture info collected by usage plug-in to Usage Preferences page Key: JBIDE-17832 URL: https://issues.jboss.org/browse/JBIDE-17832 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 4.2.0.Beta3 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17790) Usage Analytics New and Noteworthy for 4.2.0.Beta3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17790?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17790: -------------------------------------- Assignee: Alexey Kazakov > Usage Analytics New and Noteworthy for 4.2.0.Beta3 > -------------------------------------------------- > > Key: JBIDE-17790 > URL: https://issues.jboss.org/browse/JBIDE-17790 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Usage Analytics is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Usage Analytics by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: IonicPopupWizBan.png IonicPopup.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicPopup.png, IonicPopupWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, scr.png, Scroll.png, ScrollWizBan.png, SlideBox.png, SlideBoxWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17829: ------------------------------------- I re-read your jira, and you say it's starting with java6. I'm not able to replicate this in any way. I'm not able to mark a java6 jre as a default vm install for a java7 or java8 execution environment. I've tried setting the java6 as the workspace default, but, it still doesn't change the classpath in the launch configuration. I'll keep working on this. [~mmalina] are you able to replicate this in any way at all? Try to get a wildfly to start with a java6. I'm unable to replicate, despite trying everything I can think of to force it to have the wrong jre. > Server adapter chooses wrong runtime for launches and validation is inconsistent > -------------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17829: ------------------------------------- Here are the PR's to ensure that the error message for javase-7 shows when you select the java7 exec env, and the error message for java8 shows when you select the java8 execution environment. https://github.com/jbosstools/jbosstools-server/pull/243 https://github.com/jbosstools/jbosstools-server/pull/242 > Server adapter chooses wrong runtime for launches and validation is inconsistent > -------------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17829: ------------------------------- Affects Version/s: 4.2.0.Beta3 > Server adapter chooses wrong runtime for launches and validation is inconsistent > -------------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17829: ------------------------------------- If you're confused why the error is showing at all, I will explain. If your workspace only has java6, and you select the java7 execution environment, there will be 0 possible JREs that match the java7 execution environment. Your jdk6 will not match the java7 exec env, or the java8 exec env. If you did have a java8 installed, it would match all existing java execution environments. A higher java will match lower java's exec-envs. A lower java will not match a higher java's exec-env. Again, aside from the lagging validation, this is working as expected. > Server adapter chooses wrong runtime for launches and validation is inconsistent > -------------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17829: ------------------------------------- > So something is really wrong. Max, your sense of melodrama is over-the-top. I think it's obvious that the validation is occurring using the previously selected widget, rather than with the new selection. I would not consider this a blocker at all, or be so super confused by it. As for why the launch configuration is displaying java-6 libraries, you already indicated your workspace has no java other than java6. This means, clearly, that the launch configuration could only possibly have java6 as the java to use. This also is not confusing in the least. Can you explain the reason you're confused by this? Would you expect a nonexistant java7 be on the classpath for your server, despite the fact that your workspace has no java7 declared? Aside from fixing the lagging validation, I really don't see any big problems here. > Server adapter chooses wrong runtime for launches and validation is inconsistent > -------------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Description: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). !import-failed-uncommitted-changes.png! This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. > Application wizard: stuck with application but existing project cannot be merged: uncommitted changes > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Optional > Labels: application_wizard, respin-a > Fix For: 4.2.0.Beta3 > > Attachments: import-failed-uncommitted-changes.png > > > EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) > EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). > EXEC: Choose basic cartridge and click Next button (ex. EAP 6). > EXEC: Fill in name on the next wizard page and click Next. > EXEC: Choose Use existing project and select the existing git based project. > EXEC: Finish the wizard. > *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > !import-failed-uncommitted-changes.png! > This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 2014