[JBoss JIRA] (JBIDE-16304) install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16304?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16304:
-------------------------------
Attachment: consoleText.partialtxt
consoleText.full.txt
more complete console logs attached:
[^consoleText.full.txt] [^consoleText.partialtxt]
> install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16304
> URL: https://issues.jboss.org/browse/JBIDE-16304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Attachments: consoleText.full.txt, consoleText.partial.txt
>
>
> When trying to install from central site, this error happens because Forge 2 requires JDK 7, yet the Eclipse instance is using JDK 6 to run:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2Fjbosstools-directory.xml,eclipseBundleVersion=luna.M3,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1531/consoleText}
> 17:53:58 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.aesh.core [983]
> 17:53:58 Unresolved requirement: osgi.wiring.bundle; visibility:="reexport"; filter:="(&(osgi.wiring.bundle=org.jboss.tools.aesh.runtime)(bundle-version>=0.39.0))"
> 17:53:58 -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.aesh.runtime"; bundle-version:Version="0.43.0.Alpha1-v20131211-1657-B454"; singleton:="true"
> 17:53:58 org.jboss.tools.aesh.runtime [984]
> 17:53:58 Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16304) install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16304?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16304:
-------------------------------
Attachment: (was: consoleText.partialtxt)
> install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16304
> URL: https://issues.jboss.org/browse/JBIDE-16304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Attachments: consoleText.full.txt, consoleText.partial.txt
>
>
> When trying to install from central site, this error happens because Forge 2 requires JDK 7, yet the Eclipse instance is using JDK 6 to run:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2Fjbosstools-directory.xml,eclipseBundleVersion=luna.M3,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1531/consoleText}
> 17:53:58 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.aesh.core [983]
> 17:53:58 Unresolved requirement: osgi.wiring.bundle; visibility:="reexport"; filter:="(&(osgi.wiring.bundle=org.jboss.tools.aesh.runtime)(bundle-version>=0.39.0))"
> 17:53:58 -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.aesh.runtime"; bundle-version:Version="0.43.0.Alpha1-v20131211-1657-B454"; singleton:="true"
> 17:53:58 org.jboss.tools.aesh.runtime [984]
> 17:53:58 Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16304) install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16304?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16304:
-------------------------------
Attachment: consoleText.partial.txt
> install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16304
> URL: https://issues.jboss.org/browse/JBIDE-16304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Attachments: consoleText.full.txt, consoleText.partial.txt
>
>
> When trying to install from central site, this error happens because Forge 2 requires JDK 7, yet the Eclipse instance is using JDK 6 to run:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2Fjbosstools-directory.xml,eclipseBundleVersion=luna.M3,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1531/consoleText}
> 17:53:58 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.aesh.core [983]
> 17:53:58 Unresolved requirement: osgi.wiring.bundle; visibility:="reexport"; filter:="(&(osgi.wiring.bundle=org.jboss.tools.aesh.runtime)(bundle-version>=0.39.0))"
> 17:53:58 -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.aesh.runtime"; bundle-version:Version="0.43.0.Alpha1-v20131211-1657-B454"; singleton:="true"
> 17:53:58 org.jboss.tools.aesh.runtime [984]
> 17:53:58 Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16304) install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16304?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16304 at 12/13/13 2:04 PM:
--------------------------------------------------------------
more complete console logs attached:
[^consoleText.full.txt] [^consoleText.partial.txt]
was (Author: nickboldt):
more complete console logs attached:
[^consoleText.full.txt] [^consoleText.partialtxt]
> install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16304
> URL: https://issues.jboss.org/browse/JBIDE-16304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Attachments: consoleText.full.txt, consoleText.partial.txt
>
>
> When trying to install from central site, this error happens because Forge 2 requires JDK 7, yet the Eclipse instance is using JDK 6 to run:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2Fjbosstools-directory.xml,eclipseBundleVersion=luna.M3,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1531/consoleText}
> 17:53:58 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.aesh.core [983]
> 17:53:58 Unresolved requirement: osgi.wiring.bundle; visibility:="reexport"; filter:="(&(osgi.wiring.bundle=org.jboss.tools.aesh.runtime)(bundle-version>=0.39.0))"
> 17:53:58 -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.aesh.runtime"; bundle-version:Version="0.43.0.Alpha1-v20131211-1657-B454"; singleton:="true"
> 17:53:58 org.jboss.tools.aesh.runtime [984]
> 17:53:58 Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16304) install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16304:
----------------------------------
Summary: install grinder runs with JDK6 but needs JDK7 for Forge 2 installation / run
Key: JBIDE-16304
URL: https://issues.jboss.org/browse/JBIDE-16304
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.2.0.Alpha1
Reporter: Nick Boldt
Attachments: consoleText.full.txt, consoleText.partial.txt
When trying to install from central site, this error happens because Forge 2 requires JDK 7, yet the Eclipse instance is using JDK 6 to run:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Fmaster%2Fjbosstools-directory.xml,eclipseBundleVersion=luna.M3,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/1531/consoleText}
17:53:58 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.aesh.core [983]
17:53:58 Unresolved requirement: osgi.wiring.bundle; visibility:="reexport"; filter:="(&(osgi.wiring.bundle=org.jboss.tools.aesh.runtime)(bundle-version>=0.39.0))"
17:53:58 -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.aesh.runtime"; bundle-version:Version="0.43.0.Alpha1-v20131211-1657-B454"; singleton:="true"
17:53:58 org.jboss.tools.aesh.runtime [984]
17:53:58 Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-440) BYOE does not appear to be an acronym that's actually defined in the install guide
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-440?page=com.atlassian.jira.plug... ]
Nick Boldt edited comment on TOOLSDOC-440 at 12/13/13 1:26 PM:
---------------------------------------------------------------
I think I'd just redefine the concept in section 3.3. Something like:
{quote}
3.3. Install JBoss Developer Studio *Into Your Own Eclipse*
You can obtain JBoss Developer Studio from *the* Eclipse Marketplace or use the .zip file available from the Red Hat JBoss Developer Studio Update website. The latter option provisions for online and offline installation modes; Eclipse can install directly from the online .zip file or you can download the .zip file first and then Eclipse can install from this local copy.
Select one of the procedures below, which will guide you through the JBoss Developer Studio *"Bring Your Own Eclipse" (BYOE)* installation process.
{quote}
was (Author: nickboldt):
I think I'd just redefine the concept in section 3.3. Something like:
{quote}
3.3. Install JBoss Developer Studio *Into Your Own Eclipse*
You can obtain JBoss Developer Studio from *the* Eclipse Marketplace or use the .zip file available from the Red Hat JBoss Developer Studio Update website. The latter option provisions for online and offline installation modes; Eclipse can install directly from the online .zip file or you can download the .zip file first and then Eclipse can install from this local copy.
Select one of the procedures below, which will guide you through the JBoss Developer Studio *"Bring Your Own Eclipse" (BYOE)* installation process.
{quote}
> BYOE does not appear to be an acronym that's actually defined in the install guide
> ----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-440
> URL: https://issues.jboss.org/browse/TOOLSDOC-440
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Installation Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
>
> Feedback from [~nickboldt]:
> {quote}
> It seems we don't clearly define the term BYOE.
> Only place I can see where it's called out is in section 1.2:
> "For distinction, this latter JBoss Developer Studio installation is
> called JBoss Developer Studio BYOE (Bring Your Own Eclipse). "
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> Then later there are two references within the BYOE install section:
> "JBoss Developer Studio 7.x - Bring Your Own Eclipse"
> https://access.redhat.com/site/documentation//en-US/Red_Hat_JBoss_Develop...
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-440) BYOE does not appear to be an acronym that's actually defined in the install guide
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-440?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-440:
-------------------------------------
I think I'd just redefine the concept in section 3.3. Something like:
{quote}
3.3. Install JBoss Developer Studio *Into Your Own Eclipse*
You can obtain JBoss Developer Studio from *the* Eclipse Marketplace or use the .zip file available from the Red Hat JBoss Developer Studio Update website. The latter option provisions for online and offline installation modes; Eclipse can install directly from the online .zip file or you can download the .zip file first and then Eclipse can install from this local copy.
Select one of the procedures below, which will guide you through the JBoss Developer Studio *"Bring Your Own Eclipse" (BYOE)* installation process.
{quote}
> BYOE does not appear to be an acronym that's actually defined in the install guide
> ----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-440
> URL: https://issues.jboss.org/browse/TOOLSDOC-440
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Installation Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
>
> Feedback from [~nickboldt]:
> {quote}
> It seems we don't clearly define the term BYOE.
> Only place I can see where it's called out is in section 1.2:
> "For distinction, this latter JBoss Developer Studio installation is
> called JBoss Developer Studio BYOE (Bring Your Own Eclipse). "
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> Then later there are two references within the BYOE install section:
> "JBoss Developer Studio 7.x - Bring Your Own Eclipse"
> https://access.redhat.com/site/documentation//en-US/Red_Hat_JBoss_Develop...
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16303) Maven Pop-up should enable/expose mvn clean package
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16303?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16303:
-----------------------------------
Component/s: maven
> Maven Pop-up should enable/expose mvn clean package
> ---------------------------------------------------
>
> Key: JBIDE-16303
> URL: https://issues.jboss.org/browse/JBIDE-16303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: Jim Tyrrell
> Attachments: Screen shot 2013-12-13 at 6.16.55 AM.png
>
>
> When building and importing projects, every so often something goes sideways in the import/building of a project. I have to jump to the mvn command line and often I need to run mvn clean package to execute a "build" that re-sets whatever went sideways. Generally if the network goes away the above command will enable it to work.
> If you know of other commands that should be exposed please let me know.
> I wonder if Update Project should execute this command? I don't know enough about maven to know if this makes sense.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov commented on JBIDE-2720:
-----------------------------------------------
[~dagz213], I will apply this patch next week, was too busy with other tasks.
[~carsten.pfeiffer] Do we need to rebuild xulrunner to apply this patch?
> 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: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months