May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14706) openshift-java-client: add support for initial git url when creating a new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14706?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14706: ------------------------------------------ In the integration tests I currently install the spring-eap6-quickstart which failes here and there when jboss fails to start up. Talking about it with bill deCoste my impression is that I should deploy a simplistic demo-app which I then try to access instead. > openshift-java-client: add support for initial git url when creating a new application > -------------------------------------------------------------------------------------- > > Key: JBIDE-14706 > URL: https://issues.jboss.org/browse/JBIDE-14706 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > > In order to fullfill JBIDE-14588 we need to add the ability to the openshift-java-client to tell it create a new application with a given initial git url that the initial application code and configuration will get cloned from. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14712) LICENCE should be LICENSE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14712?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14712. ------------------------------ Assignee: Nick Boldt Resolution: Rejected No, it shouldn't. Both spellings are valid: http://en.wikipedia.org/wiki/License http://www.future-perfect.co.uk/grammartips/grammar-tip-license-licence.asp These files were copied in from the original providers VERBATIM, using their spelling convention, and I'm not about to tell them they have to adhere to American English conventions, since I myself do not. I may be neighbo*u*r to the US, but the rest of the former British colonies are all horses of a different colo*u*r. And we have licences, not licenses. > LICENCE should be LICENSE > ------------------------- > > Key: JBIDE-14712 > URL: https://issues.jboss.org/browse/JBIDE-14712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng, locus > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > LICENCE should be LICENSE see https://github.com/nickboldt/jbosstools-locus/pull/3 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-14544: -------------------------------------- Suggestion from Max: go and find org.jboss.tools.aerogear.hybrid.core-*.jar file, do unzip -d org.jboss.tools.aerogear.hybrid.core-<exactsameasonthejar> org.jboss.tools.aerogear.hybrid.core-*.jar then remove the .jar, start eclipse with -clean and try this usecase again > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Priority: Blocker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12815: ------------------------------------ Turns out as usual I documented why I needed these IN THE CODE. {code:title=https://github.com/nickboldt/jbosstools-locus/blob/master/pom.xml#L265}  <repository> <id>JBoss Tools Target Platform Site</id> <url>http://download.jboss.org/jbosstools/updates/juno/</url> <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>true</enabled> </releases> </repository>  <repository> <id>Orbit Update Site</id> <url>http://download.jboss.org/jbosstools/updates/requirements/orbit/S20130427...</url> <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>true</enabled> </releases> </repository> {code} I suppose we could include some of these deps as m2 deps instead of p2 deps if we enable pomDependencies=consider. {code:title=http://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts#What_happens_under_the_hood} <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>target-platform-configuration</artifactId> <version>${tycho-version}</version> <configuration> <pomDependencies>consider</pomDependencies> </configuration> </plugin>{code} > Create a JBoss Tools Orbit > -------------------------- > > Key: JBIDE-12815 > URL: https://issues.jboss.org/browse/JBIDE-12815 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, locus > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > Attachments: pom.xml > > > Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository. > In a first time, we could simply create some OSGi "wrappers" around those jars. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-344) NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-344?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-344: ------------------------------------- Maven 3.0.4 is ALMOST the latest; 3.0.5 is the current release: http://maven.apache.org/docs/3.0.5/release-notes.html Users can choose to download this newer one and point Eclipse or JBDS at that insted. But yes, as Burr points out... * JBDS 7 inlcudes m2e 1.4, which embeds Maven 3.0.4. * JBDS 6 includes m2e 1.3, which embeds Maven 3.0.4. * JBDS 5 includes m2e 1.0, which embeds Maven 3.0.2. > NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > --------------------------------------------------------------------------------------- > > Key: TOOLSDOC-344 > URL: https://issues.jboss.org/browse/TOOLSDOC-344 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0 > > > Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > I am thinking of this particularly in relation to the Getting Started Guide [http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...] and the Ticket Monster introduction [http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/]. > As part of the assumptions, the Getting Started Guide states: '... a number of assumptions are made about your system ... Maven is installed' -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14126: ------------------------------------- HTML5 in system browser + local Weinre Server works. HTML5 in JBDS internal browser + local Weinre Server doesn't works. I think I did click on Target link and it didn't work. I have added screenshot just to show that Target is connected. I will check it with JBDS 7.0.0.Beta1b build. > Weinre Inspector is showing no data within Elements tab > ------------------------------------------------------- > > Key: JBIDE-14126 > URL: https://issues.jboss.org/browse/JBIDE-14126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta2 > > Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png > > > 1. Open www.amazon.com page in Browsersim > 2. Run Weinre Inspector via Browsersim context menu "Weinre" > ERROR: No elements shown on Elements tab > Client is connected: > !phonegapamazon.png! > 3. Run Weinre server locally. > 4. Set Browsersim to use local Weinre server > 5. Run Weinre Inspector as in step 2. > ERROR: No elements shown on Elements tab > Client is connected: > !localamazon.png! > 6. Create HTML5 project from JBoss Central > 7. Insert script tag allowing debugging via local Weinre server to index.html > 8. Run HTML5 project on Server > 9. Open HTML5 index.html in system borwser > ASSERT: Weinre debugging works > !localhtml5.png! > ERROR: Weinre debugging is not working from JBDS internal browser > 10. Open index.html of HTML5 project in Browsersim > 11. Open Weinre debug link in Browser > ERROR: No elements shown on Elements tab > Client is connected: > !localbrowsersimhtml5.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-14126: ------------------------------------------------ 1. amazon.com with default server: one of possible reasons is that weinre works not very fast, it need some time to build DOM tree. 2. amazon.com via local server: reproduces for me. Page reload helps me to to make everything work fine. 3. HTML5 in system browser: Cannot understand when weinre works and when not. Vlado. please, update description. 4. HTML5 in BrowserSim: due to your screenshot I understand that you does not click on target. Select it and everything will be fine. Actyally we can do nothinng with weinre unstable working. So I think this ticked could be rosolved with "Wont fix" resolution. > Weinre Inspector is showing no data within Elements tab > ------------------------------------------------------- > > Key: JBIDE-14126 > URL: https://issues.jboss.org/browse/JBIDE-14126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta2 > > Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png > > > 1. Open www.amazon.com page in Browsersim > 2. Run Weinre Inspector via Browsersim context menu "Weinre" > ERROR: No elements shown on Elements tab > Client is connected: > !phonegapamazon.png! > 3. Run Weinre server locally. > 4. Set Browsersim to use local Weinre server > 5. Run Weinre Inspector as in step 2. > ERROR: No elements shown on Elements tab > Client is connected: > !localamazon.png! > 6. Create HTML5 project from JBoss Central > 7. Insert script tag allowing debugging via local Weinre server to index.html > 8. Run HTML5 project on Server > 9. Open HTML5 index.html in system borwser > ASSERT: Weinre debugging works > !localhtml5.png! > ERROR: Weinre debugging is not working from JBDS internal browser > 10. Open index.html of HTML5 project in Browsersim > 11. Open Weinre debug link in Browser > ERROR: No elements shown on Elements tab > Client is connected: > !localbrowsersimhtml5.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6368) Should nest categories in update site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin... ] Mickael Istria updated JBIDE-6368: ---------------------------------- Fix Version/s: 4.1.0.Beta2 (was: LATER) Priority: Minor (was: Blocker) Nested categories are now possible with Tycho 0.18 (without depending on a recent p2 version for consumer). How should we categorize our features then? > Should nest categories in update site > ------------------------------------- > > Key: JBIDE-6368 > URL: https://issues.jboss.org/browse/JBIDE-6368 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Affects Versions: 3.2.x > Reporter: John Verhaeg > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.1.0.Beta2 > > Attachments: nested-categories-p2-update-site.png > > > As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our update site. So, instead of having lots of sibling categories for the various tools in JBT alongside a sibling "All JBoss Tools" category, the latter should be promoted to a parent category for the others (dropping the "All" prefix). For example: > - JBoss Tools > - SOA Development > - JBoss ESB Tools > - Drools Core > ... > - Data Services > - Hibernate > - ModeShape > - Smooks > - Teiid Data Tools Connectivity > - Teiid Designer Design-Time > - Teiid Designer Runtime > BTW, IMO having features in multiple categories blows. I don't like seeing this with other Eclipse projects either. Just my 2 cents. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14619: --------------------------------------- This is a WTP bug. To reproduce it, it is enough to activate some other workbench part and click some control at the left side of the server editor. See http://screencast.com/t/6Q769T5a I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=409584 > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Snjezana Peco > Fix For: LATER > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14619: ---------------------------------- Component/s: upstream > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Snjezana Peco > Fix For: LATER > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- 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, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2013