[JBoss JIRA] (JBIDE-20636) Push changes: Management interface wont come up while deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20636:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Push changes: Management interface wont come up while deployment
> ----------------------------------------------------------------
>
> Key: JBIDE-20636
> URL: https://issues.jboss.org/browse/JBIDE-20636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
>
> Reference: https://github.com/openshift/origin/issues/4502
> {code}
> Preparing build for deployment
> Deployment id is f2c69660
> Activating deployment
> Starting PHPMyAdmin cartridge
> Starting MySQL 5.5 cartridge Deploying JBoss
> Starting jbossas cartridge
> Found 127.3.158.129:8080 listening port
> Found 127.3.158.129:9999 listening port
> CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification
> -------------------------
> Git Post-Receive Result: success
> Activation status: success
> Deployment completed with status: success
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21421) New Server adapter using same build config and server is ignored
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21421?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21421:
-----------------------------------
Fix Version/s: 4.3.1.Beta2
Assignee: Viacheslav Kabanovich
Resolution: Done
PR applied in master and 4.3.x. Thanks [~scabanovich]!
Note the server name pattern was changed to be closer to OpenShift 2. It's now *servicename at OpenShift 3 (host)*
> New Server adapter using same build config and server is ignored
> ----------------------------------------------------------------
>
> Key: JBIDE-21421
> URL: https://issues.jboss.org/browse/JBIDE-21421
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created.
> I would expect one of following:
> a) An existing server adapter will be updated according to the latest details filled in server adapter wizard
> b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
Priority: Major (was: Minor)
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
I've set the ACKs needed to make this into JBDS 9.1 (CDW workflow).
Next, I need to know a few clarifications:
a) How should this be installed in JBDS?
* default: installed OOTB (included in JBDS core feature / installer / BYOE / marketplace)
* recommended: listed in the Marketplace connector as another checked feature (which a user can choose to NOT install) and added to Abridged JBDS category (Core Tools)
* optional-marketplace: listed in the Marketplace connector as another unchecked feature (which a user can choose to install) and added to Abridged JBDS category (Core Tools)
* optional-central: new Central connector
b) If we want this in JBT too, how should this be installed in JBT?
* default: installed OOTB (required by JBT Community Central feature)
* recommended: listed in the Marketplace connector as another checked feature (which a user can choose to NOT install) and added to Abridged JBDS category (Core Tools)
* optional-marketplace: listed in the Marketplace connector as another unchecked feature (which a user can choose to install) and added to Abridged JBDS category (Core Tools)
* optional-central: new Central connector
* none: do not add to JBT
c) should these features be in another category other than Core Tools
* Additional Tools?
* General Tools?
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21450) Allow for any adaptable to IServerModule to be opened via LiveReload
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21450:
-------------------------------------
Summary: Allow for any adaptable to IServerModule to be opened via LiveReload
Key: JBIDE-21450
URL: https://issues.jboss.org/browse/JBIDE-21450
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: livereload
Affects Versions: 4.3.1.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.1.Beta2
The "Open in Web Browser via LiveReload" is only available if the selection is an `IServerModule` but this could be extended to any type of element that can be adapted to an `IServerModule, to provide more flexibility to other tools such as OpenShift where the server adapter is used as the target (ie, there is no server module for the deployed application)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21450) Allow for any adaptable to IServerModule to be opened via LiveReload
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21450?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21450:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> Allow for any adaptable to IServerModule to be opened via LiveReload
> --------------------------------------------------------------------
>
> Key: JBIDE-21450
> URL: https://issues.jboss.org/browse/JBIDE-21450
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> The "Open in Web Browser via LiveReload" is only available if the selection is an `IServerModule` but this could be extended to any type of element that can be adapted to an `IServerModule, to provide more flexibility to other tools such as OpenShift where the server adapter is used as the target (ie, there is no server module for the deployed application)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-20915:
---------------------------------------
[~mhusnain] please let me know where we should document the "delay" option in the documentation, since the issue here is not really a bug.
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months