5:58 p.m.
Hi all,
due to how testsuite works (the modules/ dir is not copied to instances
but referenced),
the module for the JDBC driver is added in the original dir,
*when running with other than H2 db* using -Dds=... .
Is everyone ok with that?
Regards,
Ondra
5:59 p.m.
I would prefer we setup a more general solution for this in the test suite infrastructure,
as there are a few tests that need to add modules. Basically as part of the server build /
arquillian config I would prefer a second modules dir to be specified in the target
directory, and any new modules can then be added to this directory, so there is no need to
touch the original modules directory.
Stuart
On 01/08/2012, at 8:58 AM, Ondřej Žižka <ozizka(a)redhat.com> wrote:
Hi all,
due to how testsuite works (the modules/ dir is not copied to instances but referenced),
the module for the JDBC driver is added in the original dir,
*when running with other than H2 db* using -Dds=... .
Is everyone ok with that?
Regards,
Ondra
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:30 p.m.
New subject: -Dmodule.path=/foo/modules:/bar/modules ? /// Re: Testsuite: Running with alternative DB will change the tested AS dir
Is this possible already? If, then how?
I would expect File.pathSeparator-separated list of directories put to
module.path, like
-Dmodule.path=/foo/modules:/bar/modules
Is that supported?
Ondra
On Wed, 2012-08-01 at 08:59 +1000, Stuart Douglas wrote:
I would prefer we setup a more general solution for this in the test
suite infrastructure, as there are a few tests that need to add modules. Basically as part
of the server build / arquillian config I would prefer a second modules dir to be
specified in the target directory, and any new modules can then be added to this
directory, so there is no need to touch the original modules directory.
Stuart
On 01/08/2012, at 8:58 AM, Ondřej Žižka <ozizka(a)redhat.com> wrote:
> Hi all,
>
> due to how testsuite works (the modules/ dir is not copied to instances but
referenced),
> the module for the JDBC driver is added in the original dir,
> *when running with other than H2 db* using -Dds=... .
>
> Is everyone ok with that?
>
> Regards,
> Ondra
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:48 p.m.
New subject: -Dmodule.path=/foo/modules:/bar/modules ? /// Re: Testsuite: Running with alternative DB will change the tested AS dir
Yes, that is exactly how it should work.
Stuart
On 01/08/2012, at 9:30 AM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
Is this possible already? If, then how?
I would expect File.pathSeparator-separated list of directories put to module.path,
like
-Dmodule.path=/foo/modules:/bar/modules
Is that supported?
Ondra
On Wed, 2012-08-01 at 08:59 +1000, Stuart Douglas wrote:
>
> I would prefer we setup a more general solution for this in the test suite
infrastructure, as there are a few tests that need to add modules. Basically as part of
the server build / arquillian config I would prefer a second modules dir to be specified
in the target directory, and any new modules can then be added to this directory, so there
is no need to touch the original modules directory.
>
> Stuart
>
> On 01/08/2012, at 8:58 AM, Ondřej Žižka <ozizka(a)redhat.com> wrote:
>
> > Hi all,
> >
> > due to how testsuite works (the modules/ dir is not copied to instances but
referenced),
> > the module for the JDBC driver is added in the original dir,
> > *when running with other than H2 db* using -Dds=... .
> >
> > Is everyone ok with that?
> >
> > Regards,
> > Ondra
> > _______________________________________________
> > jboss-as7-dev mailing list
> > jboss-as7-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
7:54 p.m.
New subject: -Dmodule.path=/foo/modules:/bar/modules ? /// Re: Testsuite: Running with alternative DB will change the tested AS dir
I do that kind of manipulation in the domain test suite to make an extra
extension available:
https://github.com/jbossas/jboss-as/blob/df5e5b2854cfedf255944c5fc464962f...
On 8/1/12 7:48 AM, Stuart Douglas wrote:
Yes, that is exactly how it should work.
Stuart
On 01/08/2012, at 9:30 AM, Ondrej Zizka <ozizka(a)redhat.com
<mailto:ozizka@redhat.com>> wrote:
> Is this possible already? If, then how?
> I would expect File.pathSeparator-separated list of directories put
> to module.path, like
>
> -Dmodule.path=/foo/modules:/bar/modules
>
> Is that supported?
>
> Ondra
>
>
>
> On Wed, 2012-08-01 at 08:59 +1000, Stuart Douglas wrote:
>> I would prefer we setup a more general solution for this in the test suite
infrastructure, as there are a few tests that need to add modules. Basically as part of
the server build / arquillian config I would prefer a second modules dir to be specified
in the target directory, and any new modules can then be added to this directory, so there
is no need to touch the original modules directory.
>>
>> Stuart
>>
>> On 01/08/2012, at 8:58 AM, Ondřej Žižka <ozizka(a)redhat.com
<mailto:ozizka@redhat.com>> wrote:
>>
>> > Hi all,
>> >
>> > due to how testsuite works (the modules/ dir is not copied to instances but
referenced),
>> > the module for the JDBC driver is added in the original dir,
>> > *when running with other than H2 db* using -Dds=... .
>> >
>> > Is everyone ok with that?
>> >
>> > Regards,
>> > Ondra
>> > _______________________________________________
>> > jboss-as7-dev mailing list
>> >jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
>> >https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
4527
days inactive
4528
days old
4 comments
4 participants
participants (4)
-
Brian Stansberry -
Ondrej Zizka -
Ondřej Žižka
-
Stuart Douglas