That scenario is possible with any maven artefact that the built relies on. AFAIK the
ShrinkWrap maven resolver will use the version cached in the local repository, so it is no
different to any other maven dependency.
Stuart
On 15/07/2011, at 4:16 AM, Jesper Pedersen wrote:
On Thursday, July 14, 2011 02:09:40 PM Jaikiran Pai wrote:
> I was writing a similar testcase sometime back which required a jar to
> be added to the deployment. But I wasn't too sure if it was a good idea
> to use the Maven resolver within the testcase. I haven't looked into how
> it's implemented, but trying to resolve via maven during each test run
> would probably slow down things a bit, isn't it?
>
> On Thursday 14 July 2011 08:17 PM, Scott Marlow wrote:
>> Can someone help bring in the Maven extension to ShrinkWrap in AS7.1
>> testsuite? I wanted to ask, before trying to hack it on my own. I
>> think this would help us create better and more complete tests.
Please, no.
I see this:
#1 Code gets committed
#2 You/Jenkins update
#3 Nexus repo is down/can't be resolved/can't be accessed/...
#4 ¤%"%#¤%"¤&"!%"!#¤%!"#!
and having a Maven resolver running in the testsuite is just asking for
trouble.
Just add the needed .jar's to the testsuite/ - we already have examples of
this.
Best regards,
Jesper
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev