May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-19056. ---------------------------------- > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17991) Generalize usage of Sonar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17991?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17991: --------------------------------------- [~mickael_istria], I'm not sure about this JIRA, can it be closed? Thanks! > Generalize usage of Sonar > ------------------------- > > Key: JBIDE-17991 > URL: https://issues.jboss.org/browse/JBIDE-17991 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We should generalize SonarQube usage for all JBoss Tools components. > To do so we need to: > * Create jobs for all components > * Get access to a SonarQube manager account to manage rules we want or don't want: https://engineering.redhat.com/rt/Ticket/Display.html?id=308405 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19056: --------------------------------------- [~mickael_istria], I'm not sure about this JIRA, can it be closed? Thanks! > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19219) Install Grinder doesn't support Oomph popups

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19219?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19219. --------------------------------- I assume this is done and working. Closing. > Install Grinder doesn't support Oomph popups > -------------------------------------------- > > Key: JBIDE-19219 > URL: https://issues.jboss.org/browse/JBIDE-19219 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > With the introduction of Oomph, install-grinder now faces many popups and pages that it doesn't know how to deal with. > Either we have to rework it to support Oomph, or we have to find a way to disable Oomph. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18795) Birt build fails in master

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18795?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18795. --------------------------------- I verified that the build passed recently (May 22). So I assume this worked for Alpha1. Right now it is failing, but I checked the console itself and the build is actually ok, but for some reason the workspace log is missing so the artifact archiver fails to save it. > Birt build fails in master > -------------------------- > > Key: JBIDE-18795 > URL: https://issues.jboss.org/browse/JBIDE-18795 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.3.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.0.Alpha1 > > > The birt build fails because the org.hibernate.eclipse.libs plugin has been removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19641: --------------------------------------- [~rob.stryker], I tried this again today on OS X and JBoss Tools 4.3.0.Alpha2 and still the same result - at the beginning I can see disk activity -> the content is copied over on the disk. But then the disk activity stops and the percentage is slowly moving, but nothing is happening. It will never succeed. I tried the same on RHEL 7 with OpenJDK 1.8 and JBDS 9.0.0.Beta1 nightly (from May 22) and the embedded EAP 6.4 and I get exactly the same result. I am merely following the steps from this JIRA. I would love to be able to give you some stacktrace or something, but I don't have any. Do you have a suggestion how I can get something for you? > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19750: ---------------------------------------- eng-ops has installed libwebkitgtk3 on some slaves, but installation now seems to be failing earlier and for a new reason "Getting a lock required more than 10000 ms. There might be a synchronization problem in this callstack or just the build/dispose process of some components took too long!" It's still working for me locally. > Install grinder fails to run on RHEL7: No more handles! > ------------------------------------------------------- > > Key: JBIDE-19750 > URL: https://issues.jboss.org/browse/JBIDE-19750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > {code} > 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301. > ... > 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet] > 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec > 13:43:18 > 13:43:18 Testcase: testInstall took 252.166 sec > {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests. > Wondering if ... > a) passing through a different *swt.browser.DefaultType*, &/or > b) using a newer SWTBot (which works with Luna [1] now?) > ... might help. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19711: --------------------------------------------- we are past M7. We are targeting RC1, but sounds like we can't hook this in anyway before Eclipse SR1 becomes something we can use (after our Beta2). > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19720. ------------------------------- Verified with JBT 4.3.0-Beta1-v20150527-0620-B9985 > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17" > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.0.Beta1 > > > {code} > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > Another code path: > {code} > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-19852: ------------------------------------------------- Thomas Hauser <thauser(a)redhat.com> changed the Status of [bug 1225450|https://bugzilla.redhat.com/show_bug.cgi?id=1225450] from NEW to ASSIGNED > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015