January 2014 - jbosstools-issues - Jboss List Archives

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2669: ------------------------------------------- Now trying to build master and I'm now seeing this warning (in addition to the warning about unresolved property): [WARNING] p2 repository with URL http://download.jboss.org/jbosstools/updates/nightly/core/master is associated with multiple IDs; was 'jbosstools-site', now is 'jbosstools' And it is still failing for me on a clean build. Retrying to see if I can spot why. > 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: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2745: ------------------------------------------- [~nickboldt] not sure what you mean by eye candy ;) This is about making it controllable to install, uninstall and identify which plugins/features/connector are supported and which are not. I don't believe we can allow *everything* to get into these updatesites - we would need to put some requirements and tests on these like that osgi rules are followed and the combinations of the tools does not fight each other. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- 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] (JBDS-2875) Support EAP 6.3

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2875?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2875: ------------------------------------------- [~ldimaggio] yes that is correct. > Support EAP 6.3 > --------------- > > Key: JBDS-2875 > URL: https://issues.jboss.org/browse/JBDS-2875 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements, server > Reporter: Michelle Murray > Assignee: Max Rydahl Andersen > -- 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] (JBDS-2866) CordovaSim Debugger

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-2866: ----------------------------------- [~ldimaggio], you can watch a demo - http://www.youtube.com/watch?v=C8dMNWWfK3A&feature=youtu.be > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-447: ------------------------------------- Sprint: For 7.1.1 > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.1.1, 4.2.0 > > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- 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-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-447: ------------------------------------- Fix Version/s: 4.1.1 > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.1.1, 4.2.0 > > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- 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-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-447: ------------------------------------------ Since SSL features are not yet implemented in JBDS, can only add a note to the JBDS User Guide OpenShift Tools chp that certificates are automatically accepted without prompting at this time. In terms of the other info: * setting up connections to different servers - this is covered in 9.2.3 Connect to OpenShift [1]. * similar info to 2.3 Configuring Client Tools in OpenShift doc (login, setting SSH Keys, checking for Git, setting up a domain, associated applications) - this is covered as appropriate in various sections in 9.2 Features of OpenShift Tools [2]. If there are specifics missing please open separate and new jiras for these. [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... [2] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- 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-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-445: ------------------------------------- Sprint: For 7.1.1 > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.0 > > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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-443) Simple guide to show app signing and deploying for iOS and Android

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-443: ------------------------------------- Parent: TOOLSDOC-356 Issue Type: Sub-task (was: Enhancement) > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Tadeas Kriz > Assignee: Michelle Murray > Fix For: 4.2.0 > > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- 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-446) document how to debug on openshift JEE applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-446?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-446: ------------------------------------- Sprint: For 7.1.1 > document how to debug on openshift JEE applications > --------------------------------------------------- > > Key: TOOLSDOC-446 > URL: https://issues.jboss.org/browse/TOOLSDOC-446 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.1.2, 4.2.0 > > > would be great if Docs at https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > could outline how to enable/disable debugging and how to use port forwarding to connect to the debugger. > References: > https://community.jboss.org/en/tools/blog/2012/02/08/debugging-and-browsi... > http://vimeo.com/44548968 -- 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 January 2014