You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mick Knutson <mi...@gmail.com> on 2007/08/06 23:04:02 UTC
[m2] urgent issue with modules and sub-modules for initial builds
I have several levels of my modules
Such as:
pom.xml
--> utilities/common/pom.xml
--> utilities/common/pom.xml
--> utilities/common/build-tools/pom.xml
Now when I have a new repo and I run a "mvn clean install"
I get :
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/delta/esp/dap/utilities/common/1.0.0.0/common-1.0.0.0.pom
[WARNING] Unable to get resource '
org.delta.esp.dap.utilities:common:pom:1.0.0.0' from repository central (
http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.delta.esp.dap.utilities
ArtifactId: common
Version: 1.0.0.0
Reason: Unable to download the artifact from any repository
org.delta.esp.dap.utilities:common:pom:1.0.0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.delta.esp.dap.utilities:common for project:
org.delta.esp.dap.utilities.common:bu
ild-tools:jar:1.0.0.0
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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: org.delta.esp.dap.utilities:common for project:
org.delta.esp.dap.utiliti
es.common:build-tools:jar:1.0.0.0
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
DefaultMavenProjectBuilder.java:1198)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal
(DefaultMavenProjectBuilder.java:697)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal
(DefaultMavenProjectBuilder.java:431)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(
DefaultMavenProjectBuilder.java:195)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java
:455)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java
:499)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java
:499)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359)
... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM '
org.delta.esp.dap.utilities:common' not found in repository: Unable to
download the arti
fact from any repository
org.delta.esp.dap.utilities:common:pom:1.0.0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:528)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
DefaultMavenProjectBuilder.java:1194)
... 19 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository
org.delta.esp.dap.utilities:common:pom:1.0.0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:197)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:73)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:482)
... 20 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:308)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:185)
... 22 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Mon Aug 06 13:57:20 PDT 2007
[INFO] Final Memory: 3M/7M
[INFO]
------------------------------------------------------------------------
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
RE: [m2] urgent issue with modules and sub-modules for initial builds
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Or just switch to "enforce" instead of "enforce-once". As noted in the
issue, the aggregator portion of enforce-once isn't working (never has)
so the two goals are effectively the same in terms of performance.
(enforce-once runs on each child, the intent is for it to just run once)
-----Original Message-----
From: Tomislav Stojcevich [mailto:stojcevicht@gmail.com]
Sent: Monday, August 13, 2007 2:15 PM
To: Maven Users List
Subject: Re: [m2] urgent issue with modules and sub-modules for initial
builds
The real solution is reverting to the enforcer 1.0-alpha-2 release. I
was using 1.0-alpha-3 which for some reason isn't listed as the
current release.
The JIRA for the bug in question is
http://jira.codehaus.org/browse/MENFORCER-14
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] urgent issue with modules and sub-modules for initial builds
Posted by Tomislav Stojcevich <st...@gmail.com>.
The real solution is reverting to the enforcer 1.0-alpha-2 release. I
was using 1.0-alpha-3 which for some reason isn't listed as the
current release.
The JIRA for the bug in question is http://jira.codehaus.org/browse/MENFORCER-14
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] urgent issue with modules and sub-modules for initial builds
Posted by Tomislav Stojcevich <st...@gmail.com>.
Actually, using version in the usage also causes the problem. But
removing the version tag of the plugin works. I'm submitting bug
report.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] urgent issue with modules and sub-modules for initial builds
Posted by Tomislav Stojcevich <st...@gmail.com>.
Do you have the maven-enforcer-plugin in your pluginManagement section?
I removed it from mine and forced the version in the usage instead of
in the management section and my build worked.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] urgent issue with modules and sub-modules for initial builds
Posted by Tomislav Stojcevich <st...@gmail.com>.
I'm having the same issue. Perhaps the cause is the same as whatever
fixed http://jira.codehaus.org/browse/MNG-2434?
Is anybody else experiencing this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org