December 2011 - shrinkwrap-issues

[JBoss JIRA] (SHRINKWRAP-372) create a way to LibraryContainer#assAsLibrary by a given marker file

by Mark Struberg (Created) (JIRA)

create a way to LibraryContainer#assAsLibrary by a given marker file -------------------------------------------------------------------- Key: SHRINKWRAP-372 URL: https://issues.jboss.org/browse/SHRINKWRAP-372 Project: ShrinkWrap Issue Type: Enhancement Reporter: Mark Struberg When working with CDI Extensions we need to 'package' a whole JAR (or it's whole content) into a JavaArchive which can be used for addAsLibrary based on the marker file "/META-INF/beans.xml". This is needed as we cannot simply addAsPackage because the extension jar files would each overwrite other beans.xml files. Something like LibraryContainer#addContainingLibraries(String markerResource); LibraryContainer#addContainingLibraries(String markerResource, String packageNameInclude, String packageNameExclude); Example: ShrinkWrap.create(WebArchive.class, "test.jar").addContainingLibraries("/META-INF/beans.xml"); would package all JARs which have a resource "/META-INF/beans.xml", pack them into JavaArchives and add those to the WebArchive. With packageNameInclude and packageNameExclude we could add rules about which jars to add and exclude. But I'm sure there is already an established pattern for such a thing in ShrinkWrap. -- 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

12 years, 2 months

5
7
0 / 0

[JBoss JIRA] (SHRINKWRAP-369) ShrinkWrapClassLoader does not find service provider in WAR

by Martin Kouba (Created) (JIRA)

ShrinkWrapClassLoader does not find service provider in WAR ----------------------------------------------------------- Key: SHRINKWRAP-369 URL: https://issues.jboss.org/browse/SHRINKWRAP-369 Project: ShrinkWrap Issue Type: Bug Components: api Affects Versions: 1.0.0-beta-3 Reporter: Martin Kouba I ran into this issue when working with *Arquillian* and *Weld EE 1.1 Embedded container* (that uses ShrinkWrapClassLoader under the hood). ShrinkWrap correctly builds web archive with CDI extension (this was also discussed in SHRINKWRAP-266). Output: {code} test.war /WEB-INF/ /WEB-INF/classes/ /WEB-INF/classes/META-INF/ /WEB-INF/classes/META-INF/services/ /WEB-INF/classes/META-INF/services/javax.enterprise.inject.spi.Extension {code} However no extensions are found. *org.jboss.shrinkwrap.api.classloader.ShrinkWrapClassLoader* probably does not find any resource when looking for "META-INF/services/javax.enterprise.inject.spi.Extension". Note that I'm not quite sure whether it's ShrinkWrapClassLoader or WeldEEMockContainer issue. -- 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

12 years, 3 months

7
13
0 / 0

[JBoss JIRA] (SHRINKDESC-101) Update Release Configuration

by Andrew Rubinger (Created) (JIRA)

Update Release Configuration ---------------------------- Key: SHRINKDESC-101 URL: https://issues.jboss.org/browse/SHRINKDESC-101 Project: ShrinkWrap Descriptors Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Update the release process to account for a parent-less BOM, etc. Similar task already done in SHRINKWRAP-373. -- 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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (SHRINKWRAP-376) Create SWD "depchain" module

by Andrew Rubinger (Created) (JIRA)

Create SWD "depchain" module ---------------------------- Key: SHRINKWRAP-376 URL: https://issues.jboss.org/browse/SHRINKWRAP-376 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: resolver-1.1.0-alpha-2, resolver-2.0.0-alpha-1 Also called a "A-BOM" in EAP, or "depchain" in AS, this POM aggregates dependencies for a project, in the right scope, in one view: For instance: {code}foo-api foo-impl foo dep: foo-api (compile) foo-impl (runtime){code} In this case, "foo" would be the module we're looking to create. A user then makes a dependency upon this POM in coordination with a dep on the BOM in "import" scope in depMgt (in order to honor exclusions). An example of this in use is: https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L128 https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L156 In the example above we have the dep on the AS7 API in two places as required; in turn the AS7 API POM exports out transitives as we need. In that case the AS7 API is both BOM and Library POM. -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (SHRINKWRAP-375) Plugin (Environment) Integration depends upon a settings.xml file to exist

by Andrew Rubinger (Created) (JIRA)

