Env-Entry should be mappable in WebAppDescriptor
------------------------------------------------
Key: SHRINKDESC-26
URL: https://jira.jboss.org/browse/SHRINKDESC-26
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Reporter: Aslak Knutsen
<env-entry>
<env-entry-name>name</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>value</env-entry-value>
</env-entry>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide addAsServiceProvider overload that supports "serviceInterface" as String
--------------------------------------------------------------------------------
Key: SHRINKWRAP-336
URL: https://issues.jboss.org/browse/SHRINKWRAP-336
Project: ShrinkWrap
Issue Type: Feature Request
Components: api
Affects Versions: 1.0.0-beta-6
Reporter: Aslak Knutsen
In some cases you want to package ServiceProviderInterfaces to might not be available/loadable at package time.
This only work if CDI API is on client path
{code}
.addAsServiceProvider(Extension.class, CDIExtension.class);
{code}
A possible overload could be:
{code}
.addAsServiceProvider("javax.enterprise.inject.spi.Extension", "my.cdi.CDIExtension");
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create tool for XSD->Java generator
-----------------------------------
Key: SHRINKDESC-92
URL: https://issues.jboss.org/browse/SHRINKDESC-92
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Components: gen
Reporter: Jesper Pedersen
Create a Java tool that can generate Java classes based on an XSD.
This way projects outside of ShrinkWrap/Descriptors can support their own JEE extensions.
The tool should be published as a Maven artifact.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Deleting a directory specified by a File with a trailing slash does not work
----------------------------------------------------------------------------
Key: SHRINKWRAP-348
URL: https://issues.jboss.org/browse/SHRINKWRAP-348
Project: ShrinkWrap
Issue Type: Bug
Reporter: Geoffrey De Smet
Priority: Minor
We have a directory gwtutil with 10+ classes in there, which we want to delete from the archive
This does nothing, it does not even fail-fast:
{code}
webArchive.delete(ArchivePaths.create("WEB-INF/classes/org/drools/guvnor/gwtutil/"));
{code}
This does work:
{code}
webArchive.delete(ArchivePaths.create("WEB-INF/classes/org/drools/guvnor/gwtutil"));
{code}
The difference is the absence of the trailing /.
Using arquillian bom CR5
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/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
MavenResolver does not take settings.xml specified on command line into account when resolving repositories
-----------------------------------------------------------------------------------------------------------
Key: SHRINKWRAP-292
URL: https://issues.jboss.org/browse/SHRINKWRAP-292
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Affects Versions: 1.0.0-beta-3
Reporter: Aslak Knutsen
Running Maven using the following startup args does not work with the MavenResovler, the new defined settings.xml is not read
mvn install -s settings.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/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
ShrinkWrap MavenResolver unable to resolve version from parent POM.
-------------------------------------------------------------------
Key: SHRINKWRAP-312
URL: https://issues.jboss.org/browse/SHRINKWRAP-312
Project: ShrinkWrap
Issue Type: Bug
Affects Versions: 1.0.0-beta-5
Environment: Windows 7, Java 6
Reporter: Michal Huniewicz
All versions of artifacts are stored in the parent POM as Maven properties. There is a dependencyManagement section where they are used.
When a child project uses Maven dependency resolver to load artifacts, the version cannot be established with MavenDependencyResolver.
Sample parent POM:
https://github.com/m1key/audiolicious/blob/master/pom.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
LogTransferListerer should be renamed
-------------------------------------
Key: SHRINKWRAP-342
URL: https://issues.jboss.org/browse/SHRINKWRAP-342
Project: ShrinkWrap
Issue Type: Enhancement
Components: ext-resolver
Affects Versions: 1.0.0-beta-5
Reporter: Karel Piwko
Assignee: Karel Piwko
Priority: Minor
Fix For: resolver-1.1.0-alpha-1
There's a type in LogTransferListerer name. Class should be renamed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira