[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24322:
-------------------------------------
Steps to Reproduce:
0) Windows operating system
1) Remove rsync from the PATH. To check if rsync cannot be detected, simply try to run _rsync_ command in the cmd cli. You can do it via multiple ways: a) go to the installation directory of the sygwin -> to the _bin_ directory -> find there _rsync_ binary and rename it. b) if you have cwRsync installed separately, then uninstall it, or also simply remove it. Finally, command _which rsync_ must output _"which: no rsync in <PATH env var>"_.
2) Create openshift connection in Openshift Explorer
3) create any eap application, e.g. jboss-eap70-openshift
4) wait till pod is built and run.
5) create server adapter
6) make changes in the sources and save them.
Publish will happen. If you continue to do publishes, it will lead to the nested directories.
Workaround Description: Make sure to have rsync installed and added to the PATH env variable.
Workaround: Workaround Exists
added steps to reproduce + workaround
> Openshift publisher keeps getting more nested
> ---------------------------------------------
>
> Key: JBIDE-24322
> URL: https://issues.jboss.org/browse/JBIDE-24322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: - OS: Windows 7
> - JbossDev: 10.3.0.0
> - Openshift Client: 3.4
> - Openshift Enterprise: 3.4
> - Workspace location: it's inside a network drive
> Reporter: Rob Stryker
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit.
> We noticed that during the publishing or local change.
>
> The Publish function, always creates a nested deploy directory inside an existing one.
> For instance inside /opt/eap/standalone/deployments/
> 1st Publish:
> deploy/server.war/
> 2nd Publish:
> deploy/deploy/server.war/
> 3nd Publish:
> deploy/deploy/deploy/server.war/
>
> So with 3 publish, you end up with 3 deployed same application.
> This happen also inside the local workspaces for the synchronisation:
> .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift
> The EAP7 images is the jboss-eap70-openshift:latest.
>
> Do you have any idea why this happen?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24367) Server New and Noteworthy for 4.4.4.Final
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24367?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24367:
--------------------------------
Fix Version/s: 4.4.4.Final
> Server New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24367
> URL: https://issues.jboss.org/browse/JBIDE-24367
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Rob Stryker,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Server 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 Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Server 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 Server 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 Server 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 Server, 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
[JBoss JIRA] (JBIDE-24411) Refresh the OpenSHift Explorer tree after "edit connection" wizard ended
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-24411:
---------------------------------------
Summary: Refresh the OpenSHift Explorer tree after "edit connection" wizard ended
Key: JBIDE-24411
URL: https://issues.jboss.org/browse/JBIDE-24411
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.4.AM3
Reporter: Aurélien Pupier
Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice)
So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh.
it would be nice to refresh automatically the tree when the connection has been edited
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4357.
------------------------------
Resolution: Won't Fix
It seems that m2e works fine. So we can ignore this error message. Closing.
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.GA
>
> Attachments: m2e171.png, rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-23869 at 5/5/17 4:59 AM:
-----------------------------------------------------------------
there is no more a ClassCastException but now it is "Invalid status of type java.lang.String('Failure') received" which is not more useful at all.
I tested with
Red Hat JBoss Developer Studio
Version: 10.4.0.GA
Build id: GA-v20170504-2114-B29
Build date: 20170504-2114
!failure.png|thumbnail!
was (Author: aurelien.pupier):
there is no more a ClassCastException but now it is "Invalid status of type java.lang.String('Failure') received" which is not more useful at all.
I tested with
Red Hat JBoss Developer Studio
Version: 10.4.0.GA
Build id: GA-v20170504-2114-B29
Build date: 20170504-2114
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.Final
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-23869:
------------------------------------
Attachment: failure.png
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.Final
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24408) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24408:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
Key: JBIDE-24408
URL: https://issues.jboss.org/browse/JBIDE-24408
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server, jmx, archives
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [Server]: 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-server at https://github.com/jbosstools/jbosstools-server
Searching for commits present in master and missing from jbosstools-4.4.x
Commit hash "e4ea00" is the last common ancestor of master and jbosstools-4.4.x
e4ea00 is 37 commits ago in branch jbosstools-4.4.x
e4ea00 is 34 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: JBIDE-23869-consume-jolokia-snapshot-with-our-classcast-fix https://github.com/jbosstools/jbosstools-server/commit/a4b6166f61da59e22a...
** possible match: https://github.com/jbosstools/jbosstools-server/commit/a910e333f88ba38c5e...
*** Inspect the difference between the two patches: http://sprunge.us/QJDU
* missing: JBIDE-24233-force-connections-for-wf8-and-above-to-use-http-remoting-protocol https://github.com/jbosstools/jbosstools-server/commit/b18d91e68861956074...
** possible match: https://github.com/jbosstools/jbosstools-server/commit/b5e4c0d194f5103ee0...
*** Inspect the difference between the two patches: http://sprunge.us/YhRR
* missing: JBIDE-24138-fix-test-case-for-oxygen-api-changes https://github.com/jbosstools/jbosstools-server/commit/569d7acdd38b64af5d...
* missing: JBIDE-24138-Implement-QueryMBeans-for-JolokiaMBeanServerConnection https://github.com/jbosstools/jbosstools-server/commit/cb974c9f9791a32a77...
** possible match: https://github.com/jbosstools/jbosstools-server/commit/2c02ace0653c097733...
*** Inspect the difference between the two patches: http://sprunge.us/XUZe
* missing: Bump-root-pom-so-update-site-appears-correct https://github.com/jbosstools/jbosstools-server/commit/f2848a0506a76b1fe8...
** possible match: https://github.com/jbosstools/jbosstools-server/commit/3dd7251c190dce7a6a...
*** Inspect the difference between the two patches: http://sprunge.us/SRMR
* missing: JBIDE-22717-Remvoe-Event-Log https://github.com/jbosstools/jbosstools-server/commit/d82e9f9b649b4cca27...
* missing: Failing-Unit-Tests-secure-storage-related-MASTER-ONLY https://github.com/jbosstools/jbosstools-server/commit/d84d2b1278ea946659...
* missing: JBIDE-24043-upversion-master https://github.com/jbosstools/jbosstools-server/commit/e3a065a0ea76caae92...
* missing: JBIDE-24029-JBIDE-24031 https://github.com/jbosstools/jbosstools-server/commit/778cc2dc271e5fef9b...
** possible match: https://github.com/jbosstools/jbosstools-server/commit/82d51ba3185088bc21...
*** Inspect the difference between the two patches: http://sprunge.us/RMNB
* missing: JBIDE-23956-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-server/commit/442b33bc7e241b7e96...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server 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-24408) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24408?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24408:
----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-24408
> URL: https://issues.jboss.org/browse/JBIDE-24408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
>
> For JBIDE 4.4.4.Final [Server]: 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-server at https://github.com/jbosstools/jbosstools-server
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "e4ea00" is the last common ancestor of master and jbosstools-4.4.x
> e4ea00 is 37 commits ago in branch jbosstools-4.4.x
> e4ea00 is 34 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-23869-consume-jolokia-snapshot-with-our-classcast-fix https://github.com/jbosstools/jbosstools-server/commit/a4b6166f61da59e22a...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/a910e333f88ba38c5e...
> *** Inspect the difference between the two patches: http://sprunge.us/QJDU
> * missing: JBIDE-24233-force-connections-for-wf8-and-above-to-use-http-remoting-protocol https://github.com/jbosstools/jbosstools-server/commit/b18d91e68861956074...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/b5e4c0d194f5103ee0...
> *** Inspect the difference between the two patches: http://sprunge.us/YhRR
> * missing: JBIDE-24138-fix-test-case-for-oxygen-api-changes https://github.com/jbosstools/jbosstools-server/commit/569d7acdd38b64af5d...
> * missing: JBIDE-24138-Implement-QueryMBeans-for-JolokiaMBeanServerConnection https://github.com/jbosstools/jbosstools-server/commit/cb974c9f9791a32a77...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/2c02ace0653c097733...
> *** Inspect the difference between the two patches: http://sprunge.us/XUZe
> * missing: Bump-root-pom-so-update-site-appears-correct https://github.com/jbosstools/jbosstools-server/commit/f2848a0506a76b1fe8...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/3dd7251c190dce7a6a...
> *** Inspect the difference between the two patches: http://sprunge.us/SRMR
> * missing: JBIDE-22717-Remvoe-Event-Log https://github.com/jbosstools/jbosstools-server/commit/d82e9f9b649b4cca27...
> * missing: Failing-Unit-Tests-secure-storage-related-MASTER-ONLY https://github.com/jbosstools/jbosstools-server/commit/d84d2b1278ea946659...
> * missing: JBIDE-24043-upversion-master https://github.com/jbosstools/jbosstools-server/commit/e3a065a0ea76caae92...
> * missing: JBIDE-24029-JBIDE-24031 https://github.com/jbosstools/jbosstools-server/commit/778cc2dc271e5fef9b...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/82d51ba3185088bc21...
> *** Inspect the difference between the two patches: http://sprunge.us/RMNB
> * missing: JBIDE-23956-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-server/commit/442b33bc7e241b7e96...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server 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-24410) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [LiveReload]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24410:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [LiveReload]
Key: JBIDE-24410
URL: https://issues.jboss.org/browse/JBIDE-24410
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [LiveReload]: 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-livereload at https://github.com/jbosstools/jbosstools-livereload
Searching for commits present in master and missing from jbosstools-4.4.x
Commit hash "f8c816" is the last common ancestor of master and jbosstools-4.4.x
f8c816 is 3 commits ago in branch jbosstools-4.4.x
f8c816 is 3 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: JBIDE-24007-move-up-to-Jetty-9.4.0-9.4.1-137 https://github.com/jbosstools/jbosstools-livereload/commit/991c884493689f...
* missing: JBIDE-23954-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-livereload/commit/0036fd533226b4...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for LiveReload 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-24409) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Freemarker]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24409?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24409:
----------------------------------
Assignee: Jeff MAURY
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Freemarker]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24409
> URL: https://issues.jboss.org/browse/JBIDE-24409
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
>
> For JBIDE 4.4.4.Final [Freemarker]: 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-freemarker at https://github.com/jbosstools/jbosstools-freemarker
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "63fa6e" is the last common ancestor of master and jbosstools-4.4.x
> 63fa6e is 3 commits ago in branch jbosstools-4.4.x
> 63fa6e is 2 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-23950-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-freemarker/commit/a3dd2ef81f7f7b...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Freemarker 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