May 2012 - shrinkwrap-issues - Jboss List Archives

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

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Ales Justin commented on SHRINKRES-27: -------------------------------------- >> Also, "provided" doesn't mean "optional". I know what it means in Mvn terms. ;-) I'm just saying in my case it means optional. > 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: ------------------------------------------ I'll have a look to see what's provided by Aether's "Artifact#getProperties" in terms of getting this *after* resolution. Far as I know, this information is part of the dependency declaration to determine transitivity levels, and might not be available as a resolution result. Also, "provided" doesn't mean "optional". "optional" means that some of the runtime will work without this dependency, but the user may declare the dependency if he/she wants all features. "provided" means that the dependency is not transitive (and is expected to be *provided* by some other framework or runtime, ie. "JBossAS provides Hibernate so JPA applications wouldn't export the dependency explicitly"). > 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 Ales Justin (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Ales Justin commented on SHRINKRES-27: -------------------------------------- Ah, ok. Afais, scope is also not really import type. Anyway, I still see I could use/need this info. e.g. "provided" for me also means it's optional. > 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] (SHRINKWRAP-404) Expose underlying Asset source in the individual API's

by Aslak Knutsen (JIRA)

Aslak Knutsen created SHRINKWRAP-404: ---------------------------------------- Summary: Expose underlying Asset source in the individual API's Key: SHRINKWRAP-404 URL: https://issues.jboss.org/browse/SHRINKWRAP-404 Project: ShrinkWrap Issue Type: Feature Request Reporter: Aslak Knutsen In some cases it is interesting to get the 'real source' of an Asset beyond the InputStream. Where on disk is the FileAsset read from? Both for Tooling integration and e.g. the JRebel Arquillian extension it is needed to know where a source came from to do the linking. File FileAsset.getFile String ClassLoaderAsset.getResource Class<?> ClassAsset.getClass 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

2
7
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: ------------------------------------------ Import type is different from <optional>true</optional>... http://maven.apache.org/guides/introduction/introduction-to-dependency-me... > 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 Ales Justin (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Ales Justin commented on SHRINKRES-27: -------------------------------------- Import type for me is important to know if the import is optional or not. > 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: ------------------------------------------ That's an interesting interpretation as well. So far I've stubbed out an API for this in my tree: {code}public void dependencyInfo() { final ArtifactInfo longhand = DependencyResolvers.use(MavenResolverSystem.class).resolve("G:A:V") .withoutTransitivity().asSingle(ArtifactInfo.class); final ArtifactInfo shortcut = Maven.RESOLVER.resolve("G:A:V").withoutTransitivity() .asSingle(ArtifactInfo.class); final MavenCoordinate coordinate = shortcut.getCoordinate(); final String groupId = coordinate.getGroupId(); final String artifactId = coordinate.getArtifactId(); final String version = coordinate.getVersion(); final String resolvedVersion = shortcut.getResolvedVersion(); final String type = shortcut.getType(); final boolean isSnapshot = shortcut.isSnapshotVersion(); final String classifier = shortcut.getClassifier(); final File file = shortcut.getArtifact(FileFormatProcessor.INSTANCE); final File file2 = shortcut.getArtifact(File.class); final InputStream in = shortcut.getArtifact(InputStreamFormatProcessor.INSTANCE); final InputStream in2 = shortcut.getArtifact(InputStream.class); final JavaArchive archive = shortcut.getArtifact(new ArchiveFormatProcessor<JavaArchive>(JavaArchive.class)); }{code} I think both are valid use cases. So I'll make another issue for the case that Karel notes above, and modify this issue to more clearly reflect the case I'd posted here. > 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Karel Piwko commented on SHRINKRES-27: -------------------------------------- I read this as an ability to make dependency:tree or dependency:list programatically. This would be great because it would be using Aether so result will match Maven 3 resolution. What about: {code} Maven.RESOLVER.resolve("G:A:V").withTransitivity().asSingle(DependencyGraph.class); {code} {code} Maven.RESOLVER.resolve("G:A:V").withTransitivity().asSingle(DependencyList.class); {code} Seems to hijack the API to fit a bit different purpose though. > 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] Created: (SHRINKWRAP-249) Support add directory content

by Aslak Knutsen (JIRA)

Support add directory content ----------------------------- Key: SHRINKWRAP-249 URL: https://issues.jboss.org/browse/SHRINKWRAP-249 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Affects Versions: 1.0.0-alpha-11 Reporter: Aslak Knutsen A common use case is to add multiple Assets from your directory structure: addManifestResource("src/main/resources/META-INF/name", "name") addManifestResource("src/main/resources/META-INF/name2", "name2") This can be quite painful if you have a lot of items, e.g. html/jsp/jsf We should support adding of recursive directory content, where target path is resolved as relative to where you add from: addManifestResource("src/main/resources/META-INF/") The expected target in the archive would be, root + CONTAINER_PATH + ('file.getName()' + parentDirectory if in a subdirectory of specified import source ) src/main/resources/META-INF/test.html -> (CONTAINER_PATH) + test.html src/main/resources/META-INF/images/test.jpg -> (CONTAINER_PATH) + images/test.jpg -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
12
0 / 0

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2012