Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 andy.seaborne.apache@gmail.com designates 74.125.82.175 as permitted sender)
Sender: Andy Seaborne <andy.seaborne.apache@gmail.com>
Message-ID: <4EEF74DF.5050707@apache.org>
Date: Mon, 19 Dec 2011 17:31:11 +0000
From: Andy Seaborne <andy@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: jena-dev@incubator.apache.org
Subject: Help with parent POMs
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

One of the problems with both the Jenkins setup and with resetting after 
the release build has been with the parent POM.

After "svn update" all the modules, dependency resolution isn't causing 
the new 1-incubating-SNAPSHOT POM to be pulled in. How should the parent 
POM get placed in the repo?

(relativePath assumes available in the file system).

https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution

The only solution I have found is to "mvn install" it which seems to be 
missing the point.

Is this broken for other people as well?

How can I get the new parent POM pulled into the local repo without 
checking JenaTop out?

Jenkins jobs seem to be failing when run on a server where jena-top is 
not available.

	Andy