Let me think about this, but I tried to move the JDEV plugin to maven plugins, no luck so far....
On 8/26/07, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > -------------- Original message ---------------------- > From: "Adam Winer" <[EMAIL PROTECTED]> > > Today, our repository looks like: > > trunk > > trinidad > > plugins > > > > branches > > trinidad-xyz-branch > > trinidad > > plugins > > etc.... > > > > tags > > maven-plugin-parent-1... > > trinidad-1... > > > > What's weird here is that we release and tag the plugins independently > > of the core, but we still maintain the trunk and branches with these two > > together. > > > > Going forward, I suspect we'll want the ability to do quick releases > > of the core without touching the plugins. (I'm tempted to do a 1.0.3 > > release in the near future.) But as long as our trunk repository is > > what it is, that doesn't seem that feasible. And I don't see any reason > > why we shouldn't be able to do a quick plugins release to resolve > > any Myfaces Core issues without touching the rest of Trinidad. > > > > So: my proposal is that we should redo the repos to be: > > > > http://svn.apache.org/repos/asf/myfaces/trinidad/core > > trunk > > branches > > tags > > http://svn.apache.org/repos/asf/myfaces/trinidad/plugins > > trunk > > branches > > tags > > > > ... and let the two release independently. There still > > would be cases (potentially many) where we have to > > release plugins, then the core, in lockstep. This would > > have been true for 1.0.1 and 1.0.2, for instance. But it'd > > definitely better reflect our tagging strategy. > > > > Maybe the trinidad plugins should be move to myfaces/maven since JSF 1.2 has > a dependency? > > > > -- Adam > > Gary > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
