[JBoss JIRA] (JBIDE-21453) Server Adapter: use rsync flag instead of local filtered-copy
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21453?page=com.atlassian.jira.plugi... ]
Xavier Coulon edited comment on JBIDE-21453 at 3/24/16 5:07 AM:
----------------------------------------------------------------
ok, I'll keep the {{pod -> local}} rsync operation. Anyway, we'd rather no break this part so close to the release.
was (Author: xcoulon):
ok, I'll keep the {{pod -> local }} rsync operation. Anyway, we'd rather no break this part so close to the release.
> Server Adapter: use rsync flag instead of local filtered-copy
> -------------------------------------------------------------
>
> Key: JBIDE-21453
> URL: https://issues.jboss.org/browse/JBIDE-21453
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> With https://github.com/openshift/origin/issues/6143 *oc rsync* now allows specific white-listed flag to be used.
> Our current implementation works around this by doing a local copy where excluded bits are filtered (not copied). We need to use exclusion flags if available.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-19910:
----------------------------------
Component/s: server
> Add w3 schemes to XML catalog
> -----------------------------
>
> Key: JBIDE-19910
> URL: https://issues.jboss.org/browse/JBIDE-19910
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> We should add w3 schemes which are used in our quickstarts/examples to XML catalog because:
> 1) w3 servers are intentionally slow
> 2) it seems that wsdl validator does no caching of previously downloaded schemes
> I will take a look at examples and list schemes here.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-19910.
---------------------------------
Resolution: Done
closing after updating the components list.
> Add w3 schemes to XML catalog
> -----------------------------
>
> Key: JBIDE-19910
> URL: https://issues.jboss.org/browse/JBIDE-19910
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> We should add w3 schemes which are used in our quickstarts/examples to XML catalog because:
> 1) w3 servers are intentionally slow
> 2) it seems that wsdl validator does no caching of previously downloaded schemes
> I will take a look at examples and list schemes here.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3704) The installer gets stuck on Download page and never goes to Getting Started
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3704?page=com.atlassian.jira.plugin.... ]
Jan Richter edited comment on JBDS-3704 at 3/24/16 4:18 AM:
------------------------------------------------------------
I'm going to try once more (then I'll leave this and start somewhere else). The code from the provided PR introduces a more or less useless condition when checking if JBDS is installed - it now succeeds whether or not the installer thinks so.
Bottom line - I'd like to ask you to instead remove this condition entirely to avoid confusion.
I believe that is relevant to this particular issue.
was (Author: jrichter1):
I'm going to try once more (then I'll leave this and start somewhere else). The code from the provided PR introduces a more or less useless condition when checking if JBDS is installed - it now succeeds whether or not the installer thinks so.
Bottom line - I'd like to ask you to instead remove this condition entirely to avoid confusion.
> The installer gets stuck on Download page and never goes to Getting Started
> ---------------------------------------------------------------------------
>
> Key: JBDS-3704
> URL: https://issues.jboss.org/browse/JBDS-3704
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: havoc
>
> It happens if the installer installs JBDS and works fine if it just sets up some already existing one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21965?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21965:
--------------------------------
Description:
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
AFTER | BEFORE
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
was:
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
AFTER BEFORE
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
> oc rsync triggered when adding/removing breakpoints
> ---------------------------------------------------
>
> Key: JBIDE-21965
> URL: https://issues.jboss.org/browse/JBIDE-21965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
> in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
> AFTER | BEFORE
> !http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21965?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21965:
--------------------------------
Description:
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
AFTER BEFORE
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
was:
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
> oc rsync triggered when adding/removing breakpoints
> ---------------------------------------------------
>
> Key: JBIDE-21965
> URL: https://issues.jboss.org/browse/JBIDE-21965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
> in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
> AFTER BEFORE
> !http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21965?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21965:
--------------------------------
Fix Version/s: 4.3.1.CR1
> oc rsync triggered when adding/removing breakpoints
> ---------------------------------------------------
>
> Key: JBIDE-21965
> URL: https://issues.jboss.org/browse/JBIDE-21965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
> in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21965:
-----------------------------------
Summary: oc rsync triggered when adding/removing breakpoints
Key: JBIDE-21965
URL: https://issues.jboss.org/browse/JBIDE-21965
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years