October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15784) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15784?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15784. ------------------------------- > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15784 > URL: https://issues.jboss.org/browse/JBIDE-15784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15811) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15811: ----------------------------------- Summary: CordovaSim: mark component description as "Experimental" Key: JBIDE-15811 URL: https://issues.jboss.org/browse/JBIDE-15811 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: browsersim Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 Reporter: Vlado Pakan Assignee: Yahor Radtsevich Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 Since CordovaSim is an experimental feature, its description should be changed from {{JBoss Tools Apache Cordova Simulator}} to {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15811) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15811?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-15811: -------------------------------- Fix Version/s: (was: 4.1.1.Beta1) > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15811 > URL: https://issues.jboss.org/browse/JBIDE-15811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.2.0.Alpha1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15811) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15811?page=com.atlassian.jira.plugi... ] Vlado Pakan resolved JBIDE-15811. --------------------------------- Resolution: Done > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15811 > URL: https://issues.jboss.org/browse/JBIDE-15811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.2.0.Alpha1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15784) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15784?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-15784: -------------------------------- Fix Version/s: (was: 4.2.0.Alpha1) > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15784 > URL: https://issues.jboss.org/browse/JBIDE-15784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15784) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15784?page=com.atlassian.jira.plugi... ] Vlado Pakan resolved JBIDE-15784. --------------------------------- Resolution: Done > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15784 > URL: https://issues.jboss.org/browse/JBIDE-15784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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-15784) CordovaSim: mark component description as "Experimental"

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15784?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15784. ------------------------------- Verified with JBT 4.1.1 Beta1a Beta1-v20131026-0906-B486 > CordovaSim: mark component description as "Experimental" > -------------------------------------------------------- > > Key: JBIDE-15784 > URL: https://issues.jboss.org/browse/JBIDE-15784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Labels: respin-a > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > Since CordovaSim is an experimental feature, its description should be changed from > {{JBoss Tools Apache Cordova Simulator}} > to > {{JBoss Tools Apache Cordova Simulator (Experimental)}} -- 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] (JBTIS-199) Update category names for installer.

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBTIS-199?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBTIS-199: ------------------------------------ Just to make it clear - Option B is the winner Option [B]: > JBoss Business Process and Rules development > JBoss Data Virtualization development > JBoss Integration development > JBoss SOA 5.x development > Update category names for installer. > ------------------------------------ > > Key: JBTIS-199 > URL: https://issues.jboss.org/browse/JBTIS-199 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.1.3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Beta5 > > > I've received two potentially contradictory BZs ([1], [2]) and there's been recent discussion > involving the JBDSIS 7.0.0.Beta4 category names. This would affect both equinox/p2 and JBoss > Central mylyn/discovery labelling. The issue is the following - currently the p2 installer presents > the user with this: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse development > > JBoss SOA 5.x development > > JBoss SOA development > The site category name definitions are inconsistent because there's a mixture of product names and > abstract concept labelling. The idea was to have FuseSource users and legacy 5.x SOA users have > an easy time finding what they needed to install and a general user could figure out what they wanted > by the abstract concept label. These are expandable categories - if the user wants to know what their > getting they can expand the category. > BZ [1] suggests changing the following: > Option [A]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse development > > JBoss SOA 5.x development > > JBoss Fuse Service Works > That clearly leaves us with 2 "Fuse" categories, one of which doesn't contain the Fuse features, and > expands on the product name based category labelling. If you're installing 'Fuse Service Works' it > could be argued that you'd expect to find that as a choice. > Alan made an interesting suggestion to combine SOA and Fuse, keeping the abstract labelling and > resulting in the following: > Option [B]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Integration development > > JBoss SOA 5.x development > That leaves the 'SOA 5.x' category as an outlier. Acceptable? Would something like this be better? > Option [C]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Integration development > > JBoss Legacy Integration development > > Applying the combine Fuse algorithm to [A] you could also have this: > > Option [D]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse Service Works > > JBoss SOA 5.x development > So - we're post-beta and I'm happy to accommodate the consensus - WDYT? > Thanks, > --paull > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1021282 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1021283 -- 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 Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14544: ------------------------------------- With JBT Beta1a Beta1-v20131026-0906-B486 I'm getting this error: {noformat} Device with serial number ???????????? is not available {noformat} JBoss Hybrid Mobile Plugins v. 1.0.100.Beta1-v20131025-0513-B47 Before with JBT Beta1 JBT 4.1.1 Beta1-v20131020-0207-B454 and same workspace I was getting this error {noformat} APK installation did not succeed {noformat} JBoss Hybrid Mobile Plugins v. 1.0.100.Beta1-v20131018-1426-B43 > 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 > Labels: respin-a > Fix For: 4.1.x, 4.2.x > > Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png > > 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-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-15499 at 10/29/13 10:38 AM: ------------------------------------------------------------------ {quoute} which mechanism is it you would use to register DND ? {quote} {code} DropTarget target = new DropTarget(control, DND.DROP_MOVE | DND.DROP_COPY | DND.DROP_LINK); target.setTransfer(new Transfer[] { URLTransfer.getInstance() }); ... target.addDropListener(...); {code} {quote} looks like DropTarget is a bit tricky but they seem to have added api to get listeners - at least that is what https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388 documents. {quote} We would use that API if the MPC client used it too. However, the MPC client doesn't use the API so if our plugin would register DND before the MPC client, the MPC client would throw an annoying exception that would propose to shutdown Eclipse. We can't control the order in which DNDs are registered. I can create a bug against MPC and add a patch if you want. I have created a PR. If you don't have the MPC plugin, you will be able to drag an url to an Eclipse instance (the toolbar, menu, or a view or editor that doesn't have a drop target). Otherwise, you can drag it to the JBoss Central editor. The MPC plugin will work as usual. The installation works as follows: - if some connector can't be found or is already installed, Eclipse will show a dialog with those informations and allows a user to continue or stop the installation. If the user wants to continue with the installation, Eclipse will call the standard P2's install wizard (including the Remediation page). I will fix JBIDE-14794 immediately after applying this PR. See http://screencast.com/t/e6lmfJktil. The screencast uses the http://download.jboss.org/jbosstools/central/install?connectors=org.tigri... url. was (Author: snjeza): {quoute} which mechanism is it you would use to register DND ? {quote} {code} DropTarget target = new DropTarget(control, DND.DROP_MOVE | DND.DROP_COPY | DND.DROP_LINK); target.setTransfer(new Transfer[] { URLTransfer.getInstance() }); ... target.addDropListener(...); {code} {quote} looks like DropTarget is a bit tricky but they seem to have added api to get listeners - at least that is what https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388 documents. {quote} We would use that API if the MPC client used it too. However, the MPC client doesn't use the API so if our plugin would register DND before the MPC client, the MPC client would throw an annoying exception that would propose to shutdown Eclipse. We can't control the order in which DNDs are registered. I can create a bug against MPC and add a patch if you want. I have created a PR. If you don't have the MPC plugin, you will be able to drag an url to an Eclipse instance (the toolbar, menu, or a view or editor that doesn't have a drop target). Otherwise, you can drag it to the JBoss Central editor. The MPC plugin will work as usual. The installation works as follows: - if some connector can't be found or is already installed, Eclipse will show a dialog with those informations and allows a user to continue or stop the installation. If the user wants to continue with the installation, Eclipse will call the standard P2's install wizard (including the Remediation page). I will fix JBIDE-14794 immediately after applying this PR. See http://screencast.com/t/e6lmfJktil. The screencast uses the https://devstudio.jboss.com/central/install?connector=org.tigris.subversi... url. > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013