March 2010 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] Created: (SHRINKWRAP-58) Add overview.html, package.html for JavaDoc

by Andrew Lee Rubinger (JIRA)

Add overview.html, package.html for JavaDoc ------------------------------------------- Key: SHRINKWRAP-58 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-58 Project: ShrinkWrap Issue Type: Feature Request Components: api, assembly, build, impl-base, spi Reporter: Andrew Lee Rubinger Identified as a gap by Jesper -- 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

3
5
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-85) Support Event/Listener style callbacks

by Aslak (JIRA)

Support Event/Listener style callbacks -------------------------------------- Key: SHRINKWRAP-85 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-85 Project: ShrinkWrap Issue Type: Feature Request Reporter: Aslak A interesting featre would be to beablt to add listeners for events on ContainerTypes or paths. /META-INF/* or all events generated via ClassContainer usecase 1, if/when we add something like a ManifestDescriptor, instead of having it like the WebArchiveDescriptor.addServlet, adding a addMenifestLibrary that delegates down to addLibrary and update the 'classpath: ' manifest entry.. we could register a listener on the LibraryContainer and get callbacks when a 'normal' addLibrary happens usecase 2, could deploy a 'live' archive to embedded.. one could register a listener on all changes in the archive and auto redeploy it on events.. deploy it once, redeploy on change -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-140) Support loading artifacts from a Maven repository

by Pete Muir (JIRA)

Support loading artifacts from a Maven repository ------------------------------------------------- Key: SHRINKWRAP-140 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-140 Project: ShrinkWrap Issue Type: Feature Request Reporter: Pete Muir The ability to define the coordinates of an artifact have it added to your artifact would be huge. -- 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, 6 months

8
13
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-48) Create a ManifestAsset

by Aslak (JIRA)

Create a ManifestAsset ---------------------- Key: SHRINKWRAP-48 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-48 Project: ShrinkWrap Issue Type: Feature Request Reporter: Aslak Assignee: Andrew Lee Rubinger Priority: Optional It would be nice to be able to manipulate the MANIFEST.MF file 'via' the ManifestContainer. A simple Wrapper Asset impl over java.util.jar.Manifest should work i guess.. -- 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, 8 months

5
13
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-88) Look at Import/Export API methods for consistency/convenience

by Aslak (JIRA)

Look at Import/Export API methods for consistency/convenience ------------------------------------------------------------- Key: SHRINKWRAP-88 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-88 Project: ShrinkWrap Issue Type: Task Components: api, impl-base Reporter: Aslak make import/export api naming/arguments equalequal import(url|file|resource) export(url|file) -- 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

4
7
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

13 years

2
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-135) Archive.addDirectories is not atomic

by Andrew Lee Rubinger (JIRA)

Archive.addDirectories is not atomic ------------------------------------ Key: SHRINKWRAP-135 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-135 Project: ShrinkWrap Issue Type: Bug Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Must either fail or succeed for all directories, not be left in inconsistent state. This problem is described by German in the linked Forum post. -- 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, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-117) Inconsistencies in the API of what FIle means

by Aslak Knutsen (JIRA)

Inconsistencies in the API of what FIle means --------------------------------------------- Key: SHRINKWRAP-117 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-117 Project: ShrinkWrap Issue Type: Bug Components: api Reporter: Aslak Knutsen ExplodedImporter.importDirectory(FIle) -> must be a directory addXX(File) -> must be a file As a bare minimum we at least have to document properly which supports what.. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-139) Ability to generate OSGi bundle headers

by Pete Muir (JIRA)

Ability to generate OSGi bundle headers --------------------------------------- Key: SHRINKWRAP-139 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-139 Project: ShrinkWrap Issue Type: Feature Request Reporter: Pete Muir As we control the classpath generating an OSGi bundle header should be straightforward. Introducing an API to customize it is perhaps harder, but should be possible. May want to look at delegating to BND (http://www.aqute.biz/Code/Bnd). -- 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, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-47) Design a way to handle multiple 'linked' Descriptor files

by Aslak (JIRA)

Design a way to handle multiple 'linked' Descriptor files --------------------------------------------------------- Key: SHRINKWRAP-47 URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-47 Project: ShrinkWrap Issue Type: Feature Request Reporter: Aslak Assignee: Andrew Lee Rubinger When working with Archive Descriptors, doing a single web.xml is easy. But when we move over to the container specific descriptors where some of the info in the 'auto' generated web.xml will be needed to map something together in the jboss-web.xml. ie: web.xml -> resource-ref -> res-ref-name jboss-web.xml -> resource-ref -> res-ref-name + jndi-name The point being some of the info in web.xml is needed to create the jboss-web.xml. Is there a way to link/automate this descriptor creation, so that the user avoid having to 'manually' add them both places. ie: desc = new WebArchiveDescriptor(JbossWebDescriptor, GlassfishWebDescriptor); desc.addResourceRef(DataSource, Name, JndiName) { this.addResourceRef(DataSource, Name); JbossWebDescriptor.add(Name, JndiName); GlassfishWebDescriptor.add(Name, JndiName); } I do realize that JNDI names could be a bad example, since in the old versions they were all container specific and in the new version they are standardized and not needed, but I'm sure there are other usecases... -- 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, 7 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues March 2010