To be exact, DefaultMavenProjectBuilder goes to extra trouble to end
up with a 'dynamic' version of the Build, not the resolved version,
and this test needs the resolved one.
On Mon, Feb 2, 2015 at 12:19 PM, Benson Margulies wrote:
> Somewhere between 2.0 and 2.2, MavenProjectBuild
Somewhere between 2.0 and 2.2, MavenProjectBuilder changed to build
projects with property references in them. For example,
.getBuild().getDirectory():
${project.basedir}/target
There are tests in archetype that are pretty confused by this. Can
someone remind me of how to obtain an interpolated
started
> looking at MavenProjectBuilder in Maven 2.2.1 and ModelBuilder in Maven
> 3.0.4.
>
> After some experimenting I end up needing either Repositories (M2) or
> ModelResolvers (M3). Does anyone know of any examples of how to use any
> of these in a stand-alone tool?
I would recomm
Hi
I'm working on a stand-alone tool (not invoked via Maven) that currently
reads POM files using the MavenXpp3Reader. Now there is a need to use
interpolated models instead of the plain file content. So I started
looking at MavenProjectBuilder in Maven 2.2.1 and ModelBuilder in Maven
Wouldn't it be better to set the default value of third parameter to
"false"?
I am not sure if we will need to have a method with 2 parameters but for
compatibility with existing code imo "false" is better.
Michal
> +public MavenProject build( File projectDescriptor,
> boolean usePare
