October 2010 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] Created: (SHRINKWRAP-175) Review Filter usage in API for consistency and applicability

by Andrew Lee Rubinger (JIRA)

Review Filter usage in API for consistency and applicability ------------------------------------------------------------ Key: SHRINKWRAP-175 URL: https://jira.jboss.org/browse/SHRINKWRAP-175 Project: ShrinkWrap Issue Type: Task Components: api Reporter: Andrew Lee Rubinger Fix For: 1.0.0-beta-1 Usage of "Filter" is currently sprinkled about inconsistenty. Ensure it's applied on all multi-* operations (like ClassContainer.addClasses) and its JavaDoc is updated. -- 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, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-110) Code Review and Action Items on ExtensionLoader/ServiceExtensionLoader

by Andrew Lee Rubinger (JIRA)

Code Review and Action Items on ExtensionLoader/ServiceExtensionLoader ---------------------------------------------------------------------- Key: SHRINKWRAP-110 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-110 Project: ShrinkWrap Issue Type: Task Components: api, impl-base Reporter: Andrew Lee Rubinger We should do a community review on the ExtensionLoader API and ServiceExtensionLoader implementation. This is the mechanism used to power Assignable.as(); * Archives API should not expose extension loading configuration (SHRINKWRAP-102) * ServiceExtensionLoader needs documentation at class-level and on methods * ServiceExtensionLoader is not Thread-safe (or documented that this is the responsibility of the client, ArchiveBase, which does not sync access) * OK to always use TCCL at time of instantiation to find extension impls and classes? * ServiceExtensionLoader instance needs to be carried in the state of every archive? Should some Assignable types be given access to different service extension loaders? To me this looks like a singular point of configuration possibly warranting use of a Singleton. * All extension loading as a feature needs Wiki documentation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-172) Clean up API

by Andrew Lee Rubinger (JIRA)

Clean up API ------------ Key: SHRINKWRAP-172 URL: https://jira.jboss.org/browse/SHRINKWRAP-172 Project: ShrinkWrap Issue Type: Task Components: api Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-beta-1 Container task for minor API changes needed before we can lock to backwards-compat in 1.0.0-beta-1 -- 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, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-179) Container.setXX methods should support the new Package construct

by Aslak Knutsen (JIRA)

Container.setXX methods should support the new Package construct ---------------------------------------------------------------- Key: SHRINKWRAP-179 URL: https://jira.jboss.org/browse/SHRINKWRAP-179 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Affects Versions: 1.0.0-alpha-9 Reporter: Aslak Knutsen We support this construct for adding, Container.addXX(Package, Name) adds a Named resource inside a Package Container.setXX() methods should support the same. -- 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

13 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-235) Add print methods to Archive

by Dan Allen (JIRA)

Add print methods to Archive ---------------------------- Key: SHRINKWRAP-235 URL: https://jira.jboss.org/browse/SHRINKWRAP-235 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Affects Versions: 1.0.0-alpha-11 Reporter: Dan Allen Priority: Minor Fix For: 1.0.0-alpha-12 An extremely common use case for the "toString" methods on Archive are to print the contents of the Archive to stdout. System.out.println(archive.toString(true)); Having to wrap the call in System.out.println is really annoying (even with editor shortcuts). ShrinkWrap should provide parallel print methods, that print to stdout (or perhaps to an optional stream argument). archive.print() archive.print(true) archive.print(Formatter) * parallel methods that accept a stream if warranted * I'd also settle for printArchive() This feature is consistent with the ever popular Exception#printStackTrace(). -- 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

13 years, 1 month

4
12
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-187) Existing folders will silently be overwritten by files

by Aslak Knutsen (JIRA)

Existing folders will silently be overwritten by files ------------------------------------------------------ Key: SHRINKWRAP-187 URL: https://jira.jboss.org/browse/SHRINKWRAP-187 Project: ShrinkWrap Issue Type: Bug Components: impl-base Affects Versions: 1.0.0-alpha-10 Reporter: Aslak Knutsen Example archive.addResource("my-local-resource.xml", "/META-INF/my.xml") // becomes /META-INF/my.xml archive.addResource("my-local-resource2.xml", "/META-INF") // becomes the file META-INF, the existing Folder META-INF and sub files are deleted The second line could be a simple typo on the users side, but with no warning or error you have to debug the archive to even figure out what happened. -- 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

13 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-160) Add more convenience method to Filters

by Aslak Knutsen (JIRA)

Add more convenience method to Filters -------------------------------------- Key: SHRINKWRAP-160 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-160 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Reporter: Aslak Knutsen Some more useful Filters should be added: Filters.exclude(Package...) Filters.include(Package...) Filters.exclude(Class<?>...) Filters.include(Class<?>...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (SHRINKDESC-20) BeansDescriptor should not fail if stream is empty

by Dan Allen (JIRA)

BeansDescriptor should not fail if stream is empty -------------------------------------------------- Key: SHRINKDESC-20 URL: https://jira.jboss.org/browse/SHRINKDESC-20 Project: ShrinkWrap Descriptors Issue Type: Feature Request Components: api Affects Versions: 1.0.0-alpha-1 Reporter: Dan Allen beans.xml is permitted to be empty, in which case it simply serves to mark an archive as a bean archive. The BeansDescriptor should not choke if it tries to load an empty file. -- 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

13 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-236) Introduce Asset criteria to find contents in archive

by Dan Allen (JIRA)

Introduce Asset criteria to find contents in archive ----------------------------------------------------- Key: SHRINKWRAP-236 URL: https://jira.jboss.org/browse/SHRINKWRAP-236 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Affects Versions: 1.0.0-alpha-11 Reporter: Dan Allen The read capabilities on Archive are largely inadequate. You can get the content by an archive path or you can flip through all the content and filter the results by path name. However, there are much more logical structures inside the archive that ShrinkWrap does not expose an API to locate. For instance, I want to pull out one or more WebModules from an EnterpriseArchive. However, if we were to introduce a closed set of read methods, the user would eventual outgrow them and find themselves in the same position. My recommendation is to follow the lead of Weld Extensions and use an Archive criteria API. I believe it's a good choice because it feels familiar to Java EE developers with it's JPA-like syntax and it's completely extensible. For example: ArchiveContentQuery<EnterpriseArchive> query = ArchiveContentQueries.<EnterpriseArchive>createQuery(EnterpriseArchive.class) .addCriteria(new TypedAssetCriteria(WebArchive.class)); List<WebArchive> wars = query.getResuiltList(); This is so much simpler than using a filter on a tree walker. It's also crucial for manipulation of the Archive within Arquillian. see http://docs.jboss.org/weld/extensions/reference/latest/en-US/html/propert... -- 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

13 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-224) Create a ShrinkWrap Descriptors extension module

by Aslak Knutsen (JIRA)

Create a ShrinkWrap Descriptors extension module ------------------------------------------------ Key: SHRINKWRAP-224 URL: https://jira.jboss.org/browse/SHRINKWRAP-224 Project: ShrinkWrap Issue Type: Feature Request Components: descriptors Reporter: Aslak Knutsen Assignee: Aslak Knutsen ShrinkWrap Descriptors needs a ShrinkWrap extension module for integration into ShrinkWrap Archive Type apis. DescriptorAsset(Descriptor) { openStrema() { DescriptorExporter.export(descriptor) } } -- 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

13 years, 1 month

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues October 2010