[
https://issues.jboss.org/browse/SHRINKRES-180?page=com.atlassian.jira.plu...
]
Karel Piwko commented on SHRINKRES-180:
---------------------------------------
Hi Markus,
I believe that we always include provided - as MavenImporter needs to them in order to
compile java code. However, I'll try to split compilation resolution from archive
composition.
The other part is to check whether we are propagating *provided* scope correctly. Would
you be able to just load the pom.xml (not using importer but just Maven.resolver() and
resolve hibernate-search to see whether hibernate-core will be downloaded?
transitive dependencies updated from provided to compile
--------------------------------------------------------
Key: SHRINKRES-180
URL:
https://issues.jboss.org/browse/SHRINKRES-180
Project: ShrinkWrap Resolvers
Issue Type: Bug
Affects Versions: 2.2.0-alpha-2
Reporter: Markus Schulz
Assignee: Andrew Rubinger
Fix For: 2.2.0-alpha-3
Attachments: deptree.txt, MavenResolverTest.java, transitivetest-pom.xml
i have a pom with something like:
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-search</artifactId>
<version>4.2.0.Final</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<scope>provided</scope>
</dependency>
hibernate-search internally dependes on hibernate-core (scope compile). But in don't
want to get hbernate-core in my deployment, therefore it's forced to provided.
But:
File[] testLibs = Maven.configureResolver()
.workOffline()
.loadPomFromClassLoaderResource("transitivetest-pom.xml")
.importRuntimeDependencies()
.resolve()
.withTransitivity()
.asFile();
still contains hibernate-core.jar
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)