Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[milo-dev] Milo setup problems

Dear Milo community,

 

I am trying to set up Milo in Eclipse. I have checked it out over “Import …” -> Maven/Check out Maven Projects from SCM.

However, I am facing the following difficulties:

1)      In the “bsd-parser-core” and “bsd-parser-gson” projects, the imports in the under org.opcfoundation cannot be resolved. In the pom.xml of “bsd-parser-core” there is a maven error at line 53 “null (org.codehaus.mojo:jaxb2-maven-plugin:2.2:xjc:xjc:generate-sources)” which suggests a problem with the JAXB2 Maven Plugin (stack trace below)

2)      When running milo > maven clean and then maven install, the Test milo\opc-ua-stack\stack-core\src\test\java\org\eclipse\milo\opcua\stack\core\types\BuiltinDataTypeDictionaryInitializerTest.java throws an AssertionErrorjava.lang.AssertionError: null at org.eclipse.milo.opcua.stack.core.types.BuiltinDataTypeDictionaryInitializerTest.testInitialize(BuiltinDataTypeDictionaryInitializerTest.java:37)”
I have fixed this (very dirty) by just uncommenting line 37 //assertNotEquals(structures.size(), 0); which worked like a charm. The maven install ran successfully but there is no run configuration that I could use to start the Hello World example.

I have now tried a fresh import from existing Maven project (after downloading it again via git), and ran milo > maven clean and maven install. The Second issue has been resolved, there is no AssertionError anymore. However, I do not get any run configuration nor does it work to execute one of the projects as Java Application.

 

Some specs:

-          My eclipse version is  Oxygen.3 Release (4.7.3RC2)

-          java version "1.8.0_152"

 

The first issue seems to be similar to @samber86’s question in #226, however, he has been referred to the mailing list.

 

I would appreciate any help on this topic. Thank you in advance!

 

Best regards,


Patrick Pschorn

 

 

null (org.codehaus.mojo:jaxb2-maven-plugin:2.2:xjc:xjc:generate-sources):

org.apache.maven.plugin.MojoExecutionException

                at org.codehaus.mojo.jaxb2.javageneration.AbstractJavaGeneratorMojo.performExecution(AbstractJavaGeneratorMojo.java:482)

                at org.codehaus.mojo.jaxb2.AbstractJaxbMojo.execute(AbstractJaxbMojo.java:257)

                at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

                at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)

                at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)

                at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)

                at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)

                at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)

                at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)

                at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)

                at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)

                at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)

                at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)

                at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)

                at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)

                at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)

                at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)

                at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)

                at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)

                at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)

                at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

Caused by: java.lang.NullPointerException

                at org.codehaus.mojo.jaxb2.shared.environment.ToolExecutionEnvironment.restore(ToolExecutionEnviron


Back to the top