Folks, A general theme of these comments is, 'and what are we going to put in our new pom version?'
I didn't go there in my writeup, since I was concerned with the mechanics of 'how do we have a new POM *at all*'. But I see the point; we can't make a new pom model every week, so we need to combine a substantial list of proposed enhancements. Perhaps other could add more wiki content to start this? When I think about this, I find myself wishing that we could invent a middle ground between 'no changes at all' and 'a new major version.' In the same way that individual plugins can add new <configuration/> elements any time, I'd like to enhance my overall proposal to include a section on 'future-proofing' the next schema rev by adding a few judicious <xs:any/> specifications and documenting some conventions for their use. In other words, as of 'pom5', any tool that reads a POM should be prepared to gracefully ignore things it doesn't expect in some specified areas of the schema. How broad should this be? I'd also like to specify that all parsers should be namespace-aware, so that third-parties can define their own POM additions via namespaces. FInally, for today, does anyone have any sympathy for focussing on RNG schema instead of W3C? On Wed, Jul 27, 2011 at 7:28 AM, Kristian Rosenvold <[email protected]> wrote: > Nice work. I somehow think that the starting point for this disucssion > should be the intended functionality of such a change; so I'd like to > start the discussion with the use cases. > > One very simple use case which I personally would appreciate is more > compact pom format; "less bloat". I could see us supporting a simple > "4.1" format that is bidirectionally mappable between 4.0 and 4.1, > and the mapping could happen both in a "maven 3.1" and/or a repository > manager. > > I somehow think just determining what would be necessary for such a feature > would be a > nice start; I'm quite sure a lot of our users would love a leaner pom format. > > Kristian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
