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 projec
Shane has reworked maven project with an eye towards these use cases.
This stuff is in maven 3.0
Sent from my iPhone
On Aug 25, 2008, at 8:26 PM, 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 p
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?
Shane Isbell wrote:
Basically, you just put in into the pom. The id
references an external pom snippe
Hi Shane,
A few questions on this:
On 26/08/2008, at 12:26 AM, Shane Isbell wrote:
Basically, you just put in into the pom. The id
references an external pom snippet and injects it.
What does the id look like? Is the snippet a standalone file, or is it
referenced from an existing POM? And
Basically, you just put in 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]> 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 o
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 shoul
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
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.
Aside from the potential for solving this in the new project builder
code, the existing implementation has a major limitation:
If a parent POM specified a child in its dependencyManagement section
with scope == import, and that child specifies this parent POM in its
section, then you wind up
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 t
11 matches
Mail list logo
