[
https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749162#comment-16749162
]
Chris Poulsen commented on FC-263:
----------------------------------
Thanks, since switching to gradle I have been hit by a couple of places where
maven seems way more lenient with respect to what it accepts. Though I did not
expect it to accept invalid xml.
We still have a good amount of work left on other parts of our software before
the permission server can not be postponed anymore, so I guess that waiting for
next release is not going to cause us any major grief. (And as a work-around I
could use a version with the fixed pom from our local maven repository, while
waiting for the 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)
