[jira] [Comment Edited] (JCR-3929) Can not create new repository
[
https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056725#comment-15056725
]
Anton P. edited comment on JCR-3929 at 12/14/15 9:31 PM:
-
Met this issue in Version jackrabbit-core-2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
Checked jackrabbit-core-2.10.1:
ConsistencyCheckerImpl line 246 (same code)
Root cause: key = null
{code:title=ConcurrentCache.getSegment(K key)}
private Map> getSegment(K key) {
// Unsigned shift right to prevent negative indexes and to
// prevent too similar keys to all get stored in the same segment
return segments[(key.hashCode() >>> 1) % segments.length];
}
{code}
was (Author: anton p.):
Met this issue in Version jackrabbit-core-2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
Checked jackrabbit-core-2.10.1:
ConsistencyCheckerImpl line 246 (same code)
> Can not create new repository
> -
>
> Key: JCR-3929
> URL: https://issues.apache.org/jira/browse/JCR-3929
>
[jira] [Comment Edited] (JCR-3929) Can not create new repository
[
https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056725#comment-15056725
]
Anton P. edited comment on JCR-3929 at 12/14/15 9:25 PM:
-
Met this issue in Version jackrabbit-core-2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
Checked jackrabbit-core-2.10.1:
ConsistencyCheckerImpl line 246 (same code)
was (Author: anton p.):
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
Checked jackrabbit-core-2.10.1:
ConsistencyCheckerImpl line 246 (same code)
> Can not create new repository
> -
>
> Key: JCR-3929
> URL: https://issues.apache.org/jira/browse/JCR-3929
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Kamil
>
> Creation of fresh repository doesn't work with versions >= 2.7.1
> When I use version 2.6.5 or 2.7.0, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
>
[jira] [Comment Edited] (JCR-3929) Can not create new repository
[
https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056725#comment-15056725
]
Anton P. edited comment on JCR-3929 at 12/14/15 9:25 PM:
-
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
Checked jackrabbit-core-2.10.1:
ConsistencyCheckerImpl line 246 (same code)
was (Author: anton p.):
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
> Can not create new repository
> -
>
> Key: JCR-3929
> URL: https://issues.apache.org/jira/browse/JCR-3929
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Kamil
>
> Creation of fresh repository doesn't work with versions >= 2.7.1
> When I use version 2.6.5 or 2.7.0, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
> - everything work correctly.
> When I switch from 2.7.0 to 2.7.1, remove old repository fold
[jira] [Comment Edited] (JCR-3929) Can not create new repository
[
https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056725#comment-15056725
]
Anton P. edited comment on JCR-3929 at 12/14/15 9:12 PM:
-
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
try {
Map batch = pm.getAllNodeInfos(null,
NODESATONCE);
Map allInfos = batch;
NodeId lastId = null; *// when batch is empty - lastId remains
null*
while (!batch.isEmpty()) {
for (Map.Entry entry : batch.entrySet()) {
NodeId id = entry.getKey();
lastId = id;
count++;
if (count % 1000 == 0) {
log.info(pm + ": loaded " + count + " infos...");
}
if (!CHECKAFTERLOADING) {
// check immediately
NodeInfo nodeInfo = entry.getValue();
checkBundleConsistency(id, nodeInfo, fix,
lostNFound, reports, batch);
}
}
batch = pm.getAllNodeInfos(lastId, NODESATONCE);
if (CHECKAFTERLOADING) {
allInfos.putAll(batch);
}
}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) { *// when lastId = null - cause NPE*
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
} catch (ItemStateException ex) {
throw new RepositoryException("getting nodeIds", ex);
}
{code}
was (Author: anton p.):
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) {
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
{code}
> Can not create new repository
> -
>
> Key: JCR-3929
> URL: https://issues.apache.org/jira/browse/JCR-3929
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Kamil
>
> Creation of fresh repository doesn't work with versions >= 2.7.1
> When I use version 2.6.5 or 2.7.0, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
> - everything work correctly.
> When I switch from 2.7.0 to 2.7.1, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
> I obtain following exception:
> {noformat}
> 2015-11-03 13:16:42.568 INFO [localhost-startStop-1] RepositoryImpl.java:257
> Starting repository...
> 2015-11-03 13:16:42.578 INFO [localhost-startStop-1]
> LocalFileSystem.java:164 LocalFileSystem initialized at path
> D:\jackrabbitdocuments\repository
> 2015-11-03 13:16:42.696 INFO [localhost-startStop-1]
> NodeTypeRegistry.java:870 no custom node type definitions found
> 2015-11-03 13:16:42.974 INFO [localhost-startStop-1]
> DatabaseJournal.java:375 Initialized local revision to 0
> 2015-11-03 13:16:42.975 INFO [localhost-startStop-1]
> DatabaseJournal.java:384 Cluster revision janitor thread not started
> 2015-11-03 13:16:42.976 INFO [localhost-startStop-1]
> DatabaseJournal.java:280 DatabaseJournal initialized.
> 2015-11-03 13:16:42.979 INFO [localhost-startStop-1]
> LocalFileSystem.java:164 LocalFileSystem initialized at path
> D:\jackrabbitdocuments\version
> 2015-11-03 13:16:43.122 ERROR [localhost-startStop-1] RepositoryImpl.java:367
> failed to start Repository: Cannot instantiate persistence manager
> org.apache.jackrabbit.core.persistence.pool.PostgreSQLPersistenceManager
> javax.jcr.RepositoryException: Cannot instantiate persistence manager
> org.apache.jackr
[jira] [Commented] (JCR-3929) Can not create new repository
[
https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056725#comment-15056725
]
Anton P. commented on JCR-3929:
---
Met this issue in Version 2.6.5:
lastId equals null for new repository (no nodes exist)
{code:title=ConsistencyCheckerImpl.java:143}
if (CHECKAFTERLOADING) {
if (pm.exists(lastId)) {
// check info
for (Map.Entry entry :
allInfos.entrySet()) {
checkBundleConsistency(entry.getKey(),
entry.getValue(), fix, lostNFound, reports, allInfos);
}
} else {
log.info("Failed to read all nodes, starting over");
internalCheckConsistency(uuids, recursive, fix,
reports, lostNFoundId);
}
}
{code}
> Can not create new repository
> -
>
> Key: JCR-3929
> URL: https://issues.apache.org/jira/browse/JCR-3929
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Kamil
>
> Creation of fresh repository doesn't work with versions >= 2.7.1
> When I use version 2.6.5 or 2.7.0, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
> - everything work correctly.
> When I switch from 2.7.0 to 2.7.1, remove old repository folder
> (D:\jackrabbitdocuments), drop/recreate journal database and start the server
> I obtain following exception:
> {noformat}
> 2015-11-03 13:16:42.568 INFO [localhost-startStop-1] RepositoryImpl.java:257
> Starting repository...
> 2015-11-03 13:16:42.578 INFO [localhost-startStop-1]
> LocalFileSystem.java:164 LocalFileSystem initialized at path
> D:\jackrabbitdocuments\repository
> 2015-11-03 13:16:42.696 INFO [localhost-startStop-1]
> NodeTypeRegistry.java:870 no custom node type definitions found
> 2015-11-03 13:16:42.974 INFO [localhost-startStop-1]
> DatabaseJournal.java:375 Initialized local revision to 0
> 2015-11-03 13:16:42.975 INFO [localhost-startStop-1]
> DatabaseJournal.java:384 Cluster revision janitor thread not started
> 2015-11-03 13:16:42.976 INFO [localhost-startStop-1]
> DatabaseJournal.java:280 DatabaseJournal initialized.
> 2015-11-03 13:16:42.979 INFO [localhost-startStop-1]
> LocalFileSystem.java:164 LocalFileSystem initialized at path
> D:\jackrabbitdocuments\version
> 2015-11-03 13:16:43.122 ERROR [localhost-startStop-1] RepositoryImpl.java:367
> failed to start Repository: Cannot instantiate persistence manager
> org.apache.jackrabbit.core.persistence.pool.PostgreSQLPersistenceManager
> javax.jcr.RepositoryException: Cannot instantiate persistence manager
> org.apache.jackrabbit.core.persistence.pool.PostgreSQLPersistenceManager
> at
> org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(RepositoryImpl.java:1354)
> [jackrabbit-core-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(RepositoryImpl.java:487)
> [jackrabbit-core-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java:312)
> [jackrabbit-core-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:590)
> [jackrabbit-core-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.jca.JCARepositoryManager.createNonTransientRepository(JCARepositoryManager.java:124)
> [jackrabbit-jca-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.jca.JCARepositoryManager.createRepository(JCARepositoryManager.java:79)
> [jackrabbit-jca-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createRepository(JCAManagedConnectionFactory.java:216)
> [jackrabbit-jca-2.7.1.jar:2.7.1]
> at
> org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createConnectionFactory(JCAManagedConnectionFactory.java:153)
> [jackrabbit-jca-2.7.1.jar:2.7.1]
> at
> org.springframework.jca.support.LocalConnectionFactoryBean.afterPropertiesSet(LocalConnectionFactoryBean.java:118)
> [spring-tx-4.2.0.RELEASE.jar:4.2.0.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
> [spring-beans-4.2.0.RELEASE.jar:4.2.0.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
> [spring-beans-4.2.0.RELEASE.jar:4.2.0.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
> [spring-beans-4.2.0.RELEASE.jar:4.2.0.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapable
[jira] [Commented] (JCR-3937) jackrabbit-jcr-commons bundle incorrectly has google dependency in Export-Package uses clause
[
https://issues.apache.org/jira/browse/JCR-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056035#comment-15056035
]
David Bosschaert commented on JCR-3937:
---
Hi [~mreutegg], yes including it in the parent pom would even be better. And it
would probably be good to use 3.0.1 as [~jsedding] suggests.
I had to flip the declaration of the Import-Package as follows
{code}org.apache.jackrabbit.api.security.user;version="[2.2,3)";resolution:=optional,
*{code}
because otherwise the org.apache.jackrabbit.api.security.user package was
imported twice. This is clearly a change in behaviour of the
maven-bundle-plugin/bnd since the 3.0.x release...
> jackrabbit-jcr-commons bundle incorrectly has google dependency in
> Export-Package uses clause
> -
>
> Key: JCR-3937
> URL: https://issues.apache.org/jira/browse/JCR-3937
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
>Affects Versions: 2.11.3
>Reporter: David Bosschaert
> Attachments: JCR-3937-2.patch, JCR-3937.patch
>
>
> jackrabbit-jcr-commons 2.11.3 has the following Export-Package line:
> {code}org.apache.jackrabbit.value;uses:="javax.jcr,org.apache.jackrabbit.util,com.google.common.collect";version="2.2.1"{code}
> The google uses is actually unnecessary and generated by a bug in the
> maven-bundle-plugin. Using the latest version of that makes the google
> transitive dependency go away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCR-3937) jackrabbit-jcr-commons bundle incorrectly has google dependency in Export-Package uses clause
[
https://issues.apache.org/jira/browse/JCR-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055990#comment-15055990
]
Julian Sedding commented on JCR-3937:
-
I suggest to update to maven-bundle-plugin version 3.0.1 due to FELIX-5062. See
also OAK-3706.
> jackrabbit-jcr-commons bundle incorrectly has google dependency in
> Export-Package uses clause
> -
>
> Key: JCR-3937
> URL: https://issues.apache.org/jira/browse/JCR-3937
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
>Affects Versions: 2.11.3
>Reporter: David Bosschaert
> Attachments: JCR-3937-2.patch, JCR-3937.patch
>
>
> jackrabbit-jcr-commons 2.11.3 has the following Export-Package line:
> {code}org.apache.jackrabbit.value;uses:="javax.jcr,org.apache.jackrabbit.util,com.google.common.collect";version="2.2.1"{code}
> The google uses is actually unnecessary and generated by a bug in the
> maven-bundle-plugin. Using the latest version of that makes the google
> transitive dependency go away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JCR-3937) jackrabbit-jcr-commons bundle incorrectly has google dependency in Export-Package uses clause
[
https://issues.apache.org/jira/browse/JCR-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-3937:
--
Attachment: JCR-3937-2.patch
Thanks for the patch.
I think it would be better to update the plugin version in the parent pom
jackrabbit-parent/pom.xml. This way all modules will use the same version.
What is the reason for your second change related to Import-Package? Is this
just about style or does the sequence matter?
> jackrabbit-jcr-commons bundle incorrectly has google dependency in
> Export-Package uses clause
> -
>
> Key: JCR-3937
> URL: https://issues.apache.org/jira/browse/JCR-3937
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
>Affects Versions: 2.11.3
>Reporter: David Bosschaert
> Attachments: JCR-3937-2.patch, JCR-3937.patch
>
>
> jackrabbit-jcr-commons 2.11.3 has the following Export-Package line:
> {code}org.apache.jackrabbit.value;uses:="javax.jcr,org.apache.jackrabbit.util,com.google.common.collect";version="2.2.1"{code}
> The google uses is actually unnecessary and generated by a bug in the
> maven-bundle-plugin. Using the latest version of that makes the google
> transitive dependency go away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
