[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM2
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19715:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.5.0.AM2
>
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-20850.
------------------------------
Resolution: Won't Fix
Won't fix. Too much else to worry about.
> target platform matrix job's install test step fails silently when using incompatible Eclipse version
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20850
> URL: https://issues.jboss.org/browse/JBIDE-20850
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.5.0.AM1
>
>
> For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform:
> {code}
> [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554)
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158)
>
> BUILD FAILED
> /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> {code}
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034)
> [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859)
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> And yet the build is successful here:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> This is most likely because all three configs are set to use the same Eclipse JEE bundle:
> {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz
> {code}
> So... I guess there are two things we need here:
> a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1
> b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months