incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Haywood <>
Subject Re: Isis building error
Date Sun, 07 Nov 2010 14:50:56 GMT
Hi Vango,
Must admit that that message doesn't really make sense to me, because 
the parent of alternatives/progmodel/groovy/pom.xml is simply 
alternatives/progmodel/pom.xml, which is local and in the default 
location for parents.

Some thoughts:
1. Re-run svn update at trunk to make sure you have the latest version 
of everything.  If svn update bombs out, then run again (or use the 
trunk/ script).
2. delete ~/.m2/repository/org/apache/isis, in case some sort of 
corruption has occurred in there
3. make sure there's nothing "special" configured in your 
~/.m2/settings.xml.  If you have put something in there, post it here so 
we can assess whether that's the issue.
4. Run the command again, but without the -o.   It *is* necessary to run 
the build without -o at least once to bring down all non-local 
dependencies (which takes an age to run); perhaps we're getting a 
misleading error message if you never did that.

If still no joy, then let us know your operating system + version, Maven 
version, Java version, to see if someone else can reproduce the problem.


On 07/11/2010 12:14, Vangjel Stavro wrote:
> Hi isis-devs,
> I am trying to build the code with the following command:
> mvn clean install -D modules=all -o
> in the parent folder i.e isis/source-code-as-downloaded-from-svn-repository
> and I get the following error:
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project ->  [Help 1]
> [ERROR]   The project
> org.apache.isis.alternatives.progmodel:groovy:0.1-SNAPSHOT
> (/home/vango/Workspace/Isis/alternatives/progmodel/groovy/pom.xml) has 1
> error
> [ERROR]     Non-resolvable parent POM: Could not find artifact
> org.apache.isis:alternatives:pom:0.1-SNAPSHOT and 'parent.relativePath'
> points at wrong local POM @ line 6, column 10 ->  [Help 2]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> [ERROR] [Help 2]
> Could someone help me with this?
> Cheers,
> Vangjush Stavro

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message