shrinkwrap-issues May 2012

shrinkwrap-issues@lists.jboss.org

1 participants
54 discussions

[JBoss JIRA] (SHRINKWRAP-299) addAsResources() does not remove /classes segment when adding output directory to deployment

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-299?page=com.atlassian.jira.pl... ] Andrew Rubinger updated SHRINKWRAP-299: --------------------------------------- Labels: starter (was: ) > addAsResources() does not remove /classes segment when adding output directory to deployment > -------------------------------------------------------------------------------------------- > > Key: SHRINKWRAP-299 > URL: https://issues.jboss.org/browse/SHRINKWRAP-299 > Project: ShrinkWrap > Issue Type: Bug > Affects Versions: 1.0.0-beta-3 > Reporter: Lincoln Baxter III > Labels: starter > > {code} > @Deployment(testable = false) > public static WebArchive getDeployment() > { > return ShrinkWrap > .create(WebArchive.class, "rewrite-test.war") > .addAsResource(new File("../api/target/classes/com")) > .addAsResource(new File("../api/target/classes/META-INF")) > .addAsResource(new File("../impl-servlet/target/classes/com")) > .addAsResource(new File("../impl-servlet/target/classes/META-INF")) > .addAsLibraries(DependencyResolvers.use(MavenDependencyResolver.class) > .artifacts("org.jboss.weld.servlet:weld-servlet:1.1.1.Final") > .resolveAs(GenericArchive.class)) > .setWebXML("jetty-web.xml") > .addAsWebResource( > new StringAsset("<beans/>"), > ArchivePaths.create("WEB-INF/beans.xml")) > .addAsWebResource("jetty-env.xml", > ArchivePaths.create("WEB-INF/jetty-env.xml")); > } > {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

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-356) Alter maven config and/or directory names to help with mvn eclipse:eclipse

by Eric Lefevre-Ardant (Created) (JIRA)

Alter maven config and/or directory names to help with mvn eclipse:eclipse -------------------------------------------------------------------------- Key: SHRINKWRAP-356 URL: https://issues.jboss.org/browse/SHRINKWRAP-356 Project: ShrinkWrap Issue Type: Task Environment: maven eclipse with eclipse:eclipse plugin Reporter: Eric Lefevre-Ardant Priority: Minor I prefer not to use the m2e plugin to work under Eclipse. My preference goes to running "mvn eclipse:eclipse". A problem is that eclipse:eclipse is a bit limited and assumes that the name of the directories are the names of the modules. That is not the case for the "api" and "spi" modules, so some manual fixing is required under Eclipse. It would be nice to get rid of this manual fix. -- 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
2
0 / 0

[JBoss JIRA] (SHRINKRES-27) Allow for full dependency info from MavenDependencyResolver::resolve

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-27: ------------------------------------------ I don't think "import type" is a valid inbound property after resolution. That's something used to define the transitivity of a dependency. Does an API wrapper around these properties (excluding the mutable operations and the "properties" Map) fulfill the issue, Ales? https://gist.github.com/2580793 > Allow for full dependency info from MavenDependencyResolver::resolve > -------------------------------------------------------------------- > > Key: SHRINKRES-27 > URL: https://issues.jboss.org/browse/SHRINKRES-27 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven, impl-maven > Affects Versions: 2.0.0-alpha-1 > Reporter: Ales Justin > Assignee: Andrew Rubinger > > It would be useful to be able to grab full dependency info, not just files. > e.g. name, version, import type, etc -- 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

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-27) Allow for full dependency info from MavenDependencyResolver::resolve

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-27: ------------------------------------------ Sounds like a translation wrapper around Aether's "Artifact". > Allow for full dependency info from MavenDependencyResolver::resolve > -------------------------------------------------------------------- > > Key: SHRINKRES-27 > URL: https://issues.jboss.org/browse/SHRINKRES-27 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven, impl-maven > Affects Versions: 2.0.0-alpha-1 > Reporter: Ales Justin > Assignee: Andrew Rubinger > > It would be useful to be able to grab full dependency info, not just files. > e.g. name, version, import type, etc -- 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

1
0
0 / 0

← Newer
1
2
3
4
5
6
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2012