[
https://issues.apache.org/jira/browse/PDFBOX-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880876#action_12880876
]
Jukka Zitting commented on PDFBOX-544:
--------------------------------------
In my experience maintaining separate components only makes sense if they need
to be deployable separately. Do we have a reasonable case where one would need
to deploy one part of FontBox without deploying the others?
> Improved module structure
> -------------------------
>
> Key: PDFBOX-544
> URL: https://issues.apache.org/jira/browse/PDFBOX-544
> Project: PDFBox
> Issue Type: Improvement
> Components: FontBox
> Affects Versions: 0.8.0-incubator
> Reporter: Villu Ruusmann
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The development and maintenance of font formats would be easier if the
> FontBox project would be modularized so that every font format is contained
> in a separate sub-module. Consider different requirements for build- and/or
> run-time dependencies, Java language features, release schedule etc.
> Since FontBox uses Maven2 as its software project management and
> comprehension tool, the modularization activity itself is pretty
> straightforward:
> *) Change the current /pom.xml to proper parent POM.
> *) For every subdirectory under /src/main/java/org/apache/fontbox create a
> separate subdirectory, create a child POM file into it and copy over all the
> relevant files.
> *) Establish module interdependencies. For example, the 'ttf' sub-module
> would depend on 'cmap' and 'encoding' sub-modules, the 'cff' sub-module would
> depend on 'afm' sub-module and so on. There doesn't seem to be any blocking
> cyclic interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
