Hello team,
In JR parent pom we have the release plugin set to 2.1. It seems that
this version does not allow the ovveride of arguments with something like
`mvn -Darguments="-DskipTests" release:prepare`
which is useful for skipping tests. I normally run all the pedantic and
integration tests ma
Hi Davide,
I'm fine with updating the parent pom version if the build
still works with this change.
please note, you can tests for release:prepare already now
with:
mvn release:prepare -DpreparationGoals=clean
Regards
Marcel
On 12/08/15 10:02, "Davide Giannella" wrote:
>Hello team,
>
>In JR
The Apache Jenkins build system has built Jackrabbit-trunk (build #2311)
Status: Still Failing
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2311/ to
view the results.
A candidate for the Jackrabbit 2.11.0 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.11.0/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/2.11.0/
The SHA1 checksum of the archive is
c2a2289b391f827
[X] +1 Release this package as Apache Jackrabbit 2.11.0
Davide
On 12/08/15 14:23, "Davide Giannella" wrote:
>Please vote on releasing this package as Apache Jackrabbit 2.11.0.
>The vote is open for the next 72 hours and passes if a majority of at
>least three +1 Jackrabbit PMC votes are cast.
All checks OK.
+1 Release this package as Apache Jackrabbit 2.11.0
[X] +1 Release this package as Apache Jackrabbit 2.11.0
alex
On Wed, Aug 12, 2015 at 2:23 PM, Davide Giannella wrote:
> A candidate for the Jackrabbit 2.11.0 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/2.11.0/
>
> The release candidate is a zip archive of
While looking through the changes for this version, I noticed recent commit
r1694984 [1] was incorrectly marked/commented with issue OAK-2231, not a
Jackrabbit JCR issue.
As result these changes are not tracked/reported in the RELEASE-NOTES.txt
either.
It might be good to at least still create
