Yeah, all I'm trying to grab is...
<plugin>
<version>______</version>
</plugin>
and
<dependency>
<version>_______</version>
</dependency>
I know I have to do a little digging to figure out the artifactId and the
groupId if they are defined by properties, but I need to know:
1. if there is a version specified
2. what the text specifying the version is (to see if it uses ${____})
I then go and relate this information back to the interpolated and original
models from project builder...
since project builder messes with both the original and the interpolated
models I have to go down to the raw source..... I was parsing the XML
directly with a pull parser... but I suspect that's far worse than using the
raw model from MavenXpp3Reader
;-)
-Stephen
2009/3/16 John Casey <[email protected]>
> Unless someone else knows more about it than I do, I'd say you're probably
> right; it's in that 1%. :-)
>
> The problem with skipping the project builder is that assembly of project
> instances is really complex, and skipping any of these steps may result in
> project instances with apparent bugs that may not work correctly in the rest
> of the build.
>
> As long as the Model instance you read directly from XML isn't used except
> to grab some very limited information from the XML file (not, for instance,
> from something that may be interpolated within that file), you should be
> okay...
>
> -john
>
>
> Stephen Connolly wrote:
>
>> Hey!
>>
>> So either my memory is wrong or i remember somebody saying it's a "bad
>> thing"(TM) to use MavenXpp3Reader from a plugin....
>>
>> I know that 99% of the time one should use model builder directly, but I
>> have a use case where I just want the results before *any* interpolation
>> what so ever is performed...
>>
>> Am I still doing a "bad thing" or is this the 1% i suspect it is?
>>
>> -Stephen
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
