Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Running tests using failsafe from a shaded jar?
From: Jason van Zyl <jason@takari.io>
In-Reply-To: 
 <CAK8jvqyHv5jzT8K_3ML3VHG5Bh2FYmV86YSmc6AFSrMMySuVkw@mail.gmail.com>
Date: Mon, 23 Nov 2015 08:22:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <407EC743-AC39-45B3-B332-E01C5C9D0D74@takari.io>
References: 
 <CAK8jvqyBE1TPvNNDVLWmHa0ytcG4X_VxPSG3K-1t9xVxLdc49A@mail.gmail.com>
 <CA+nPnMzmsdbCUHbgvtzar8PBnWw+whTt8Wfbi2OCG33vy=bpkw@mail.gmail.com>
 <CAK8jvqyHv5jzT8K_3ML3VHG5Bh2FYmV86YSmc6AFSrMMySuVkw@mail.gmail.com>
To: Maven Users List <users@maven.apache.org>

Mirko,

You=E2=80=99ll notice if you look at the source that it=E2=80=99s a =
JSR330 component. So there is a the sisu-maven-plugin which generates a =
META-INF/sisu/javax.inject.Named as part of the build. You will want to =
look in your shaded JAR and make sure you have one of those files, I=E2=80=
=99m not certain if there is a resource transformer that deals with this =
file so you might have to make one of those. I say might because it =
depends on how you start up the container for Maven. If you don=E2=80=99t =
particularly care about startup speed you can make the container scan =
the classpath and it will create all the bindings from the classes in =
the scan. By default in Maven we get the container to use the index file =
cited above because it=E2=80=99s much faster at creating all the =
bindings. Your error results from there being no binding for the =
DefaultClassRealmManager so it=E2=80=99s likely not finding the =
javax.inject.Named file.

If you look at some of the test cases[1] in maven-core you=E2=80=99ll =
see where the container is created and see how the scanning behaviour is =
changed. To try something quickly you can just turn the classpath =
scanning on and see if it=E2=80=99s fast enough. You might also have to =
lift a few bits from the PlexusTestCase class itself but it=E2=80=99s =
very similar to how the container if created in the MavenCli class which =
also serves as an example.

[1]: =
https://github.com/apache/maven/blob/master/maven-core/src/test/java/org/a=
pache/maven/AbstractCoreMavenComponentTestCase.java

> On Nov 22, 2015, at 2:03 AM, Mirko Friedenhagen =
<mfriedenhagen@gmail.com> wrote:
>=20
> Hello Stephen, I will share how to do this in general. As it it not as =
easy
> as I hoped I will firstly extract a POC project and share that on =
GitHub
> immediately with the risk of never succeeding :-)
>=20
> Regards
> Mirko
> --=20
> Sent from my mobile
> Am 21.11.2015 23:34 schrieb "Stephen Connolly" <
> stephen.alan.connolly@gmail.com>:
>=20
>> If you get this working, any chance you could share your work?
>>=20
>> On 21 November 2015 at 21:20, Mirko Friedenhagen =
<mfriedenhagen@gmail.com>
>> wrote:
>>=20
>>> Hello,
>>>=20
>>> I want to use to run tests on machine, where Maven is not installed
>>> and access to a repository is not allowed.
>>> However I want to (ab-)use the failsafe plugin so I may use the fine
>>> machinery which allows to specify tests and get XML reports.
>>>=20
>>> Using maven-embedded I created an App class which just runs
>>> failsafe:integration tests, all dependencies are found in a shaded
>>> jar.
>>> I already used
>>> =
org.apache.maven.plugins.shade.resource.ComponentsXmlResourceTransformer
>>> so a complete looking META-INF/plexus/components.xml is created.
>>>=20
>>> When I start the jar with java -jar MY_SHADED_JAR.jar I always get =
the
>>> following error:
>>>=20
>>> 22:09:57.365 [main] WARN  Sisu - Error injecting:
>>> org.apache.maven.project.DefaultProjectBuildingHelper
>>>=20
>>> com.google.inject.ProvisionException: Unable to provision, see the
>>> following errors:
>>>=20
>>>=20
>>> 1) No implementation for =
org.apache.maven.classrealm.ClassRealmManager
>>> was bound.
>>>=20
>>>  while locating =
org.apache.maven.project.DefaultProjectBuildingHelper
>>>=20
>>>=20
>>> Looking into components.xml DefaultClassRealmManager is not there =
but
>>> is referenced twice.
>>>=20
>>> Grepping through the components.xml files in a Maven installation, I
>>> do not see where the DefaultClassRealmManager is instantiated.
>>>=20
>>> Regards Mirko
>>> --
>>> http://illegalstateexception.blogspot.com/
>>> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
>>> https://bitbucket.org/mfriedenhagen/
>>>=20
>>> =
---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>=20
>>>=20
>>=20

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org