[ 
http://jira.codehaus.org/browse/MNG-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135029#action_135029
 ] 

John Casey commented on MNG-3536:
---------------------------------

We need to look into converging the interpolation code in this branch with the 
code in plexus-interpolation, which is a split-off of the interpolator code 
from plexus-utils. It can be found here:

http://svn.codehaus.org/plexus/plexus-sandbox/trunk/plexus-components/plexus-interpolation

I've already refactored the trunk project builder to use plexus-interpolation, 
and the assembly plugin is using the pre-split code in plexus-utils, but will 
be updated to use plexus-interpolation once it's released to avoid 
inconsistencies with forced versions of plexus-utils from mavens past.

In short, we have interpolation needs that go beyond the project builder, and 
need to handle other model class trees than maven-model. If we can use the same 
codebase to achieve this, it will help greatly in the consistency department.

We already have an interpolator in maven-project, one in plexus-utils that has 
moved into plexus-interpolation, another in plexus-expression-evaluator (not 
used in maven, afaik), and now this one...hopefully we can find a way to 
consolidate some of this work and realign all of our efforts to some 
extent...and maybe refocus on consistency regardless of the model (or file) 
being interpolated.

> REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore
> -----------------------------------------------------------------------------
>
>                 Key: MNG-3536
>                 URL: http://jira.codehaus.org/browse/MNG-3536
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.9
>         Environment: MacOSX, Java 6, Maven 2.0.9
>            Reporter: Sébastien Arbogast
>            Priority: Critical
>             Fix For: 2.0.10
>
>         Attachments: core-integration-testing-plugins.patch, 
> interpolator.it.patch, test.zip
>
>
> On one of my projects, I have the following property:
>  
> <model.uri>file:${project.build.sourceDirectory}/myapp.xmi</model.uri>
>  
> Knowing that in the same POM, sourceDirectory is configured that way:
>  
> <sourceDirectory>${project.basedir}/src/main/uml</sourceDirectory>
>  
> With Maven 2.0.8, model.uri was correctly mapped to 
> /Users/sarbogast/dev/myapp/src/main/uml/myapp.xmi
> But with Maven 2.0.9, now it's mapped to 
> /Users/sarbogast/dev/myapp/Users/sarbogast/dev/myapp/src/main/uml/myapp.xmi, 
> which is not good at all.
>  
> I have attached a test project that builds with Maven 2.0.8 but not with 
> Maven 2.0.9.
> It's not the simplest project ever but it's a real AndroMDA skeleton project.
> All the configuration is in mda/pom.xml

-- 
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


Reply via email to