[
https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670153#action_12670153
]
Reinhard Poetz commented on COCOON3-19:
---------------------------------------
According to http://www.apache.org/legal/src-headers.html#3party we should not
modify or remove any copyright notices or licenses within third-party works.
This means we have to keep the original license header (According to
https://stax-utils.dev.java.net/ Stax-Utils has a BSD style license) and have
to include a reference in the NOTICE file.
Andreas (or anybody else), could you please list all the files that are taken
from StAXUtils and point me to the original license? Thanks!
> [PATCH] stax-sax converter
> --------------------------
>
> Key: COCOON3-19
> URL: https://issues.apache.org/jira/browse/COCOON3-19
> Project: Cocoon 3
> Issue Type: Sub-task
> Components: cocoon-stax
> Reporter: Andreas Pieber
> Assignee: Cocoon Developers Team
> Attachments: cocooon-stax-converter.patch
>
>
> We experimented with wrappers to add SAX-components to StAX pipelines and
> with Adapters between StAX pipelines and SAX pipelines. IMO they work quite
> fine :)
> The problem with this patch is that it relies on the stax-utils project. Most
> classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils
> (https://stax-utils.dev.java.net/) project. This was required since there's
> an architectural issue so that stax-utils can not be used directly as
> reference. I posted at the stax-utils dev mailing list two weeks ago, if they
> could make some of their methods protected instead of private so that we
> could resolve this issue, but I did not receive an answer.
> I created a seperated issue for this problem since there's the opened
> question of how to mark the redistributed classes from the stax-utils
> project. I think Reinhard know ways of how to resolve this problem :)
> I created this issue as an subtask of COCOON3-18 since first the patch of
> COCOON3-18 have to be applied before this patch could be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
