On 27/06/2009, at 3:44 PM, Lachlan Deck wrote:
> While we're enabling/disabling features we still seem to be hanging
> onto 'WOLips Maven' which I believe confuses users as it should be
> called 'WOLips Maven 1' at the very least.
>
> Does anyone use 'WOLips Maven' intentionally when installing WOLips?
> i.e, does anyone use Maven 1? Will anyone object to this going away?
>
> I've never heard any mention of anyone using it in the time I've
> been on this list.
>
> (To avoid confusion for anyone responding: 'WOLips Apple Maven
> Integration' requires m2eclipse only and both are for maven 2)
>
> My vote is that if nobody responds that they actually use it then
> it's removed.
The intention is to give WOLips a good spring clean once we have
nightly running on 3.5, removing a lot of deprecated and/or duplicated
code. Finishing off the integration of the new component wizard. Trim
the fat basically.
So yes, I am all for getting rid of anything like this that is just
legacy clutter that nobody actually uses anymore because they moved on
to something else.
I would like to see a show of hands of who actually uses the apple
maven plugin also. My understanding was that plugin was originally to
provide a way to integrate with an ADC protected maven nightly build
repo that never really happened.
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Sat Jun 27 2009 - 09:03:59 EDT