shrinkwrap-issues May 2018

shrinkwrap-issues@lists.jboss.org

1 participants
4 discussions

[JBoss JIRA] (SHRINKRES-222) Environment variables are not replaced when using ParsedPomFile.getProperties()

by Falko Modler (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-222?page=com.atlassian.jira.plu... ] Falko Modler commented on SHRINKRES-222: ---------------------------------------- [~mjobanek] I am indeed loading a pom.xml that is not in a project directory but resides on the classpath instead. Unfortunately, using the file from target is not an option for me. > Environment variables are not replaced when using ParsedPomFile.getProperties() > ------------------------------------------------------------------------------- > > Key: SHRINKRES-222 > URL: https://issues.jboss.org/browse/SHRINKRES-222 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.1.1 > Environment: Windows 7 x64 > Reporter: Falko Modler > > In Maven you can define properties using environment variables, e.g.: > {{<someProp>$\{env.SOME_ENV\}<someProp>}} > See also: http://books.sonatype.com/mvnref-book/reference/resource-filtering-sect-p... > On the command line, those placeholders a replaced as expected. This can be checked via {{mvn help:effective-pom}}. > Unfortunately, {{ParsedPomFile.getProperties()}} does *not* replace those placeholders. It returns them "as is" (e.g. {{"$\{env.SOME_ENV\}"}}). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-271) Maven dependency resolution is not reactor-aware

by Sebastian Schuberth (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plu... ] Sebastian Schuberth edited comment on SHRINKRES-271 at 5/22/18 2:30 PM: ------------------------------------------------------------------------ Turns out there's no need to reimplement the Maven Reator to be able to resolve inter-module dependencies. Instead you can use the trick from our [OSS Review Toolkit project|https://github.com/heremaps/oss-review-toolkit] to create a ["fake" LocalRepositoryManager|https://github.com/heremaps/oss-review-toolkit/blo...] that pretends that the POM files of the currently analyzed project are available in the local repository. was (Author: sschuberth): Turns out there's no need to reimplement the Maven Reator to be able to resolve inter-module dependencies. Instead you can use the trick from our [OSS Review Toolkit project|https://github.com/heremaps/oss-review-toolkit] to create [a "fake" LocalRepositoryManager|https://github.com/heremaps/oss-review-toolkit/blo...] that pretends that the POM files of the currently analyzed project are available in the local repository. > Maven dependency resolution is not reactor-aware > ------------------------------------------------ > > Key: SHRINKRES-271 > URL: https://issues.jboss.org/browse/SHRINKRES-271 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.6 > Environment: Windows 10 64-bit > Reporter: Sebastian Schuberth > > Maven dependency resolution does not seem to be reactor-aware in the sense that inter-module dependencies in a multi-module project are not resolved properly unless they are manually installed in the local Maven cache. > The general problem when using the Maven command line tool is well described at http://stackoverflow.com/questions/1677473/maven-doesnt-recognize-sibling.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-271) Maven dependency resolution is not reactor-aware

by Sebastian Schuberth (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plu... ] Sebastian Schuberth commented on SHRINKRES-271: ----------------------------------------------- Turns out there's no need to reimplement the Maven Reator to be able to resolve inter-module dependencies. Instead you can use the trick from our [OSS Review Toolkit project|https://github.com/heremaps/oss-review-toolkit] to create [a "fake" LocalRepositoryManager|https://github.com/heremaps/oss-review-toolkit/blo...] that pretends that the POM files of the currently analyzed project are available in the local repository. > Maven dependency resolution is not reactor-aware > ------------------------------------------------ > > Key: SHRINKRES-271 > URL: https://issues.jboss.org/browse/SHRINKRES-271 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.6 > Environment: Windows 10 64-bit > Reporter: Sebastian Schuberth > > Maven dependency resolution does not seem to be reactor-aware in the sense that inter-module dependencies in a multi-module project are not resolved properly unless they are manually installed in the local Maven cache. > The general problem when using the Maven command line tool is well described at http://stackoverflow.com/questions/1677473/maven-doesnt-recognize-sibling.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-214) NoResolvedResultException when trying to resolve a POM

by Alex Kravets (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-214?page=com.atlassian.jira.plu... ] Alex Kravets commented on SHRINKRES-214: ---------------------------------------- Also interested in proposed resolution. > NoResolvedResultException when trying to resolve a POM > ------------------------------------------------------ > > Key: SHRINKRES-214 > URL: https://issues.jboss.org/browse/SHRINKRES-214 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Michael Schnell > > Trying to resolve a "pom" results in an org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to resolve dependencies, none of them were found. > Looking at the local Maven repository, the POM was actually loaded from the remote repo, but it's not returned: > {code:java} > Maven.resolver().resolve("org.jboss:jboss-parent:pom:12").withoutTransitivity().asSingleFile(); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2018