May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14376) JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing

by Sebastien Blanc (JIRA)

Sebastien Blanc created JBIDE-14376: --------------------------------------- Summary: JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing Key: JBIDE-14376 URL: https://issues.jboss.org/browse/JBIDE-14376 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Environment: Fedora 17 Reporter: Sebastien Blanc JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing. See logs : https://gist.github.com/sebastienblanc/5501833 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14377) "Run Android Emulator" on Jboss Aerogear tools only works if eclipse is launched from command line

by Sebastien Blanc (JIRA)

Sebastien Blanc created JBIDE-14377: --------------------------------------- Summary: "Run Android Emulator" on Jboss Aerogear tools only works if eclipse is launched from command line Key: JBIDE-14377 URL: https://issues.jboss.org/browse/JBIDE-14377 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Environment: Fedora 17 Reporter: Sebastien Blanc "Run Android Emulator" on Jboss Aerogear tools only works if eclipse is launched from command line -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12345) Creating a new jBPM3 project does not open the jBPM perspective

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-12345: ----------------------------------- AFAIK this is supposed to be picked up automatically by Jenkins. I'll check it tomorrow. > Creating a new jBPM3 project does not open the jBPM perspective > --------------------------------------------------------------- > > Key: JBIDE-12345 > URL: https://issues.jboss.org/browse/JBIDE-12345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-2720: --------------------------------------- [~yradtsevich] Have you tried on a very recent version integration-build Eclipse? (> April 30th as the error could be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=406912#c2 ) > 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: Yahor Radtsevich > Fix For: 4.0.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 jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2624 at 5/2/13 12:13 PM: ----------------------------------------------------------- Crap. Missed [~maxandersen]'s comments. The Usage feature is simply a container for the Usage plugin, so it can be installed w/o causing problems. As to o.j.t.common.mylyn, should it also be moved from Core in JBT? was (Author: nickboldt): Crap. Missed [~maxandersen]'s comments. The Usage feature is simply a container for the Usage plugin, so it can be installed w/o causing problems. As to Mylyn, should it also be moved from Core in JBT? > Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category > ----------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2624 > URL: https://issues.jboss.org/browse/JBDS-2624 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Trivial > Attachments: InstallContentAfterRunningUniversalInstaller.png > > > After installation Eclipse Install dialog looks like: > !InstallContentAfterRunningUniversalInstaller.png! > These two features should not be visible after installation: > 1. Usage Feature - should be included into JBDS product feature > 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2624: ---------------------------------- Crap. Missed [~maxandersen]'s comments. The Usage feature is simply a container for the Usage plugin, so it can be installed w/o causing problems. As to Mylyn, should it also be moved from Core in JBT? > Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category > ----------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2624 > URL: https://issues.jboss.org/browse/JBDS-2624 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Trivial > Attachments: InstallContentAfterRunningUniversalInstaller.png > > > After installation Eclipse Install dialog looks like: > !InstallContentAfterRunningUniversalInstaller.png! > These two features should not be visible after installation: > 1. Usage Feature - should be included into JBDS product feature > 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2624. ------------------------------ Resolution: Done Commmitted in trunk; respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_tr... > Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category > ----------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2624 > URL: https://issues.jboss.org/browse/JBDS-2624 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Priority: Trivial > Attachments: InstallContentAfterRunningUniversalInstaller.png > > > After installation Eclipse Install dialog looks like: > !InstallContentAfterRunningUniversalInstaller.png! > These two features should not be visible after installation: > 1. Usage Feature - should be included into JBDS product feature > 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2624: -------------------------------- Assignee: Nick Boldt > Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category > ----------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2624 > URL: https://issues.jboss.org/browse/JBDS-2624 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Trivial > Attachments: InstallContentAfterRunningUniversalInstaller.png > > > After installation Eclipse Install dialog looks like: > !InstallContentAfterRunningUniversalInstaller.png! > These two features should not be visible after installation: > 1. Usage Feature - should be included into JBDS product feature > 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-2720: ------------------------------------ Attachment: vpe-win-jdk64.png c-runtime-error.png Carsten you are *awesome*! Just tried to run VPE with the latest SWT on Windows with JVM 64-bit. It works! !vpe-win-jdk64.png|thumbnail! However, an error message appears before the Browser widget is loaded: {code:none} Runtime Error! Program ...\javaw.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. {code} !c-runtime-error.png|thumbnail! > 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: Yahor Radtsevich > Fix For: 4.0.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 jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2543) JBDS70_0411: [Commit] (Dev) (P1) Offline - Examples/Archetypes - Cache Script

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2543?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2543: -------------------------------------- If we go for an implementation from inside Eclipse (a "Pre-load dependencies to work offline" button), we can also think about making this work an Eclipse application as well, and make this initialization an optional installation step. It would make installation longer, but people don't care when an installation is long. > JBDS70_0411: [Commit] (Dev) (P1) Offline - Examples/Archetypes - Cache Script > ----------------------------------------------------------------------------- > > Key: JBDS-2543 > URL: https://issues.jboss.org/browse/JBDS-2543 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Fred Bricon > > Central archetype/project examples > Level 0: caching projectexamples.xml, stacks.yml > Level 1: provide a default version > Provide a script that pre-caches everything (e.g. Maven dependencies) for an instructor/demo'er in the field (online once, then offline), the instructor can then provide his ZIPPED .m2/repository to his students via flash drive - all students offline -- 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, 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 May 2013