June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14805) import org.jboss.tools.livereload result in no java source being imported

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14805?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14805: ---------------------------------- Issue Type: Bug (was: Feature Request) Assignee: Xavier Coulon Affects Version/s: 4.1.0.Beta1 > import org.jboss.tools.livereload result in no java source being imported > -------------------------------------------------------------------------- > > Key: JBIDE-14805 > URL: https://issues.jboss.org/browse/JBIDE-14805 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > find org.jboss.tools.livereload in Plug-Ins view > right click the plugin and Import as source > assert project is imported with full source. > currently: src folder is missing. -- 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-14811) Display non-default scope in dependency identification page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14811?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14811: -------------------------------- Attachment: display-dependency-scope.png Fixde with commit https://github.com/jbosstools/jbosstools-central/commit/f99c3a3857f50a1fe... !display-dependency-scope.png! > Display non-default scope in dependency identification page > ----------------------------------------------------------- > > Key: JBIDE-14811 > URL: https://issues.jboss.org/browse/JBIDE-14811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.0.Beta2 > > Attachments: display-dependency-scope.png > > > When converting a project to maven, in the dependency identification page, if the user double-clicks on a dependency to change the scope, there are no visual indications of the change. > If a non default scope (anything other than compile) is used, it should be displayed next to the dependency id -- 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-14811) Display non-default scope in dependency identification page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14811?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-14811. --------------------------------- Resolution: Done > Display non-default scope in dependency identification page > ----------------------------------------------------------- > > Key: JBIDE-14811 > URL: https://issues.jboss.org/browse/JBIDE-14811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.0.Beta2 > > Attachments: display-dependency-scope.png > > > When converting a project to maven, in the dependency identification page, if the user double-clicks on a dependency to change the scope, there are no visual indications of the change. > If a non default scope (anything other than compile) is used, it should be displayed next to the dependency id -- 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-14811) Display non-default scope in dependency identification page

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-14811: ----------------------------------- Summary: Display non-default scope in dependency identification page Key: JBIDE-14811 URL: https://issues.jboss.org/browse/JBIDE-14811 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.1.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Priority: Minor Fix For: 4.1.0.Beta2 When converting a project to maven, in the dependency identification page, if the user double-clicks on a dependency to change the scope, there are no visual indications of the change. If a non default scope (anything other than compile) is used, it should be displayed next to the dependency id -- 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-14414) ECFTransport fails on many platform urls

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14414?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14414. --------------------------------- Resolution: Done pushed to b2 as part of foundation > ECFTransport fails on many platform urls > ---------------------------------------- > > Key: JBIDE-14414 > URL: https://issues.jboss.org/browse/JBIDE-14414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > While making some new test cases, I discovered that the class fails badly (I experienced a deadlock I mentioned in email when using a bundleentry url) and did not have any support for urls that the class LOOKS like it supports. > Support needs to be enhanced for this. > I'm making tests in the new potential "core", and I do not wish to make temporary tests in 'common' before we move the class, so for now I will only be committing this to my 'creation of core' topic branch. -- 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-14405) WaitJob inside ECFTransport is not safe and is impossible to be interrupted

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14405?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14405. --------------------------------- Resolution: Done our fix pushed to b2 > WaitJob inside ECFTransport is not safe and is impossible to be interrupted > --------------------------------------------------------------------------- > > Key: JBIDE-14405 > URL: https://issues.jboss.org/browse/JBIDE-14405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > The WaitJob in ECFTransport is not safe and is impossible to be interrupted. This has to do with eclipse's internal implementation of Job.join(), however there are ways to work around it. > The internal implementation of Job.join() has special logic IGNORING interrupts specifically for the case where the job being joined requires Display.syncExec implementations. Since WaitJob does not require any UI or syncExec, we can work around this by carefully implementing our own join-like method. > See also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=293312 -- 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-14810) Rename foundation plugin to foundation.core

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-14810: ----------------------------------- Summary: Rename foundation plugin to foundation.core Key: JBIDE-14810 URL: https://issues.jboss.org/browse/JBIDE-14810 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.1.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.0.Beta2 Foundation should be renamed to foundation.core -- 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-14809) application wizard: cannot create application on OpenShift Enterprise: "Invalid initial git URL"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14809?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14809: ------------------------------------- Attachment: invalid-initial-git-url.png > application wizard: cannot create application on OpenShift Enterprise: "Invalid initial git URL" > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-14809 > URL: https://issues.jboss.org/browse/JBIDE-14809 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: invalid-initial-git-url.png > > -- 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-14809) application wizard: cannot create application on OpenShift Enterprise: "Invalid initial git URL"

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-14809: ---------------------------------------- Summary: application wizard: cannot create application on OpenShift Enterprise: "Invalid initial git URL" Key: JBIDE-14809 URL: https://issues.jboss.org/browse/JBIDE-14809 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Beta2 -- 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: ------------------------------------------------- Jiri Pallich <jpallich(a)redhat.com> made a comment on [bug 966571|https://bugzilla.redhat.com/show_bug.cgi?id=966571] (In reply to Matthias Clasen from comment #4) > For the desktop engineering side, we are fine with this update. Hi Matthias, Could you please grant the devel_ack+ in that case? Thanks, Jiri > 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

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