EKB structure

8 views
Skip to first unread message

Felix Mayerhuber

unread,
Aug 18, 2012, 11:11:44 PM8/18/12
to openen...@googlegroups.com
Hi,

just to inform you: I have merged my change for the issue OPENENGSB-3238 into the master, which means that there is now 4 separate bundles for the EKB implementation instead of one. Since now the paths for the bundles have changed(e.g. "components/ekb-api" got "components/ekb/api"), your Eclipse may don't like this change on the fly. So if you load the recent version, don't forget to delete the old project files and generate them new through mvn eclipse:eclipse.

Kind regards
Felix

Peter

unread,
Aug 23, 2012, 5:29:21 AM8/23/12
to openen...@googlegroups.com
Hi,

I'm not sure if it has something to do with it, but I cannot compile the requirement domain anymore (see Jenkins error and the detailed error message i get from maven below).

Any idea how to fix it?

Thank you!

Cheers,
Peter

Error output:

[ERROR] Failed to execute goal on project org.openengsb.domain.requirement: Could not resolve dependencies for project org.openengsb.domain:org.openengsb.domain.requirement:bundle:1.0.0-SNAPSHOT: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project org.openengsb.domain.requirement: Could not resolve dependencies for project org.openengsb.domain:org.openengsb.domain.requirement:bundle:1.0.0-SNAPSHOT: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
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:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.openengsb.domain:org.openengsb.domain.requirement:bundle:1.0.0-SNAPSHOT: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find org.openengsb.framework.ekb:org.openengsb.framework.ekb.api:jar:1.0.0-SNAPSHOT in http://repo1.maven.org/maven2/org/openengsb/ was cached in the local repository, resolution will not be reattempted until the update interval of npanday.repo.1 has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427)
... 26 more

Felix Mayerhuber

unread,
Aug 23, 2012, 5:31:30 AM8/23/12
to openen...@googlegroups.com
Hi,

by having a very short look at your error message, I would say the
problem is that you reference the EKB api bundle in the version
1.0.0-SNAPSHOT. This bundle doesn't exist. Try to use version
3.0.0-SNAPSHOT instead.

Kind regards
Felix

Peter

unread,
Aug 23, 2012, 6:09:57 AM8/23/12
to openen...@googlegroups.com
Hallo,

I don't reference EKB api in my pom.xml directly. It works when I change the version of the requirement domain to 3.0.0-SNAPSHOT but i've been told that i should use 1.0.0-SNAPSHOT.

So can I use 3.0.0-SNAPSHOT? - In this case the version also would need to be updated in JIRA, ...

cheers
Peter

Felix Mayerhuber

unread,
Aug 23, 2012, 7:47:29 AM8/23/12
to openen...@googlegroups.com
Hi,

ok, I think the problem is in the parents. There, in the third parent,
all dependencies of the OpenEngSB are listed, with the property
${project.version} as version. Since this property is 1.0.0-SNAPSHOT for
you, this produces problems. BUT there seems to be a problem here
anyway. I don't think that the shared parent should be in the parent
hierarchy of the domain parent? Need to know what Christoph and Andi say
about that.

Kind regards
Felix

Andreas Pieber

unread,
Aug 24, 2012, 6:11:28 AM8/24/12
to openen...@googlegroups.com
oh hell... ${project.version} in parents is pretty devastating...
which parents are we talking about? Hasn't this been fixed already by
all the moving and changes christoph had done to them :-)

kind regards,
Andreas

Felix Mayerhuber

unread,
Aug 24, 2012, 7:53:29 AM8/24/12
to openen...@googlegroups.com
No, this isn't already fixed. The problem is: the domains has as parent
"openengsb-domain-parent". This has as its parent
"openengsb-bundle-settings". This again has as its parent
"openengsb-shared-settings" which causes the problem. Quick fix would to
use a different property for this dependencies. But since Christoph
said, that he want to remove the shared parent anyway, this would be the
way to go.

Kind regards
Felix

Christoph Gritschenberger

unread,
Aug 24, 2012, 7:58:44 AM8/24/12
to openen...@googlegroups.com
I'll create a separate pull-request taking care of the parents soon.
Maybe Monday.

kind regards,
Christoph

Andreas Pieber

unread,
Aug 24, 2012, 8:04:38 AM8/24/12
to openen...@googlegroups.com
Looks great! Thanks a ton Christoph!

Kind regards,
Andreas
Reply all
Reply to author
Forward
0 new messages