[
https://issues.apache.org/jira/browse/PDFBOX-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved PDFBOX-387.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0-incubator
Assignee: Jukka Zitting
Thanks! I committed the updated POM files in revision 718459.
In revision 718464 I made some further improvements like SNAPSHOT versions,
org.apache.pdfbox groupId, the Apache parent POM, better dependency scopes, etc.
The main purpose of the POM files in PDFBox is to serve as Maven metadata when
deploying releases to the central Maven repository. An additional benefit is
that the POMs make it easier to set up the project in many IDEs.
The normal build is based on Ant, and building with Maven is not supported.
Perhaps we should add some big warning (or even an error) to the Maven build to
discourage people from using Maven for other than the purposes listed above.
> new Maven pom.xml files for pdfbox, fontbox, and jempbox
> --------------------------------------------------------
>
> Key: PDFBOX-387
> URL: https://issues.apache.org/jira/browse/PDFBOX-387
> Project: PDFBox
> Issue Type: Improvement
> Reporter: Sean Sullivan
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.8.0-incubator
>
> Attachments: fontbox-pom.xml, jempbox-pom.xml, pom.xml
>
>
> I checked out the pdfbox trunk code from svn.apache.org and tried using Maven
> to compile the project. It simply did not work.
> The two pom.xml files (pdfbox, fontbox) in Subversion are incomplete and
> jempbox library doesn't event have a pom.xml file.
> I created a pom.xml file for jempbox and edited the other two (pdfbox,
> fontbox) pom.xml files.
> I am attaching 3 pom.xml files to this issue. Please review these files and
> commit to svn.apache.org
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
