[
http://issues.ops4j.org/browse/PAXEXAM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12109#action_12109
]
Toni Menzel commented on PAXEXAM-35:
------------------------------------
Thanks Richard, commited your patch. But normally you should(and can) commit
yourself as of we practice "open participation".
I added your patch myself to actually see if its better than my frustrative
adventures with the plugin api yesterday morning.
but, i have the feeling that i interpreted more into you initial request +
maven plugins capabilities (at least not documented):
Checkout the latest exam.
There's now a new pax-exam-it-05 which contains two projects:
1. a dependency bundle (very simple, we want to depend on it)
2. a test project with pom set up to use our plugin
So, what i want to archive is to let:
# mvn clean package
pass through. Meaning, that the dependency bundle just exists in this maven
session (no local repo).
So i think it must be possible to let the plugin tell me this file and not the
local repo one.
Of cause, once its in local repo, it all works. But that has not the effect i
expected initially.
(mvn clean install)
Is it possible to access the "reactor session" inside the plugin ? Then i would
expect getting Artifact instances that return the project path when calling
getFile() like this:
<my_exam_checkout>/pax-exam-it-05/adependencybundle/target/pax-exam-it-05-adependencybundle-0.4.0-SNAPSHOT.jar
Maven must know about this, do we ?
> Let maven resolve dependencies in plugin up-front and provide resolved urls
> in generated paxexam.args
> -----------------------------------------------------------------------------------------------------
>
> Key: PAXEXAM-35
> URL: http://issues.ops4j.org/browse/PAXEXAM-35
> Project: Pax Exam
> Issue Type: Improvement
> Components: maven-paxexam-plugin
> Reporter: Richard Wallace
> Assignee: Toni Menzel
> Attachments: PAXEXAM-35.patch
>
>
> Suggestion from Richard Wallace on Mailinglist:
> The only thing I think would be an improvement is if the
> dependencies, instead of being passed using the mvn: URIs, would be
> resolved by the maven plugin and passed as file: URIs instead. This
> way, if I've got a project structure like
> myproject/
> bundle1/
> pom.xml
> bundle2/
> pom.xml
> integration-tests/
> pom.xml
> I can run the integration tests from the root project directory,
> myproject, and have the bundles that pax runner is configured with be
> the jars in myproject/bundle1/target/bundle1-1.0-SNAPSHOT.jar and
> myproject/bundle2/target/bundle2-1.0-SNAPSHOT.jar. As it stands now,
> because you pass the mvn: URI instead of the file: URI, pax runner
> will try and find the bundle jars in the local repository or try and
> download them from a remote repository rather than use the jars that
> were created as part of the build. It's really handy to not have to
> install the bundles into a local repository until the integration
> tests pass. This can be particularly important in doing CI.
--
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
