> > <deploy:copy-deps todir="${maven.build.dir}"
> > projectDescriptor="${x.getFile()}"/>
>
> everytime I read something like this on this list, I wonder how you can know
> that this es even possible. Where do I have to look to find out, that there
> is a property defined "reactorProjects" and that a getFile() assumingly gets
> the project file (as a java File object, as String, ... ?)
>
> Do you all read the jelly scripts for all the plugins to learn what is
> possible? I started doing that, but I wonder if there is a better way.
indeed thats what i do.. reading the ReactorTag source (or the numerous examples
available out there) you can know that if postProcessing is set to true in
maven:reactor a variable named reactorProjects is set in the context
(http://maven.apache.org/xref/org/apache/maven/jelly/tags/maven/ReactorTag.html#335).
reading the deploy plugin you can see that deploy:copy-deps passes the
projectDescriptor var to the maven:pom tag
(maven_home_local/plugins/maven-deploy-plugin-1.1/plugin.jelly#140) ; also
maven:pom accepts a file as parameter
(http://maven.apache.org/tags.html#maven:reactor) and Project has a property of
type File
(http://maven.apache.org/xref/org/apache/maven/project/Project.html#194) so you
can jump quickly on the conclusion.. as you can see pretty much of the needed
information is available online.
ive described here the path i personnally take to discover that. that might seem
to be a bit complicate, however it needs much less time than writing this mail
(about 1 or 2 minutes), then 1 minute to test (creating a simple project
structure for that purpose) the assumptions that have been made (for instance
testing that the File property has been correctly set and is available).
last, im not sure to really understand what you mean by "read the jelly scripts
for all the plugins". i dont think that reading all the plugins are actually
quite good (assuming is would make sense to read them *all*), instead i prefer
to lazyread them. you can know which plugins are available and what they
globally do by looking at the plugin doc, that should be enough..
comments about the "process" described here are welcome. please forgive me if
replied a bit out of topic.
regards,
-- gd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
