[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21294:
-------------------------------------
yeah why do we keep coding bugs? That's inacceptable! :-)
> NPE when starting CDK server
> ----------------------------
>
> Key: JBIDE-21294
> URL: https://issues.jboss.org/browse/JBIDE-21294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21294:
---------------------------------------
[~fbricon], yes, that's what I realized when I saw the field empty.
So there are two issues:
1. Why is vagrant location empty when it worked for me in other instances?
2. Why is there am ugly NPE if it's empty? There should be a basic check if the field is empty.
> NPE when starting CDK server
> ----------------------------
>
> Key: JBIDE-21294
> URL: https://issues.jboss.org/browse/JBIDE-21294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21284) compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21284?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21284:
------------------------------------
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=1459 spinning against master.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=123 spinning against 4.3.1.Beta1x branch.
> compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21284
> URL: https://issues.jboss.org/browse/JBIDE-21284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4": For input string: "raw:4" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> 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: org.apache.maven.plugin.MojoFailureException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:176)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.osgi.framework.Version.parseInt(Version.java:170)
> at org.osgi.framework.Version.<init>(Version.java:126)
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:120)
> ... 21 more
> Caused by: java.lang.NumberFormatException: For input string: "raw:4"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.osgi.framework.Version.parseInt(Version.java:168)
> ... 23 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21284) compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21284?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21284:
-------------------------------
Fix Version/s: 4.3.1.Beta2
> compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21284
> URL: https://issues.jboss.org/browse/JBIDE-21284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4": For input string: "raw:4" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> 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: org.apache.maven.plugin.MojoFailureException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:176)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4"
> at org.osgi.framework.Version.parseInt(Version.java:170)
> at org.osgi.framework.Version.<init>(Version.java:126)
> at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:120)
> ... 21 more
> Caused by: java.lang.NumberFormatException: For input string: "raw:4"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.osgi.framework.Version.parseInt(Version.java:168)
> ... 23 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21294:
-------------------------------------
it fails in the File constructor because vagrantLoc is null :
{code}
String vagrantLoc = CDKConstantUtility.getVagrantLocation(s);
if( s == null || !(new File(vagrantLoc).exists())) {
{code}
> NPE when starting CDK server
> ----------------------------
>
> Key: JBIDE-21294
> URL: https://issues.jboss.org/browse/JBIDE-21294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
by Martin Malina (JIRA)
Martin Malina created JBIDE-21294:
-------------------------------------
Summary: NPE when starting CDK server
Key: JBIDE-21294
URL: https://issues.jboss.org/browse/JBIDE-21294
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
{code}
An internal error occurred during: "Starting cdk-v2 CDK Server".
java.lang.NullPointerException
at java.io.File.<init>(File.java:277)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
I did add the user credentials in the server editor.
Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
[1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21072) Application wizard: Server templates tree is not rendered
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21072?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-21072:
---------------------------------------
I think the patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=465280 fixes the issue. The patch has been applied, but the bug is reopened and the patch can be reverted.
I propose to keep the workaround for now.
> Application wizard: Server templates tree is not rendered
> ---------------------------------------------------------
>
> Key: JBIDE-21072
> URL: https://issues.jboss.org/browse/JBIDE-21072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3, upstream
> Fix For: 4.3.1.Beta1
>
> Attachments: wizard.png
>
>
> When I select at first a local template then proceed to next wizard page in a New OpenShift Application wizard and hit back button then tree containing server templates is not rendered correctly. Only search text field is shown but the tree with templates is missing there.
> !wizard.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3565:
----------------------------------
We could include SOME of the TP; much of it is already in the installer jar. So I'll take some time to figure out what deps are missing and throw a PR at [~pleacu] to get those missing deps added into his JBDS IS TP.
> Include Target Platform Zip with JBDS for offline install on CSP
> ----------------------------------------------------------------
>
> Key: JBDS-3565
> URL: https://issues.jboss.org/browse/JBDS-3565
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta1
> Environment: Customer Support Portal
> Reporter: Mustafa Musaji
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2
>
>
> Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip.
> This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months