[JBoss JIRA] (JBIDE-13805) Validations for mobile hybrid project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13805?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-13805:
---------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Validations for mobile hybrid project
> -------------------------------------
>
> Key: JBIDE-13805
> URL: https://issues.jboss.org/browse/JBIDE-13805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> config.xml editor needs validators for data entry. Editor itself is using jface databinding therefore jface validators should be able to help. Valid values depends on whether Phonegap or pure cordova values are supported.
> Also a validator for project structure can also be put in use.
--
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, 3 months
[JBoss JIRA] (JBIDE-15912) [Aerogear] Support for aerogear backend pieces
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15912?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15912:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: LATER
(was: 4.2.x)
> [Aerogear] Support for aerogear backend pieces
> ----------------------------------------------
>
> Key: JBIDE-15912
> URL: https://issues.jboss.org/browse/JBIDE-15912
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.x
> Reporter: Gorkem Ercan
> Priority: Minor
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> * Ability to publish these pieces on servers or openshift
> * creating adaptors to existing enterprise services and connecting to LDAP service for auth*
> * Emulate creation of native push notifications for testing
> * Ability to configure push service
> * Ability to create mobile app authentication keys
--
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, 3 months
[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2848:
------------------------------------
Thanks Max - that's helpful - do we know when we will have a definition of the full list? Beta1? Beta2?
> Usage Stats for actual used features
> ------------------------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, usage
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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, 3 months
[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2776:
------------------------------------
So - a reasonable test case would be for us to upload a project for each of the archetypes that we include in Central?
> Support quickstarts in OpenShift UI
> -----------------------------------
>
> Key: JBDS-2776
> URL: https://issues.jboss.org/browse/JBDS-2776
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
> Attachments: new-application-2.png
>
>
> OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI:
> !new-application-2.png!
> JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users.
--
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, 3 months
[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2913:
--------------------------------------
This is out of the box EAP 6.2.1 in JBDS 7.1.0. So looks like a regression indeed.
> Console log when running EAP 6.2.x not formatted correctly
> ----------------------------------------------------------
>
> Key: JBDS-2913
> URL: https://issues.jboss.org/browse/JBDS-2913
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: server
> Affects Versions: 7.1.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Attachments: EAP-6.1.0.png, EAP-6.2.1.png
>
>
> When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0)
--
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, 3 months
[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-245:
-----------------------------------
I think this is possible. We know Teiid has issues because of changes to JBT servers. The issues with SY are that it only works with Graphiti 0.10. I've asked [~pleacu] to update the TP to use Graphiti 0.10, so we can move forward. (We already know we'll need to migrate to the next version for Luna and we're the only ones using it, so...)
As for anything more than that, from SY at least, we're busy working on features for FSW 6.1, which I think you'd agree takes priority over ensuring compatibility with alpha builds.
I believe we're planning a release to support JBDS 8 in the late summer after its release, so there shouldn't be a repeat of not having any integration tools for a JBDS release.
> Please update JBTIS TP dependencies to Luna Alpha1
> --------------------------------------------------
>
> Key: JBTIS-245
> URL: https://issues.jboss.org/browse/JBTIS-245
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Greetings - welcome to Luna!
> An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3].
> I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others.
> Thanks!
> [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al...
> [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration...
--
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, 3 months
[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-16661 at 2/27/14 9:38 AM:
-------------------------------------------------------------------------
The difference betwenn BrowserSim and CordovaSim launch process is that CordovaSim is launched using Run As. So it has two objects(ILaunch and IProgressMonitor) which allows to have this console(see screenshot). For BrowserSim it is not easy. Now I have no idea which of two objects available from launch config opens this console. I'm not sure if we can create necessary stubs for BrowserSim.
Another problem is in communication between browsersim/cordovasim and eclipse(view source). How it works now: write message to console, read it and do all necessary stuff. Now it looks like we will not be able to read this messages.
was (Author: kmarmaliykov):
The difference betwenn BrowserSim and CordovaSim launch process is that CordovaSim is launched using Run As. So it has two objects which allows to have this console(see screenshot). For BrowserSim it is not easy. Now I have no idea which of two objects available from launch config opens this console. I'm not sure if we can create necessary stubs for BrowserSim.
Another problem is in communication between browsersim/cordovasim and eclipse(view source). How it works now: write message to console, read it and do all necessary stuff. Now it looks like we will not be able to read this messages.
> Eclipse Console Logging for CordovaSim
> --------------------------------------
>
> Key: JBIDE-16661
> URL: https://issues.jboss.org/browse/JBIDE-16661
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
> Attachments: Screenshot 2014-02-27 16.23.47.png
>
>
> If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching.
> My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser".
--
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, 3 months
[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-16661:
------------------------------------------------
The difference betwenn BrowserSim and CordovaSim launch process is that CordovaSim is launched using Run As. So it has two objects which allows to have this console(see screenshot). For BrowserSim it is not easy. Now I have no idea which of two objects available from launch config opens this console. I'm not sure if we can create necessary stubs for BrowserSim.
Another problem is in communication between browsersim/cordovasim and eclipse(view source). How it works now: write message to console, read it and do all necessary stuff. Now it looks like we will not be able to read this messages.
> Eclipse Console Logging for CordovaSim
> --------------------------------------
>
> Key: JBIDE-16661
> URL: https://issues.jboss.org/browse/JBIDE-16661
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
> Attachments: Screenshot 2014-02-27 16.23.47.png
>
>
> If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching.
> My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser".
--
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, 3 months
[JBoss JIRA] (JBDS-2840) Java 8
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2840?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2840:
---------------------------------------
[~maxandersen], your devel approve list is very clear and helpful. Could you just state where devel stands on start/stop/debug EAP 6.3 with Java 8 VM.
> Java 8
> ------
>
> Key: JBDS-2840
> URL: https://issues.jboss.org/browse/JBDS-2840
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, upstream
> Reporter: Burr Sutter
> Priority: Critical
>
> Support for Java 8
> - The IDE running with Java 8 on all OS platforms
> - The capabilities in Eclipse Luna for code editing/support
> - EAP 6.3 with Java 8 (start, stop,deploy, debug, etc)
--
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, 3 months