Hi Scott,
sorry for the link. We just decided to break resolver life cycle from
ShrinkWrap one. Currently, the pom as well as the project itself can be
found at
Hi Karel,
Thanks for the answer. I noticed that the [1] link is not valid. Does
that reflect a different solution taking place perhaps? Or should I not
read into that? ;)
Do you have a new link that I should take the dependencies from?
Also, which AS7 project/module should have its dependencies updated, to
work around this (the as7/testsuite project?).
Scott
On 07/26/2011 09:12 AM, Karel Piwko wrote:
> Hi Scott,
>
> this is likely caused by too strict exclusions in jboss-as-parent. As a
> workaround, you have to enumerate all dependencies from [1] directly in
> the project/module where you want to use the resolver.
>
> This was caused by
https://issues.jboss.org/browse/AS7-954, I filed
>
https://issues.jboss.org/browse/AS7-1403 to track the problem.
>
> Karel
>
> [1]
>
https://github.com/shrinkwrap/shrinkwrap/blob/master/extension-resolver/i...
>
> On Mon, 2011-07-25 at 15:51 -0400, Scott Marlow wrote:
>> On 07/15/2011 08:50 AM, Karel Piwko wrote:
>>> Hi All,
>>>
>>> see comments inline.
>>>
>>> Karel
>>>
>>> On Fri, 2011-07-15 at 01:19 -0400, Scott Marlow wrote:
>>>> We already include org.hibernate:hibernate-core:jar:4.0.0.Beta1 and I
>>>> want to test against org.hibernate:hibernate-core:jar:3.6.4.Final.
>>>>
>>>> It is possible that the org.hibernate:hibernate-core:jar:3.6.4.Final
>>>> artifact will not be in the local maven repo, when the unit test
starts.
>>>> If the ShrinkWrap maven resolver would download it into the local
>>>> maven cache, we should get good enough performance (similar to if the
>>>> artifact was downloaded during the build).
>>>>
>>> MavenDependencyResolver will act exactly that way, if the local
>>> repository contains the artifact, it will be fetched from there, if not
>>> remote repositories will be touched.
>>
>> I tried calling
>>
"DependencyResolvers.use(MavenDependencyResolver.class).artifact("org.hibernate:hibernate-core:3.6.5.Final").resolveAs(GenericArchive.class)"
>> from an existing AS7 testsuite test but got a CNFE on class
>> org.sonatype.aether.resolution.ArtifactResolutionException.
>>
>> as7/tools/maven/lib/aether-api-1.9.jar seems to have this class. Which
>> pom.xml do I need to update for ShrinkWrap to have access to aester api?
>>
>> Thanks,
>> Scott
>
>