API inconsistency - allow to delete Class or Package from the Archive --------------------------------------------------------------------- Key: SHRINKWRAP-411 URL: https://issues.jboss.org/browse/SHRINKWRAP-411 Project: ShrinkWrap Issue Type: Enhancement Components: api Reporter: Piotr Nowicki Labels: API, archive, class, delete, package User might want to delete some resources from the created Archive (e.g. because he doesn't have any control over how it was created in the first place.) Right now he can only use a String-based path to the resource he want to delete. It seems to be an API inconsistency as he can Archive.add(-) Package or Class objects, but cannot invoke Archive.delete(Archive) / Archive.delete(Package). Example: https://gist.github.com/2989390

API inconsistency - allow to delete Class or Package from the Archive --------------------------------------------------------------------- Key: SHRINKWRAP-411 URL: https://issues.jboss.org/browse/SHRINKWRAP-411 Project: ShrinkWrap Issue Type: Enhancement Components: api Reporter: Piotr Nowicki Assignee: Piotr Nowicki Labels: API, archive, class, delete, package Fix For: 1.1.0-alpha-3 User might want to delete some resources from the created Archive (e.g. because he doesn't have any control over how it was created in the first place.) Right now he can only use a String-based path to the resource he want to delete. It seems to be an API inconsistency as he can Archive.add(-) Package or Class objects, but cannot invoke Archive.delete(Archive) / Archive.delete(Package). Example: https://gist.github.com/2989390

API inconsistency - allow to delete Class or Package from the Archive --------------------------------------------------------------------- Key: SHRINKWRAP-411 URL: https://issues.jboss.org/browse/SHRINKWRAP-411 Project: ShrinkWrap Issue Type: Enhancement Components: api Reporter: Piotr Nowicki Assignee: Piotr Nowicki Labels: API, archive, class, delete, package Fix For: 1.1.0-alpha-3 User might want to delete some resources from the created Archive (e.g. because he doesn't have any control over how it was created in the first place.) Right now he can only use a String-based path to the resource he want to delete. It seems to be an API inconsistency as he can Archive.add(-) Package or Class objects, but cannot invoke Archive.delete(Archive) / Archive.delete(Package). Example: https://gist.github.com/2989390