incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Svante Schubert (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ODFTOOLKIT-126) ODFDOM JAR should become an OSGi component
Date Fri, 06 Apr 2012 00:14:23 GMT

    [ https://issues.apache.org/jira/browse/ODFTOOLKIT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247878#comment-13247878
] 

Svante Schubert commented on ODFTOOLKIT-126:
--------------------------------------------

Hi Jeremias,
Here the Netbeans DIFF with your patch adapted for the latest trunk version. Please review
and respond if similar changes might be possible for the other ODF Toolkit components.

Thanks,
Svante
                
> ODFDOM JAR should become an OSGi component
> ------------------------------------------
>
>                 Key: ODFTOOLKIT-126
>                 URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-126
>             Project: ODF Toolkit
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 0.8.5
>         Environment: Operating System: All
> Platform: All
>            Reporter: Svante Schubert
>            Assignee: Svante Schubert
>            Priority: Minor
>             Fix For: 0.8.7
>
>         Attachments: odfdom-osgi.diff, vcs-diff1306862663200911416.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> This feature was already last year briefly discussed on the list and as it basically
only needs new manifest entries easily editable by our pom.xml, it seems to be a low hanging
fruit for us!
> Taking our general test driven approach, we might want to need a test first, telling
us, that our current odfdom.jar is no OSGi package and apply the manifest entries afterwards.
> Two approaches seems reasonable and should be investigated:
> http://www.aqute.biz/Code/Bnd
> or
> Pax Exam
> http://wiki.ops4j.org/display/paxexam/Pax+Exam
> an integration testing framework for OSGi, which might help us as well on integration
testing.
> NOTE: Currently the JUnit tests work on the class files not on JAR and tests requiring
access to the manifest (within the JAR) fail, as it is not in a directory aside, but only
in the JAR.
> To become a good OSGi package there are in addition to the manifest entries some basic
rules for OSGi packages, which might help us as well in general.
> For instance the lately discussed semantic of versioning numbers.
> See
> http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf
> I am curious, if there are more useful rules for ODFDOM suggested by OSGi.
> If someone is curious to dive into this, I would love to get some feed-back on the above
given approaches (pro/con) and/or just review some patch given.
> Cheers,
> Svante

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message