March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3391: -------------------------------- Issue Type: Bug (was: Enhancement) > Installer should not require UI to report errors in automated mode > ------------------------------------------------------------------ > > Key: JBDS-3391 > URL: https://issues.jboss.org/browse/JBDS-3391 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18666) Central search for customer portal doesnt work

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18666?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18666: --------------------------------- Attachment: portal.png Closing as this is working now - JBDS 8.1.0.GA > Central search for customer portal doesnt work > ---------------------------------------------- > > Key: JBIDE-18666 > URL: https://issues.jboss.org/browse/JBIDE-18666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.2.Final, 4.2.0.CR2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > Attachments: portal.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3391: ----------------------------- CDW release: + (was: ?) > Installer should not require UI to report errors in automated mode > ------------------------------------------------------------------ > > Key: JBDS-3391 > URL: https://issues.jboss.org/browse/JBDS-3391 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3391: -------------------------------- > Installer should not require UI to report errors in automated mode > ------------------------------------------------------------------ > > Key: JBDS-3391 > URL: https://issues.jboss.org/browse/JBDS-3391 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3391: -------------------------------- CDW qa_ack: + (was: ?) > Installer should not require UI to report errors in automated mode > ------------------------------------------------------------------ > > Key: JBDS-3391 > URL: https://issues.jboss.org/browse/JBDS-3391 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3391: -------------------------------- Issue Type: Enhancement (was: Bug) > Installer should not require UI to report errors in automated mode > ------------------------------------------------------------------ > > Key: JBDS-3391 > URL: https://issues.jboss.org/browse/JBDS-3391 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19537) Document some of known problems in VPE FAQ related to using WebKit based internal browser

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19537?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19537: ------------------------------------------------ I add this question to FAQ, Denis, please take a look into PR. Disabling this feature for Linux is not very good idea. But this problem can be partially resolved after removing XULRunner, it will give us a chance to use SWT.Mozilla on some Linux distros. > Document some of known problems in VPE FAQ related to using WebKit based internal browser > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19537 > URL: https://issues.jboss.org/browse/JBIDE-19537 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.3.Final > > > In latest 4.2.3.CR1 selecting "Change to HTML5" option in Browser Engine dialog sometime leads to problems after restart under Linux. It looks really bad because eclipse just disappear, never come back and there is no any trace of problem in logs. For me the reason was bluejeans.*.so files installed as part of BlueJeans. I also remember there was problem reported with google talk plugin. > This should at least be documented in FAQ as known problems. Another more restrictive option is disable this feature for Linux completely. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19513: --------------------------------------- [~ibuziuk], [~mickael_istria] Yes, actually I need the websocket.client bundle to run my JUnit tests (the test starts a websocket client that connects to the Livereload server). I guess this will be done in a second PR for JBIDE-19497, right ? Thanks > multiple versions of jetty and java.servlet plugins in JBDS 9 > ------------------------------------------------------------- > > Key: JBIDE-19513 > URL: https://issues.jboss.org/browse/JBIDE-19513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa, target-platform, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha2 > > > These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix. > {code} > org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5 > org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5 > - and - > javax.servlet_3.1.0.v201410161800 and 3.0.0{code} > Pre-existing ignored/known issues: > {code} > org.eclipse.jdt.annotation_1.1.100.v20140704-0625 > com.jcraft.jsch_0.1.50.v201403120620 > org.apache.commons.logging_1.0.4.v201101211617 > javax.wsdl_1.5.1.v201012040544 {code} > See detailed reports here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18250) ESB 4.2.x build issue

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18250?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-18250. -------------------------------- Fixed in December 2014 - closing. > ESB 4.2.x build issue > --------------------- > > Key: JBIDE-18250 > URL: https://issues.jboss.org/browse/JBIDE-18250 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.2.0.Beta3 > Reporter: Brian Fitzpatrick > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR1 > > > Looking into 4.2.x ESB build issue: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/32/ > {code} > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...> > at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:84) > at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:65) > at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:55) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:212) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:146) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:119) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1) > at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:215) > at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:100) > at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > ... 11 more > Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location > at org.eclipse.tycho.p2.target.TargetDefinitionResolver.getUnitInstance(TargetDefinitionResolver.java:213) > at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:127) > at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:79) > ... 22 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17618) Server start button disabled after Eclipse restart

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17618?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-17618. -------------------------------- Not reproducible - closing > Server start button disabled after Eclipse restart > -------------------------------------------------- > > Key: JBIDE-17618 > URL: https://issues.jboss.org/browse/JBIDE-17618 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.2.Final > > Attachments: disabled-server-start.png > > > When you restart Eclipse with the Server View open, right after the IDE start, the first server will be selected, but the Start button cannot be clicked. > !disabled-server-start.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2015