Ok, full steam ahead then...
> Make SourceSet an interface.
will do.
> Invent an AbstractFile interface that will be used everywhere instead
> of File.
already done.
> Then make FileSourceSet and FileFile implementation for trivial use,
> and IDEASourceSet and IDEAFile for your plugin.
>
> I
2 7:01 am
Subject: Re: idea plugin, was: [Xdoclet-devel] XDoclet 2.0
> > If it's functional but maybe a bit annoying then it's ok to
> commit it
> > right after the beta 1 release.
>
> ok, willdo.
>
> > Re the file interface: that's good idea. We n
> If it's functional but maybe a bit annoying then it's ok to commit it
> right after the beta 1 release.
ok, willdo.
> Re the file interface: that's good idea. We need it. It's actually
> somehow an existing FR. To implement the
> provide-an-xdoclet-facade-component effectively we should provid
I'm
> assuming
> Ara/Aslak will have something to say here?), or (b) if it will even
> fix my
> problem but I'll raise the issue now to ask.
>
> cheers
> dim
>
> - Original Message -
> From: "Mathias Bogaert" <[EMAIL PROTECTED]>
I'm assuming
Ara/Aslak will have something to say here?), or (b) if it will even fix my
problem but I'll raise the issue now to ask.
cheers
dim
- Original Message -
From: "Mathias Bogaert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, Sep
Hi guys,
I've written my thoughts on XDoclet 2.0 in the design doc. It it available at (the
latest docs):
http://users.pandora.be/ees/xdoclet/development/design.html
Could you ALL have a look at it, AND comment on it?
If we all agree on this stuff, we can begin thinking about APIs and concrete