[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24382:
----------------------------------
Attachment: byoe_keep2.png
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Ondrej Dockal
> Fix For: 4.4.4.Final
>
> Attachments: BYOE_keep.png, BYOE_show.png, BYOE_update.png, byoe_keep2.png, byoe_update2.png, devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt, p2diff_460.txt, p2diff_460_summary.txt, processing_information_1.png, processing_information_2.png, processing_information_3.png, rh_central_remediation_page_keep.png, rh_central_remediation_page_show.png
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24382:
----------------------------------
Attachment: Spectacle.h12044.png
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Ondrej Dockal
> Fix For: 4.4.4.Final
>
> Attachments: BYOE_keep.png, BYOE_show.png, BYOE_update.png, Spectacle.M12044.png, Spectacle.h12044.png, devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt, p2diff_460.txt, p2diff_460_summary.txt, processing_information_1.png, processing_information_2.png, processing_information_3.png, rh_central_remediation_page_keep.png, rh_central_remediation_page_show.png
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24382:
----------------------------------
Attachment: Spectacle.M12044.png
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Ondrej Dockal
> Fix For: 4.4.4.Final
>
> Attachments: BYOE_keep.png, BYOE_show.png, BYOE_update.png, Spectacle.M12044.png, devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt, p2diff_460.txt, p2diff_460_summary.txt, processing_information_1.png, processing_information_2.png, processing_information_3.png, rh_central_remediation_page_keep.png, rh_central_remediation_page_show.png
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24407) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24407?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-24407.
---------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Arquillian]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24407
> URL: https://issues.jboss.org/browse/JBIDE-24407
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Jeff MAURY
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Arquillian]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-arquillian at https://github.com/jbosstools/jbosstools-arquillian
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "0f1a72" is the last common ancestor of master and jbosstools-4.4.x
> 0f1a72 is 4 commits ago in branch jbosstools-4.4.x
> 0f1a72 is 6 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: Revert-JBIDE-24342-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/fd35c22fbd7d82...
> * missing: JBIDE-24342-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/1d7f35cbe27e2f...
> * missing: Updating-version-to-1.2.500-SNAPSHOT https://github.com/jbosstools/jbosstools-arquillian/commit/f993a36f2ce4d1...
> * missing: JBIDE-23966-Compile-errors-in-org.jboss.tools.arquillian.ui-on-Oxygen-132 https://github.com/jbosstools/jbosstools-arquillian/commit/688254a1c55b3e...
> * missing: JBIDE-23945-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/c2cbacdf20a582...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Arquillian task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24407) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24407?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-24407:
----------------------------------
Fix Version/s: 4.4.4.Final
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Arquillian]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24407
> URL: https://issues.jboss.org/browse/JBIDE-24407
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Jeff MAURY
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Arquillian]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-arquillian at https://github.com/jbosstools/jbosstools-arquillian
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "0f1a72" is the last common ancestor of master and jbosstools-4.4.x
> 0f1a72 is 4 commits ago in branch jbosstools-4.4.x
> 0f1a72 is 6 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: Revert-JBIDE-24342-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/fd35c22fbd7d82...
> * missing: JBIDE-24342-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/1d7f35cbe27e2f...
> * missing: Updating-version-to-1.2.500-SNAPSHOT https://github.com/jbosstools/jbosstools-arquillian/commit/f993a36f2ce4d1...
> * missing: JBIDE-23966-Compile-errors-in-org.jboss.tools.arquillian.ui-on-Oxygen-132 https://github.com/jbosstools/jbosstools-arquillian/commit/688254a1c55b3e...
> * missing: JBIDE-23945-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-arquillian/commit/c2cbacdf20a582...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Arquillian task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24358) Central New and Noteworthy for 4.4.4.Final
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24358?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-24358.
-------------------------------
Resolution: Rejected
Nothing new here
> Central New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24358
> URL: https://issues.jboss.org/browse/JBIDE-24358
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Fred Bricon
> Priority: Critical
>
> Fred Bricon,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Central by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Central 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Central, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months