See
http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-ocm/69/
See
http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-ocm/68/
On Wed, Apr 22, 2009 at 10:12, Jukka Zitting wrote:
>> Jukka: do you mind merging this change into 1.5 branch as well?
>
> Not at all, I'll take care of it.
thanks a lot.
regards
marcel
Hi,
On Wed, Apr 22, 2009 at 10:06 AM, Marcel Reutegger
wrote:
> that's kind of my fault. the test failure is caused by the idle
> workspace timeout that had been enabled
> with changes for JCR-2048. in trunk I fixed the broken test case
> without a JCR svn log message. it's
> here: http://svn.apa
d merging this change into 1.5 branch as well?
regards
marcel
On Tue, Apr 21, 2009 at 14:07, Apache Hudson Server
wrote:
> See
> http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-core/51/
>
>
>
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/28/changes
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/27/changes
Changes:
[jukka] 1.5: Added the list of contributors to the release notes.
--
[...truncated 398 lines...]
[INFO] Building jar:
http://hudson.zones.apache.org/hudson/job
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/26/changes
Changes:
[jukka] 1.5: Merged revision 746609 (JCR-1952)
--
[...truncated 400 lines...]
[INFO] Building jar:
http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/ws
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/25/changes
Changes:
[jukka] 1.5: Upgrade jcr-commons version to 1.5.3-SNAPSHOT
[jukka] 1.5: Merged revisions 746602 and 746603 (JCR-1952). Ignored other
revisions.
--
[...truncated 416
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/20/changes
Hi,
On Wed, Feb 11, 2009 at 2:44 PM, Apache Hudson Server
wrote:
> Error: JAVA_HOME is not defined correctly.
> We cannot execute /home/hudson/tools/java/latest1.4/bin/java
I migrated this job to a new Hudson slave server, but it seems like it
doesn't yet have Java 1.4 installed. I'll fix that.
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/19/changes
Changes:
[jukka] 1.5: Merged revision 738087 (JCR-1956). Ignored other revisions.
[jukka] 1.5: Merged revision 736020 (JCR-1941)
[jukka] 1.5: Merged revision 735401 (JCR-1889)
[jukka] 1.5: Upgrade version to 1.5.3
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/11/changes
Hi,
Oops, my fault. Fixed in revision 732121.
BR,
Jukka Zitting
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/10/changes
Changes:
[jukka] 1.5: Merged revision 720540 (JCR-1879)
[jukka] 1.5: Merged revision 731934 (JCR-1920). Ignored other revisions.
--
[...truncated 228 lines...]
[INFO
Hi,
Some query tests were temporarily failing in the 1.5 branch. The build
got back to stable simply by re-running it, so it looks like a random
failure, perhaps due to some synchronization issue.
I'm going to push forward with the 1.5 release. If this problem
reappears we can treat it as a known
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/4/changes
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/3/changes
Changes:
[jukka] 1.5: Updated release notes.
[jukka] 1.5: Ignored trunk revisions
[jukka] 1.5: Merged revisions 720940, 721186, 721191, 721194 and 721235
(JCR-1357)
[jukka] 1.5: Merged revisions 720679 and 720687
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5-Java14/2/changes
--
[...truncated 3323 lines...]
A
zonestorage/hudson/home/hudson/hudson/jobs/Jackrabbit-1.5-Java14/workspace/jackrabbit-1.5/jackrabbit-webapp/src/main/webapp/WEB-INF
AU
Hi,
Is there a chance to see JCR-134 included in the release ?
My collegue Sébastien provided a patch. Have you got time to review it ?
It's important for us and our customers, as repositories keep growing
even when workspaces and nodes are cleaned, and after years in
production, it may happen
Hi,
On Tue, Oct 28, 2008 at 9:27 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> There are still some loose ends with the following three issues that I
> want resolved before we do the release.
>
> [JCR-1775] Transaction-safe versioning
> [JCR-1813] Invalid journal records during XATransactions
>
Hi,
On Tue, Oct 28, 2008 at 2:57 PM, Sébastien Launay
<[EMAIL PROTECTED]> wrote:
> I would like to see JCR-134 fixed for this release.
> I have submitted a patch months ago and have not received any feedback
> so far.
Sorry for the lack of feedback, I'll give it a look and see if we
could get it
Hi,
On Tue, Oct 28, 2008 at 12:07 PM, Bart van der Schans
<[EMAIL PROTECTED]> wrote:
> It would be cool if JCR-1835 could make it in the release. It's quite
> trivial, but not of major importance though.
It's in 1.5 now. Thanks for the input.
BR,
Jukka Zitting
prove the out of the box experience with Jackrabbit. I
>> think this should be the primary goal for Jackrabbit 1.5, and thus I
>> consider the issues JCR-1455 (content explorer) and JCR-1357 (quick
>> start) to be the driving features of the 1.5 release.
>> [...]
>> I&
Hi Jukka,
It would be cool if JCR-1835 could make it in the release. It's quite
trivial, but not of major importance though.
Regards,
Bart
On 28-10-2008 10:51, Thomas Müller wrote:
Hi,
I didn't commit the patch for JCR-1825 yet because I didn't have time
yet to write a test case (or at leas
Hi,
I didn't commit the patch for JCR-1825 yet because I didn't have time
yet to write a test case (or at least test it manually). Unless
somebody has time to test it, it's probably better to not commit it.
Regards,
Thomas
On Tue, Oct 28, 2008 at 9:27 AM, Jukka Zitting <[EMAIL PROTECTED]>
Hi,
On Thu, Oct 9, 2008 at 3:40 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> I will be doing a few preview builds of the 1.5 branch so everyone
> will have a chance to test things and report back with any detected
> issues. Assuming no blockers, I plan to roll the final release
> candidate and s
Hi,
One final note; I will be using the merge tracking feature in
Subversion to manage the 1.5 branch. This makes it easier to pick and
merge only those changes from trunk that should be included in the
branch.
For now, until 1.5.0 is released, I will be tracking all the remaining
open issues tag
Hi,
Another related point, I would like to make a minor change to our
version numbering practice: keep the final .z in x.y.z even if it's 0.
Then all our version numbers would follow the same pattern.
This change would make cases like the 1.2.1 release (where we dropped
the 1.2 release candidate
Hi,
As a corollary to my previous message, I would also like to implement
the following changes:
* Binaries generated from the source release are still made available
both on the download page and the Maven repository, but we no longer
advertise each individual component for download. The downloa
Jackrabbit version. In Jackrabbit 1.5 I want to solve
these issues.
I strongly feel that a purely component-based release structure, i.e.
one in which each of our 16 components has completely independent
release cycle, is too fine-grained and makes building all of
Jackrabbit from anything but a
On 10 Oct 2008, at 00:40, Jukka Zitting wrote:
Since there are no major issues pending for 1.
Is the new user management feature documented somewhere, except for
the jsr-283 draft?
--
Torgeir Veimo
[EMAIL PROTECTED]
Hi,
On Tue, Oct 7, 2008 at 2:46 PM, Angela Schreiber <[EMAIL PROTECTED]> wrote:
>> Does anyone have any blocking concerns about the 1.5 release?
>
> JCR-1765 Config: make all elements in the security configuration
> optional
>
>> it's done with that but i didn't commit it yet.
>
>
Does anyone have any blocking concerns about the 1.5 release?
JCR-1765 Config: make all elements in the security configuration
optional
> it's done with that but i didn't commit it yet.
JCR-1783 JCR2SPI: incomplete changelog...
> i am working on that right now.
angela
Hi,
On Wed, Apr 16, 2008 at 4:29 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> As discussed after the 1.4 release, there's still a lot we can and
> should do to improve the out of the box experience with Jackrabbit. I
> think this should be the primary goal for Jackra
control API
>> and whether or not a form of it was guaranteed to be included in the
>> 1.5 release?
>
> Jackrabbit 1.5 will be based on the current trunk, so the current JCR
> 283 access control work will be included in the release.
>
> However as you've noticed, we
Hi,
On Tue, Jun 10, 2008 at 7:24 PM, Micah Whitacre <[EMAIL PROTECTED]> wrote:
> I was curious about the state of the new JSR 283 access control API
> and whether or not a form of it was guaranteed to be included in the
> 1.5 release?
Jackrabbit 1.5 will be based on the curren
Sorry about the email misfire email should have read
Hey all,
I was curious about the state of the new JSR 283 access control API
and whether or not a form of it was guaranteed to be included in the
1.5 release? I know that it is currently in flux while it is working
through issues such as
Hey All,
On Thu, May 22, 2008 at 2:27 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> On Thu, May 22, 2008 at 2:37 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> > Yes, I've read the spec draft, but the sections on access control
> > policies (6.11.2) is very generic, leaving a lot to be desired by
Hi,
On Thu, May 22, 2008 at 2:37 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> Yes, I've read the spec draft, but the sections on access control
> policies (6.11.2) is very generic, leaving a lot to be desired by the
> different implementations (as I suspect you know :). Allthough I
> prefer writi
Vidar Ramdal wrote:
OK, that's fine. I suppose the o.a.j.api.jsr283 interfaces will mirror
jcr-2.0.jar as much as possible, right?
right. and we are pointing out the non-final status,
since we know that there will almost certainly be
some rearrangement within the next couple of weeks.
i don't
On Thu, May 22, 2008 at 1:07 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Thu, May 22, 2008 at 12:52 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
>> So devs, how do I create an instance of an ACE?
>
> You may want to check the JSR 283 public draft for general guidance
> about how the ne
Hi,
On Thu, May 22, 2008 at 12:52 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> So devs, how do I create an instance of an ACE?
You may want to check the JSR 283 public draft for general guidance
about how the new access control system is designed to work. See also
the o.a.j.api.jsr283.security p
Vidar Ramdal wrote:
Vidar Ramdal wrote:
How do I create an instance of an ACE? Both PolicyEntryImpl
and ACEImpl are package local, as is ACLEditor ...
i think this is a mistake (leftover).
you can change it in your checkout.
the ACL stuff will be reworked soon due to modified
specification. s
Continuing a thread (http://markmail.org/message/tz3zfoddbmwgllgy )
from [EMAIL PROTECTED]:
Vidar Ramdal wrote:
I want to set access control policies so that a parent
node (e.g. /node) is readable for Everyone, but a child
node (/node/childnode) is only readable for specific princip
Hi,
On Sat, May 10, 2008 at 3:48 PM, Tobias Bocanegra
<[EMAIL PROTECTED]> wrote:
> i checked the versions of the jackrabbit 1.5 builds on the snapshot
> repo [0] and it seams that the latest is
> jackrabbit-core-1.5-20080425.154857-133.jar which is about 3 weeks
> old. a
hi,
i checked the versions of the jackrabbit 1.5 builds on the snapshot
repo [0] and it seams that the latest is
jackrabbit-core-1.5-20080425.154857-133.jar which is about 3 weeks
old. are there no longer nightly builds, or has the repository
changed?
--
regards, toby
[0]
http
Hi,
On Tue, Apr 22, 2008 at 10:11 AM, Angela Schreiber <[EMAIL PROTECTED]> wrote:
> Jukka Zitting wrote:
> > I guess we'd disable the ACL editor in Jackrabbit 1.5, and bring it
> > back in Jackrabbit 2.0 when Angela's work for JSR 283 access control
> > is fin
; > >
> > > > I've been testing "CRX Content Explorer" and looks great :) But now I
> > > > have a question because I've seen the Access-Control Editor : how do
> > you
> > > > implement the ACL? There is no default ACL m
at :) But now I
> > > have a question because I've seen the Access-Control Editor : how do
> you
> > > implement the ACL? There is no default ACL managemente in Jackrabbit.
> > >
> >
> > I guess we'd disable the ACL editor in Jackrabbit 1.5
L? There is no default ACL managemente in Jackrabbit.
I guess we'd disable the ACL editor in Jackrabbit 1.5, and bring it
back in Jackrabbit 2.0 when Angela's work for JSR 283 access control
is finished.
it's already committed to jackrabbit trunk. i just didn't
change the d
fault ACL managemente in Jackrabbit.
I guess we'd disable the ACL editor in Jackrabbit 1.5, and bring it
back in Jackrabbit 2.0 when Angela's work for JSR 283 access control
is finished.
BR,
Jukka Zitting
El lun, 21-04-2008 a las 00:22 +0200, Greg Klebus escribió:
> We at Day decided to donate the CRX Content Explorer, part of our
> Content Repository Extreme product, to the community / Jackrabbit. For
> those, who'd like to have a look at the current CRX content explorer,
> please see the live CRX
explorer) in trunk
> latest in May. That's a fairly tight schedule, but I'm confident that
> we can make it since the required work is mostly about integrating
> existing code and solutions.
I wanted to refer to a specific feature planned for Jackrabbit 1.5 -
the Content Expl
> Speaking of major changes with respect to JCR 2.0 and whether
> introducing them into JR 1.5 makes sense, I'm in favor of introducing
> new features that do not affect existing code (let alone break the
> build) and that are backed by some basic tests (that will of course
> not cover every c
Hi,
Speaking of major changes with respect to JCR 2.0 and whether
introducing them into JR 1.5 makes sense, I'm in favor of introducing
new features that do not affect existing code (let alone break the
build) and that are backed by some basic tests (that will of course
not cover every conceivable
Am 18.04.2008 um 11:07 schrieb Thomas Mueller:
Branching (and specially merging) is more work.
With SVN. Are there any plans in the ASF to try out and switch to git
[1]?
Alex
[1] http://git.or.cz/
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://d
Hi,
Am Freitag, den 18.04.2008, 11:26 +0200 schrieb Thomas Mueller:
> Hi,
>
> > > If we have enough
> > > test cases (I know...) even major changes shouldn't be a problem.
> >
> > Unless, the changes are so big, as they might make it impossible for a
> > longer time to have regular checkins
Hi,
> > If we have enough
> > test cases (I know...) even major changes shouldn't be a problem.
>
> Unless, the changes are so big, as they might make it impossible for a
> longer time to have regular checkins one one hand and stable builds
> (nightlies I should say) on the other hand. In th
Hi,
Am Freitag, den 18.04.2008, 11:07 +0200 schrieb Thomas Mueller:
> Hi,
>
> > > There are a number of things going on within trunk, especially in
> > > relation to JSR 283, but for 1.5 these new features only need to
> > > stable enough that they don't break things if people are *not* using
Hi,
> > There are a number of things going on within trunk, especially in
> > relation to JSR 283, but for 1.5 these new features only need to
> > stable enough that they don't break things if people are *not* using
> > them.
>
> This kind of worries me ! I would rather like to have major cod
hot at a release plan for Jackrabbit 1.5. There's
> been a lot of talk about the next release and related release
> processes on various forums, and I wanted to summarize a plan here to
> keep everyone up to date and the momentum going towards the release.
> For some background information
hi jukka
On Wed, Apr 16, 2008 at 4:29 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Here's my first shot at a release plan for Jackrabbit 1.5. There's
> been a lot of talk about the next release and related release
> processes on various forums, and I
Hi,
Here's my first shot at a release plan for Jackrabbit 1.5. There's
been a lot of talk about the next release and related release
processes on various forums, and I wanted to summarize a plan here to
keep everyone up to date and the momentum going towards the release.
For some
Hi,
On Fri, Feb 29, 2008 at 9:57 PM, Esteban Franqueiro
<[EMAIL PROTECTED]> wrote:
> Is there an ETA on Jackrabbit 1.5?
Not yet.
My current planning is that we should release 1.5 in Q2 this year and
that the release should contain the following major new features:
* Runnable J
Hi again.
Is there an ETA on Jackrabbit 1.5?
Regards,
Esteban Franqueiro
[EMAIL PROTECTED]
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary
67 matches
Mail list logo
