mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <sro...@gmail.com>
Subject Re: Release help, stuck on gpg-sign?
Date Thu, 22 Oct 2009 12:31:40 GMT
To be more clear on the project.version thing, I see:

[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Transforming 'Mahout utilities'...
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Transforming 'Mahout examples'...
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating mahout-utils to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}

On Thu, Oct 22, 2009 at 1:27 PM, Sean Owen <srowen@gmail.com> wrote:
> OK these questions may be for mahout-dev, maybe Grant who set this up --
>
> Are we supposed to run from the parent module, or root level? which
> pom.xml should operate the build? I'm definitely seeing errors about
> ${project.version} not being
>
> What is '-Papache-release' -- I'm trying to figure out whether this is
> supposed to be set or not. Some people mentioned this, not seeing it
> in docs.
>
> I don't see that we have any instance of maven-release-plugin -- should we?
>
> I have Subversion 1.6.2 FWIW.
>
> On Thu, Oct 22, 2009 at 2:37 AM, Benson Margulies <bimargulies@gmail.com> wrote:
>>  Maven always knows how to expand ${project.version} where it is allowed,
>> which does not include inside of <parent/> elements. It's a basic maven
>> feature.
>

Mime
View raw message