Yeah, +1 for both Freeman －－－－－－－－－－－－－ Freeman Fang
FuseSource Email:[email protected] Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-8-23, at 上午7:55, Jamie G. wrote: > I like the bundle:classes concept as described - I've been in > situations where such a command would have been useful. > > The bundle:find-class concept sounds interesting too -- I can imagine > a developer wanting to know what bundles export a given class in the > running environment, then decide upon what range their import should > have. > > Depending on the feed back for the idea, and the resulting additional > ideas perhaps you could enter a 'new feature' jira entry for each? > > Cheers, > Jamie > > On Wed, Aug 22, 2012 at 3:25 PM, Jean-Baptiste Onofré <[email protected]> > wrote: >> As already discussed, it looks good to me (bundle:classes seems fine). >> >> Regards >> JB >> >> >> On 08/22/2012 06:46 PM, Heath Kesler wrote: >>> >>> I was thinking about adding a command or adding options to an existing >>> command that would allow the user to display a list of classes in a bundle. >>> This will allow users to see what classes are actually in a bundle, not what >>> they think should be in the bundle. Assuming can be a bad thing ;-) >>> >>> I am looking for feedback on the idea, and if this should be a new command >>> or a option on an existing command. I was thinking it should be a new >>> command but looking to the dev group for suggestions. >>> >>> Cheers >>> Heath >>> >> >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com
