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 i
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
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 m
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 san
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?
-
I think we can now remove the deploy namespace from:
artifact
dist
jar
release
True?
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
