January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14407) Manage different Cordova versions

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14407?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-14407: --------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: LATER) > Manage different Cordova versions > --------------------------------- > > Key: JBIDE-14407 > URL: https://issues.jboss.org/browse/JBIDE-14407 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.2.0.Alpha2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Ability to target different supported cordova versions... Tools at least should offer the ability to migrate to the latest supported Cordova version. > Also all the cordova templates and files should be able to update independent of the rest of the plugins. > This requires a UI for switching targeted cordova runtimes. > .cordova/config.json can be populated with the engine information. Phonegap uses the following format. > {"lib":{"www":{"id":"phonegap","version":"3.0.0","uri":"https://github.com/phonegap/phonegap-app-hello-world/archive/3.0.0.tar.gz"}},"id":"AAA","name":"HelloWorld"} -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16338) JQuery Mobile 1.4 class="ui-*" content assist

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-16338: -------------------------------------- Summary: JQuery Mobile 1.4 class="ui-*" content assist Key: JBIDE-16338 URL: https://issues.jboss.org/browse/JBIDE-16338 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.Alpha2 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16294) JQuery Mobile 1.4 data-* content assist

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16294: ----------------------------------- Attachment: scr.png > JQuery Mobile 1.4 data-* content assist > --------------------------------------- > > Key: JBIDE-16294 > URL: https://issues.jboss.org/browse/JBIDE-16294 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: scr.png > > > http://api.jquerymobile.com/data-attribute/ -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16294) JQuery Mobile 1.4 data-* content assist

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16294: ----------------------------------- Description: http://api.jquerymobile.com/data-attribute/ !scr.png! was:http://api.jquerymobile.com/data-attribute/ > JQuery Mobile 1.4 data-* content assist > --------------------------------------- > > Key: JBIDE-16294 > URL: https://issues.jboss.org/browse/JBIDE-16294 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: scr.png > > > http://api.jquerymobile.com/data-attribute/ > !scr.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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-229) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-229?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-229. ------------------------------ Fix Version/s: 4.1.3.Final 7.0.0.Final-JBDSIS Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/pull/169 > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-229 > URL: https://issues.jboss.org/browse/JBTIS-229 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Fix For: 4.1.3.Final, 7.0.0.Final-JBDSIS > > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-227) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-227?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-227. ------------------------------ Fix Version/s: 4.1.3.Final 7.0.0.Final-JBDSIS Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/pull/168 > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-227 > URL: https://issues.jboss.org/browse/JBTIS-227 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > Fix For: 4.1.3.Final, 7.0.0.Final-JBDSIS > > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-230) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-230?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-230. ------------------------------ Fix Version/s: 4.1.3.Final 7.0.0.Final-JBDSIS Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/pull/167 > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-230 > URL: https://issues.jboss.org/browse/JBTIS-230 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Dan Florian > Fix For: 4.1.3.Final, 7.0.0.Final-JBDSIS > > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible if the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2669: -------------------------------------- I prefer com.jboss.devstudio over com.redhat.jbdevstudio because it is IMO a more explicit name. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16323) Cordovasim: Need to make some UI enhancements

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16323?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-16323: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/203 (was: https://github.com/jbosstools/jbosstools-vpe/pull/202) > Cordovasim: Need to make some UI enhancements > --------------------------------------------- > > Key: JBIDE-16323 > URL: https://issues.jboss.org/browse/JBIDE-16323 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha2 > > Attachments: barcode.png, proposal.png > > > There were several UI proposals for CordovaSim design: > - cordovasim takes up *Alot* of real estate. Need to make just one row for all panels - http://snag.gy/2gb2B.jpg. > - need to add icon to all "select" tags to make it more user-friendly -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16128: --------------------------------------------- if tycho would run integrations tests in a repository project you could do the assert against the previous released version to notice differences. > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- 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

11 years, 9 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 January 2014