sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <>
Subject [jira] [Resolved] (SIS-63) Fix <prerequisites> in sis-build-helper after Apache upgrated the Maven used by Jenkins
Date Mon, 01 Jul 2013 11:15:19 GMT


Martin Desruisseaux resolved SIS-63.

       Resolution: Won't Fix
    Fix Version/s: 0.3

We abandoned usage of {{maven.version}} property, and nailed down the version number in the
dependency section of the {{sis-build-helper}} plugin instead. Consequently we do not need
anymore the prerequisites.

> Fix <prerequisites> in sis-build-helper after Apache upgrated the Maven used by
> ---------------------------------------------------------------------------------------
>                 Key: SIS-63
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Build process
>            Reporter: Martin Desruisseaux
>            Priority: Trivial
>             Fix For: 0.3
> The {{pom.xml}} file of the {{sis-build-helper}} module uses the {{$\{maven.version\}}}
property, which has been introduced only in Maven 3.0.4 ([MNG-4112|]).
Consequently we should put the following section in the {{pom.xml}} file:
> {code:xml}
> <prerequisites>
>   <maven>3.0.4</maven>
> </prerequisites>
> {code}
> However at the time of writing this issue, we can not because Apache Jenkins is still
using Maven 3.0.3. We had to relax the prerequisite, but users need to be aware that they
must declare explicitly their Maven version if (and only if) older than 3.0.4, using the {{-D}}
option like below:
> {noformat}
> --define maven.version=3.0.3
> {noformat}
> We should declare the correct prerequisite, namely 3.0.4, when Jenkins will accept it.
This would allow users of older Maven versions who did not declared the above-cited property
to get a proper error message rather than a message about undefined property.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message