[
https://issues.redhat.com/browse/SHRINKRES-282?page=com.atlassian.jira.pl...
]
Paolo Antinori commented on SHRINKRES-282:
------------------------------------------
This is so old that I don't even remember what I was trying to achieve at that time.
I just wanted to follow up with a pointer in a possible other direction, just to ad the
conversation for anyone that might be doing Maven pom manipulation:
The last time I have to perform tasks in this context I have used this other project:
https://release-engineering.github.io/pom-manipulation-ext/guide/plugin-m...
Check it out if it might either be an alternative to the original problem or if it could
be an inspiration on how to fix this on Shrinkwrap
Resolve just a pom.xml
----------------------
Key: SHRINKRES-282
URL:
https://issues.redhat.com/browse/SHRINKRES-282
Project: ShrinkWrap Resolvers
Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Paolo Antinori
Priority: Major
What's the correct way to resolve a pom.xml ? My use case is to obtain a BOM.
{code}
Maven.resolver().resolve("org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:pom:3.0.0-beta-2").withoutTransitivity().asFile();
{code}
{code}
MavenResolvedArtifact artifact =
Maven.resolver().resolve("org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:pom:3.0.0-beta-2").withoutTransitivity()
.asSingle(MavenResolvedArtifact.class);
{code}
they both fail? Am I doing something wrong or is this behavior broken for pom files?
--
This message was sent by Atlassian Jira
(v8.13.1#813001)