August 2011 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] Created: (SHRINKWRAP-319) Add jboss-deprecated Repository to Default Config

by Andrew Rubinger (JIRA)

Add jboss-deprecated Repository to Default Config ------------------------------------------------- Key: SHRINKWRAP-319 URL: https://issues.jboss.org/browse/SHRINKWRAP-319 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Required to get at trove:trove, a dependency of the VDF extension: [ERROR] Failed to execute goal on project shrinkwrap-extension-vdf: Could not resolve dependencies for project org.jboss.shrinkwrap:shrinkwrap-extension-vdf:jar:1.0.0-beta-6-SNAPSHOT: Failed to collect dependencies for [org.jboss.shrinkwrap:shrinkwrap-api:jar:1.0.0-beta-6-SNAPSHOT (compile), org.jboss.shrinkwrap:shrinkwrap-impl-base:jar:1.0.0-beta-6-SNAPSHOT (test), org.jboss.shrinkwrap:shrinkwrap-extension-vfs3:jar:1.0.0-beta-6-SNAPSHOT (provided), junit:junit:jar:4.8.2 (test), org.jboss:jboss-vfs:jar:3.0.0.CR5 (provided), org.jboss.deployers:jboss-deployers-vfs:jar:2.2.0.Alpha4 (provided), org.jboss.logging:jboss-logging-spi:jar:2.2.0.CR1 (compile), org.jboss.logging:jboss-logging-jdk:jar:2.2.0.CR1 (test), org.jboss.logmanager:jboss-logmanager:jar:1.2.0.CR1 (test), org.jboss.logging:jboss-logging-logmanager:jar:2.2.0.CR1 (test), org.jboss.threads:jboss-threads:jar:2.0.0.CR4 (test), org.jboss.threads:jboss-threads-metadata:jar:2.0.0.CR4 (test), org.jboss.reloaded:jboss-reloaded-vdf-bootstrap-minimal:jar:0.1.4 (test)]: Failed to read artifact descriptor for trove:trove:jar:2.1.1: Could not transfer artifact trove:trove:pom:2.1.1 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom -> [Help 1] For users behind the VPN, this build *will* succeed, as it'll use the old Nexus location (redirects still work behind the JBoss VPN). Else this will fail. So put in place in the POM access to the new deprecated repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-318) Support adding web and WEB-INF resources with relative path of source

by Ian Brandt (JIRA)

Support adding web and WEB-INF resources with relative path of source --------------------------------------------------------------------- Key: SHRINKWRAP-318 URL: https://issues.jboss.org/browse/SHRINKWRAP-318 Project: ShrinkWrap Issue Type: Enhancement Components: api Affects Versions: 1.0.0-beta-5 Reporter: Ian Brandt I've noticed with WebArchives that {{addAsResource(String)}} preserves the relative path of the source. E.g. {{addAsResource("some/file")}} is added to the archive as "WEB-INF/classes/some/file". On the other hand {{addAsWebResource(String)}} and {{addAsWebInfResource(String)}} do not preserve the relative source path. I have the webapp resources for my app under test copied to the test classpath relative from the web root. Any time I have a WEB-INF resource under one or more subfolders I find that I have to do {{addAsWebInfResource("WEB-INF/jsp/path/to/some.jsp", "jsp/path/to/some.jsp")}} or {{addAsWebInfResource("WEB-INF/jsp/path/to/some.jsp", "WEB-INF/jsp/path/to/some.jsp")}}. It would be preferable to just be able to say {{addAsWebResource("WEB-INF/jsp/path/to/some.jsp")}}, but when I do that the JSP is added to the archive as "some.jsp" at the web root. I believe the API would be more intuitive if the {{addAs{_}X{_}(String{_}\[, ...\]{_})}} methods were consistent with regards to preserving the relative path of the source resource. It would also be useful to have the option of preserving the source resource's path, or not. Perhaps {{addAsResource(String)}} and {{addAsRelativeResource(String)}}, etc.? Note however that I haven't considered the other {{add}} overloads ({{Asset}}, {{File}}, etc.) as I haven't used them yet. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-317) Update maven-resources-plugin

by Andrew Rubinger (JIRA)

Update maven-resources-plugin ----------------------------- Key: SHRINKWRAP-317 URL: https://issues.jboss.org/browse/SHRINKWRAP-317 Project: ShrinkWrap Issue Type: Task Components: build Reporter: Andrew Rubinger Assignee: Andrew Rubinger By explicitly setting a version at our level, we override and downgrade from the inherited in jboss-parent. Newer versions of m2e show warnings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-316) When adding a resource from classpath shrinkwrap should provide a way to choose the specific source for the resource.

by José Freitas (JIRA)

