-
1. Re: What is this circular dependency issue in common-core?
pgier Jun 7, 2007 11:44 PM (in response to starksm64)Looks like it doesn't like the dependency on the snapshot version of the parent. You can try to release from the parent pom, but then you would have to release all the modules together.
If it's ok, I'd like to remove the module list from the parent pom (under the build directory). Then the project parent can be released just as a pom . And the modules can be released individually. -
2. Re: What is this circular dependency issue in common-core?
starksm64 Jun 7, 2007 11:49 PM (in response to starksm64)Yes, that is fine.
-
3. Re: What is this circular dependency issue in common-core?
pgier Jun 8, 2007 12:47 AM (in response to starksm64)I released the common parent to 2.2.0. But there seems to still be a problem with dependency resolution, because of the purge local repository. I'll try to either get this one to work, or I can switch to a new parent version.
-
4. Re: What is this circular dependency issue in common-core?
pgier Jun 8, 2007 10:12 AM (in response to starksm64)Ok, I think it should be good to go now. If you grab the updates from svn, then the release should be ok. I removed the purge local repository step from the parent pom because that seemed to be causing the problem. So that part might have to be a manual step until I figure out how to better automate it.
For the common project, I'd like to remove the common parent since each of the common modules have their own release schedule and are separate in svn. Most of the configuration is in the jboss-parent anyway, so I will probably just have the modules point directly to that one. -
5. Re: What is this circular dependency issue in common-core?
starksm64 Jun 11, 2007 8:11 PM (in response to starksm64)It still was not building for me:
[starksm@succubus common-core]$ mvn release:prepare -DdryRun=true [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/jboss/jboss-common/2.2.1/jboss-common-2.2.1.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: jboss ArtifactId: jboss-common Version: 2.2.1 Reason: Unable to download the artifact from any repository jboss:jboss-common:pom:2.2.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: jboss:jboss-common for project: null:jboss-common-core:jar:2.2.0-SNAPSHOT at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: jboss:jboss-common for project: null:jboss-common-core:jar:2.2.0-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'jboss:jboss-common' not found in repository: Unable to download the artifact from any repository jboss:jboss-common:pom:2.2.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1157) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository jboss:jboss-common:pom:2.2.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124) ... 20 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Mon Jun 11 16:50:46 PDT 2007 [INFO] Final Memory: 2M/74M [INFO] ------------------------------------------------------------------------
until I updated my local repository maven2/jboss/jboss-common location to pull in the new parent pom. -
6. Re: What is this circular dependency issue in common-core?
starksm64 Jun 11, 2007 9:29 PM (in response to starksm64)The 2.2.0.GA release has been put out.
https://svn.jboss.org/repos/common/common-core/tags/2.2.0.GA/
https://svn.jboss.org/repos/repository.jboss.org/maven2/jboss/jboss-common-core/2.2.0.GA/ -
7. Re: What is this circular dependency issue in common-core?
kabirkhan Jun 12, 2007 4:45 AM (in response to starksm64)Thank you
-
8. Re: What is this circular dependency issue in common-core?
pgier Jun 12, 2007 10:33 AM (in response to starksm64)"scott.stark@jboss.org" wrote:
It still was not building for me:[starksm@succubus common-core]$ mvn release:prepare -DdryRun=true etc...
until I updated my local repository maven2/jboss/jboss-common location to pull in the new parent pom.
Sorry about that, I guess when it looked in the relative path, it only found the new snapshot version. And the common-core pom didn't have the jboss repository listed, so it didn't know to get it from there.
I changed the common projects so that they now extend directly from the jboss-parent. And they now have the appropriate repository configuration so that they can find the parent.
The common projects will also be getting a group ID of "org.jboss" now instead of just "jboss". This will follow the maven conventions a little better, and allow us to differentiate open source projects vs. commercial projects (com.jboss) in the future if we want to.