On 8/25/08, Ralph Goers <[EMAIL PROTECTED]> wrote:
>
> I'm still confused. If I had thought that it could be done that way I would
> have done it in the first place. How does that get past schema checking? Or
> are you adding it to the xsd somewhere?


The mavenImport tag is processed in the project builder prior to passing it
to the Xpp3Reader, which then does the schema validation. There is still the
outstanding problem that these import tags could not be directly read by
modello.

Shane

Shane Isbell wrote:
>
>> Basically, you just put in <mavenImport id=""/> into the pom. The id
>> references an external pom snippet and injects it. Right now, there is
>> nothing that can resolve these snippets so that's one thing that needs to be
>> added (I'm thinking Mercury here).
>>  Shane
>>
>>  On 8/25/08, *Ralph Goers* <[EMAIL PROTECTED] <mailto:
>> [EMAIL PROTECTED]>> wrote:
>>
>>
>>
>>    Ralph Goers wrote:
>>
>>
>>
>>        Ralph Goers wrote:
>>
>>
>>
>>            Ralph Goers wrote:
>>
>>
>>
>>                Shane Isbell wrote:
>>
>>                    I've been refactoring more of the project builder
>>                    code and encountered a
>>                    rule that if a
>>                    dependencyManagement/dependencies/dependency
>>                    element has
>>                    type=pom and scope=import, the dependency
>>                    management section of that
>>                    dependency should be imported into the containing
>>                    pom model. This is a
>>                    one-off rule that doesn't easily fit into the new
>>                    project builder which
>>                    keeps all pom specific rules in the
>>                    PomClassicTransformer class. This type
>>                    of behavior could be handled instead by
>>                    mixins/imports within the latest
>>                    maven-shared-model code. The way this would work
>>                    is that you could use a
>>                    mavenImport tag in the dependencyManagement
>>                    section of the pom and then the
>>                    framework would handle importing the xml fragment
>>                    containing the dependency
>>                    info. Thoughts?
>>
>>                    Shane
>>
>>                I'm not sure I completely follow. Can you provide an
>>                example?
>>
>>
>>            Shane, can you please provide an example of the way it
>>            would work?
>>
>>
>>        I'm still waiting for an example.  I'd really like to
>>        understand what you are talking about.
>>
>>    Pinging one more time.  I'd really like to understand this.
>>
>>    Ralph
>>
>>
>>

Reply via email to