| Summary: | does papyrus need org.pushingpixels.trident? | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | David Williams <david_williams> |
| Component: | Core | Assignee: | Camille Letavernier <cletavernier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cletavernier, rschnekenburger, vincent.lorenzo |
| Version: | unspecified | Flags: | cletavernier:
documentation-
|
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
David Williams
Hello David, I've never heard of this plug-in/feature. We're not using it in Papyrus (Not directly, at least). Could this be related to E4/XWT, on which Papyrus depends ? Yes, it could be related to e4/xwt. As far as I know, xwt will not be part of the Juno repository, so ... not sure how you "package up" the rest of xwt, but you might need to do a bit more to get this third party bundle too? (or, convince xwt to change the way they do it?). Be sure to work out with the e4/xwt team that even if they are not putting xwt into Juno, that you are [if I am seeing things right]. This would have to be carefully coordinated, since there might be a reason that they are not ... for example, maybe they don't sign jars, or don't do some other requirement required for inclusion? Just to cross reference, I opened bug 370974 on the general issue if one project can be on release train, if a dependency is not. (dont't mean to cause problems for you ... but, seems an important issue). Thanks, The following actions have been taken: - XWT has been forked to the Papyrus namespace, according to CQ 6333 - A CQ has been opened so that Papyrus can depend on org.pushingpixels.trident (CQ 6393) I think the problem is fixed. |