cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <and...@objectstyle.org>
Subject Re: docbook build failure
Date Tue, 29 May 2012 09:50:05 GMT
IIRC Maven 3 is expected not only for Docbook (?) It's been out there for a long time and there's
no reason for us to support Maven 2 builds.

On May 28, 2012, at 10:14 PM, Aristedes Maniatis wrote:

> Yes, since maven will try to recursively build right through the project. If it is a
problem, I can revert it (since it didn't fix the problem on buildbot I was hoping it would).
But someday we should move to maven 3. Is that day now? Any objections to me making the whole
project maven3?
> 
> Ari
> 
> 
> On 29/05/12 11:34am, Michael Gentry wrote:
>> Well, that output was from the top level, so even a mvn install right now currently
aborts due to the docbook part.
>> 
>> mrg
>> 
>> On May 28, 2012, at 7:34 PM, Aristedes Maniatis <ari@maniatis.org> wrote:
>> 
>>> Well, just the docbook part.  Is that a problem? Can we move to maven 3 for the
whole project?
>>> 
>>> Ari
>>> 
>>> On 29/05/12 9:13am, Michael Gentry wrote:
>>>> So you can't build now without Maven 3?
>>>> 
>>>> ~/Projects/Cayenne31$ mvn clean install
>>>> [INFO] Scanning for projects...
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Unable to build project
>>>> '/home/mrg/Projects/Cayenne31/docs/docbook/pom.xml; it requires Maven
>>>> version 3
>>>> [INFO] ------------------------------------------------------------------------
>>>> 
>>>> mrg
>>>> 
>>>> 
>>>> On Wed, May 23, 2012 at 10:47 AM, Aristedes Maniatis <ari@maniatis.org>
wrote:
>>>>> That was my hunch, but I forced the pom to a minimum of maven 3 and it
>>>>> didn't help.
>>>>> 
>>>>> Ari
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 23/05/12 11:03pm, Andrus Adamchik wrote:
>>>>>> 
>>>>>> I noticed you've asked about Maven version in INFRA-4023 comment.
I think
>>>>>> this is the most likely cause.
>>>>>> 
>>>>>> Andrus
>>>>>> 
>>>>>> 
>>>>>> On May 23, 2012, at 3:52 AM, Aristedes Maniatis wrote:
>>>>>> 
>>>>>>> Does anyone have ideas about this one:
>>>>>>> 
>>>>>>> 
>>>>>>> http://ci.apache.org/builders/cayenne-nightly/builds/224/steps/compile_1/logs/stdio
>>>>>>> 
>>>>>>> It works for me locally, so I'm out of ideas. Why does
>>>>>>> ${project.parent.basedir} come out as null? Isn't that a built-in
maven
>>>>>>> property? I guess I could replace it with "../" but that seems
less robust
>>>>>>> somehow.
>>>>>>> 
>>>>>>> 
>>>>>>> Ari
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> -------------------------->
>>>>>>> Aristedes Maniatis
>>>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49
102A
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> --
>>>>> -------------------------->
>>>>> Aristedes Maniatis
>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>>>> 
>>>>> 
>>> 
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>>> 
>>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
> 
> 
> 


Mime
View raw message