Sounds good to me.
I'd like to take a look the hashCode plugin. I could actually use that
one.
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
> Sent: Monday, August 29, 2005 3:22 PM
> To: dev_at_jaxb.dev.java.net; lexi_at_dev.java.net;
> sallan1000_at_aol.com; dev_at_jaxb2-commons.dev.java.net
> Subject: jaxb2-commons
>
>
>
> I just created https://jaxb2-commons.dev.java.net/ as discussed with
> Lexi. This project aims to collect/host plugins and utility code that
> people write that are too small to merit its own project. So
> in a sense
> it works like a sandbox/incubator.
>
> This includes runtime utilities like our FilterList, or
> JAXBIterator, or
> small plugins like hashCode/equals plugin, toString plugin,
> EJB3 plugin
> that Scott Allan wrote, and etc.
>
>
> Before I start moving contents, I think we should discuss and
> decide the
> repository structure.
>
> Based on my experience with jakarta-commons-sandbox and stax-utils
> project, it seems to me that allowing each component owner to own its
> directory (like below) works better than ...
>
> jaxb2-commons
> +- pluginX
> | +- src
> | +- test
> | +- whatever
> +- pluginY
> | +- src
> | +- test
> | +- whatever
> +- utilityZ
> +- src
> ...
>
> ... having a single source module and put all the source code in one
> directory:
>
> jaxb2-commons
> +- src
> +- test
> +- doc
> ...
>
> This allows individual component owner to choose their own style in
> their own plugin (like someone can use Maven while others are
> using Ant,
> etc.) Plugins tend to have differing maturity, so having this
> separation
> would also help users deciding which one to use, etc.
>
> Any thoughts?
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com
>
_____
<< ella for Spam Control >> has removed 26231 Spam messages and set
aside 2 Newsletters for me
You can use it too - and it's FREE! www.ellaforspam.com