On 14 June 2011 19:46, Matt Benson <[email protected]> wrote: > On Tue, Jun 14, 2011 at 1:38 PM, Simone Tripodi > <[email protected]> wrote: >> Hi all guys, >> thanks a lot for the feedbacks!!! >> Two minor notes: >> >> * code is already available (and rearranged) in sandbox[1], so feel >> free to play with it!!! > > > I know the code is there :) ... that's why I acknowledged the > silliness my reluctance to "get my hands dirty" until after the > component is named/moved. > >> * I like commons-classpath too, anyway the component contains also >> the stuff to scan Classes/Annotations, so 'classpath' would sound too >> restrictive... or not? :P >> > > I can see why you might think so; however it seems to me the > implication of "visit these classes and do X when you find Y" carries > the implication that the classes in question were most likely > discovered by classpath scanning. Does the codebase currently contain > (fluent?) code to directly chain the output of a classpath scan to > such a "class visit"?
How does it relate to the Sandbox Clazz component? Alternatively, if it's not just about class path, perhaps could call it ClassUtils? Just a thought. > Matt > >> I can take care about quickly renaming/repackaging once we decided how >> to call it, thanks in advance!!! >> All the best! >> Simo >> >> [1] https://svn.apache.org/repos/asf/commons/sandbox/meiyo/trunk >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Tue, Jun 14, 2011 at 8:25 PM, Matt Benson <[email protected]> wrote: >>> On Tue, Jun 14, 2011 at 1:17 PM, Gary Gregory <[email protected]> >>> wrote: >>>> On Jun 14, 2011, at 14:15, Matt Benson <[email protected]> wrote: >>>> >>>>> On Tue, Jun 14, 2011 at 9:42 AM, Simone Tripodi >>>>> <[email protected]> wrote: >>>>>> Hi all guys, >>>>>> I invested a little of my spare time on rearranging stuff on Meiyo and >>>>>> put it in a decent condition, what is needed is the following: >>>>>> >>>>>> * involve more people, technical review are more than accepted; feel >>>>>> free to discuss improvement and commit! >>>>>> * take a decision: >>>>>> - merging parts in different existing components; >>>>>> - releasing it as a new component; in this case, we have to >>>>>> promote it as a proper component and we already agreed a new name is >>>>>> needed. >>>>>> >>>>>> WDYT? Many thanks in advance, have a nice day!!! >>>>> >>>>> Can we go ahead and decide the (deliberately bland) name of the >>>>> sandbox component? Obvious (to me) candidates include: >>>>> >>>>> * [scancp] >>>>> * [cpscan] >>>>> * [classpath] >>>>> >>>> Classpath is nice. >>> >>> Actually, continuing to think about this, I am inclined to agree. >>> Though James's response came in while I was composing this :) , I also >>> am thinking that I and probably others have bits of classpath-related >>> code that might complement a general-purpose [classpath] component. >>> >>> Matt >>> >>>> >>>> Gary >>>> >>>>> Are there others? Once this is decided we can set up the >>>>> trunks-sandbox external (and won't need to change it later). It >>>>> sounds silly, but I'd rather have the code in my checkout of >>>>> trunks-sandbox before doing anything serious to it personally. >>>>> >>>>> Matt >>>>> >>>>>> All the best, >>>>>> Simo >>>>>> >>>>>> http://people.apache.org/~simonetripodi/ >>>>>> http://www.99soft.org/ >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
