August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24798) ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24798: ---------------------------------- Summary: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) Key: JBIDE-24798 URL: https://issues.jboss.org/browse/JBIDE-24798 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim, build, updatesite Affects Versions: 4.5.0.Final Reporter: Nick Boldt Priority: Critical After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata). https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24798) ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24798: ---------------------------------- Assignee: Nick Boldt > ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24798 > URL: https://issues.jboss.org/browse/JBIDE-24798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, build, updatesite > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > > After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata). > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4498) Multiple BundleExceptions in the log

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4498?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4498: ---------------------------------- The removal of lpgjavaruntime happened as a consequence of rebuilding locally as part of this commit https://github.com/jbdevstudio/jbdevstudio-product/commit/4828673f4e8935e... But I'm not sure WHY those were removed. I'm happy to add them back if you think that's better. > Multiple BundleExceptions in the log > ------------------------------------ > > Key: JBDS-4498 > URL: https://issues.jboss.org/browse/JBDS-4498 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: rh-eclipse47.log_clean_start_strict.txt > > > There are multiple errors in the log after start of 11.0-0.20170804.0022.el7. See the log: > [^rh-eclipse47.log_clean_start_strict.txt] > Interesting is that these errors dissapeared after installation of everything from Central. Maybe we really missing something? > Start of clean Devstudio (and then installation from Central): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Start after installation from Central (no bundleException): > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[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.1.0.AM2 (was: 11.0.0.GA) > 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.1.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24673) install tests (central, EA) are broken and failing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24673?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24673. ------------------------------ Resolution: Done Fixed. > install tests (central, EA) are broken and failing > --------------------------------------------------- > > Key: JBIDE-24673 > URL: https://issues.jboss.org/browse/JBIDE-24673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, updatesite > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Checking these test jobs, I see they've been red for a while but no one has noticed. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So, a few things need to be done here: > a) make the tests pass > b) ensure emails are sent for unexpected failures to jbosstools-dev, nboldt, jmaury -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.x > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup for Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4488: ----------------------------- Fix Version/s: 11.1.0.AM2 > Very slow initial startup for Eclipse > ------------------------------------- > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.1.0.AM2 > > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4498) Multiple BundleExceptions in the log

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4498?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4498: ------------------------------------ I think that we are missing net.sourceforge.lpg.lpgjavaruntime, I have installed it using this command \[1\] and start eclipse again. Now I haven't any error in the log. \[1\] ./eclipse -consolelog -console -debug -clean -application org.eclipse.equinox.p2.director -r https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.2.Fin... -i net.sourceforge.lpg.lpgjavaruntime There is content of ./eclipse/platform.../plugins: {code} net.sourceforge.lpg.lpgjavaruntime_1.1.0.v201004271650.jar org.apache.commons.lang_2.6.0.v201404270220.jar org.apache.lucene.core_3.5.0.v20120725-1805.jar org.glassfish.hk2.osgi-resource-locator_2.5.0.v20161103-1916.jar org.glassfish.jersey.bundles.repackaged.jersey-guava_2.22.1.v20161103-1916.jar org.glassfish.jersey.core.jersey-common_2.22.1.v20161103-1916.jar {code} I am not sure if it is important for you, but I see that it also installed "org.apache.lucene.core 3.5.0.v20120725-1805" which was mentioned in the log. We have it in another version: /opt/rh/rh-eclipse47/root/usr/lib/eclipse/plugins/org.apache.lucene.core_6.1.0.jar > Multiple BundleExceptions in the log > ------------------------------------ > > Key: JBDS-4498 > URL: https://issues.jboss.org/browse/JBDS-4498 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: rh-eclipse47.log_clean_start_strict.txt > > > There are multiple errors in the log after start of 11.0-0.20170804.0022.el7. See the log: > [^rh-eclipse47.log_clean_start_strict.txt] > Interesting is that these errors dissapeared after installation of everything from Central. Maybe we really missing something? > Start of clean Devstudio (and then installation from Central): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Start after installation from Central (no bundleException): > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1156) Prepare Marketplace entry for Integration Stack 11.0.0.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1156?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1156: ------------------------------------------ I agree > Prepare Marketplace entry for Integration Stack 11.0.0.GA > --------------------------------------------------------- > > Key: JBTIS-1156 > URL: https://issues.jboss.org/browse/JBTIS-1156 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 11.0.0.GA > > > Prepare Marketplace entry for Integration Stack 11.0.0.GA. > [~pleacu] what categories will be available? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1156) Prepare Marketplace entry for Integration Stack 11.0.0.GA

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1156?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1156: ----------------------------------- Hey [~apodhrad] I was thinking of having these categories for Devstudio IS 11.0.0.GA com.jboss.devstudio.core.feature - required com.jboss.devstudio.integration-stack.bpr.feature - optional com.jboss.devstudio.integration-stack.soa.feature - optional Since SwitchYard is deprecated I was not going to have it have its own category. It''ll be available through the soa feature. The ds.feature will be gone for this release and back in the next one. wdyt? > Prepare Marketplace entry for Integration Stack 11.0.0.GA > --------------------------------------------------------- > > Key: JBTIS-1156 > URL: https://issues.jboss.org/browse/JBTIS-1156 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 11.0.0.GA > > > Prepare Marketplace entry for Integration Stack 11.0.0.GA. > [~pleacu] what categories will be available? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017