i see that the repo is already up to 3.14 do you do the testing on branch
3.13?
As in:
git clone https://github.com/apache/jena --branch 3.13.0
On Wed, Sep 25, 2019 at 6:15 PM Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Apache Jena 3.13.0.
> This is the second proposed
I was trying to do a site:site build to see if we can build the site
differently and came up with a bunch of sptobugs errors that might fit
nicely into a 3.13.1 fix as well.
On Thu, Sep 26, 2019 at 10:30 AM Marco Neumann
wrote:
> i see that the repo is already up to 3.14 do you do the testing
Did you look at Adam's use of Sonar?
On 9/26/19 10:42 AM, Claude Warren wrote:
I was trying to do a site:site build to see if we can build the site
differently and came up with a bunch of sptobugs errors that might fit
nicely into a 3.13.1 fix as well.
On Thu, Sep 26, 2019 at 10:30 AM Marco
(Please remove VOTE if it is discussion.)
On 9/26/19 10:29 AM, Marco Neumann wrote:
i see that the repo is already up to 3.14 do you do the testing on branch
3.13?
The release process, specifically the maven release plugin, moves the
version on.
If an RC fails, then the release manager
+1
maven clean install
BUILD SUCCESS 6:05 min
Apache Maven 3.6.1
Maven home: /opt/maven
Java version: 12.0.2, vendor: Private Build, runtime:
/usr/lib/jvm/java-12-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-29-generic", arch: "amd64", family:
[ x ] +1 Approve the release
Built from tag with:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_222, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default
afs commented on a change in pull request #612: JENA-1764: Fix
Automatic-Module-Name metadata
URL: https://github.com/apache/jena/pull/612#discussion_r328569363
##
File path: jena-shacl/pom.xml
##
@@ -35,7 +35,7 @@
-MM-dd'T'HH:mm:ssZ
