August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24798) Testing: 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 commented on JBIDE-24798: ------------------------------------ Last time Browsersim got an actual code change was on Feb 27, 2017 so this is hardly an urgent requirement. However, the last time Browsersim 3.8.4 snapshot was pushed to Nexus [1] was on Aug 2, 2017, which suggests we're missing two more commits [2] in August. [1] https://repository.jboss.org/nexus/#nexus-search;gav~~browsersim~~~ [2] https://github.com/jbosstools/jbosstools-browsersim/commits/master And I don't see recent browsersim zips here, either: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... > Testing: 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 > Fix For: 4.5.1.AM2 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24798) Testing: 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 updated JBIDE-24798: ------------------------------- Priority: Minor (was: Critical) > Testing: 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: Minor > Fix For: 4.5.1.AM2 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23510: ------------------------------------ Hey [~fbricon] when do you plan to release pde.source.lookup feature 0.0.4? > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM1) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23272) Make target platform update process better

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23272?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23272. ------------------------------ Resolution: Done Child tasks are all done (except JBIDE-22620). > Make target platform update process better > ------------------------------------------ > > Key: JBIDE-23272 > URL: https://issues.jboss.org/browse/JBIDE-23272 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Epic to collect the issues related to TP maintenance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3894) Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3894: ----------------------------- Fix Version/s: 11.1.0.AM2 (was: 11.1.0.AM1) > Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio > --------------------------------------------------------------------- > > Key: JBDS-3894 > URL: https://issues.jboss.org/browse/JBDS-3894 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central-update, target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM2 > > > In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds. > Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4499) Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4499?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4499: ----------------------------- Fix Version/s: 11.1.0.AM2 (was: 11.1.0.AM1) > Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher > --------------------------------------------------------------- > > Key: JBDS-4499 > URL: https://issues.jboss.org/browse/JBDS-4499 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.GA > Environment: DevTools repository: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-1.0-rh-ecli... > Devstudio repository: https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.1.0.AM2 > > > I have installed last staged build \[1\] and now I have this error message in the log after start: > {code} > !ENTRY org.eclipse.linuxtools.jdt.docker.launcher 4 0 2017-08-07 12:04:20.933 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.jdt.docker.launcher [1118] > Another singleton bundle selected: osgi.identity; osgi.identity="org.eclipse.linuxtools.jdt.docker.launcher"; type="osgi.bundle"; version:Version="1.0.0.201708031854"; singleton:="true" > at org.eclipse.osgi.container.Module.start(Module.java:444) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > {code} > \[1\] https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... > Content of /opt/rh/rh-eclipse47 > {code} > find /opt/rh/rh-eclipse47/ -iname "*org.eclipse.linuxtools.jdt.docker.launcher*" > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher.source_1.0.0.201708031854.jar > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708031854.jar > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708010032.jar > {code} > I don't see any impact to the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24843) Update description of org.jboss.tools.cdi.xml and xml.ui plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24843?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24843: ------------------------------------ PR for next sprint: https://github.com/jbosstools/jbosstools-javaee/pull/442 > Update description of org.jboss.tools.cdi.xml and xml.ui plugins > ---------------------------------------------------------------- > > Key: JBIDE-24843 > URL: https://issues.jboss.org/browse/JBIDE-24843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, updatesite > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > This is a followup of JBDS-4495 . We deprecated seam 3 and moved it to central. We wanted to keep cdi itself still in the coretools feature. > But there are these two plugins: > org.jboss.tools.cdi.xml.ui_1.8.100.v20170801-1456.jar > org.jboss.tools.cdi.xml_1.8.100.v20170801-1421.jar > They don't have seam in the name, but their descriptions say: > JBoss Tools Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Jeff checked the code and it doesn't seem like this has anything to do with Seam, so we should change the description. > I'm not sure myself what to call them -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24653) Update Central to include latest Windup built with Oxygen

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24653?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24653: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM1) > Update Central to include latest Windup built with Oxygen > --------------------------------------------------------- > > Key: JBIDE-24653 > URL: https://issues.jboss.org/browse/JBIDE-24653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central-update > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > Once [~jsteele] has it ready, update Central to include the latest Windup bits built with Oxygen. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24844: ------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.1.AM1) > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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