camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: [DISCUSS - Camel 2.0] - Move not used components to a sandbox area
Date Mon, 01 Jun 2009 08:52:39 GMT
Hi Willem

Thanks for the help.

I have moved the components to the sandbox. Their new home is here:
https://svn.apache.org/repos/asf/camel/sandbox/

And I have changed the various pom.xml files in camel to not include
these components.
I cleaned my local m2 repo and did a full rebuild / install. It
completed on my laptop.

But let me know if you have any problems after upgrading from SVN.



On Sun, May 31, 2009 at 9:41 AM, Willem Jiang <willem.jiang@gmail.com> wrote:
> Hi Claus
>
> You can create the directory yourself with the svn command line.
> svn mkdir https://svn.apache.org/repos/asf/camel/sandbox
> The you can check out this direct in you local work space and add the
> files that you want.
> If you want to move the below components into the sandbox, please use
> the  "svn move" command
> In this way, we can trace back the change histories from the module in
> the sandbox
>
> BTW, please remember to remove the assembly descriptions of this
> components in apache-camel module.
>
> Willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> To sum up the list of components to be moved to a sandbox area are:
>> - camel-activemq-web
>> - camel-supercsv
>> - camel-swing
>> - camel-uface
>> - camel-hamcrest
>> - camel-jhc
>>
>> Who can help me setup the sandbox in the SVN and move the components?
>>
>>
>>
>>
>> On Tue, May 19, 2009 at 10:17 AM, James Strachan
>> <james.strachan@gmail.com> wrote:
>>> Damn, I forgot how much crappy unfinished code I'd written - great
>>> catch Claus :)
>>>
>>> 2009/5/18 Claus Ibsen <claus.ibsen@gmail.com>:
>>>> Hi
>>>>
>>>> In Camel 2.0 we have several components that are not used, abandoned
>>>> and/or in a questionable quality. We have touched this issue before
>>>> and kinda agreed to move them to a sandbox area in SVN. Maybe using a
>>>> different name.
>>> Having a sandbox project in subversion (say at
>>> https://svn.apache.org/repos/asf/camel/sandbox/) sounds like a good
>>> idea (like Commons at Apache or Mojo at codehaus etc).
>>>
>>> Leaving the sandbox as a fully working maven multi-project (so folks
>>> can build/run/test the sandbox components) can act as a little
>>> experimentation area where folks can drop in all kinds of wacky ideas
>>> and experiments until they blossom into a fully formed component we
>>> can add to the main trunk?
>>>
>>>
>>>
>>>> I have compiled a list for suggested components to be moved:
>>>> =================
>>>>
>>>> camel-activemq-web
>>>> - not documented
>>>> - not used
>>>> - Kinda experiment code from James
>>> I needed this for testing of Camel, ActiveMQ and camel-web; but since
>>> it doesn't have any actual test cases I guess we can zap it :)
>>>
>>>
>>>> camel-spring-javaconfig
>>>> - depends on Spring JavaConfig SNAPSHOT
>>>> - Spring JavaConfig is kinda @deprecated as its moved to be part of
>>>> Spring 3.0 core
>>>> - not documented
>>>> - not used
>>>> - Kinda experiment code from James
>>>> - remove the camel-example-spring-javaconfig also
>>> As Willem said - since JavaConfig is part of Spring 3, we should
>>> absolutely have JavaConfig support out of the box
>>>
>>>
>>>> camel-supercsv
>>>> - has not been active maintained for a long time
>>>> - not documented
>>>> - not used
>>>> - and we have 2-3 other CSV components (flatpack, csv, bindy)
>>>>
>>>>
>>>> camel-swing
>>>> - has not been active maintained for a long time
>>>> - not documented
>>>> - not used
>>>> - confusing concept what you can integrate with Swing.
>>>> - (Kinda experiment code from James)
>>>>
>>>>
>>>> camel-uface
>>>> - has not been active maintained for a long time
>>>> - not documented
>>>> - not used
>>>> - confusing concept what you can integrate with Swing / UFace.
>>>> - Kinda experiment code from James
>>> Agreed with all the others above.
>>>
>>>
>>>
>>>> And the next two is more up for debate
>>>> ===================
>>>>
>>>> camel-testng
>>>> - has not been active maintained for a long time
>>>> - not documented
>>>> - not used
>>>> - testng is loosing the battle against JUnit 4.x
>>> Yeah, its still of limited use
>>>
>>>
>>>> camel-hamcrest
>>>> - has not been active maintained for a long time
>>>> - not documented
>>>> - not used
>>>> - we do not used it internally for unit testing either
>>> Agreed. I hoped to round out this library one day to a bunch more
>>> useful assertions, but have never got the chance.
>>>
>>> Sorry! :)
>>>
>>> --
>>> James
>>> -------
>>> http://macstrac.blogspot.com/
>>>
>>> Open Source Integration
>>> http://fusesource.com/
>>>
>>
>>
>>
>
>



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Mime
View raw message