IIRC, path resolution was taking place in the project builder...which
would mean that it could have happened during kenney's cleanup of the
interpolation. Not sure, though. (I'm fairly certain on the timing of
the path translation, though...I'm pretty sure it happened during
project-building, not plugin configuration...)
-john
On Jul 29, 2007, at 12:36 PM, Jason van Zyl wrote:
I'm trying to find the source of the problem, but it0088 is broken
on trunk and that's the very nasty ${project.build.directory} not
resolving to a full path which caused a tremendous amount of grief
between the 2.0. and 2.0.1 releases.
I can tell immediately what broke it, but if anyone was mucking
about with mojo configurations that is probably it.
The IT is it0088 which uses the support plugin here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/
trunk/core-integration-testing-plugins/maven-it-plugin-generate-
properties/src/main/java/org/apache/maven/plugin/coreit/
InterpolatedPomConfigurationMojo.java
In a nutshell the problem is that ${project.build.directory} used
in a plugin configuration like so:
<configuration>
<projectBuildDirectory>${project.build.directory}</
projectBuildDirectory>
</configuration>
Is not making it into the mojo fully resolved but only as "target"
which is bad.
I will dig around but if you touched anything in the interpolation,
mojo configuration bits take a look. Once this is fixed I think we
can start pushing out early alphas for those that want to live on
the edge.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
