On 22 Feb 07, at 10:12 AM 22 Feb 07, Joakim Erdfelt wrote:
I have plans to make that entire stack isolated and unaffected by
reporting / dao / web / indexing / etc...
As well as making an import applet utilize the conversion routines too
(want this to be lightweight too).
Good, then let's move it out of archiva.
The branch currently has the conversion routines separated out for the
archiva-cli module (bad name).
As seen here: http://joakim.erdfelt.com/maven/archiva-branch-
multimodule.png
To use the existing conversion routines via command line, you have the
following deps...
archiva-cli
archiva-converter
archiva-discoverer
archiva-common
I plan on splitting out the consumer and builder portions of common
into
a new lib, making the dependencies for conversion even lighter.
I would be happy to be in control of the conversion routines / client.
I would like them separated please, there is no need for them to be
in archiva at all.
Jason.
- Joakim
Jason van Zyl wrote:
Hi,
There are a couple more complaints about some m1 conversions and with
your large refactoring planned I would like to separate out the
conversion tools. I would like to work on the conversion tools to
make
the conversion process better which is essentially running as a
separate process now anyway. I'm not planning on ever working on
Archiva but the conversion tools need to be fixed.
Can we please move those out into share and you guys can incorporate
them from there in any fashion and so that I can reuse them.
Conversion is really an entirely separate tool chain and should be
separated.
Thanks,
Jason.
