[ 
https://issues.apache.org/jira/browse/JCR-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515499#comment-15515499
 ] 

Julian Reschke edited comment on JCR-4028 at 9/23/16 5:56 AM:
--------------------------------------------------------------

Interesting. Some projects are missing, and jackrabbit-spi-commons has a 
timestamp 4 days later than the other parts; dunn what went wrong here.

The problem is also present in 
https://repo.maven.apache.org/maven2/org/apache/jackrabbit/jackrabbit-spi-commons/2.6.6/...


was (Author: reschke):
Interesting. Some projects are missing, and jackrabbit-spi-commons has a 
timestamp 4 days later than the other parts; dunn what went wrong here.

> Artifact for jackrabbit-spi:2.6.6 is missing in Maven central repository
> ------------------------------------------------------------------------
>
>                 Key: JCR-4028
>                 URL: https://issues.apache.org/jira/browse/JCR-4028
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi
>    Affects Versions: 2.6.6
>         Environment: Maven 3.3
>            Reporter: Torsten Friebe
>            Priority: Minor
>
> The jackrabbit-spi-2.6.6.jar is missing in Maven central repository. When 
> defining the dependency in a Maven POM  
> {code}
> <dependency>
>       <groupId>org.apache.jackrabbit</groupId>
>       <artifactId>jackrabbit-spi</artifactId>
>       <version>2.6.6</version>
> </dependency>
> {code}
> For unknown reasons the 2.6.6 version provides not all artifacts:
> ​http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.jackrabbit%22%20AND%20v%3A%222.6.6%22
> as compared to 2.6.5 release version:
> ​http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.jackrabbit%22%20AND%20v%3A%222.6.5%22
> To enable a smooth upgrade from 2.6.5 to 2.6.6 (to fix JCR-3883 / 
> CVE-2015-1833) it would be very helpful if the missing artifacts are added to 
> the maven central repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to