[MGNLGS-145] See if we can pull out javax.xml.stream:stax-api and org.apache.geronimo.specs:geronimo-stax-api_1.0_spec from our builds Created: 09/Oct/14 Updated: 27/Nov/18 Resolved: 05/Nov/18 |
|
| Status: | Closed |
| Project: | Google Sitemap (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.1 |
| Type: | Task | Priority: | Critical |
| Reporter: | Zak Greant | Assignee: | Michael Mühlebach |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cleanup, licence, license | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | 6.0 library update |
| Sprint: | Basel 159 |
| Story Points: | 3 |
| Description |
|
Both these artifacts are the same ("Java Streaming API for XML", JSR-173) . The API is included in the JDK since 1.6, so we really don't need to bundle them. Their license information is inconsistent in pom.xml (Apache for the former, GPL+CDDL for the latter) and partly incompatible for us (because of GPL) They're currently coming from JaxB (through google-sitemap module) and Tika, respectively. We might have to add them to the "banned dependencies" in our parent poms. |
| Comments |
| Comment by Magnolia International [ 09/Oct/14 ] |
|
Can someone do even just a manual test and verification (i.e. pull the jars out of a webapp and make sure everything works as expected, including whatever's using jaxb in the sitemap module). I'd also be grateful if someone could compare those jars with the JDK and find relevant information about them. |
| Comment by Antti Hietala [ 06/Jun/18 ] |
|
Timebox to 3 SP |