[JBoss JIRA] Created: (SHRINKDESC-25) Import / Export should be able to handle unmapped entires
by Aslak Knutsen (JIRA)
Import / Export should be able to handle unmapped entires
---------------------------------------------------------
Key: SHRINKDESC-25
URL: https://jira.jboss.org/browse/SHRINKDESC-25
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Reporter: Aslak Knutsen
When using JAXB marshal/unmarshal, things that are not mapped in the JAXB model will not be exported. This means the Descriptors will have to map every possible option which is a bit tedious, and all comments etc will be gone.
The JAXB Binder should fix this according to spec/javadoc, but the RI bundled with JDK does this in a very simple way. It can map partial parts of a xml doc, but that part has to be fully mapped. but even fully mapped, comments are lost. (the complete mapped node is replaced, not merged like in EclipseLink Moxy)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (SHRINKDESC-47) Support for Java 1.5
by David Allen (JIRA)
Support for Java 1.5
--------------------
Key: SHRINKDESC-47
URL: https://issues.jboss.org/browse/SHRINKDESC-47
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Components: api
Environment: Release 0.1.4
Java 1.5.0_06 (Sun)
Reporter: David Allen
The compiler plugin was setup to target Java 1.6 only. Despite ShrinkWrap and Arquillian targeting 1.5, with this project included, everything is limited to Java 1.6 environments only.
I have already re-built 0.1.4 locally with 1.5 and everything works fine. Is there some reason why Java 1.6 is required for ShrinkWrap Descriptors?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (SHRINKWRAP-233) addClass with DefaultPackage opens addPackage to null arguments
by Aslak Knutsen (JIRA)
addClass with DefaultPackage opens addPackage to null arguments
---------------------------------------------------------------
Key: SHRINKWRAP-233
URL: https://jira.jboss.org/browse/SHRINKWRAP-233
Project: ShrinkWrap
Issue Type: Bug
Reporter: Aslak Knutsen
When adding a Class in addClass, we do a addPackage with a Filter to match inner classes of that class.
When adding a Class in Default package, the Package we padd to addPackage is null. Meaning addPackage can't verify non null values.
The downside is, if someone happens to add, e.g.
addPakcage(true, Package.get("some-missing-package")), addPackage will be called with null, and null means /, which means all found packages are added.
We need to split addPackage(boolean, Filter, Package...) into two methods, one external which does the null checks from the user and one internal that does not check for null(to support Class in default package).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months