[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2844.
-------------------------------
This was tested and verified during JBDS 8.0.0.Beta3 testing.
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 8.0.0.Beta3
>
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2847:
-------------------------------------
Hi [~xcoulon], do you have an estimate where this might be ready? Is the description still valid? That the goal is to have all the samples from the github repo working smoothly in JBDS out of the box. I am assigned to test this when it's ready :)
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18026) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18026?page=com.atlassian.jira.plugi... ]
Peter Palaga commented on JBIDE-18026:
--------------------------------------
I am working on a fix for JBIDE-11287. Could the present issue please be fixed after my JBIDE-11287 fix is merged so that it does not introduce conflicts? I hope to be able to submit the PR for JBIDE-11287 within a couple of days.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18026
> URL: https://issues.jboss.org/browse/JBIDE-18026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Freemarker]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18005?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18005:
-------------------------------------
Assigning to [~dgolovin] to apply PR (looks good to me).
[~snjeza], please avoid assigning issues to me till sept 1st, as I'm on PTO. With Max away, Denis has all superpowers
> Disable automatic Portlet configuration via pom property
> --------------------------------------------------------
>
> Key: JBIDE-18005
> URL: https://issues.jboss.org/browse/JBIDE-18005
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.2.0.CR1
>
>
> add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
> an xml template should be made available for ctrl+space in the properties section. See JBIDE-17885
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15798:
--------------------------------------
Also added the related Eclipse Thym bug report.
> Missing scroolbar in Cordova Feature Dialog
> -------------------------------------------
>
> Key: JBIDE-15798
> URL: https://issues.jboss.org/browse/JBIDE-15798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file in Cordova Configuration Editor
> 3. Go to Platform Properties tab. and click on Add.... button to add features
> 4. Type some text to Find text field to specify search condition which cannot be fulfilled to get empty list of plugins
> 5. Clear Find: text field
> ERROR: Opened dialog has no scroll bar
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15798:
--------------------------------------
This is one of the components that has moved to Eclipse Thym. Do you think you can resend the PR to https://github.com/eclipse/thym?
> Missing scroolbar in Cordova Feature Dialog
> -------------------------------------------
>
> Key: JBIDE-15798
> URL: https://issues.jboss.org/browse/JBIDE-15798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file in Cordova Configuration Editor
> 3. Go to Platform Properties tab. and click on Add.... button to add features
> 4. Type some text to Find text field to specify search condition which cannot be fulfilled to get empty list of plugins
> 5. Clear Find: text field
> ERROR: Opened dialog has no scroll bar
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-15798:
--------------------------------
Assignee: Gorkem Ercan (was: Vlado Pakan)
> Missing scroolbar in Cordova Feature Dialog
> -------------------------------------------
>
> Key: JBIDE-15798
> URL: https://issues.jboss.org/browse/JBIDE-15798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file in Cordova Configuration Editor
> 3. Go to Platform Properties tab. and click on Add.... button to add features
> 4. Type some text to Find text field to specify search condition which cannot be fulfilled to get empty list of plugins
> 5. Clear Find: text field
> ERROR: Opened dialog has no scroll bar
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-15798) Missing scroolbar in Cordova Feature Dialog
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15798?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15798:
-------------------------------------
I'm not a gatekeeper [~gercan] could you verify attached PR please?
> Missing scroolbar in Cordova Feature Dialog
> -------------------------------------------
>
> Key: JBIDE-15798
> URL: https://issues.jboss.org/browse/JBIDE-15798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file in Cordova Configuration Editor
> 3. Go to Platform Properties tab. and click on Add.... button to add features
> 4. Type some text to Find text field to specify search condition which cannot be fulfilled to get empty list of plugins
> 5. Clear Find: text field
> ERROR: Opened dialog has no scroll bar
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-16575 at 8/1/14 2:33 AM:
-------------------------------------------------------------
Integration tests of BrowserSim are run as part of VPE integration tests nad it is so because BrowserSim was part of VPE.
And it makes sense to test BrowserSim from Eclipse i. e. BrowserSim integration with Eclipse for example:
- displaying javascript errors to Eclipse console
- displaying source code of web page opened in Browsersim in Eclipse
- livereload functionality i.e. resource changed and saved in Eclipse is changed in BrowserSIm
Right now there are 2 types of tests:
- tests running BrowserSim via clicking on Toolbar Button in Eclipse checking if BrowserSim is able to run, opens selected web page and displays errors to Eclipse console - working now also with JavaFX
- tests running BrowserSim as Eclipse process not working now with JavaFX
was (Author: vpakan):
Integration tests of BrowserSim are run as part of VPE integration tests nad it is so because BrowserSim was part of VPE.
And it makes sense to test BrowserSim from Eclipse i. e. BrowserSim integration with Eclipse for example:
- displaying javascript errors to Eclipse console
- displaying source code of web page opened in Browsersim in Eclipse
- livereload functionality i.e. resource changed and saved in Eclipse is changed in BrowserSIm
Right now there are 2 types of test:
- tests running BrowserSim via clicking on Toolbar Button in Eclipse checking if BrowserSim is able to run, opens selected web page and displays errors to Eclipse console - working now also with JavaFX
- tests running BrowserSim as Eclipse process not working now with JavaFX
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months