Thomas Rabaix wrote:
> Looks like the lexer are duplicated with PHP_CodeSniffer ? Am I wrong ?
> 
> Are you trying to build a specific "symfony" environment for continuous 
> integration (.... sismo ...) ?

No, Sismo does not depend on Lime or anything else for that matter. 
Sismo works with whatever language and tool you use. It is totally agnostic.

Fabien

> 
> On Fri, Jul 31, 2009 at 3:03 PM, Marijn Huizendveld 
> <[email protected] <mailto:[email protected]>> wrote:
> 
> 
>     Will Lime also be released as a Symfony Component?
> 
>     Kind regards,
> 
>     Marijn
> 
>     On Jul 31, 2009, at 2:53 PM, Fabien Potencier wrote:
> 
>      >
>      >
>      > weaverryan wrote:
>      >> Hey guys-
>      >>
>      >> Will Symfony 2 continue using Lime or will there be a shift to
>      >> phpunit? I always like to do things the "symfony" way and for
>     our big
>      >> project I just want to make sure the Lime way isn't about to change
>      >> in
>      >> the future.
>      >
>      > Switching to PHPUnit would be too costly, so we will stick with lime.
>      > Bernhard is working on Lime 2, which will be much better than lime
>      > 1. It
>      > will also have a compatibility layer, so that the old tests will
>     still
>      > work as expected. You can have a look at the 2.0-experimental branch
>      > if
>      > you want
>      > (http://svn.symfony-project.org/tools/lime/branches/2.0-
>      > experimental/).
>      >
>      > Fabien
>      >
>      >>
>      >> Thanks!
>      >>>
>      >>
>      >
>      > >
> 
> 
> 
> 
> 
> 
> -- 
> Thomas Rabaix
> http://rabaix.net
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to