xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Adams <gl...@skynav.com>
Subject Re: Latest 2.2.0-SNAPSHOT broken fop-2.2.0-20161020.085836-42
Date Fri, 21 Oct 2016 01:07:38 GMT
You could always download the source tree from trunk and build the maven
artifacts locally.

On Thu, Oct 20, 2016 at 6:31 PM, Jon Wu <jon@wuservices.com> wrote:

> Thanks for the quick fix Glenn!
>
> Do you know if there's an easy way for me to use some FOP 2.2 without
> depending on the latest SNAPSHOT until the final is released?
>
> Wasn't sure if there was an easy solution to using a newer than official
> version and staying on the same build without having my own Maven server,
> but I'm pretty new to SBT/Ivy/Maven. The current version works for what
> I've needed it for, but pointing to SNAPSHOT causes long daily dependency
> resolutions and it could break any time of course.
>
> On Thu, Oct 20, 2016 at 3:01 PM Glenn Adams <glenn@skynav.com> wrote:
>
>> Stand by. I will commit a fix to this configuration bug in a few moments.
>>
>> On Thu, Oct 20, 2016 at 2:38 PM, Jon Wu <jon@wuservices.com> wrote:
>>
>> Can SNAPSHOT be republished?
>>
>> I've been using 2.2.0-SNAPSHOT for compatibility with the latest PDFBox,
>> but my build broke this morning because I think the last published snapshot
>> is bad.
>>
>> Should https://repository.apache.org/content/repositories/snapshots/org/
>> apache/xmlgraphics/fop/2.2.0-SNAPSHOT/fop-2.2.0-20161020.085836-42.pom,
>> have <version>2.2.0-SNAPSHOT</version> instead of
>> <version>${fop.version}</version> like the other POM files?
>>
>> I get this error in SBT
>> [warn] io problem while parsing ivy file: https://repository.apache.org/
>> content/repositories/snapshots/org/apache/xmlgraphics/fop/2.2.0-
>> SNAPSHOT/fop-2.2.0-20161020.085836-42.pom: Impossible to load parent for
>> file:/Users/jon/.ivy2/cache/org.apache.xmlgraphics/fop/
>> ivy-2.2.0-SNAPSHOT.xml.original. Parent=org.apache.xmlgraphics#
>> fop-parent;${fop.version}
>>
>> ----- RELATED QUESTION -----
>> It's brittle for my build to depend on the latest SNAPSHOT working,
>> however there are so many transitive dependencies of the latest FOP. Is
>> there an easy way for me to keep referring to the same SNAPSHOT build + all
>> its dependencies?
>>
>>
>>

Mime
View raw message