[
https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744200#comment-16744200
]
Shawn McKinney commented on FC-263:
-----------------------------------
> That dependency has been broken since ultimo 2015 how can that be possible,
> are no one actually compiling against the released stuff?
I've verified a <TAB. character is in position one of that file,
[accelerator-1.0-RC41.pom|http://central.maven.org/maven2/org/openldap/accelerator/1.0-RC41/accelerator-1.0-RC41.pom].
What I can't verify is that the dependency is broken. It compiles just fine in
every env I've tested in since 2015, which includes windows, various flavors of
linux, Mac, etc.
Can you supply a test case where this dependency doesn't resolve?
> 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)
The accelerator is used for a new LDAPv3 control for RBAC operations with
OpenLDAP. If you aren't using this protocol, (not calling any APIs under
AccelMgr), then you can downgrade to lower version w/out any side effect
whatsoever.
> 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)
