June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19890) compilation failure: The method release() is undefined for the type RevWalk

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19890: ---------------------------------------- Summary: compilation failure: The method release() is undefined for the type RevWalk Key: JBIDE-19890 URL: https://issues.jboss.org/browse/JBIDE-19890 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Compiling openshift currently fails with the following maven error: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[451] [ERROR] rw.release(); [ERROR] ^^^^^^^ [ERROR] The method release() is undefined for the type RevWalk [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[454] [ERROR] tw.release(); [ERROR] ^^^^^^^ [ERROR] The method release() is undefined for the type TreeWalk [ERROR] 2 problems (2 errors) [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) 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: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:418) at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19820: ----------------------------------------------- In my case validation adds 2 to 4 minutes and this contribution to time changes more from start to start than importing without it. > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta1 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2849) Document Offline Usage

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-2849. ------------------------------ > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.0.Beta2 > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: JBDS80_Approved_Scope > Fix For: 8.1.0.GA > > > Working with the Training team, document how JBDS is to be used in an offline state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2849) Document Offline Usage

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2849: ------------------------------- Fix Version/s: 8.1.0.GA > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.0.Beta2 > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: JBDS80_Approved_Scope > Fix For: 8.1.0.GA > > > Working with the Training team, document how JBDS is to be used in an offline state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2849) Document Offline Usage

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Len DiMaggio resolved JBDS-2849. -------------------------------- Resolution: Done > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.0.Beta2 > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: JBDS80_Approved_Scope > Fix For: 8.1.0.GA > > > Working with the Training team, document how JBDS is to be used in an offline state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19829: ---------------------------------- Agreed. This was going to be part of the cleanup work that needs to be done. -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering Red Hat Office: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Add Oauth support to the Openshift Connection Wizard > ---------------------------------------------------- > > Key: JBIDE-19829 > URL: https://issues.jboss.org/browse/JBIDE-19829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png > > > Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth > * Remove server type verify button > * Add v3 auth box (Auto/OAuth/Basic) > * Optional... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19829: ---------------------------------- I dont know when v1beta1 will be dropped. I'll see if I can find out today. -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering Red Hat Office: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Add Oauth support to the Openshift Connection Wizard > ---------------------------------------------------- > > Key: JBIDE-19829 > URL: https://issues.jboss.org/browse/JBIDE-19829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png > > > Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth > * Remove server type verify button > * Add v3 auth box (Auto/OAuth/Basic) > * Optional... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19820: ------------------------------------------ Im importing with validation enabled. numbers before fix: M6 628,575,577,612 (in seconds) = average 598s M6+ batch feature: 843,832,924,877 (in seconds) = average 869s M6 + CDI 794,712 = average 753s after fix M7 632,691,651,638 = 653s M7 + batch feature 792,750,726,800 = 767s M7 + CDI feature 778, 738 = 758s I will measure with validation off. But different machine will have some impact on these numbers too. > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta1 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19786: --------------------------------------------- what is ETA of when staging will have recent update/release ? > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19463: --------------------------------------------- I dont follow why it is a problem when we already talk JMX to the server. If this was for some completely unknown server I grok there is an issue, but why is it not working for servers we *do know* ? And how is this different from former jmx UI code where I could connect to remote servers ? Sorry for the questions but trying to grok what is causing the problem of simply being able to connect ? browsing custom types is a different issue. > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- 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 June 2015