September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22879: ----------------------------------- Assignee: Rob Stryker > JavaEE jars files are built with another java version than used for compilation > ------------------------------------------------------------------------------- > > Key: JBIDE-22879 > URL: https://issues.jboss.org/browse/JBIDE-22879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: LATER > > Attachments: test-projects.zip > > > I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it. > When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7. > This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23142) [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23142?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23142. --------------------------------- Fix Version/s: 4.4.2.AM1 Resolution: Done Small changes were made to both UI and Core classes to allow for modifying the vagrant location, and, to ensure defaults and searches are used in case the user has not set one or the setting is invalid. > [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-23142 > URL: https://issues.jboss.org/browse/JBIDE-23142 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Fix For: 4.4.2.AM1 > > > Steps to replicate: > 1) Create a new cdk server adapter on windows > 2) Open launch configuration and find the vagrant location > 3) Move that vagrant to another folder which is also on path > 4) Re-open launch config, note the launch config errors, and you cannot change it > Ideally, it will locate the new vagrant location. If not, it should allow you to set the new vagrant location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22879: -------------------------------- Fix Version/s: LATER > JavaEE jars files are built with another java version than used for compilation > ------------------------------------------------------------------------------- > > Key: JBIDE-22879 > URL: https://issues.jboss.org/browse/JBIDE-22879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Fix For: LATER > > Attachments: test-projects.zip > > > I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it. > When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7. > This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23142) [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23142?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23142: ------------------------------------- https://github.com/jbosstools/jbosstools-openshift/pull/1307 pushing to master > [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-23142 > URL: https://issues.jboss.org/browse/JBIDE-23142 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > > Steps to replicate: > 1) Create a new cdk server adapter on windows > 2) Open launch configuration and find the vagrant location > 3) Move that vagrant to another folder which is also on path > 4) Re-open launch config, note the launch config errors, and you cannot change it > Ideally, it will locate the new vagrant location. If not, it should allow you to set the new vagrant location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-864) Target Platform - 4.4.0.Alpha2 update m2e-wtp for neon

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-864?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-864: ----------------------------- Description: *Reason:* Update m2e-wtp *Project page/sources:* *Version:* 1.3.1 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/m2e-wtp/milestones/neon/1.3/1.3.1.20160831-1005 *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp *Include Sources:* Yes *Affected JBoss Tools components:* IS *Include in JBDS:* Yes - JBDSIS *Type of dependency:* distribution *List of bundles added/removed:* {code} > org.jboss.tools.maven.jsf [1.3.1.20160831-1005] > org.jboss.tools.maven.jpa [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005] > org.maven.ide.eclipse.wtp [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005] > org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005] > org.eclipse.m2e.wtp [1.3.1.20160831-1005] > org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005] > org.sonatype.tycho.m2e.feature.feature.group [0.9.0.201609061714] > org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005] > org.sonatype.tycho.m2e.feature.feature.jar [0.9.0.201609061714] > org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005] > org.sonatype.tycho.m2e [0.9.0.201609061714] > org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005] === Summary === http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Al... contains 0 unique IUs file:/home/pleacu/git-clone/jbosstools-integration-stack.neon/target-platform/target/target-platform-ea.target.repo contains 21 unique IUs {code} was: *Reason:* Update m2e-wtp *Project page/sources:* *Version:* 1.3.1 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/m2e-wtp/milestones/neon/1.3/1.3.1.20160831-1005 *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp *Include Sources:* Yes *Affected JBoss Tools components:* IS *Include in JBDS:* Yes - JBDSIS *Type of dependency:* distribution *List of bundles added/removed:* {code} > Target Platform - 4.4.0.Alpha2 update m2e-wtp for neon > ------------------------------------------------------ > > Key: JBTIS-864 > URL: https://issues.jboss.org/browse/JBTIS-864 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.0.Alpha2-TP > > > *Reason:* Update m2e-wtp > *Project page/sources:* > *Version:* 1.3.1 > *License and owner:* EPL > *Original p2 repo:* http://download.eclipse.org/m2e-wtp/milestones/neon/1.3/1.3.1.20160831-1005 > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp > *Include Sources:* Yes > *Affected JBoss Tools components:* IS > *Include in JBDS:* Yes - JBDSIS > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > > org.jboss.tools.maven.jsf [1.3.1.20160831-1005] > > org.jboss.tools.maven.jpa [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005] > > org.maven.ide.eclipse.wtp [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005] > > org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp [1.3.1.20160831-1005] > > org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005] > > org.sonatype.tycho.m2e.feature.feature.group [0.9.0.201609061714] > > org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005] > > org.sonatype.tycho.m2e.feature.feature.jar [0.9.0.201609061714] > > org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005] > > org.sonatype.tycho.m2e [0.9.0.201609061714] > > org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005] > === Summary === > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Al... contains 0 unique IUs > file:/home/pleacu/git-clone/jbosstools-integration-stack.neon/target-platform/target/target-platform-ea.target.repo contains 21 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Andreas Gajdosik (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Andreas Gajdosik commented on JBDS-4048: ---------------------------------------- Get-WmiObject - without any output wmic product where "name like '%%OpenJDK%%'" get name","version - outpus: "No Instance(s) Available" > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Andreas Gajdosik (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Andreas Gajdosik edited comment on JBDS-4048 at 9/7/16 5:19 PM: ---------------------------------------------------------------- Get-WmiObject - without any output wmic product where "name like '%%OpenJDK%%'" get name","version - outputs: "No Instance(s) Available" was (Author: agajdosi): Get-WmiObject - without any output wmic product where "name like '%%OpenJDK%%'" get name","version - outpus: "No Instance(s) Available" > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4048) Checking of installed OpenJDK gets stucked on windows 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4048?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-4048 at 9/7/16 5:00 PM: ------------------------------------------------------------- Please also try as alternative approach {code} wmic product where "name like '%%OpenJDK%%'" get name,version{code} What is the output? was (Author: dgolovin): Please also try as alternative approach {code}wmic product get name,version{code} What is the output? > Checking of installed OpenJDK gets stucked on windows 7 > ------------------------------------------------------- > > Key: JBDS-4048 > URL: https://issues.jboss.org/browse/JBDS-4048 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 7, x86_64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: InstallerStucked.png > > > Checking of installed component gets stucked. See pic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23142) [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23142: ----------------------------------- Summary: [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails Key: JBIDE-23142 URL: https://issues.jboss.org/browse/JBIDE-23142 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk Affects Versions: 4.4.1.Final Reporter: Rob Stryker Steps to replicate: 1) Create a new cdk server adapter on windows 2) Open launch configuration and find the vagrant location 3) Move that vagrant to another folder which is also on path 4) Re-open launch config, note the launch config errors, and you cannot change it Ideally, it will locate the new vagrant location. If not, it should allow you to set the new vagrant location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23132) When ftl file is opened in devstudio/eclipse it does not get cursor/focus

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23132?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-23132: --------------------------------------- I couldn't yet recreate this issue yet. I have installed the nightly snapshot from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre... on both Mars and Neon, but the cursor does appear in the editor when I open the ftl file (from tree with double click or in any other way). Note sure if devstudio is different, or RC1 for that mater. > When ftl file is opened in devstudio/eclipse it does not get cursor/focus > ------------------------------------------------------------------------- > > Key: JBIDE-23132 > URL: https://issues.jboss.org/browse/JBIDE-23132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.Final > Environment: Fedora 24, x86_64, devstudio: > Version: 10.1.0.GA > Build id: GA-v20160902-1725-B43 > Eclipse neon 1, RC1 > Reporter: Ondrej Dockal > Assignee: Daniel Dekany > > When I open a freemarker file (.ftl) in devstudio (project/package explorer), new tab with editor is opened, but there is missing a cursor and I cannot actually set the cursor in calling setCursorPosition and thus, opening of content assistant throws a timeoutexception. It looks like editor is not focused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016