May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13407: ------------------------------- Attachment: dialog_do-you-trust-these-certs.png > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > Attachments: dialog_do-you-trust-these-certs.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss 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-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13407: ------------------------------- Attachment: no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss 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-2628) Cannot complete the install because of a conflicting dependency.

by Ashish Chandra (JIRA)

Ashish Chandra created JBDS-2628: ------------------------------------ Summary: Cannot complete the install because of a conflicting dependency. Key: JBDS-2628 URL: https://issues.jboss.org/browse/JBDS-2628 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Environment: RHEL 6.4, Drools 6.0.0.Beta2 Reporter: Ashish Chandra Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Runtime Drools Detector 6.0.0.Beta2 (org.jboss.tools.runtime.drools.detector.feature.feature.group 6.0.0.Beta2) Software currently installed: Eclipse Platform 3.6.0.M20100909-0800 (org.eclipse.platform.ide 3.6.0.M20100909-0800) Only one of the following can be installed at once: Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012) Debug Core 3.6.0.v20100519 (org.eclipse.debug.core 3.6.0.v20100519) Cannot satisfy dependency: From: Eclipse Platform 3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW (org.eclipse.platform.feature.group 3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW) To: org.eclipse.debug.core [3.6.0.v20100519] Cannot satisfy dependency: From: Eclipse Platform 3.6.0.M20100909-0800 (org.eclipse.platform.ide 3.6.0.M20100909-0800) To: org.eclipse.platform.feature.group [3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW] Cannot satisfy dependency: From: JBoss Tools Common Core 3.4.0.Final-v20130327-0606-B69 (org.jboss.tools.common.core.feature.feature.group 3.4.0.Final-v20130327-0606-B69) To: org.jboss.tools.common.model [3.4.0.Final-v20130327-0606-B69] Cannot satisfy dependency: From: JBoss Tools Model 3.4.0.Final-v20130327-0606-B69 (org.jboss.tools.common.model 3.4.0.Final-v20130327-0606-B69) To: bundle org.eclipse.debug.core 3.7.0 Cannot satisfy dependency: From: JBoss Runtime Drools Detector 6.0.0.Beta2 (org.jboss.tools.runtime.drools.detector.feature.feature.group 6.0.0.Beta2) To: org.jboss.tools.common.core.feature.feature.group 0.0.0 -- 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-13890) OpenOn for <div data-role="page">: "Open With BrowserSim"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13890?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13890: ----------------------------------- Description: This feature may be useful for multi-page documents. 1. Open any jQueryMobile html page with HTML Editor. 2. Ctrl+Click on <div data-role="page"> 3. There should be "Open With BrowserSim" option available which opens this page with BrowserSim. http://www.screenr.com/B697 was: This feature may be useful for multi-page documents. 1. Open any jQueryMobile html page with HTML Editor. 2. Ctrl+Click on <div data-role="page"> 3. There should be "Open With BrowserSim" option available which opens this page with BrowserSim. > OpenOn for <div data-role="page">: "Open With BrowserSim" > --------------------------------------------------------- > > Key: JBIDE-13890 > URL: https://issues.jboss.org/browse/JBIDE-13890 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > This feature may be useful for multi-page documents. > 1. Open any jQueryMobile html page with HTML Editor. > 2. Ctrl+Click on <div data-role="page"> > 3. There should be "Open With BrowserSim" option available which opens this page with BrowserSim. > http://www.screenr.com/B697 -- 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-14323) Maven Update Project should be hotkey bindable

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-14323: -------------------------------------------- I think I have to go with ALT-F5 since CTRL-ALT-M is frequently used to minimize windows on some OS's. > Maven Update Project should be hotkey bindable > ---------------------------------------------- > > Key: JBIDE-14323 > URL: https://issues.jboss.org/browse/JBIDE-14323 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, upstream > Affects Versions: 4.1.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;) -- 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-14378) org.jboss.tools.jst.web.ui tests failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14378?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14378: ----------------------------------- Summary: org.jboss.tools.jst.web.ui tests failure (was: org.jboss.tools.jjst tests failure) > org.jboss.tools.jst.web.ui tests failure > ---------------------------------------- > > Key: JBIDE-14378 > URL: https://issues.jboss.org/browse/JBIDE-14378 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta1 > > > {code} > Failed tests: testInsertJSCSS(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > testInsertIntoEmptyFile(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > testAddJSCSSCheckboxSetTrue(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): expected:<true> but was:<false> > testInsertIntoNotClosedTags(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > testInsertIntoBody(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > testInsertIntoNormal(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > testInsertAround(org.jboss.tools.jst.web.ui.test.InsertJSCSSPaletteEntryTest): Unexpected line expected:<...uery.com/mobile/1.3.[0/jquery.mobile-1.3.0].min.css" />> but was:<...uery.com/mobile/1.3.[1/jquery.mobile-1.3.1].min.css" />> > {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, 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 commented on JBIDE-2720: ----------------------------------------- I created two branches in the vpe and xulrunner components with support of 64-bit XULRunner on Windows: https://github.com/yradtsevich/jbosstools-vpe/tree/xulrunner-win64 https://github.com/yradtsevich/jbosstools-xulrunner/tree/xulrunner-win64 The R6034 error is not always reproducible. On [~kmarmaliykov]'s desktop everything is working fine. > 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] (JBIDE-14384) Quick Fix for missing beans.xml file problem which creates the missing file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14384?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14384: ----------------------------------- Labels: new_and_noteworthy (was: ) > Quick Fix for missing beans.xml file problem which creates the missing file > --------------------------------------------------------------------------- > > Key: JBIDE-14384 > URL: https://issues.jboss.org/browse/JBIDE-14384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.1.x > > -- 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-13996) CDI project - missing beans.xml warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13996?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-13996 at 5/3/13 3:43 PM: ---------------------------------------------------------------- Yes, I know. But we don't support CDI 1.1 yet anyway. Missing beans.xml will be marked as a warning (not error) by default and you can disable this validation via QiuckFix. was (Author: akazakov): Yes, I know. But we doesn't support CDI 1.1 yet anyway. Missing beans.xml will be marked as a warning (not error) by default and you can disable this validation via QiuckFix. > CDI project - missing beans.xml warning > --------------------------------------- > > Key: JBIDE-13996 > URL: https://issues.jboss.org/browse/JBIDE-13996 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI > Reporter: Marián Labuda > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > I've got idea about creating feature for control if beans.xml is present or not. Bcs. all what CDI project makes CDI project is just existence of the file beans.xml. After deletion of this file, there is no warning, but the CDI project is no more CDI project. It should have some check, whether beans.xml file exists or not (i don't know, how the events in JBDS are processed) after any file deletion in CDI project folder. -- 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-14384) Quick Fix for missing beans.xml file problem which creates the missing file

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-14384: -------------------------------------- Summary: Quick Fix for missing beans.xml file problem which creates the missing file Key: JBIDE-14384 URL: https://issues.jboss.org/browse/JBIDE-14384 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.1.x -- 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