When adding a resource from classpath shrinkwrap should provide a way to choose the specific source for the resource. --------------------------------------------------------------------------------------------------------------------- Key: SHRINKWRAP-316 URL: https://issues.jboss.org/browse/SHRINKWRAP-316 Project: ShrinkWrap Issue Type: Enhancement Components: impl-base Affects Versions: 1.0.0-beta-5 Reporter: José Freitas Priority: Critical MyClass.class.getResource only use the CL from where that was loaded, and there's a need to get the resource from a specific source. like: give me "resource-x" found where MyClass.class is found. with that, we can for example pick a specific META-INF/faces-config.xml and not anyone placed on the classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-294) Honor proxy and other settings from settings.xml

by Karel Piwko (JIRA)

Honor proxy and other settings from settings.xml ------------------------------------------------ Key: SHRINKWRAP-294 URL: https://issues.jboss.org/browse/SHRINKWRAP-294 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Affects Versions: 1.0.0-beta-3 Reporter: Karel Piwko Assignee: Karel Piwko When settings.xml is loaded, we should honor all the settings present there, not just active remote repositories and the local repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-313) Provide overloaded Archive.delete(String)

by Andrew Rubinger (JIRA)

Provide overloaded Archive.delete(String) ----------------------------------------- Key: SHRINKWRAP-313 URL: https://issues.jboss.org/browse/SHRINKWRAP-313 Project: ShrinkWrap Issue Type: Task Affects Versions: 1.0.0-beta-5 Reporter: Andrew Rubinger API Inconsistency. We must have an Archive.delete(String) method which may delegate to the existing Archive.delete(ArchivePath). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-304) Add option for omitting archive extension from exploded directory name

by Ian Brandt (JIRA)

Add option for omitting archive extension from exploded directory name ---------------------------------------------------------------------- Key: SHRINKWRAP-304 URL: https://issues.jboss.org/browse/SHRINKWRAP-304 Project: ShrinkWrap Issue Type: Enhancement Components: api Affects Versions: 1.0.0-beta-2 Reporter: Ian Brandt It would be nice if ExplodedExporter offered the option of omitting the archive extension from the exploded directory name. h5. Current Method: {code:java} /** * Exports provided archive as an exploded directory structure. * * @param archive * @param parentDirectory Must be a folder * @return File for exploded archive contents * @throws IllegalArgumentException if the archive or parent directory not valid * @throws ArchiveExportException if the export process fails */ File exportExploded(File parentDirectory); {code} h5. Current Example: {code:java} Archive webArchive = ShrinkWrap.create(WebArchive.class, "test.war"); File explodedDirectory = webArchive.as(ExplodedExporter.class).exportExploded(tmpDirectory); System.out.println(explodedDirectory.getName()) // "test.war" {code} h5. Proposed Method Overload: {code:java} /** * Exports provided archive as an exploded directory structure. * * @param archive * @param parentDirectory Must be a folder * @param omitExtension Whether to omit the archive extension from the exploded directory name * @return File for exploded archive contents * @throws IllegalArgumentException if the archive or parent directory not valid * @throws ArchiveExportException if the export process fails */ File exportExploded(File parentDirectory, boolean omitExtension); {code} h5. Proposed Example {code:java} Archive webArchive = ShrinkWrap.create(WebArchive.class, "test.war"); File explodedDirectory = webArchive.as(ExplodedExporter.class).exportExploded(tmpDirectory, true); System.out.println(explodedDirectory.getName()) // "test" {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-303) Add getAsType(Class<Archive<?>> archiveType)

by Andrew Rubinger (JIRA)

Add getAsType(Class<Archive<?>> archiveType) -------------------------------------------- Key: SHRINKWRAP-303 URL: https://issues.jboss.org/browse/SHRINKWRAP-303 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger We shouldn't require users to specify an ArchiveFormat for Archive.getAsType. This, in the large majority of cases, can be inferred from the Archive type passed in (for instance, WebArchive.class generally means ArchiveFormat.ZIP). Add to the META-INF/services files for each archive type the default archive format, and use this in a getAsType(Class<Archive<?>> archiveType, ArchivePath path) method to delegate to the already in-place getAsType(Class<Archive<?>> archiveType, ArchivePath path, ArchiveFormat format) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-309) Ensure test runs can be repeated from an IDE

by Karel Piwko (JIRA)

Ensure test runs can be repeated from an IDE -------------------------------------------- Key: SHRINKWRAP-309 URL: https://issues.jboss.org/browse/SHRINKWRAP-309 Project: ShrinkWrap Issue Type: Bug Reporter: Karel Piwko Priority: Minor The test execution leaves file system in such state that repetitive test runs caused every but the first one to fail. Ensure that tests can be executed multiple times in a row. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-288) MavenDependencyResolver.load*From* and configureFrom should accept a URL and support the classpath protocol

by Pete Muir (JIRA)

MavenDependencyResolver.load*From* and configureFrom should accept a URL and support the classpath protocol ----------------------------------------------------------------------------------------------------------- Key: SHRINKWRAP-288 URL: https://issues.jboss.org/browse/SHRINKWRAP-288 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Reporter: Pete Muir This allows user to provide these files from anywhere easily enough and can cope with esoteric builds more easily than a File based system -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues August 2011