June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2389: ----------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2389 > URL: https://issues.jboss.org/browse/JBDS-2389 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 6.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > Steps to repro: > Unpack bare Juno JEE. > Install JBDS BYOE feature ("Core Features"). Restart > Install JBDS Branded Product Feature. Restart. > Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken: > {code} > java.lang.RuntimeException: Application "" could not be found in the registry. > {code} > Addtional info: > {quote} > Bare Juno JEE eclipse.ini: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > org.eclipse.epp.package.jee.product > --launcher.defaultAction > openFile > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Dosgi.requiredJavaVersion=1.5 > -Dhelp.lucene.tokenizer=standard > -XX:MaxPermSize=256m > -Xms40m > -Xmx512m > {code} > or, for Eclipse Platform Binary: > {code} > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms40m > -Xmx384m > {code} > After installing JBDS BYOE: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms512m > -Xmx1024m > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > {code} > After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini: > {code} > $➔ cat eclipse/jbdevstudio.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > -Dosgi.instance.area.default=(a)user.home/workspace > {code} > After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > {code} > {quote} > So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines > {code} > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > {code} > and replace them with the following when JBDS is uninstalled: > {code} > -application > org.eclipse.ui.ide.workbench > -showsplash > org.eclipse.platform > {code} > Also need to know what happens if there are two -product directives... can we just > add (and later remove, when uninstalling) our product to the list, or must we replace > any existing -product entries with ours? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13832) MD5 sometimes not correct

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13832?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13832: ------------------------------- Fix Version/s: (was: 4.1.0.Beta1) > MD5 sometimes not correct > ------------------------- > > Key: JBIDE-13832 > URL: https://issues.jboss.org/browse/JBIDE-13832 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.1.0.Beta2 > > > If you look for instance at this repo: http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_... , you'll notice that the .MD5 files contains string that don't match the actual files md5 checksum, which is accurate in the log files (checksum.txt). > This is most likely an issue in the publish script. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14733) JUnit tests for jQuery Mobile Palette wizards code generation + DnD code insertion

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-14733: -------------------------------------- Summary: JUnit tests for jQuery Mobile Palette wizards code generation + DnD code insertion Key: JBIDE-14733 URL: https://issues.jboss.org/browse/JBIDE-14733 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Beta2 Now we have tests that check what text is generated by the wizards. It would be useful to have tests that check what text is inserted into the editor. It's not always the same text. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14694: --------------------------------------------- if you remove https://github.com/jbosstools/jbosstools-central/pull/112 a tons of other things are removed so I assume you just means *part* of this ? And why don't we just keep a list of projects in a shortlived cache and if time it was registered is low enough we assume cheatsheet.xml was part of the open/import ? or is that too uncertain too ? > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-14694: ------------------------------------------- Assignee: Snjezana Peco (was: Max Rydahl Andersen) Okey so let us please get junit tests added for this so we avoid having commits break the actual functionallity. > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14505) CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14505?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-14505: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Beta2) > CordovaSim: BrowserSim's change skin controls should be used instead of Ripple's select device controls (Device API should know which device is selected) > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14505 > URL: https://issues.jboss.org/browse/JBIDE-14505 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.x > > > Ripple original select device controls ('Devices' Tab) was removed in CordovaSim. Need to add analogous > tab with BrowserSim skins. Selected skin will be displayed on this tab, and user will have a possibility of changing BS skins via controls. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14652) CordovaSim: cross-origin requests send default user agent string in headers

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14652?page=com.atlassian.jira.plugi... ] Yahor Radtsevich reassigned JBIDE-14652: ---------------------------------------- Assignee: Ilya Buziuk (was: Yahor Radtsevich) > CordovaSim: cross-origin requests send default user agent string in headers > --------------------------------------------------------------------------- > > Key: JBIDE-14652 > URL: https://issues.jboss.org/browse/JBIDE-14652 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.0.Beta2 > > Attachments: ua-actual-result.png > > > Cross-origin XMLHttpRequest send browser's default User Agent string in the request headers. > *Steps to reproduce:* > Create the following page in a hybrid project and open it with CordovaSim: > {code:xml|title=ua-test.html} > <script> > var client = new XMLHttpRequest(); > client.onreadystatechange = function() { > if(client.readyState == client.DONE) { > if (client.status == 200) { > alert(/<span id="body_lbUserAgent">([^>]*)<\/span>/ig.exec(client.responseText)[1]); > } else { > alert("Error code: " + client.status); > } > } > } > client.open("GET", "http://www.whatsmyuseragent.com/"); > client.send(); > </script> > {code} > *Actual result:* > A desktop User Agent is shown: > !ua-actual-result.png|thumbnail! > *Expected result:* > An iPhone User Agent is shown. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14732) Hide preview should hide preview only

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14732?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14732: ----------------------------------- Fix Version/s: 4.1.x > Hide preview should hide preview only > ------------------------------------- > > Key: JBIDE-14732 > URL: https://issues.jboss.org/browse/JBIDE-14732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Beta1 > Environment: Any > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Labels: usability > Fix For: 4.1.x > > Attachments: dialog-new.gif, dialog.gif > > > Now Hide Preview button forces to close whole right part of wizard. It looks ok, but jumps to much and hides html source too. Looks like this: > !dialog.gif! > Would it be better to have it implemented like this: > !dialog-new.gif! -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14732) Hide preview should hide preview only

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14732?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14732: ---------------------------------------- Actually, Hide Preview means Hide Both parts - Text Source Preview and Visual Preview. Not sure it's better to hide the visual part only. We could add one more button to have two buttons in total: Hide Source Preview and Hide Visual Preview. But I'm not sure that it would be looks good. Maybe we should use something else instead of buttons to show/hide source/visual preview. > Hide preview should hide preview only > ------------------------------------- > > Key: JBIDE-14732 > URL: https://issues.jboss.org/browse/JBIDE-14732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Beta1 > Environment: Any > Reporter: Denis Golovin > Labels: usability > Attachments: dialog-new.gif, dialog.gif > > > Now Hide Preview button forces to close whole right part of wizard. It looks ok, but jumps to much and hides html source too. Looks like this: > !dialog.gif! > Would it be better to have it implemented like this: > !dialog-new.gif! -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-86) JBTIS 4.0.1 Component Content - SOA-P 6 Alpha 2 (Juno)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-86?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-86: --------------------------------- Update SwitchYard and Teiid https://github.com/jbosstools/jbosstools-integration-stack/commit/f0f08e7... > JBTIS 4.0.1 Component Content - SOA-P 6 Alpha 2 (Juno) > ------------------------------------------------------ > > Key: JBTIS-86 > URL: https://issues.jboss.org/browse/JBTIS-86 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.0.1 > Environment: Eclipse Juno > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.0.1 > > > We're not quite done with Juno... > The SOA-P PM team has requested a JBTIS 4.0.1 Juno-based tools release for the SOA-P 6 Alpha 2 near the end of June. As with the JBTIS 4.0.0 SOA-P 6 Alpha, there will not be a JBDSIS associated with this release. The JBDSIS release will be based on the Kepler/SOA-P 6 Beta. This is a good opportunity for those components that went to .Final and just missed the 4.0.0 JBTIS to get in now. > To avoid confusion as we're doing both the Alpha2 and Beta work simultaneously and to make things easier for everyone, I will coordinate the content with a lone master Jira. Note however that if you'd like to test something the JBTIS master is Kepler-based. The JBTIS-4.0.x tag should be used to base any changes. -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2013