Hello Andrei!
I am not aware of any such tool. Anyway I think that a fully automated
solution might not be that simple. To run your bundle, you'd have to
provision all dependencies in the runtime classpath. Dependencies that are
in scope provided could in theory also be provisioned, but I don't think
that would be very intuitive. Also, you'd probably requires some, but not
all of the dependencies in scope test to be provisioned. For instance, you
might want to use Mockito or something like that in your test-probe.
Provisioning all test-scoped dependencies would also provision Pax Exam
itself, for instance, which is probably not what you want.
So, in my opinion, the only practical approach would be to provision
runtime-scoped dependencies, and configure the rest manually. But that is
neither one nor the other, so I don't think I like it very much.
Greetings,
Björn
On Thu, Sep 27, 2012 at 10:56 PM, Andrei Pozolotin <
[email protected]> wrote:
> Hello
>
> I am curious if there is a way to avoid completely entries like
>
> mavenBundle().groupId("org.apache.felix")
> .artifactId("org.apache.felix.fileinstall")
> .versionAsInProject(),
>
> from pax exam test options definitions
> public static Option[] options( final Option... options )
>
> it seems it should be possible to come up with some kind of maven-based
> convention,
> so all of this can be taken directly from the pom? are there tools for
> this?
>
> Thank you,
>
> Andrei
>
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
>
>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
