December 2016 - jbosstools-issues

[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: ------------------------------- Sprint: devex #125 December 2017 (was: devex #124 December 2017) > [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.4.3.AM2 > > > 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Sprint: devex #125 December 2017 (was: devex #124 December 2017) > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Sprint: devex #125 December 2017 (was: devex #124 December 2017) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20177: ------------------------------- Sprint: (was: devex #124 December 2017) > migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20177 > URL: https://issues.jboss.org/browse/JBIDE-20177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > If we can migrate this logic into the mojo... > {code} > if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then > {code} > ... we'll be able to remove this step in all jobs: > {code} > <hudson.tasks.Maven> > <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets> > <mavenName>maven-3.2.5</mavenName> > <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip > outputDirectory=${WORKSPACE}/sources > trimVersion=true > mdep.stripClassifier=true > mdep.stripVersion=true</properties> > <usePrivateRepository>false</usePrivateRepository> > <settings class="jenkins.mvn.DefaultSettingsProvider"/> > <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/> > </hudson.tasks.Maven> > {code} > ... and instead, just pass in those vars to maven: > {code} > -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing} > -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo > -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23515: ------------------------------- Sprint: devex #125 December 2017 (was: devex #124 December 2017) > Create and use Neon.2 target platform > ------------------------------------- > > Key: JBIDE-23515 > URL: https://issues.jboss.org/browse/JBIDE-23515 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.3.Final > > > Once available in December, we should move up to Neon.2 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-476) User can install software from market without acceptation license agreements [EBZ#509500]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-476?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-476: --------------------------- Fix Version/s: Neon.3 (4.6) > User can install software from market without acceptation license agreements [EBZ#509500] > ----------------------------------------------------------------------------------------- > > Key: ERT-476 > URL: https://issues.jboss.org/browse/ERT-476 > Project: Eclipse Release Train > Issue Type: Task > Components: MPC > Reporter: Friendly Jira Robot > Labels: Marketplace, bzira > Fix For: Neon.3 (4.6) > > > Created attachment 265962 > The "Review Licenses" window where the "Finish" button is available though the licence is not accepted. > User can install Red Hat JBoss Developer Studio from Eclipse Marketplace without acceptation terms of the licence agreements. > Step to reproduce: > 1) Download, unpack and start Eclipse Neon 1 > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... > 2) Help -> Eclipse Marketplace -> Search for "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install > 3) The window "Review Licenses" looks like on the attached screenshot > 4) Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install Developer Studio. > When I click "I accept..." radio button and then switch back to "I do not accept..." it starts work correctly. So, the availability of the 'Finish' button is evaluated badly only in initial state. > I tried to remove ~/.eclipse directory and start Eclipse with new workspace but it didn't solve my problem. > This problem doesn't occur when installing JBoss Tools. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-476) User can install software from market without acceptation license agreements [EBZ#509500]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-476?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot updated ERT-476: ------------------------------------ Component/s: MPC (was: Community) > User can install software from market without acceptation license agreements [EBZ#509500] > ----------------------------------------------------------------------------------------- > > Key: ERT-476 > URL: https://issues.jboss.org/browse/ERT-476 > Project: Eclipse Release Train > Issue Type: Task > Components: MPC > Reporter: Friendly Jira Robot > Labels: Marketplace, bzira > > Created attachment 265962 > The "Review Licenses" window where the "Finish" button is available though the licence is not accepted. > User can install Red Hat JBoss Developer Studio from Eclipse Marketplace without acceptation terms of the licence agreements. > Step to reproduce: > 1) Download, unpack and start Eclipse Neon 1 > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... > 2) Help -> Eclipse Marketplace -> Search for "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install > 3) The window "Review Licenses" looks like on the attached screenshot > 4) Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install Developer Studio. > When I click "I accept..." radio button and then switch back to "I do not accept..." it starts work correctly. So, the availability of the 'Finish' button is evaluated badly only in initial state. > I tried to remove ~/.eclipse directory and start Eclipse with new workspace but it didn't solve my problem. > This problem doesn't occur when installing JBoss Tools. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23021: ------------------------------------ Added into https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... using getProjectSHAs.sh script and some minor adjustments. Resolving. Future enhancements can be done in other issues. > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4227: ---------------------------------- Try ssh into the VM and get the docker and openshift services status. Or use vagrant service-manager also > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Attachments: hs_err_pid13472.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4230) JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4230?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4230: --------------------------------- Component/s: upstream > JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4230 > URL: https://issues.jboss.org/browse/JBDS-4230 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 25 with Wayland > Reporter: Ricardo Martinelli Oliveira > > Workaround: Add GDK_BACKEND=x11 in devstudio.ini file to force use x11 to run JBDS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016