Re: xmlns:deploy and plugins
At this stage of the game, might be best left alone, and just indicate in the docs that the plugin is only intended for reuse by other plugins and is deprecated otherwise. Dion Gillard wrote: On Thu, 08 Jul 2004 22:05:45 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: I think we can ditch it in 1.0 though - a fleeting message in RC4 was enough :) Jason was going to relegate release to the sandbox as incomplete last year, but we kept it around because some of the java code is being reused elsewhere. Maybe its time to shift the java code and dump the release plugin? I don't know if anyone is using it... I'm all for putting the java code where its most usedShouldn't we deprecate the plugin or something first? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlns:deploy and plugins
On Thu, 08 Jul 2004 22:05:45 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > > I think we can ditch it in 1.0 though - a fleeting message in RC4 was > enough :) > Jason was going to relegate release to the sandbox as incomplete last > year, but we kept it around because some of the java code is being > reused elsewhere. Maybe its time to shift the java code and dump the > release plugin? > > I don't know if anyone is using it... I'm all for putting the java code where its most usedShouldn't we deprecate the plugin or something first? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlns:deploy and plugins
its only there as a sanity check - sure. I'd much prefer we keep things clean, otherwise we end up with cruft everywhere. Yeah, but it makes for a less confusing experience when someone installs RC4/1.0 over the top of something older. I think we can ditch it in 1.0 though - a fleeting message in RC4 was enough :) release From what I can see in plugin.jelly, it's just using which I think we should change over. Jason was going to relegate release to the sandbox as incomplete last year, but we kept it around because some of the java code is being reused elsewhere. Maybe its time to shift the java code and dump the release plugin? I don't know if anyone is using it... I think it uses deploy:copy-deps, so that would need to be changed first? I can't see where it uses this tag. Can you point it out?? No, I was wrong on that. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlns:deploy and plugins
On Thu, 8 Jul 2004 21:47:58 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > Quoting Dion Gillard <[EMAIL PROTECTED]>: > > > I think we can now remove the deploy namespace from: > > > > artifact > > no, it contains the old deploy tag library Woops. > > dist > > jar > > its only there as a sanity check - sure. I'd much prefer we keep things clean, otherwise we end up with cruft everywhere. > > release >From what I can see in plugin.jelly, it's just using I think it uses deploy:copy-deps, so that would need to be changed first? I can't see where it uses this tag. Can you point it out?? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlns:deploy and plugins
Quoting Dion Gillard <[EMAIL PROTECTED]>: > I think we can now remove the deploy namespace from: > > artifact no, it contains the old deploy tag library > dist > jar its only there as a sanity check - sure > release I think it uses deploy:copy-deps, so that would need to be changed first? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
