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: ----------------------------- Comment: was deleted (was: I have tried the following, with no success. 1. adding a com.jboss.jbds.product/p2.inf file: {code} instructions.uninstall= \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:-product); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:com.jboss.jbds.product.product); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:-showsplash); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:platform${#58}/base/plugins/com.jboss.jbds.product); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:-application); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:org.eclipse.ui.ide.workbench); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:-showsplash); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:org.eclipse.platform); {code} Will continue to try other options, eg., using site/com.jboss.jbds.p2.inf instead or in addition.) > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12274: ------------------------------------------------- Matthias Clasen <mclasen(a)redhat.com> made a comment on [bug 966571|https://bugzilla.redhat.com/show_bug.cgi?id=966571] For the desktop engineering side, we are fine with this update. To judge the qa impact, here are the things in RHEL6 that use webkitgtk: devhelp, gimp-help-browser, libproxy-webkit, pywebkitgtk > BrowserSim borks on jquery mobile (RHEL 6.1) > -------------------------------------------- > > Key: JBIDE-12274 > URL: https://issues.jboss.org/browse/JBIDE-12274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: RHEL 6.1 > JBoss Developer Studio 5.0.0.CR1 > Reporter: Gabriel De Repentigny > Assignee: Yahor Radtsevich > Labels: upstream > Fix For: 4.0.0.Alpha1, 4.1.x > > Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png > > > I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial. > The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling). > {code:xml} > <!DOCTYPE html> > <html> > <head> > <title>jQuery Mobile Template</title> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <meta name="viewport" content="width=device-width, initial-scale=1" /> > <link rel="stylesheet" > href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" /> > <script type="text/javascript" > src="http://code.jquery.com/jquery-1.7.1.min.js"></script> > <script type="text/javascript" > src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script> > <script type="text/javascript"> > $(document).on("pageinit", "#page1", function(event){ > alert("Ready To Go"); > }); > $.getJSON("rest/events", function(events) { > // console.log("returned are " + results); > var listOfEvents = $("#listOfItems"); > listOfEvents.empty(); > $.each(events, function(index, event) { > // console.log(event.name); > listOfEvents.append("<li><a href=’#’>" + event.name + "</a>"); > }); > listOfEvents.listview("refresh"); > }); > </script> > </head> > <body> > <div data-role="page" id="page1"> > <div data-role="header"> > <h1>jQuery Mobile</h1> > </div> > <div data-role="content"> > <ul id="listOfItems" data-role="listview" data-inset="true" > data-filter="true"> > <li><a href="">One</a></li> > <li><a href="">Two</a></li> > <li><a href="">Three</a></li> > </ul> > </div> > <div data-role="footer"> > <h4>www.jboss.org/developer</h4> > </div> > </div> > </body> > </html> > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-359) Delete old guides from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-359?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-359: ------------------------------------- Tweaking the job to source from 4.0.x branch is fine; in fact we can have TWO jobs... one for <=4.0.x [1] one for >=4.1 [2]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_40/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_master/ and/or https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_41/ Since each build would target a different folder on docs.jboss.org, I don't see a problem w/ them building in parallel from different source branches. I propose this mapping: * build from _master (master branch) ** --> http://docs.jboss.org/tools/nightly/trunk/ * build from _41 (latest stable branch, eg., jbosstools-4.1.0.Beta2x; eventually the jbosstools-4.1.x branch) ** --> http://docs.jboss.org/tools/nightly/4.1.kepler/ * build from _40 (jbosstools-4.0.x branch) ** --> http://docs.jboss.org/tools/4.0.1.Final/ (later, change job to target 4.0.2.Final, etc.) As to the question of need for a _master AND a _41 job, that depends on whether you need a split between "stabilizing doc in the Beta branch" and "raw doc in the master branch". If you do, you'll be following the same pattern that the developers use, and would branch presumably at the same time that they do for code freezes. If not, then you won't need a _41 branch until master becomes the branch for JBT 4.2 (and therefore you need a job to build from the 4.1.x branch, to allow for doc changes after 4.1.0.Final is released). > Delete old guides from git > -------------------------- > > Key: TOOLSDOC-359 > URL: https://issues.jboss.org/browse/TOOLSDOC-359 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > 4.1.x onwards docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/docs > 4.0.x & prior docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/guides > The older guides are also located in 4.0.x branch. > 1. I propose deleting the guides dir in master branch to avoid future confusion about which docs are current. > 2. Removing the guides dir from master will break https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs-nigh.... > * In short term can probably solve this easily by redirecting the jenkins job to the 4.0x branch. > * In long term, need to revise jenkins job to only build the JBT user guide https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J.... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14787. ------------------------------ Resolution: Done Closed. > Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14792) Marketplace install button tooltips all say Juno, not the actual required Eclipse version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14792?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14792: ------------------------------- Fix Version/s: LATER (was: 4.1.0.Beta1) > Marketplace install button tooltips all say Juno, not the actual required Eclipse version > ------------------------------------------------------------------------------------------ > > Key: JBIDE-14792 > URL: https://issues.jboss.org/browse/JBIDE-14792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: LATER > > > Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14792) Marketplace install button tooltips all say Juno, not the actual required Eclipse version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14792?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14792: ------------------------------- Description: Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196 (was: Install button description is wrong also for JBDS7) > Marketplace install button tooltips all say Juno, not the actual required Eclipse version > ------------------------------------------------------------------------------------------ > > Key: JBIDE-14792 > URL: https://issues.jboss.org/browse/JBIDE-14792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Comment: was deleted (was: Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196) > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 - see JBIDE-14792 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Summary: Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno (was: Marketplace description says that 4.1.0 is targeting Juno) > Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 - see JBIDE-14792 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Description: Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno (was: Install button description is wrong also for JBDS7 - see JBIDE-14792) > Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Marketplace description in http://marketplace.eclipse.org/content/jboss-tools-kepler has typo; says targets Juno -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Description: Install button description is wrong also for JBDS7 - see JBIDE-14792 (was: Install button description is wrong also for JBDS7) > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 - see JBIDE-14792 -- 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, 10 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 June 2013