[ http://jira.codehaus.org/browse/MNG-2606?page=all ]
Greg Kick closed MNG-2606.
--------------------------
Resolution: Fixed
It turns out that this behavior is implemented in AntMojoWrapper... Now I just
have to figure out why I couldn't get it to work... :-)
> Add maven classpaths as parameters to ant mojos (like antrun behavior)
> ----------------------------------------------------------------------
>
> Key: MNG-2606
> URL: http://jira.codehaus.org/browse/MNG-2606
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin Creation Tools
> Reporter: Greg Kick
>
> Currently, the antrun plugin, via
> AntProjectPopulator.populateAntProjectWithMavenInformation() allows maven
> tasks run in a POM (via the antrun plugin) to access the various maven
> classpaths. This seems to be both useful and widely used. I would recommend
> adding maven.dependency.classpath, maven.compile.classpath,
> maven.runtime.classpath, maven.test.classpath and maven.plugin.classpath as
> "default" parameters alongside basedir and antMessageLevel in
> AntMojoDescriptorExtractor.
> This would have the benefit of standardizing the way these parameters are
> accessed (as I'm sure they will often be for ant mojos) and saving developers
> the hassle of having to do it every time (and figuring out how to do it for
> that matter).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
