[JBoss JIRA] (JBIDE-21430) Tab properties for Openshift Projects
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-21430:
-------------------------------------
Summary: Tab properties for Openshift Projects
Key: JBIDE-21430
URL: https://issues.jboss.org/browse/JBIDE-21430
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jeff Cantrill
Add tabbed properties for project where they content includes all the resource for a given project. This should provide a similiar visual display to what you would see in the OpenShift web console
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20473) "Import Application" context menu is always available
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20473?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20473:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> "Import Application" context menu is always available
> -----------------------------------------------------
>
> Key: JBIDE-20473
> URL: https://issues.jboss.org/browse/JBIDE-20473
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Rafael Benevides
> Fix For: 4.3.1.CR1
>
>
> I have an openshift 3 project that contains a database and a docker image.
> There's no BuildConfig since there's no sources.
> When I click on any item, the "Import Application" context menu is presented. But I can't import anything later.
> This menu should be available only when there's a BuildConfig on the project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21371:
-------------------------------------
Because the server adapter doesn't contain any IModules, no incremental deployment can happen.
Apparently the 2 possibles approaches are, as discussed with Rob :
- either implement an IModuleFactory to generate IModules, although it's unclear which criteria can be used to determine what makes an OpenShift IModule (there's a risk any kind of project could be identified as deployable on any given OpenShift Server, which is wrong).
- or implement or own Incremental Deployer thread, where we'd need to translate workspace resource deltas into module deltas (if I understood correctly)
Assigning to [~rob.stryker], who's the most savvy in that area.
> Server Adapter: implement automatic publishing
> ----------------------------------------------
>
> Key: JBIDE-21371
> URL: https://issues.jboss.org/browse/JBIDE-21371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21371 at 1/7/16 4:19 PM:
-------------------------------------------------------------
Because the server adapter doesn't contain any IModules, no incremental deployment can happen.
Apparently the 2 possibles approaches are, as discussed with Rob :
- either implement an IModuleFactory to generate IModules, although it's unclear which criteria can be used to determine what makes an OpenShift IModule (there's a risk any kind of project could be identified as deployable on any given OpenShift Server, which is wrong).
- or implement our own Incremental Deployer thread, where we'd need to translate workspace resource deltas into module deltas (if I understood correctly)
Assigning to [~rob.stryker], who's the most savvy in that area.
was (Author: fbricon):
Because the server adapter doesn't contain any IModules, no incremental deployment can happen.
Apparently the 2 possibles approaches are, as discussed with Rob :
- either implement an IModuleFactory to generate IModules, although it's unclear which criteria can be used to determine what makes an OpenShift IModule (there's a risk any kind of project could be identified as deployable on any given OpenShift Server, which is wrong).
- or implement or own Incremental Deployer thread, where we'd need to translate workspace resource deltas into module deltas (if I understood correctly)
Assigning to [~rob.stryker], who's the most savvy in that area.
> Server Adapter: implement automatic publishing
> ----------------------------------------------
>
> Key: JBIDE-21371
> URL: https://issues.jboss.org/browse/JBIDE-21371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months