Hi Jorge,
The service is up now
Chetan Mehrotra
On Fri, Aug 20, 2021 at 8:36 PM Jorge Flórez
wrote:
> Hi all,
> I am not sure if I should report this on this list, probably you already
> know.
> The site at http://oakutils.appspot.com/generate/index is down:
> Error: Ser
Welcome Mohit!
Chetan Mehrotra
On Thu, Aug 15, 2019 at 7:26 PM Matt Ryan wrote:
>
> Welcome Mohit!
>
>
> -MR
>
> On Thu, Aug 15, 2019 at 6:51 AM Julian Sedding wrote:
>
> > Welcome Mohit!
> >
> > Regards
> > Julian
> >
> > On Wed, Au
For S3 there are quite a few options and one suggested by Amit should
be good for our usecase. For Azure specific services we would need to
get an account created and use that from our Jenkins server.
Chetan Mehrotra
On Tue, Jul 31, 2018 at 1:45 PM Amit Jain wrote:
>
>
Chetan Mehrotra
On Wed, Apr 4, 2018 at 5:43 PM, Thomas Mueller
wrote:
> +1
>
> On 04.04.18, 10:23, "Tommaso Teofili" wrote:
>
> Hi all,
>
> In the context of creating an (abstract) implementation for Oak full text
> indexes [1], I'd like to
See OAK-6911
Chetan Mehrotra
On Fri, Feb 16, 2018 at 2:36 AM, Alexander Klimetschek
wrote:
> Hi,
>
> it seems the segment store will inline any binary blob up to ~16KB in the tar
> files and not store them in the BlobStore [1]. The 16 KB limit
> (Segment.MEDIUM_LIMIT) is ha
Need to backport OAK-7147 - Oak run LuceneIndexer indexes excluded parent nodes
regards
Chetan Mehrotra
+1
Chetan Mehrotra
On Thu, Jan 11, 2018 at 6:18 PM, Julian Reschke wrote:
> <https://issues.apache.org/jira/browse/OAK-7060>:
> "RDBDocumentStore.getStats() for SQLServer"
>
> (Due to other priorities this had to wait until today, but I'd like 1.8 to
> shi
Thanks Vikas for the fix!
Chetan Mehrotra
On Fri, Dec 22, 2017 at 2:14 PM, Robert Munteanu wrote:
> On Fri, 2017-12-22 at 06:07 +0530, Vikas Saurabh wrote:
>> Hi Robert,
>>
>> > I am not able to qualify whether this is a valid failure or not,
>> > therefore I&
+1
Chetan Mehrotra
On Thu, Dec 21, 2017 at 4:57 PM, Marcel Reutegger
wrote:
> Hi,
>
> I'd like to backport OAK-5317 to the maintenance branches. It is an
> improvement, but would allow users to run a DocumentNodeStore on more recent
> MongoDB version. I consider the chan
d I definitely hope that we after that can stop making incompatible
> changes as that separations allows us to stop exporting things that are
> meant to be internal...
>
> Angela
>
> On 14/11/17 18:10, "Chetan Mehrotra" wrote:
>
>>Do we want to have explicit versi
Do we want to have explicit version for all packages in oak-core-spi
or should we only do it for packages which we expect code outside of
Oak codebase would be using? As once we version it we cannot change in
backward incompatible way easily
Chetan Mehrotra
On Tue, Nov 14, 2017 at 10:05 PM
+1
Chetan Mehrotra
On Thu, Nov 2, 2017 at 9:26 AM, Vikas Saurabh wrote:
> Hi,
>
> Oak's facet implementation had these two issues [0], [1]. I would like
> to backport those to 1.6 and 1.4 branch.
>
> Thanks,
> Vikas
>
>
> [0]: OAK-6750 - Facet for relative pro
Now build should pass post 1813545
Chetan Mehrotra
On Fri, Oct 27, 2017 at 8:22 PM, Chetan Mehrotra
wrote:
> Oops ... Looks like this impacts whole build. Would look into that
> Chetan Mehrotra
>
>
> On Fri, Oct 27, 2017 at 7:54 PM, Christian Schneider
> wrote:
>> Hi
Oops ... Looks like this impacts whole build. Would look into that
Chetan Mehrotra
On Fri, Oct 27, 2017 at 7:54 PM, Christian Schneider
wrote:
> Hi Chetan,
>
> there are more similar failures. The build then breaks for me
> at oak-upgrade.
>
> .e.g:
&g
Fixed the test now with 1813536
Chetan Mehrotra
On Fri, Oct 27, 2017 at 6:37 PM, Apache Jenkins Server
wrote:
> The Apache Jenkins build system has built Jackrabbit Oak (build #919)
>
> Status: Failure
>
> Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/
> +String mmp = System.getProperty("cmmp");
Better to use system property like "oak.lucene.cmmp"
Chetan Mehrotra
On Tue, Oct 24, 2017 at 9:56 PM, wrote:
> Author: tommaso
> Date: Tue Oct 24 16:26:05 2017
> New Revision: 1813193
>
> URL: http://
+1 given its already in 1.6.2
Chetan Mehrotra
On Mon, Oct 16, 2017 at 9:47 PM, Julian Reschke wrote:
> https://issues.apache.org/jira/browse/OAK-5878
>
> - already in 1.6.2
> - affects only users with RDB persistence
> - avoids one unnecessary repo scans for VersionGC
>
> Best regards, Julian
+1
Chetan Mehrotra
On Tue, Oct 10, 2017 at 8:22 AM, Julian Reschke wrote:
> On 2017-10-10 17:16, Marcel Reutegger wrote:
>>
>> Hi,
>>
>> I'd like to backport OAK-6218 to the maintenance branches. It adds
>> additional information to a DocumentStoreExcept
Fixture looks better option here!
Chetan Mehrotra
On Mon, Oct 2, 2017 at 8:09 AM, Andrei Dulceanu
wrote:
> Hi,
>
> With OAK-6615 [0] we'd like to lay the foundation for including cold
> standby among features which could be included in a benchmark. This means
> that we
ple do configure the Felix WebConsole
[1]. You can try if standalone comes up with your changes to see it
works for basic case
Chetan Mehrotra
[1]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-examples/standalone/src/main/java/org/apache/jackrabbit/oak/standalone/WebConsoleSupport.java
side to see which component has
dependency missing. This is bit tricky in absence of Felix WebConsole.
Probably enabling SCR logs (ds.loglevel=3?) would give some insight
here
Chetan Mehrotra
[1]
27.09.2017 15:43:06.603 *INFO* [main]
org.apache.jackrabbit.oak-query-spi BundleEvent STARTED
27.09.2017
> Now the problem we are running into is, after save operation is performed,
> there is no good way for us to know if save was done (Since save in oak is
> async). So after save we refresh the page, the user sees old content.
Saves in Oak are not async. On a single cluster node if session S1
commi
/document/DocumentNodeStore.java
Chetan Mehrotra
[1]
https://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentNodeStore.java?view=log
[2]
https://github.com/apache/jackrabbit-oak/commits/trunk/oak-store-document/src/main
Its bit buried in layers. I saw few other benchmark use reflection to
access the NodeStore. So for now using that to move forward
Chetan Mehrotra
On Tue, Sep 26, 2017 at 3:32 PM, Michael Dürig wrote:
>
> I tend to agree with Davide. Especially since the use case is for
> benchmar
class. Would
that be ok to do?
Chetan Mehrotra
[1]
https://github.com/chetanmeh/jackrabbit-oak/blob/OAK-6535/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/property/PropertyIndexCleaner.java#L64
[2]
https://github.com/chetanmeh/jackrabbit-oak/blob/OAK-6535/oak-benchmarks
OAK-6635 is now resolved.
Chetan Mehrotra
On Fri, Sep 22, 2017 at 3:25 PM, Davide Giannella wrote:
> Hello team,
>
> I'm planning to cut Oak on Monday 25th.
>
> There's however a blocker which will block the release if not resolved
> or re-scheduled: https://issue
I would like to backport OAK-6637 which improves the resilience of
locking and ensures any exception should not cause the lock to be lost
preventing further index updates
Chetan Mehrotra
Its was +0 ;)
Chetan Mehrotra
On Wed, Sep 13, 2017 at 2:15 PM, Vikas Saurabh wrote:
> Hi Chetan,
>
> Was your concern a -1 or a +/- 0?
>
> Thanks,
> Vikas
> The fix is fairly simple and I'd like to backport it to 1.4 and 1.6
> branch (where OAK-3768 went).
Would the backport be of use now? As any upgrade I think would happen
first to initial release from that branch where this fix would not be
present
Chetan Mehrotra
On Wed, Sep 13, 20
n OAK-6575
As for OAK-6575 the approach taken there has been discussed in detail
at [1] and in the end there was consensus on the proposed approach by
Ian.
Chetan Mehrotra
[1] http://markmail.org/thread/lhljp2ksegw7dcod
On Mon, Sep 4, 2017 at 5:25 PM, Francesco Mari wrote:
> The POC for
You can find it
https://jackrabbit.apache.org/oak/docs/differences.html#Node_Name_Length_Limit
Chetan Mehrotra
On Fri, Sep 1, 2017 at 2:55 PM, mouli ch wrote:
> Team,
>
> What is the node name length limit which is backed by MongoDB.
>
> Thanks
> Mouli Chintakunta
I would like to backport OAK-6339 to 1.6 branch. This change would be
backported to both segment implementation as its impacting collection
of repo stats for large repo via oakRepoStats script
Chetan Mehrotra
)
+this.mountInfoProvider = services.get(0);
+else
+throw new IllegalArgumentException("Found " +
services.size() + " MountInfoProvider references, expected at most
1.");
You can also use WhiteboardUtils#getService here which hides this stuff
Chetan Mehrotra
On Tue, Aug
OAK-6227 was meant to address similar requirement. May be we add this
to CheckpointMBean
Chetan Mehrotra
On Mon, Aug 28, 2017 at 9:40 PM, Michael Dürig wrote:
>
> Hi,
>
> I would prefer to not make the
> org.apache.jackrabbit.oak.segment.SegmentNodeStore#getCheckpoints method
&
This looks interesting!.
Is this bound to Lucene or can possibly be used for Solr also (if we
generalize FulltextQueryTermsProvider concept). If yes then we can
name the module as oak-search-mt
Chetan Mehrotra
On Fri, Aug 25, 2017 at 1:14 PM, Tommaso Teofili
wrote:
> Hi all,
>
> as pa
Hi,
Is anyone getting mail notification for any pull request sent on
https://github.com/apache/jackrabbit-oak/. I see such mails for Sling
but not for Oak
Chetan Mehrotra
hich
converts the Binary to provided type and then have DataStores provide
the AdapterFactory.
This would indeed avoid any new methods in existing objects and
provide a single entry point.
+1 for this approach
Chetan Mehrotra
On Thu, Aug 24, 2017 at 6:16 AM, Ian Boston wrote:
> Hi,
>
ment for such cases (specially UC3 and UC4).
Hence the push for this approach to enable further work on them going
forward.
Chetan Mehrotra
On Thu, Aug 24, 2017 at 5:41 AM, Michael Dürig wrote:
>
>
> On 24.08.17 14:32, Chetan Mehrotra wrote:
>>>
>>> Why not just a
ferent Blob types.
Having adaptable support allows to extend this later with minimal changes.
Chetan Mehrotra
[1] https://wiki.apache.org/jackrabbit/JCR%20Binary%20Usecase#UC4
On Thu, Aug 24, 2017 at 5:25 AM, Michael Dürig wrote:
>
>
> On 24.08.17 13:38, Chetan Mehrotra wrote:
>>
ort org.apache.jackrabbit.oak.api.Adaptable
Binary b = ...
SignedBinary sb = null
if (b instanceof Adaptable) {
sb = ((Adaptable)b).adaptTo(SignedBinary.class);
}
Within Sling
Have an AdapterManager implemented in Sling JCR Base [1] which uses
above approach
Chetan Mehrotra
[1] https://github.com/apache/sl
plemented #2 can be done in Sling side
Chetan Mehrotra
On Thu, Aug 24, 2017 at 3:06 AM, Ian Boston wrote:
> Hi,
>
> On 24 August 2017 at 10:20, Julian Sedding wrote:
>
>> Hi
>>
>> On Thu, Aug 24, 2017 at 9:27 AM, Ian Boston wrote:
>> &g
e place though those layers need not
be aware of SignedBinary support (its specific to S3 impl)
Chetan Mehrotra
Adaptable) {
return (type)b.adaptTo(type);
}
return null
}
}
So just another level of abstraction.
Chetan Mehrotra
d -> S3DataRecord
- Blob -> ArrayBasedBlob
- Blob ... MongoBlob
So at JCR level where we have a PropertyState we cannot determine if
the Blob provided by it can provide a signed binary without adding
such instance of check at each place. Hence the adaptor based proposal
Chetan Mehrotra
ng BlobStore impl decides to provide the adaption
implementation.
I do not see how instance of checks can be expressed across all these layers
A rough sketch of any alternative proposal would be helpful to decide
how to move forward
Chetan Mehrotra
ementation in Oak on line of Sling Adaptor support [1]
For current usecase we would provide an adaptation to SignedBinary
public interface SignedBinary {
URI getUri()
}
Chetan Mehrotra
[1]
https://github.com/apache/sling/tree/trunk/bundles/api/src/main/java/org/apache/sling/api/adapter
O
in the distant
> (relatively) future bypassing fresh ACL constraints saved to Oak.
Fair point. Then lets drop the ttl paramater
Chetan Mehrotra
package to expose AdaptableBinary
Proposal 'org.apache.jackrabbit.oak.jcr.binary'. We would also later
possibly need an AdaptableBlob for Oak layer
2. Under which package to expose SignedBinary
Proposal 'org.apache.jackrabbit.oak.api.blob' in oak-api
Thoughts?
Chetan Mehrotra
ly be valid for certain time
To meet this requirement various approaches were suggested like using
Adaptable pattern in Sling, or having a new api in Binary object.
Would follow up with a sketch for such an API
Chetan Mehrotra
[1] http://docs.aws.amazon.com/AmazonS3/lates
> +org.slf4j.*;resolution:=optional,
This should probably not be optional as its used by code
Chetan Mehrotra
On Mon, Aug 21, 2017 at 2:09 AM, wrote:
> Author: adulceanu
> Date: Mon Aug 21 09:09:05 2017
> New Revision: 1805608
>
> URL: http://svn
At time index corruption is being seen which can be attributed to
issue fixed in OAK-5238. To address them I need to backport this to
1.4 and 1.2 branch.
This change is slightly bigger so need to be done carefully
Chetan Mehrotra
/of/output/dir
Hope this would be useful in other cases also
Chetan Mehrotra
[1] https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run#export
ontent
in version store using the NodeStore API directly. But then you would
need to be careful and understand how versioned data is stored
Chetan Mehrotra
- AccessControlValidatorProvider
- PrivilegeValidatorProvider
- UserValidatorProvider
- CacheValidatorProvider
- TokenValidatorProvider
- PermissionHook
- JcrAllCommitHook
Chetan Mehrotra
g etc. So may be better to say avoid nodetypes
with restrictive definition. However do create new nodetype (or
mixins) to mark the domain objects in your application content.
Chetan Mehrotra
I want to backport OAK-6333. This is a change in logic which would be
locked behind a feature flag. This flag would allow users to enable
true cost for query calculations and ensure that expected index gets
picked up
Chetan Mehrotra
Hi,
OAK-6493 fixes an issue around disabling of NRT Indexing feature.
Chetan Mehrotra
+1
Chetan Mehrotra
On Wed, Jul 26, 2017 at 2:22 PM, Marcel Reutegger
wrote:
> Hi,
>
> OAK-6495 is a minor improvement that falls back to the classic node state
> comparison in DocumentNodeStore when the journal is broken. I consider the
> changes low risk while they e.g. gua
+1
Chetan Mehrotra
On Tue, Jul 18, 2017 at 5:54 PM, Marcel Reutegger
wrote:
> Hi,
>
> I'd like to backport OAK-6462 to the 1.6 branch sometime after the next 1.7.x
> release. The issue can cause OOME in DocumentNodeStore based deployments with
> usage patterns that involv
OAK-5899 - PropertyDefinitions should allow for some tweakability to
declare usefulness
Chetan Mehrotra
t would be better to get #A implemented now with an
eye for requirements of #B. So that we make some progress here
Chetan Mehrotra
[1] https://wiki.apache.org/jackrabbit/JCR%20Binary%20Usecase
Instead of commons-math can we use Metric Histogram (which I also
suggested earlier in the thread). This would avoid downstream Oak
users to include another dependency as Oak is already using Metrics in
other places.
Can we reconsider this decision?
Chetan Mehrotra
On Tue, Jul 4, 2017 at 4:45
I would like to have OAK-5899 fixed for 1.6. Have marked it as a blocker.
Chetan Mehrotra
On Thu, Jul 6, 2017 at 2:52 PM, Davide Giannella wrote:
> Hello team,
>
> I'm planning to cut Oak on Monday 10th July.
>
> If there are any objections please let me know. Otherwise I wi
Fixed that with OAK-6417
Chetan Mehrotra
On Tue, Jul 4, 2017 at 3:04 PM, Chetan Mehrotra
wrote:
> While running below in oak-remote module I am seeing lots of debug
> output on console.
>
> mvn clean install -PintegrationTesting
>
> Is anyone else also observing that? Not
While running below in oak-remote module I am seeing lots of debug
output on console.
mvn clean install -PintegrationTesting
Is anyone else also observing that? Not sure why all debug logs are
getting enabled
Chetan Mehrotra
way that Metrics based logic
gets used if avialable otherwise fallback to a simple mean based
implementation [2].
May be we can make it a required dependency?
Chetan Mehrotra
[1]
http://metrics.dropwizard.io/3.1.0/apidocs/com/codahale/metrics/Histogram.html
[2]
https://github.com/apache/jackrabbit
Reverted the commit with 1800742. The build should now pass
Chetan Mehrotra
On Tue, Jul 4, 2017 at 1:51 PM, Francesco Mari wrote:
> Thanks for taking care of this.
>
> 2017-07-04 10:17 GMT+02:00 Chetan Mehrotra :
>
>> My fault. Looks like code used API from Tika 1.15 which I
My fault. Looks like code used API from Tika 1.15 which I am yet
testing. Would fix it now
Chetan Mehrotra
On Tue, Jul 4, 2017 at 1:34 PM, Francesco Mari wrote:
> When compiling trunk (r1800739) I get the following error in the oak-lucene
> module.
>
> [ERROR] Failed to
As of now yes. This would require support for per field analyzer and
also separate analyzer for index time and query time. Current design
was done to support such a usecase eventually but so far its not
implemented
Chetan Mehrotra
On Mon, Jun 26, 2017 at 1:19 PM, Alvaro Cabrerizo wrote:
> He
2. The index data may be out of sync with current session revision
state. For e.g. if a property /a/b/@foo = bar was indexed at revision
R1 and then it got changed to /a/b/@foo = baz in R2 (which is yet not
indexed) then doing a query with session at R2 should not allow that
path as part of final res
reader (see NRTIndex
class). Probably we should have a way to add description at time of
Metric creation.
Chetan Mehrotra
Hi Team,
Please have a look at proposal at OAK-6346 to set base
comparisonVersion of baseline plugin to current stable release of
1.6.0.
This is done to ensure that any in progress work in trunk which get
release perioduially does not require bump of major version for new
features
Chetan
y user of Oak as an API. I know that newly removed
method is not yet part of stable release but then we had a unstable
release with new method. I see 2 options
1. Deprecate the method instead of removing it
2. Or better specify comparisonVersion to 1.6 via [1]
Chetan Mehrotra
[1]
http://felix.ap
actual size of the index [Math.min(definition.getEntryCount(), getReader().
> *numDocs())*].
A very late reply here but I have opened OAK-6333 to remove this
artificial limit of 1000 in cost estimates. Once we have consensus on
the approach then I would fix and backport it to older branched
Chetan Mehrotra
is
Hard to give a generic advice here. It all depends on type of query,
index definition and content structure. So would need such details to
provide any suggestion.
Chetan Mehrotra
as part of that index and the repo
size in terms of Mongo stats if possible?
Chetan Mehrotra
Hi Austin,
I believe this query was asked earlier also. See thread at
https://lists.apache.org/thread.html/bb48b79ae9031c7fc3deb3992a32ac8e3ab53205e9fd362318812e30@%3Coak-dev.jackrabbit.apache.org%3E
Chetan Mehrotra
On Wed, Jun 7, 2017 at 1:25 AM, Austin Zhang wrote:
> Hi,
>
> I’m
https://issues.apache.org/jira/browse/OAK-1456>) could do the trick. I
This mode is useful for property index as in the end it removes the
async flag and makes the index synchronous which would cause issues
for lucene based index
Chetan Mehrotra
[1] https://jackrabbit.apache.org/oak/docs/query/
A minor fix in oak-run tooling https://issues.apache.org/jira/browse/OAK-5961
Chetan Mehrotra
You should be able to use same approach as used for Jackrabbit with
Oak. The standalone example application server would listen at port
8080 and support remote access via DavEx (at `/server`) and WebDAV
(at `/repository/default`).
Chetan Mehrotra
On Fri, Jun 2, 2017 at 12:23 AM, Austin Zhang
https://issues.apache.org/jira/browse/OAK-6267
This is required to fix a bug for setups where bundling is enabled. It
affects DocumentNodeStore based setups
Chetan Mehrotra
SGi service registry and
then any component can look up that service and configure a reporter
for it
Chetan Mehrotra
ak. Hence no needs for them
to be in Oak
Chetan Mehrotra
On Mon, May 29, 2017 at 6:50 PM, wrote:
> +private static final int CHILDREN_CAP = getInteger("children.cap", 100);
Better to have system property prefix with 'oak' i.e. 'oak.children.cap'
Chetan Mehrotra
pes of reporters
Chetan Mehrotra
ter. This is used in Sling to
report the metrics to Felix WebConsole [1] and [2]
Chetan Mehrotra
[1]
https://github.com/apache/sling/blob/trunk/bundles/commons/metrics/src/main/java/org/apache/sling/commons/metrics/internal/MetricWebConsolePlugin.java#L106
[2]
https://sling.apache.org/documentat
Need to backport OAK-4668 [1] to older branches. This is required to
prevent loss of checkpoint in unstable topology
Chetan Mehrotra
[1] https://issues.apache.org/jira/browse/OAK-4668
+1.
Chetan Mehrotra
On Tue, May 23, 2017 at 12:30 PM, Julian Reschke wrote:
> https://issues.apache.org/jira/browse/OAK-4863
As mentioned in previous mail can we wait for 1.7.0 release such that
all new changes in RevisionGC get some longevity testing. And after
that we do the backports.
Chetan Mehrotra
On Fri, May 19, 2017 at 12:29 PM, Julian Reschke wrote:
> https://issues.apache.org/jira/browse/OAK-5571
On Thu, May 18, 2017 at 5:51 PM, Julian Reschke wrote:
> (needed for a subsequent backport of OAK-5704)
Probably we should wait for OAK-5704 for sometime after 1.7.0 is cut
and that build is subjected some longevity testing before backporting
it to branched
Chetan Mehrotra
via this object
should be closer to the cache size you have configured. If its much
higher than configured cache size then that would need to be looked
into
What type of setup is this Document/Mongo or Tar?
Chetan Mehrotra
the restriction for each path and at the
repository state per current JCR Session (except fulltext constraints)
Chetan Mehrotra
s documents under
> /nodeA/nodeB/nodeC so any query under this path is satisfied by both
One way it would help is that entryCount for second index would be
smaller compared to first and hence queries with path restriction for
second index would have lesser cost
Chetan Mehrotra
> - Rebuilding Assets index takes several days
Is the time spent in text extraction?
Would the code always specify path restriction in the queries for
my:Asset? If yes then you can just move the index definition under
respective paths
Would that be an option
Chetan Mehrotra
On Tue, May
Any reason for having separate definitions for same nodetype?
Chetan Mehrotra
On Tue, May 16, 2017 at 7:52 PM, Alvaro Cabrerizo wrote:
> Hello,
>
> Actually, it is OAK-5449. Sorry, I hadn't seen it.
>
> On the other hand, having these two definitions under oak:in
This looks similar to OAK-5449 (not yet fixed). Can you give a sample
index definition there and some usecase details which is leading to
ambiguity in index selection.
In general index selection should not have multiple competing index
definitions hence interested in knowing setup details
Chetan
the existing commands to new approach
Chetan Mehrotra
uld be on
id which should be stable order.
Chetan Mehrotra
avoids the dependency to the Apache Felix inventory support.
Note that dependency is purely optional
Chetan Mehrotra
in single invocation.
For an example see [2] which captures the index related details in a
single page as part of OAK-6080 work.
I believe this would reduce churn while diagnosing any setup issue!
Thoughts? Would it make sense to invest here and implement various printers?
Chetan Mehrotra
[1]
htt
1 - 100 of 773 matches
Mail list logo