[
http://issues.ops4j.org/browse/PAXEXAM-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890#action_12890
]
Toni Menzel commented on PAXEXAM-124:
-------------------------------------
Are you speaking of something like we had in the infamous mvnlive url handler ?
I currently see also the following options:
- build them ourselves (like in your points). Drawback: bundles are built
differently than "usually". Its just not maven with all the plugins with its
pros and cons. Benefit: raw speed, performance, convinience.
- Maven3Embedder
Today i would probably give the maven3 embedder a shot, so mvn builds are
natively triggered - and if you trust maven so much that you just say "mvn
package-o" (translated to api, not doing Process Calls of cause) per artifact
of change (detect this ourselves) it should be also fast.
To me the first option probably will always have this bad taste of not being
the real builder.
A 3rd option perhaps would be to combine the two (not sure, speaking things
from top of my head):
Use option 1 but build but always "merge" with a known build from the real
builder (maven).
Run real builder in background concurrently. If the artifacts differ too much
(external influence that maven pulls in, changes in dependency management), it
will use the maven builder artifact as the new "base".
After this "detection" every next "merge" with smaller changes (code changes)
will just use the option1 builds (+merges).
> Better support for provisioning modules from the same project
> -------------------------------------------------------------
>
> Key: PAXEXAM-124
> URL: http://issues.ops4j.org/browse/PAXEXAM-124
> Project: Pax Exam
> Issue Type: New Feature
> Components: Core
> Reporter: Alin Dreghiciu
> Assignee: Toni Menzel
> Fix For: 1.2.0
>
>
> Most of the time one will use Pax Exam for integration tests by provisioning
> and testing modules from the same project as where the integration project
> resides. This works fine while in a maven build for example because usually
> the provisioned bundles from integration test is already build. But when
> using an IDE the most common pattern is that one will test some parts of the
> project and want to run the ITs again. This does not work as they will have
> to rebuild the changed modules first so the correct bundle content is
> provisioned, task which is error prone (you forgot and wonder why the changes
> are not in place), is time consuming and annoying.
> Will be great that there will be support in PAx Exam to avoid as much as
> possible this repetitive task. Some ideas:
> * Maven specific provisioning api based on assembly url handler (generates
> descriptor), or based on TinyBundles.
> * Best will be to just specify module name, relative to root.
> * This support will be able to find the classes to be included
> (target/classes) and generate the jar. Excellent (performance reason) will be
> to only add/remove the dif on a previous bundle.
> * This will not be quite workable for the kind of bundles where you pull in
> to the bundle external content form dependencies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
