[
https://issues.apache.org/jira/browse/JCR-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-3498:
--
Fix Version/s: 2.7.1
Added a 2.7.1 version.
OUTER JOIN behavior is improperly
Hi,
On Mon, May 6, 2013 at 9:33 PM, Julian Reschke julian.resc...@gmx.de wrote:
On 2013-05-06 21:02, Alex Parvulescu wrote:
now I'm getting signature errors :)
Import gpg keys from dist/KEYS? (my entry is new)
I updated the release checker script to automatically import the
latest keys from
[
https://issues.apache.org/jira/browse/JCRSITE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCRSITE-40.
--
Resolution: Invalid
Fix Version/s: (was: parent 6)
vincent debarr
+1
greets
claus
[
https://issues.apache.org/jira/browse/JCR-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3577:
-
Fix Version/s: 2.6.1
Allow creation of users with 'null' password
[
https://issues.apache.org/jira/browse/JCR-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650607#comment-13650607
]
Alex Parvulescu commented on JCR-3577:
--
backported to the 2.6 branch with rev 1479808.
[
https://issues.apache.org/jira/browse/JCR-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3498:
-
Fix Version/s: 2.6.1
backported to 2.6 with rev 1479810.
OUTER JOIN behavior is
Hi,
As a followup to cutting the 2.7.0 release candidate I've updated the
trunk version to 2.8-SNAPSHOT in preparation for ultimately producing
our next stable release. Please update dependencies in any downstream
projects that are tracking the latest Jackrabbit SNAPSHOTs.
Like during the
[
https://issues.apache.org/jira/browse/JCR-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3552:
-
Fix Version/s: 2.6.1
backported to 2.6 with rev 1479812.
Principal associated
[
https://issues.apache.org/jira/browse/JCR-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3519:
-
Fix Version/s: 2.6.1
backported to 2.6 with rev 1479815.
Disable IOCounters
[
https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3495:
-
Fix Version/s: 2.6.1
backported to 2.6 with rev 1479817.
Unregister from
hmm, what am I doing wrong? now it says:
marcel@ubuntu10:~/devel/jackrabbit-dev$ sh check-release.sh 2.4.4
608ae0c4b61362e72cf95f41bd4bf9732a74a7c1
check-release.sh: 46: check-release.sh: Syntax error: ( unexpected
regards
marcel
-Original Message-
From: Jukka Zitting
Hi,
On Tue, May 7, 2013 at 11:00 AM, Marcel Reutegger mreut...@adobe.com wrote:
hmm, what am I doing wrong? now it says:
Ah, it could be that the svn update that the script does is updating
the script itself, which easily leads to problems like that. Try again
after an svn update.
BR,
Jukka
Hi,
Ah, it could be that the svn update that the script does is updating
the script itself, which easily leads to problems like that. Try again
after an svn update.
I did immediately before I ran the script.
removing the function keywords in front of the info() and error() functions
seems to
I want to contribute in this release (if it happens). Could somebody tell me
how to register for this?
Thanks and regards,
Atul Maurya
Sent from my BlackBerry® smartphone
-Original Message-
From: Marcel Reutegger-6 [via Jackrabbit]
ml-node+s510166n4658571...@n4.nabble.com
Date: Tue,
Hi,
On Tue, May 7, 2013 at 11:04 AM, Marcel Reutegger mreut...@adobe.com wrote:
removing the function keywords in front of the info() and error() functions
seems to fix the issue for me.
Good point; that's the correct thing to do for better portability of
the script. Can you commit the fix?
On 2013-05-07 11:13, AtulMaurya wrote:
I want to contribute in this release (if it happens). Could somebody
tell me how to register for this?
...
It's too late for 2.4.4 (if the vote passes).
In general, see (around)
https://jackrabbit.apache.org/building-jackrabbit.html.
Best regards,
On Tue, May 7, 2013 at 11:04 AM, Marcel Reutegger
mreut...@adobe.com wrote:
removing the function keywords in front of the info() and error() functions
seems to fix the issue for me.
Good point; that's the correct thing to do for better portability of
the script. Can you commit the fix?
The Apache Jenkins build system has built Jackrabbit-trunk (build #2116)
Status: Still Failing
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2116/ to
view the results.
Please vote on releasing this package as Apache Jackrabbit 2.4.4.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[X] +1 Release this package as Apache Jackrabbit 2.4.4
regards
marcel
+1
On Tue, May 7, 2013 at 11:26 AM, Marcel Reutegger mreut...@adobe.comwrote:
Please vote on releasing this package as Apache Jackrabbit 2.4.4.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[X] +1 Release this package
Hi,
[cc += builds@a.o]
On Tue, May 7, 2013 at 11:26 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2116/
to view the results.
The problem is:
[INFO] Error while executing forked tests.; nested exception
looks like a jenkins problem
[ERROR] BUILD ERROR[INFO]
[INFO] Error while executing forked tests.; nested exception is
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException:
Error setting
Hi,
[X] +1 Release this package as Apache Jackrabbit 2.7.0
Note that I first executed the check-release.sh with maven 2.2.1 on the
path, and it failed (on my Windows/Cygwin box).
With maven 3.0.3, it's ok.
Regards,
Cédric
Le 06/05/2013 15:01, Jukka Zitting a écrit :
Hi,
A candidate for
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650749#comment-13650749
]
Tommaso Teofili commented on JCR-3534:
--
after a chat with Alexander we realized that
Hi,
Jukka Zitting jukka.zitt...@gmail.com hat am 7. Mai 2013 um 11:32 geschrieben:
Hi,
[cc += builds@a.o]
On Tue, May 7, 2013 at 11:26 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2116/
to view the
Hi everybody,
With 2.4.4 on its way, I plan to start the release process for 2.6.1
soonish.
The changes from 2.6 are listed over here:
Jukka Zitting created JCR-3591:
--
Summary: Upgrade to latest Logback
Key: JCR-3591
URL: https://issues.apache.org/jira/browse/JCR-3591
Project: Jackrabbit Content Repository
Issue Type:
Hi Julian,
I'd like to see [1] backported in 2.6.1, but I'm wondering if this has
been enough tested in 2.7, if at all.
Or do you think it's too much for just a patch release ?
Regards,
Cédric
[1] https://issues.apache.org/jira/browse/JCR-3402
Le 07/05/2013 14:08, Julian Reschke a écrit :
[
https://issues.apache.org/jira/browse/JCR-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650801#comment-13650801
]
Julian Reschke commented on JCR-3394:
-
Picking sessions from a pool somewhat randomly
On 2013-05-07 15:22, Cédric Damioli wrote:
Hi Julian,
I'd like to see [1] backported in 2.6.1, but I'm wondering if this has
been enough tested in 2.7, if at all.
Or do you think it's too much for just a patch release ?
Regards,
Cédric
...
No opinion on that. Jukka maybe?
Best regards,
Hi,
In general a big +1 to cutting 2.6.1. There are already 34 issues with
changes waiting to be released from the 2.6 branch. That's quite a lot
for a patch release, so the sooner we cut the release the better.
On Tue, May 7, 2013 at 3:31 PM, Julian Reschke julian.resc...@gmx.de wrote:
On
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated JCR-3534:
-
Attachment: JCR-3534.3.patch
updated patch which introduces special handling of
Hi,
that's probably my bad, I flipped the version support descriptor for
versioning, but only checked the VersionIT test. I'll fix it.
regards
marcel
-Original Message-
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
Sent: Dienstag, 7. Mai 2013 15:18
To: Oak devs
Subject:
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650878#comment-13650878
]
Alexander Klimetschek commented on JCR-3534:
Looks good. But some more comments
Hi,
I extended the list of known issues. The IT tests don't report
failures anymore on my machine.
regards
marcel
-Original Message-
From: Marcel Reutegger [mailto:mreut...@adobe.com]
Sent: Dienstag, 7. Mai 2013 16:01
To: oak-...@jackrabbit.apache.org
Subject: RE: Build failure
Hi,
On Mon, May 6, 2013 at 5:34 PM, Marcel Reutegger mreut...@adobe.com wrote:
SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
This
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13650886#comment-13650886
]
Tommaso Teofili commented on JCR-3534:
--
Any key generation should come from the
The Apache Jenkins build system has built Jackrabbit-trunk (build #2117)
Status: Still Failing
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2117/ to
view the results.
Hi,
The check-release script fails with following trace :
[INFO] 5. Compare svn tag with src zip contents
[INFO]
[INFO]Exporting
https://svn.apache.org/repos/asf/jackrabbit/tags/2.4.4...
[INFO]Unzipping jackrabbit-2.4.4-src.zip...
[INFO]Comparing sources...
[INFO]
diff -b -r
Le 07/05/2013 15:43, Jukka Zitting a écrit :
Hi,
In general a big +1 to cutting 2.6.1. There are already 34 issues with
changes waiting to be released from the 2.6 branch. That's quite a lot
for a patch release, so the sooner we cut the release the better.
On Tue, May 7, 2013 at 3:31 PM,
On 2013-05-07 17:36, Cédric Damioli wrote:
Hi,
The check-release script fails with following trace :
[INFO] 5. Compare svn tag with src zip contents
[INFO]
[INFO]Exporting
https://svn.apache.org/repos/asf/jackrabbit/tags/2.4.4...
[INFO]Unzipping jackrabbit-2.4.4-src.zip...
[INFO]
Oops... sorry, I've missed that !
So here is my
[x] +1 Release this package as Apache Jackrabbit 2.4.4
Regards,
Cédric
Le 07/05/2013 17:54, Julian Reschke a écrit :
On 2013-05-07 17:36, Cédric Damioli wrote:
Hi,
The check-release script fails with following trace :
[INFO] 5. Compare svn
+1
Regards,
Bart
On Tue, May 7, 2013 at 6:03 PM, Cédric Damioli cdami...@apache.org wrote:
Oops... sorry, I've missed that !
So here is my
[x] +1 Release this package as Apache Jackrabbit 2.4.4
Regards,
Cédric
Le 07/05/2013 17:54, Julian Reschke a écrit :
On 2013-05-07 17:36, Cédric
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651020#comment-13651020
]
Alexander Klimetschek commented on JCR-3534:
I think on the API level we want a
Hi everyone,
Tommaso and me were having a little 1:1 discussion in JCR-3534 starting at [0],
and would love to hear some input on the open points discussed. Otherwise we
keep repeating ourselves :-)
Most notably, I see no clear API boundary yet and would not like to have this
new jackrabbit
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651034#comment-13651034
]
Tommaso Teofili commented on JCR-3534:
--
what about having all the binary reference
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651045#comment-13651045
]
Alexander Klimetschek commented on JCR-3534:
Yeah, but then you can't use it for
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651068#comment-13651068
]
Tommaso Teofili commented on JCR-3534:
--
could you please detail why that would be the
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651079#comment-13651079
]
Alexander Klimetschek commented on JCR-3534:
Because client code must not use
[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651138#comment-13651138
]
Alexander Klimetschek commented on JCR-3534:
The main point is actually that the
Le 07/05/2013 15:43, Jukka Zitting a écrit :
Hi,
In general a big +1 to cutting 2.6.1. There are already 34 issues with
changes waiting to be released from the 2.6 branch. That's quite a lot
for a patch release, so the sooner we cut the release the better.
On Tue, May 7, 2013 at 3:31 PM,
Hi,
On Tue, May 7, 2013 at 5:17 PM, Marcel Reutegger mreut...@adobe.com wrote:
I extended the list of known issues. The IT tests don't report
failures anymore on my machine.
Works for me too, thanks!
BR,
Jukka Zitting
Build Update for apache/jackrabbit-oak
-
Build: #1499
Status: Fixed
Duration: 27 minutes and 38 seconds
Commit: 94c79ba (trunk)
Author: Angela Schreiber
Message: OAK-414 : fix UserImporter (uncomment tests)
OAK-615 : cyclic group membership (add simple
54 matches
Mail list logo
