shrinkwrap-issues November 2012

shrinkwrap-issues@lists.jboss.org

1 participants
45 discussions

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Michal Matloka reassigned SHRINKRES-27: --------------------------------------- Assignee: Michal Matloka (was: Andrew Rubinger) > 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-2 > Reporter: Ales Justin > Assignee: Michal Matloka > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-48) Implement resolve as(ResolvedArtifactInfo.class)

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-48: ---------------------------------------- Summary: Implement resolve as(ResolvedArtifactInfo.class) Key: SHRINKRES-48 URL: https://issues.jboss.org/browse/SHRINKRES-48 Project: ShrinkWrap Resolvers Issue Type: Feature Request Reporter: Andrew Rubinger Assignee: Andrew Rubinger Remove the current UnsupportedOperationExceptions in MavenFormatStageImpl -- 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

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] (SHRINKWRAP-422) Enhance the api to allow .offline() when using the .import*Dependencies() methods

by Marco Rietveld (JIRA)

Marco Rietveld created SHRINKWRAP-422: ----------------------------------------- Summary: Enhance the api to allow .offline() when using the .import*Dependencies() methods Key: SHRINKWRAP-422 URL: https://issues.jboss.org/browse/SHRINKWRAP-422 Project: ShrinkWrap Issue Type: Feature Request Components: api, impl-base Reporter: Marco Rietveld Priority: Minor It would be great if I could do something like this: {code:java} Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().offline().as(File.class); {code} But the (fluent) api doesn't permit the {{.offline()}} method for the class/interface that's returned from the {{.importRuntimeDependencies()}} methods. As a workaround, I'm doing this: {code:java} MavenResolverSystem mrs = Maven.resolver(); PomEquippedResolveStage pers = mrs.loadPomFromFile("pom.xml"); ScopeType[] runtimeScopes = new ScopeType[] { ScopeType.COMPILE, ScopeType.IMPORT, ScopeType.RUNTIME, ScopeType.SYSTEM }; ResolutionStrategy runtimeStrategy = new AcceptScopesStrategy(runtimeScopes); FormatStage fs = ((PomlessResolveStageBaseImpl) pers).resolve().offline().using(runtimeStrategy); File[] dependencyFiles = fs.as(File.class); {code} Not as pretty/easy and also, I basically cut and pasted code from the {{.importRuntimeDependencies()}} method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
10
0 / 0

[JBoss JIRA] (SHRINKRES-80) Code improvement for generic array handling

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-80: ------------------------------------ Summary: Code improvement for generic array handling Key: SHRINKRES-80 URL: https://issues.jboss.org/browse/SHRINKRES-80 Project: ShrinkWrap Resolvers Issue Type: Feature Request Components: impl-maven Affects Versions: 2.0.0-alpha-4 Reporter: Karel Piwko Assignee: Michal Matloka Priority: Optional Fix For: 2.0.0-alpha-5 As Michal figured out, handling RETURNTYPE[] can be done an easier way -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (SHRINKRES-63) Refactor "offline" feature placement in the API

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-63: ---------------------------------------- Summary: Refactor "offline" feature placement in the API Key: SHRINKRES-63 URL: https://issues.jboss.org/browse/SHRINKRES-63 Project: ShrinkWrap Resolvers Issue Type: Feature Request Affects Versions: 2.0.0-alpha-2 Reporter: Andrew Rubinger Assignee: Karel Piwko >From Karel: The location of offline() method in MavenStrategyStage unfortunately does not cover all possible use cases: Imagine the following: User loads a pom - now the first resolution happens, because an effective pom is created and this is later used to define the dependencies: final File[] longhand = Resolvers.use(MavenResolverSystem.class).configureFromPom("path/to/pom").resolve("G:A").offline() .withTransitivity().as(File.class); I don't think that delaying ".configureFromPom("path/to/pom").resolve("G:A")" call until MavenStrategyStage is reached in the right way to go, because that way we couldn't for instance cache already parsed POM file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
8
0 / 0

← Newer
1
2
3
4
5
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues November 2012