January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18766) Test latest Tern available form snaphot update site

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18766?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18766: ----------------------------------- Fix Version/s: (was: 4.2.3.Final) So Tern 0.7.0 looks fine for JBDS 8.1.0/JBT 4.2.3 as soon as we apply JBIDE-18810 Moving this task to JBT 4.3/JBDS 9.0 to make sure we also good to update Tern 0.8.0 in master. > Test latest Tern available form snaphot update site > --------------------------------------------------- > > Key: JBIDE-18766 > URL: https://issues.jboss.org/browse/JBIDE-18766 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Final > Environment: Linux, Windows, Mac > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.3.0.Alpha1 > > > We need to test latest tern in relation with JBIDE-18740 and see what is better: > * fix it in thym > * fix it by including latest tern -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Update to Luna SR2 for synchronization bug

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17895: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.2.3.Final) > Update to Luna SR2 for synchronization bug > ------------------------------------------ > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.Beta1 > > Attachments: jbds_plugins.txt > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18861: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.2.3.Final) > module start action does not delete *.undeployed file > ----------------------------------------------------- > > Key: JBIDE-18861 > URL: https://issues.jboss.org/browse/JBIDE-18861 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > If you start Wildfly with all modules enabled and started. > Now use STOP action on an EAR module. > Now stop Wildfly. > Now start Wildfly (debug or run). > It will start up without the EAR module running, this is correct behavior at this point. > Now use START on EAR module. It fails to start at all. > This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up. > If you perform a "full publish" on the module that appears to cause it to start up as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18862: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.2.3.Final) > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18755) Autocomplete shows white on white using default RHEL7 theme

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18755?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18755: ----------------------------------- Fix Version/s: (was: 4.2.3.Final) Still no target for the upstream issue. Hope it will be fixed in Mars. > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-18755 > URL: https://issues.jboss.org/browse/JBIDE-18755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Karel Piwko > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18810) 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18810?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18810: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.2.3.Final) > 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18810 > URL: https://issues.jboss.org/browse/JBIDE-18810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.1.CR1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > 'Angular' plugin won't be loaded by default when Tern.java/AngularJS-eclipse will be moved to 0.7.x stream. > The 'angular' plug-in must be contributed as a default module by tern's nature adapter extension point explicitly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18711: ----------------------------------- Fix Version/s: 4.2.3.Beta1 (was: 4.2.3.Final) > Cordova plugin addition and removal fails when config.xml is in a linked folder > ------------------------------------------------------------------------------- > > Key: JBIDE-18711 > URL: https://issues.jboss.org/browse/JBIDE-18711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace). > This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications. > To verify > 1. create a new project > 2. copy www folder to an alternate location > 3. remove www folder > 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location) > 5. add cordova plugins to the project. [Check they are added] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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: ------------------------------------------------- errata-xmlrpc <errata-xmlrpc(a)redhat.com> changed the Status of [bug 1033151|https://partner-bugzilla.redhat.com/show_bug.cgi?id=1033151] from VERIFIED to RELEASE_PENDING > 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: Konstantin Marmalyukov > Labels: upstream > Fix For: 4.3.0.Alpha1 > > 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 was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19114) Upversion plugins + features for JBT 4.2.3 / JBDS 8.1

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19114: ---------------------------------- Summary: Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 Key: JBIDE-19114 URL: https://issues.jboss.org/browse/JBIDE-19114 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.3.Beta1 Reporter: Nick Boldt Assignee: Rob Stryker Priority: Blocker Fix For: 4.2.3.Beta1 There are changes in jbosstools-server since 4.2.2.Final was released but the versions of plugins/features have not incremented. https://github.com/jbosstools/jbosstools-server/commits/jbosstools-4.2.x So, please upversion all your plugins & features, or at the very least, org.jboss.ide.eclipse.as.jmx.integration, so that it's at least up to version 3.0.2. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19056: ------------------------------------ Might be worth running this against jbosstools-server and jbosstools-forge in the 4.2.x branch too. Server should fail until JBIDE-19114 is fixed; forge should pass. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015