April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19720: -------------------------------------- Assignee: Viacheslav Kabanovich > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Another code path: > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Valentin Baciu (JIRA)

Valentin Baciu created JBIDE-19720: -------------------------------------- Summary: NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath Key: JBIDE-19720 URL: https://issues.jboss.org/browse/JBIDE-19720 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.2.3.Final Reporter: Valentin Baciu Priority: Minor java.lang.NullPointerException at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Another code path: java.lang.NullPointerException at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17314) Much UI from JVM Monitor documentation is missing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17314?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17314. --------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.x) Resolution: Out of Date This issue is out of date and the comments have ranged all over the place. The UI has changed substantially since then (introduction of JMX groups). > Much UI from JVM Monitor documentation is missing > ------------------------------------------------- > > Key: JBIDE-17314 > URL: https://issues.jboss.org/browse/JBIDE-17314 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Paul Leacu > Fix For: 4.2.1.Final > > Attachments: create-conn.png, ss-pref-tools.png, ss1.png > > > Much of the UI from http://www.jvmmonitor.org/doc/index.html#Monitoring_JVM_on_remote_host is missing and disabled. We must discover where it's gone, why it's disabled, and whether it can be re-activated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17545) Can't Full Publish project to WildFly (8.0 or 8.1)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17545?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17545. --------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.x) Resolution: Duplicate Issue Rejecting as a duplicate issue. No new feedback or replicatations in 6 months. > Can't Full Publish project to WildFly (8.0 or 8.1) > -------------------------------------------------- > > Key: JBIDE-17545 > URL: https://issues.jboss.org/browse/JBIDE-17545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Lincoln Baxter III > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > The following error is logged and publishing fails when attempting to Full Publish this project: > https://github.com/forgeide/forgeide > {code} > Publishing failed > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1118502157688228046.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/forge-javassist-2.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1738236936180964755.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jboss-modules-1.3.0.Final-forge.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp2320075067441042997.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jgrapht-0.8.3.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19719: ------------------------------------ Assignee: Gorkem Ercan > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19719: ------------------------------------ Summary: "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 Key: JBIDE-19719 URL: https://issues.jboss.org/browse/JBIDE-19719 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Attachments: jbosstools-diagnostics-20150427143128.zip This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Attachment: jbosstools-diagnostics-20150427143128.zip > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19688) Eclipse m2e, workspace resolution and Wildfly deployment issues

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19688?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19688. --------------------------------- Resolution: Rejected So the problem is your manager-test-bean project has the Web Facet. As a jar dependency, it should have the Utility Facet. To fix your problem, delete the projects from your workspace, remove .project, .classpath and .settings/ then reimport them as Maven projects. The proper Facets will be added. Then you'll see manager-test-bean deployed as a jar archive, whenever you deploy the web app to a WTP server. > Eclipse m2e, workspace resolution and Wildfly deployment issues > --------------------------------------------------------------- > > Key: JBIDE-19688 > URL: https://issues.jboss.org/browse/JBIDE-19688 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server > Reporter: Sylvain Paillé > Assignee: Fred Bricon > Attachments: manager-test-ko.zip > > > Hello ! > I just found on Wildfly a Jboss (resolved ?) related bug. > See : https://issues.jboss.org/browse/AS7-4704 > When using Eclipse and m2e plugin, deploy with "workspace resolution" make WEB-INF/lib/ jar to be exploded into directories ... > Wildfly simply ignore them when running app. > Disabling Workspace resolution is a workaround. > Have you met a similar bug ? > Thx -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19716: -------------------------------------- Assignee: Gorkem Ercan (was: Mickael Istria) > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- True, I referred my old repo before. PR for the removal from jbdevstudio-qa repo created https://github.com/jbdevstudio/jbdevstudio-qa/pull/55. Once Nick confirms his jobs are set to a new location and working it can be applied. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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