Oh, now I understand. My bad. The 2.7-M2 is never set as an artifact
version, you are only using it for documentation.
Could you use a different property name to geotools.version, to avoid
confusion? (As we use geotools.version elsewhere.)
And it might also be a good idea to set the artifact ve
Have a look.
The pom.xml uses 2.7-SNAPSHOT
the docs need to refer to 2.7-M3 to reflect the current release. They also
contain instructions on how to make use of 2.7-SNAPSHOT (for the brave).
The earlier mistake you reported was caused when merging doc changes from the
tag back to trunk.
Jody
Ben Caradoc-Davies ha scritto:
> On 02/08/10 13:34, Jody Garnett (JIRA) wrote:
>> Give that a go; the idea is that the docs will reference 2.7-M2 as the
>> stable release until next time.
>
> Jody, I don't like this. It makes trunk depend on a tag. This breaks the
> separation of concerns and gi
On 02/08/10 13:34, Jody Garnett (JIRA) wrote:
> Give that a go; the idea is that the docs will reference 2.7-M2 as the stable
> release until next time.
Jody, I don't like this. It makes trunk depend on a tag. This breaks the
separation of concerns and gives us another thing that has to be updat