[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19720:
-----------------------------------------------
Thank you. Now we can fix it in our code.
Though, the fact that absolute and workspace-relative paths in Eclipse may coincide pointing to different existing resources looks like a potential source of problems.
> 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
> Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17"
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> 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, 10 months
[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Valentin Baciu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Valentin Baciu commented on JBIDE-19720:
----------------------------------------
Hi Viacheslav Kabanovich, I sparked up the debugger and here's what I see:
- I have a project named System in my workspace
- one of the class path entries in the JRE class path container points to a jar located at /System/Library/Java/Extensions/MRJToolkit.jar
So yes, it appears that in my case too a workspace project name coincides with the first segment of a classpath entry jar location.
Hope this helps.
> 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
> Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17"
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> 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, 10 months
[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-19500:
---------------------------------------
[~maxandersen], Could you review message on this mock-up dialog:
!JVMProblemDetector.png!
> 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
> Fix For: 4.3.0.Beta1
>
> Attachments: JVMProblemDetector.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
[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19500:
----------------------------------
Attachment: JVMProblemDetector.png
> 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
> Fix For: 4.3.0.Beta1
>
> Attachments: JVMProblemDetector.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
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19590:
---------------------------------------
You can try jbosstools-hbibernate oomph setub out by downloading oomph installer and adding
{code}
-Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->http://dgolovin.github.io/jbosstools-oomph/setup/
{code}
in oomph.ini file in -vmargs part. Run oomph and then:
1. Select Eclipse IDE for Committers (Unreleased Before Mars) on first page
2. Select "Github.com/JBoss Tools Hibernate" by double click on second page
3. Provide full path to installation folder or it will use ~/org-master (should provide petter name by default)
4. Finish wizard on forth page and wait
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: hibernate-psf-import.mp4
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17281:
----------------------------------
Sprint: Sprint #4 May 2015 (was: Sprint #3 May 2015)
> parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17281
> URL: https://issues.jboss.org/browse/JBIDE-17281
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Optional
> Fix For: 4.3.0.Beta1
>
>
> The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml
> - move update site manipulations to site/pom.xml
> - etc
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19590:
----------------------------------
Sprint: Sprint #4 May 2015 (was: Sprint #3 May 2015)
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: hibernate-psf-import.mp4
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19720:
-----------------------------------------------
I managed to reproduce this exception in Linux after I created a project with a name 'home'. The exception happens because code checks if the first segment of path is the project name, and in this case assumes that it is a resource from the project. Absolute paths on my computer start with '/home/' so that the check passes (which is wrong).
[~baciuv], could you have in your workspace a project named so that workspace path to it in Eclipse workspace coincides with some existing absolute path on computer? If not, then what I have found is another bug, and solving it will not solve your case .
> 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
> Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17"
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> 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, 10 months
[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17989:
-----------------------------------
Attachment: jbds.png
For JBDS it's 2014, January 23-25th:
!jbds.png!
> keyword used for plugin tracking is missing majority of times on GA
> -------------------------------------------------------------------
>
> Key: JBIDE-17989
> URL: https://issues.jboss.org/browse/JBIDE-17989
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: devstudio-january.png, graphformissingstats.png, jbds.png, scr.png
>
>
> looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result.
> Meaning we can't see how many have installed the various plugins.
> What is weird *some* do and others do not have it.
> Need to track down the reason for that being missed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months