> It's still not entirely clear to me what the difference is between this
> and something a plugin could fire off, but I might not have my thinking
> hat on today.
this is pretty much entirely outside the purview of this thread, it was just
my usecase..so I'll just cease discussion on that and us
Right.
It's still not entirely clear to me what the difference is between this
and something a plugin could fire off, but I might not have my thinking
hat on today.
It still seems strange to me that we are re-inventing ways to validate
pieces of XML when namespaces already exist for that purpose,
sorry on the wrapping, an artifact of the convoluted way I had to move it
around to get gmail to actually send it
1) it was related to custom in that it is basically alluding to a proposel
to have a structured mechanism of inserting other models into the pom and
having maven be able discover the i
Jesse,
You've lost me a bit with this (and with the wrapping I found it really
hard to read :)
1) is this related to the custom discussion or is this just a new
element you'd like to add (if the latter, I think it deserves a new thread)
2) is this related to the current tag, or something differ
I was thinking about this a bit..
what about adding something like
runtime-model
org.codehaus.mojo.plugin
1.0-SNAPSHOT
where we can logically embed the particular types of extensions to the
+1. Strict parsing is only on for projects you build, its off for poms
in the repository.
This should be a change on trunk only, and the model version should be
changed to 4.1.0, right? We need to now start looking into dealing with
projects differently based on the model version.
Given that this
Kenney Westerhof wrote:
On Fri, 31 Mar 2006, Jason van Zyl wrote:
Some thoughts/ideas:
I didn't realize checking was on! You can specify multiple
sections etc, and it still works.
Whoops.
Also the namespace in the pom is not used.
The presence of the schema location tag is also ignored, bu
John Casey wrote:
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
After some more chatting in IRC I think that if a element was
added to the
On Fri, 31 Mar 2006, Jason van Zyl wrote:
Some thoughts/ideas:
I didn't realize checking was on! You can specify multiple
sections etc, and it still works.
Also the namespace in the pom is not used.
The presence of the schema location tag is also ignored, but this is
usually the responsibility
John Casey wrote:
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
Think the most convenient would to put the Xpp3DOM object in the
MavenProje
so, how do you gain access to the custom section? Would you have to
re-parse the whole pom? Also, would be subject to any sort of
inheritance, or would it simply be invisible to the project builder?
-john
Jason van Zyl wrote:
Jason van Zyl wrote:
Hi,
For some reason I thought that the stri
Jason van Zyl wrote:
Hi,
For some reason I thought that the strictness in model parsing had been
turned off. I was playing around trying to add a element and
noticed it is still on.
Can we enable the lax parsing in order to make the POM extensible?
The POM will will still be validated at t
Hi,
For some reason I thought that the strictness in model parsing had been
turned off. I was playing around trying to add a element and
noticed it is still on.
Can we enable the lax parsing in order to make the POM extensible?
The POM will will still be validated at the object model level
13 matches
Mail list logo
