[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Nick Boldt closed JBIDE-2720.
-----------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Won't Fix
Xulrunner is deprecated in Devstudio. Closing won't fix.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.5.1.AM1
>
> Attachments: .mozconfig, Unbenannt.PNG, Unbenannt.PNG, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-23391) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23391?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23391.
------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Won't Fix
No one is actively maintaining Central any more so it's unlikely this will get done. Closing won't fix.
> For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
> ----------------------------------------------------------------
>
> Key: JBIDE-23391
> URL: https://issues.jboss.org/browse/JBIDE-23391
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: task
> Fix For: 4.5.1.AM1
>
>
> For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui.workbench
> > org.eclipse.equinox.p2.ui
> > org.eclipse.mylyn.discovery.ui
> --
> [CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.jdt.ui
> > org.eclipse.ui.workbench
> > org.eclipse.m2e.core.ui
> --
> [CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.eclipse.jdt.ui
> > org.eclipse.ui.workbench
> > org.eclipse.m2e.core.ui{code}
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-20747.
------------------------------
Resolution: Out of Date
Not using install grinder anymore. Closing out of date.
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.1.AM1
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20747:
-------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.1.AM1
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20747:
----------------------------------
Assignee: Nick Boldt
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.x
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16575.
------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Won't Fix
Over a year with no progress. Closing won't fix.
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.5.1.AM1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22739.
------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Won't Fix
Over a year with no progress. Closing won't fix.
> Use simpler Surefire include/exclude pattern in root poms
> ---------------------------------------------------------
>
> Key: JBIDE-22739
> URL: https://issues.jboss.org/browse/JBIDE-22739
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude:
> {code}
> include = *Test*, *Test, *TestCase
> exclude = *Abstract*
> {code}
> 2. If that causes test failures because running incorrectly named
> abstract stuff, they can refactor, add their own root pom overrides, use
> a TestSuite, or use @Ignore in test classes.
> 3. If the count of tests run suddenly DROPS because the pattern isn't
> running the correct # of tests, they can add their own root pom
> overrides, or use a TestSuite.
> Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-17281.
------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
Resolution: Won't Fix
Years without progress. Closing won't fix.
> 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.5.1.AM1
>
>
> 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 reduce clutter in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml
> - move update site manipulations to site/pom.xml
> - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse
> - etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months