April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21606: ------------------------------------- I must be using an early build of eap 6.4. From a mailing list thread: Per the EAP supported configurations page [1], the user can only use EAP 6.3.2 and below if they are using Oracle or IBM Java 1.7. If they are using OpenJDK Java 1.7, then they can run up to EAP 6.4. [1] https://access.redhat.com/articles/111663 So at the very least, eap 6.4 requires Java7. > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:37 AM: ------------------------------------------------------------------------- OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2 It can be replaced with {code} "oc v([0-9\\.-\\.]*)(?:-([0-9]*)-(.*))?" {code} was (Author: scabanovich): OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2 > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22271) Test failure in server: dtd schema files missing in plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22271?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22271: -------------------------------- Fix Version/s: 4.4.0.Alpha2 > Test failure in server: dtd schema files missing in plugin > ---------------------------------------------------------- > > Key: JBIDE-22271 > URL: https://issues.jboss.org/browse/JBIDE-22271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > Server tests have been failing on this test: > org.jboss.tools.as.test.core.catalog.CatalogMissingEntriesTest.testMissingEntries (from org.jboss.tools.as.test.core.ASToolsTestSuite) > /schema/dtd/properties.dtd is not found in plugin.xml > /schema/dtd/datatypes.dtd is not found in plugin.xml > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... > Sorry if this has been reported elsewhere, I couldn't find it. > Not sure if it's too late to fix in Alpha1 or not. Up to you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:33 AM: ------------------------------------------------------------------------- OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2 was (Author: scabanovich): OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two --, like in oc v1.2.0--rc2 > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-503) Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-503?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-503. ----------------------------------- Closed as obsolete. Current JBTIS TP which is 4.3.1.Final contains JBT TP 4.52.0.FInal and Locus 1.6.0.Final > Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final > ----------------------------------------------------------------- > > Key: JBTIS-503 > URL: https://issues.jboss.org/browse/JBTIS-503 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Final-TP, 4.3.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final > *Project page/sources:* > *Version:* 4.51.0.Final > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* JBDSIS/ JBTIS > *Include in JBDS:* Yes (JBDSIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22275: ----------------------------------------------- OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two '-', like in oc v1.2.0--rc2 > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:31 AM: ------------------------------------------------------------------------- OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two --, like in oc v1.2.0--rc2 was (Author: scabanovich): OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two '-', like in oc v1.2.0--rc2 > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-499) Aggregate Mars ModeShape

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-499?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-499. ----------------------------------- Verified with JBDS-IS 9.0.0.GA and JBTIS 4.3.0.Final which contain Modeshape 3.8.0.Beta1-v20150915-1710-B210 on early access. > Aggregate Mars ModeShape > ------------------------ > > Key: JBTIS-499 > URL: https://issues.jboss.org/browse/JBTIS-499 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: modeshape > Affects Versions: 4.3.0.Alpha2, 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2, 9.0.0.Alpha2 > > > Aggregate > http://download.jboss.org/jbosstools/updates/development/mars/integration... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-505) Update category.xml for JBT core CR1a updates

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-505?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-505. ----------------------------------- Close as obsolete. The zest bundles were moved to TP, see JBTIS-630 > Update category.xml for JBT core CR1a updates > --------------------------------------------- > > Key: JBTIS-505 > URL: https://issues.jboss.org/browse/JBTIS-505 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22276) Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22276?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22276: ----------------------------------------------- Eclipse prefers 'Browse...' when it is evident what is going to be selected. > Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22276 > URL: https://issues.jboss.org/browse/JBIDE-22276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3, server_adapter_wizard > > In New OpenShift Server Adapter wizard there is a text widget for Eclipse project. Next to it there is a Browse... button which allow to select an eclipse project from workspace. > IN New OpenShift Application Wizard there is a text widget for Eclipse project to be used for a new application. Next to it there is a Browse... button which allow to select an eclipse project from workspace. (On the same wizard page user can select a template from local file system/workspace and there we use correct buttons.) > Earlier we were using Browse... button for real browsing using native file browser/chooser. Now we use it for selecting a project from workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016