[JBoss JIRA] (JBDS-4364) Conflict org.testng.eclipse 6.9.13. vs 6.11.0.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4364?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4364:
----------------------------------
So... RHSCL contains org.testng.eclipse 6.9.13, but we have something newer in Central. Why is that a problem?
Central is designed to be able to provide newer 3rd party deps than the platform.
Are you saying we need to push TestNG 6.11 into RHSCL 2.4, so that Central and RHEL 7 have the same version? If so, the version in Central becomes unnecessary. :)
cc: [~mat.booth]
> Conflict org.testng.eclipse 6.9.13. vs 6.11.0.
> ----------------------------------------------
>
> Key: JBDS-4364
> URL: https://issues.jboss.org/browse/JBDS-4364
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: OS: RHEL7
> RHSCL: http://download.eng.brq.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1.0/compos...
> Devstudio: rh-eclipse46-devstudio 10.4-0.20170421.0123.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
>
> It is possible to update TestNG via RH Central.
> # RH Central -> Software/Update
> # Enable Early Access
> # *Show installed*
> # Find "TestNG" there is written "Installed, update available"
> # Select TestNG and install updates
> # Restart
> # Then this error message will appear in the log:
> {code}
> !ENTRY org.testng.eclipse 4 0 2017-04-21 05:21:07.715
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.testng.eclipse [1649]
> Another singleton bundle selected: osgi.identity; osgi.identity="org.testng.eclipse"; type="osgi.bundle"; version:Version="6.11.0.201703011520"; singleton:="true"
> {code}
> Log: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Central constains org.testng.eclipse 6.11.0.201703011520, RPM contains 6.9.13.201701201452.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4377:
----------------------------------
Well, your commandline approach lists the IUs to install explicitly. Since I added a 3rd top-level IU into the mix, you simply needed to pass that one in too.
What happens if you omit the -i flag completely? Will it just do the default and install all three?
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
> So we need to figure out how to include BOTH versions in the installer jar.
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4357:
-----------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.AM3)
> 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: Nick Boldt
> 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] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4357:
--------------------------------
Assignee: Lukáš Valach (was: Nick Boldt)
> 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-24368) Visual Editor New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24368:
----------------------------------
Summary: Visual Editor New and Noteworthy for 4.4.4.Final
Key: JBIDE-24368
URL: https://issues.jboss.org/browse/JBIDE-24368
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-templates, visual-page-editor-core
Reporter: Jeff MAURY
Priority: Critical
Ilya Buziuk,
Search for your component's New and Noteworthy issues:
Queries:
* [Completed Visual Editor 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 Visual Editor, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
Document the ones relevant for Visual Editor 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 Visual Editor 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 Visual Editor 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 Visual Editor, 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