[
https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749138#comment-16749138
]
Shawn McKinney commented on FC-263:
-----------------------------------
Well that explains it. Have never used/tested with Gradle. I'm fine with
cutting another release of the openldap accelerator, with the fix of removing
the tab from position 0. Can't give precise time of when that will be, although
could be rather soon, some numbers of weeks. In the meantime, perhaps you can
use the previous release?
> Unable to resolve maven dependencies for fortress-core v2.0.3
> -------------------------------------------------------------
>
> Key: FC-263
> URL: https://issues.apache.org/jira/browse/FC-263
> Project: FORTRESS
> Issue Type: Bug
> Environment: gradle
> Reporter: Chris Poulsen
> Assignee: Shawn McKinney
> Priority: Major
>
> fortress-core depends on org.openldap:accelerator-(api|impl):1.0-RC41
> which in turn has a parent: org-openldap:accelerator:1.0-RC41
> The parent pom is invalid xml, due to some crap before the <?xml?> entry
> (Content not allowed in prolog).
> Artifact link:
> [https://mvnrepository.com/artifact/org.openldap/accelerator/1.0-RC41]
> Direct pom link:
> [http://central.maven.org/maven2/org/openldap/accelerator/1.0-RC41/accelerator-1.0-RC41.pom]
> That dependency has been broken since ultimo 2015 how can that be possible,
> are no one actually compiling against the released stuff?
> It seems that the 1.0-RC40 pom is valid, but is it safe to use that as a
> replacement? The endless series of RC releases does not exactly inspire
> confidence (or indicate that fortress-core itself is mature/stable due to
> non-released dependencies)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
