The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/676
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
[X] +1 Release this package as Apache Jackrabbit Oak 1.0.7
Hi,
I have some questions regarding the POC I am working on:
Lifecycle management
I have seen that it is not implemented in Oak while specified by the JCR.
Is there any plan to implement it ?
Observation
How does it scale ?
I need to have some custom operations executed on node creation, move,
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/677
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
If we set reindex to true in any index definition then Oak would
remove the existing index content before performing the reindex. This
would work fine if the index content are stored within NodeStore
itself.
It is important to also specify that this appears as a single commit thanks
to
Hi,
As for external Lucene indexes, what about this:
* in the :data node, store a index creation time, in milliseconds since
1970
* use that as a path prefix for the actual index files
So if the index is configured as follows:
/oak:index/lucene { path: /quickstart/repo/lucenIndex }
Then
Hi,
On 09/10/14 16:56, Marcel Reutegger mreut...@adobe.com wrote:
Please vote on releasing this package as Apache Jackrabbit Oak 1.0.7.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
The vote passes as follows:
+1 Marcel
Hi,
Then would use that UUID as the prefix ...
Sorry, that should be Then would use that _time_ as the prefix ... - I
thought about using a UUID first, but then changed to milliseconds since
1970, as that's easier (you immediately see which one is the latest
directory). But UUID would work as
Hello Team,
today, 12PM BST I will cut oak 1.1.1 (or at least try to).
https://issues.apache.org/jira/browse/OAK-2184
all the issues are resolved/closed but
https://issues.apache.org/jira/browse/OAK-2173.
if you wish to delay the cut for some time please contact me directly;
otherwise I will
Hi Davide,
It would be good to have a bit more warning before cutting a release. 30 or
so mins doesn't give anybody enough time to fix pending issues.
best,
alex
On Mon, Oct 13, 2014 at 11:50 AM, Davide Giannella dav...@apache.org
wrote:
Hello Team,
today, 12PM BST I will cut oak 1.1.1 (or
Errata corrige:
looking at my daily schedule it'll be 2.30pm BST.
On 13/10/2014 10:50, Davide Giannella wrote:
Hello Team,
today, 12PM BST I will cut oak 1.1.1 (or at least try to).
https://issues.apache.org/jira/browse/OAK-2184
all the issues are resolved/closed but
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/679
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
This one looks like window specific issue
--
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean)
on project oak-mk-api: Failed to clean project:
On 08/10/2014 13:36, Marcel Reutegger wrote:
Hi,
On 08/10/14 14:20, Marcel Reutegger mreut...@adobe.com wrote:
because we don't have a 1.2 version ;)
I'll create one in JIRA and update unresolved issues.
Done. Please change the fix version back to 1.1.x when you
resolve an issue currently
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/681
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
On 13/10/14 12:55, Davide Giannella dav...@apache.org wrote:
Question for clarifying some doubts I have.
Everything in trunk will be 1.2 (next stable release) and when we cut an
unstable one we use 1.1.x. Is that right?
Yes.
The idea of the 1.2 fix version is to indicate what issues we
Aloha,
Just wondering if there is any progress on the new REST API and what the
relevant tickets are for its completion.
Also of course hoping that the old HTTP API will be made available somehow in
the default distribution again (at least in the mean time).
regards,
Lukas Kahwe Smith
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/628
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason: scheduler
Build Source
On 13/10/2014 11:25, Alex Parvulescu wrote:
Hi Davide,
It would be good to have a bit more warning before cutting a release. 30 or
so mins doesn't give anybody enough time to fix pending issues.
Hello Alex,
I agree but I sent out the announcement today at 10.50am BST for the
2.30pm BST that
Hello folks,
Did the discussion eventually led to this public release ? I have still
requests to access the binary from customers and even from the support
organization.
Where can I get the oak-run 1.0.7 ?
https://issues.adobe.com/secure/attachment/282322/oak-run-1.0.7-SNAPSHOT.jar is
a
Good morning,
I'd like to update
http://jackrabbit.apache.org/creating-releases.html#CreatingReleases-ReleaseArtifacts
for adding some more details here and there for the first-timer on the
release process.
What/where should I update?
Cheers
Davide
21 matches
Mail list logo
