June 2016 - jbosstools-issues - Jboss List Archives

[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: ------------------------------- Sprint: devex #116 June 2016 > 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.4.x > > > 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 (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[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 updated JBIDE-20850: ------------------------------- Sprint: devex #116 June 2016 > 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.4.x > > > 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 (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16158: ------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #115 May 2016, devex #117 June 2016 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #115 May 2016, devex #116 June 2016) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22229: ------------------------------- Sprint: devex #115 May 2016, devex #117 June 2016 (was: devex #115 May 2016, devex #116 June 2016) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-309) [terminal] Provide extension point to interpret command like refresh IResource created with the local terminal [EBZ#496109]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-309: --------------------------------------- Summary: [terminal] Provide extension point to interpret command like refresh IResource created with the local terminal [EBZ#496109] Key: ERT-309 URL: https://issues.jboss.org/browse/ERT-309 Project: Eclipse Release Train Issue Type: Task Components: Target Management Reporter: Friendly Jira Robot I'm studying how to provide an Angular2 console to support features of https://github.com/angular/angular-cli For instance you can set the command: * ng new myproject And angular-cli initialize an Angular2 project. I could do that with a standard console but I would like to do that with terminal because it supports several thing like completion wuth tab, coloration, etc So my idea is to capture the command "ng new myproject" and wait for that this command is finished to refresh the IProject projectname. After debugging tm, I have noticed that it exists ITerminalServiceOutputStreamMonitorListener that I could use it to catch typped command like "ng new myproject". Those listener are getted with: ------------------------------------------- ITerminalServiceOutputStreamMonitorListener[] stdoutListeners = (ITerminalServiceOutputStreamMonitorListener[])properties.get(ITerminalsConnectorConstants.PROP_STDOUT_LISTENERS); ------------------------------------------- But I have not found how to contribute to this list of ITerminalServiceOutputStreamMonitorListener? Have you an idea how to do contribute to list of ITerminalServiceOutputStreamMonitorListenerfor Local terminal. Must I create my own LocalLauncherDelegate to put this list listeners in the execute LocalLauncherDelegate#method? Many thanks for your help! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22452) Application Wizard: Git reference text widget does not validate values

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22452?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22452: -------------------------------- Story Points: 2 > Application Wizard: Git reference text widget does not validate values > ---------------------------------------------------------------------- > > Key: JBIDE-22452 > URL: https://issues.jboss.org/browse/JBIDE-22452 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > > On the Build Configuration wizard page there is a text widget for git reference. Tooltip say there could be put branch, tag or commit. There is no validation at the moment. Although the field is optional, it would be nice if there is any value, it would be validated. Commits are hexadecimal values what is less restrictive then tags or branches. For tag and branches see reference at https://git-scm.com/docs/git-check-ref-format or use "git check-ref-format --help". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-308) 1-818-850-7806 Gmail Customer Service Phone Number, Hotmail Customer Service Phone Number

by suraj 247 (JIRA)

suraj 247 created ERT-308: ----------------------------- Summary: 1-818-850-7806 Gmail Customer Service Phone Number,Hotmail Customer Service Phone Number Key: ERT-308 URL: https://issues.jboss.org/browse/ERT-308 Project: Eclipse Release Train Issue Type: Bug Reporter: suraj 247 Attachments: gmail password change.jpg, hotmail contact number.jpg Hotmail Technical Support Number <<1-818-850-7806>> Set Up a Hotmail Account <<1-818-850-7806>> How Do I Change My Hotmail Password <<1-818-850-7806>> my hotmail account has been hacked <<1-818-850-7806>> retrieve hotmail password <<1-818-850-7806>> hotmail login help <<1-818-850-7806>> hotmail customer support phone number <<1-818-850-7806>> hotmail settings <<1-818-850-7806>> gmail phone number {{1-818-850-7806}} gmail tech support {{1-818-850-7806}} gmail support number {{1-818-850-7806}} gmail help phone number {{1-818-850-7806}} gmail contact number {{1-818-850-7806}} contact gmail support {{1-818-850-7806}} gmail technical support {{1-818-850-7806}} gmail support email {{1-818-850-7806}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22614) NPE in CDIProject.rebuildXML(CDIProject.java:1458)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22614?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22614: ----------------------------------- Fix Version/s: 4.4.x > NPE in CDIProject.rebuildXML(CDIProject.java:1458) > -------------------------------------------------- > > Key: JBIDE-22614 > URL: https://issues.jboss.org/browse/JBIDE-22614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Aurélien Pupier > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > I'm currently trying to write some integration tests and found this NPE in log. > {noformat} > !ENTRY org.eclipse.core.resources 4 2 2016-06-17 15:43:54.521 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildXML(CDIProject.java:1458) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1214) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > i'm not sure about the impact yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22614) NPE in CDIProject.rebuildXML(CDIProject.java:1458)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22614?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22614: -------------------------------------- Assignee: Viacheslav Kabanovich > NPE in CDIProject.rebuildXML(CDIProject.java:1458) > -------------------------------------------------- > > Key: JBIDE-22614 > URL: https://issues.jboss.org/browse/JBIDE-22614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Aurélien Pupier > Assignee: Viacheslav Kabanovich > > I'm currently trying to write some integration tests and found this NPE in log. > {noformat} > !ENTRY org.eclipse.core.resources 4 2 2016-06-17 15:43:54.521 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildXML(CDIProject.java:1458) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1214) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > i'm not sure about the impact yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3953: -------------------------------------- thanks [~akurtako] for the workaround! I created a follow-up on the problem with central - JBIDE-22616 > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.x > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016