Plugin (Environment) Integration depends upon a settings.xml file to exist -------------------------------------------------------------------------- Key: SHRINKWRAP-375 URL: https://issues.jboss.org/browse/SHRINKWRAP-375 Project: ShrinkWrap Issue Type: Bug Reporter: Andrew Rubinger Assignee: Karel Piwko If no ~/.m2/settings.xml is present on the user's environment, the following error is encountered: {code}java.lang.IllegalArgumentException: Settings.xml file /home/alr/.m2/settings.xml does not represent a readable file at org.jboss.shrinkwrap.resolver.api.maven.Validate.isReadable(Validate.java:98) at org.jboss.shrinkwrap.resolver.api.maven.MavenConfigurationTypes$2.configure(MavenConfigurationTypes.java:77) at org.jboss.shrinkwrap.resolver.api.maven.MavenConfigurationTypes$2.configure(MavenConfigurationTypes.java:32) at org.jboss.shrinkwrap.resolver.impl.maven.MavenDependencyResolverImpl.configureFrom(MavenDependencyResolverImpl.java:31) at org.jboss.shrinkwrap.resolver.impl.maven.PluginIntegrationTestCase.loadCurrentProject(PluginIntegrationTestCase.java:26){code} -- 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

12 years, 4 months

4
3
0 / 0

[JBoss JIRA] (SHRINKWRAP-373) Update SWR Release Process

by Andrew Rubinger (Created) (JIRA)

Update SWR Release Process --------------------------- Key: SHRINKWRAP-373 URL: https://issues.jboss.org/browse/SHRINKWRAP-373 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 1.0.0-cr-2 * Use jboss-parent:8 * Release Plugin Config Changes: * <pushChanges>false</pushChanges> * <localCheckout>true</localCheckout> -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (SHRINKWRAP-374) Create SWR "depchain" module

by Andrew Rubinger (Created) (JIRA)

Create SWR "depchain" module ---------------------------- Key: SHRINKWRAP-374 URL: https://issues.jboss.org/browse/SHRINKWRAP-374 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Reporter: Andrew Rubinger Assignee: Andrew Rubinger Also called a "A-BOM" in EAP, or "depchain" in AS, this POM aggregates dependencies for a project, in the right scope, in one view: For instance: {code}foo-api foo-impl foo dep: foo-api (compile) foo-impl (runtime){code} In this case, "foo" would be the module we're looking to create. A user then makes a dependency upon this POM in coordination with a dep on the BOM in "import" scope in depMgt (in order to honor exclusions). An example of this in use is: https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L128 https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L156 In the example above we have the dep on the AS7 API in two places as required; in turn the AS7 API POM exports out transitives as we need. In that case the AS7 API is both BOM and Library POM. -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (SHRINKWRAP-371) Put Distribution Configuration in the BOM POM

by Andrew Rubinger (Created) (JIRA)

Put Distribution Configuration in the BOM POM --------------------------------------------- Key: SHRINKWRAP-371 URL: https://issues.jboss.org/browse/SHRINKWRAP-371 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger With no jboss-parent, now the BOM POM needs distribution configuration for release/deploy. -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (SHRINKWRAP-370) Update ShrinkWrap Release Process

by Andrew Rubinger (Created) (JIRA)

Update ShrinkWrap Release Process ---------------------------------- Key: SHRINKWRAP-370 URL: https://issues.jboss.org/browse/SHRINKWRAP-370 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 1.0.0-cr-2 * Use jboss-parent:8 * Release Plugin Config Changes: * <pushChanges>false</pushChanges> * <localCheckout>true</localCheckout> -- 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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (SHRINKWRAP-368) MavenImporter on war files should support a configuration that supports "skipping the build" in the IDE (and preferably use it by default)

by Geoffrey De Smet (Created) (JIRA)

MavenImporter on war files should support a configuration that supports "skipping the build" in the IDE (and preferably use it by default) ------------------------------------------------------------------------------------------------------------------------------------------ Key: SHRINKWRAP-368 URL: https://issues.jboss.org/browse/SHRINKWRAP-368 Project: ShrinkWrap Issue Type: Enhancement Affects Versions: 1.0.0-cr-1 Reporter: Geoffrey De Smet Assignee: Karel Piwko Currently the MavenImporter on war files requires "mvn package" to be run every time (not only the first time), to update the exploded directory at "target/{finalName}". This means if you change something in your code and want to (re)run a test, and forget to run "mvn package" first, you're running the old code (and the results are not representative of the changed code). Karel and Geoffrey discussed this at JUDCon London. The following things can be probably presumed: - The IDE compiles all classes from src/main/java to target/classes. - The IDE copies all non-filtered resources from src/main/resources to target/classes. - That target/classes is copied into the war at WEB-INF/classes. - Most src/main/webapp dirs are copied unaltered into the root of the war. (*) - "mvn compile" is run once after any "mvn clean": in other words, all src/main/filtered-resources are in target/classes So MavenImporter doesn't have to require "mvn package" to build the exploded dir first (which it then zips, enriches and sends to arquillian). Instead, it can construct the war zip directly from target/classes and src/main/webapp. That is at least one less copy and more importantly, to run the test from the IDE without having to build first. Note: all examples above used the explicit directory locations, but in reality the pom.xml's <build> section should be used to determinate the directory locations for a certain project. -- 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

12 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues December 2011