Am 01.11.2011 um 10:03 schrieb Andy Seaborne:
> On 31/10/11 21:35, Andy Seaborne wrote:
>> On 31/10/11 20:49, Thorsten Möller wrote:
>>> Incidentally, I did a fresh checkout yesterday and stumbled upon this
>>> point as well. With the current POM one is forced to checkout JenaTop
>>> as a sibling even when one just wants Jena, ARQ, or any other Jena
>>> project. I suggest removing the relativePath property as this will
>>> resolve the issue (parent POM will be downloaded automatically from
>>> Maven Central if not already in the local Maven repository). The
>>> relativePath property should only be set if it is anyway necessary
>>> (for whatever reason) to do a complete checkout of all
>>> modules/projects. I can file a Jira request in case you agree.
>>>
>>> Thorsten
>>
>> It's a temporary necessity while we get the POM structure for the first
>> releases (minimal change to system structure) working, i.e. JenaTop is
>> changing to get a system working. It'll go away sometime, maybe soon.
>
> To be clear "it'll go away" refers to <relativePath>
... which is what I understood. Thanks.
BTW, as this is (once again) a Maven related thread: I get a few warnings at
build time caused by use of deprecated features, see below. Warnings want go
away by nature, isn't it.
ARQ:
[WARNING] DEPRECATED [tasks]: Use target instead
[INFO] [antrun:run {execution: ant-timestamp}]
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
Jena:
[WARNING] DEPRECATED [tasks]: Use target instead
[INFO] [antrun:run {execution: default}]
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
More serious, however, is that Junit tests for ARQ/trunk[rev1195889] do not
pass on my machine (Maven 2.2.1, Java 1.6.0_26, OSX 10.6.8). Seems to be a
locale-specific issue, see https://issues.apache.org/jira/browse/JENA-150.
Thorsten
