I just did the release process with:
-DreleaseVersion=3.4.0
-DdevelopmentVersion=3.5.0-SNAPSHOT
-Dtag=jena-3.4.0-rc1
and it worked fine, much better than asking version number questions.
I'll update the cwiki documentation.
Andy
On 10/07/17 13:50, Andy Seaborne wrote:
Thanks for the pointer - I'll give it a try this time.
Andy
On 10/07/17 11:44, [email protected] wrote:
This didn't work for me in previous releases because of the different
versions between Fuseki1, Fuseki2, and the rest of Jena (it gave the
same versions to all), but after Andy's PR unifying the versions, I
think it should.
ajs6f
Rob Vesse wrote on 7/10/17 5:16 AM:
A useful cheat to avoid being prompted full version at all is to
explicitly specify them as maven properties i.e.
-DreleaseVersion=3.4.0 -DdevelopmentVersion=3.5.0-SNAPSHOT
Rob
On 09/07/2017 22:40, "Andy Seaborne" <[email protected]> wrote:
On 08/07/17 14:42, [email protected] wrote:
> +1 to the timing of a release and +1 to uniformizing version
numbering.
JENA-1373 and PR#269.
"mvn clean install2 with a maven repo cleaned of all previous
SNAPSHOTs
worked.
I haven't yet tried the maven release plugin with
-DautoVersionSubmodules which would mean be asked only once each
for the
release version and next version. That would be a bonus.
Andy