pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PDFBOX-499) Maven pom.xml & directory structure incorrect for the FontBox 0.8-incubating release
Date Wed, 05 Aug 2009 10:19:14 GMT

     [ https://issues.apache.org/jira/browse/PDFBOX-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting updated PDFBOX-499:

    Affects Version/s: 0.8.0-incubator
        Fix Version/s:     (was: 0.8.0-incubator)

I copied the 0.8.0-incubating files to 0.8.0-incubator, so any downstream dependencies to
that version should work as soon as the copied files are synced to Maven central.

Because of this issue, the version of the release for Maven clients is "0.8.0-incubator" instead
of "0.8.0-incubating". This shouldn't be too much of an issue, and I wouldn't create a new
release just to fix this issue. Lets just keep this in mind when we do the next FontBox release.

> Maven pom.xml & directory structure incorrect for the FontBox 0.8-incubating release
> ------------------------------------------------------------------------------------
>                 Key: PDFBOX-499
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-499
>             Project: PDFBox
>          Issue Type: Task
>          Components: FontBox
>    Affects Versions: 0.8.0-incubator
>            Reporter: Niall Pemberton
>            Priority: Critical
>         Attachments: foxbox-assembly.patch, foxbox-pom.patch, pom.xml
> The version number in the pom.xml for the FontBox 0.8-incubating release is incorrectly
set to "0.8.0-incubator" rather than "0.8.0-incubating"
> Also the directory structure in the maveb2 repo is also incorrect:
> http://repo1.maven.org/maven2/org/apache/pdfbox/fontbox/0.8.0-incubator/
> ..it should be
> http://repo1.maven.org/maven2/org/apache/pdfbox/fontbox/0.8.0-incubating/
> I believe this needs a new releass to fix this.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message