On 01/17/2011 09:21 AM, Jordi Boggiano wrote:
On Mon, Jan 17, 2011 at 8:09 AM, Fabien Potencier
Agreed, but then it should be Symfony\Bundle\Framework\FrameworkBundle
(last one being the bundle class), because its not
Component\FinderComponent, so repeating bundle all over the place in
the namespace doesn't make sense imo.
+1
On 01/17/2011 05:06 AM, Jeremy Mikola wrote:
> I don't support renaming src/ to bundles/, as I think "src" is both
> more descriptive for general developers of many languages/frameworks.
> Once a developer reads about Symfony2, he'll learn the "everything is
> a bundle" mantra, and the "src/" name will still make sense IMO.
> Also, four less characters in a top-level name will be much
> appreciated when we're typing this in our terminals.
+1
On 01/17/2011 05:06 AM, Jeremy Mikola wrote:
> Lastly, I suppose I understand why some folks might use vendor/ to
> store all of their external libraries (e.g. git submodules, svn
> exports), but in my experience with OpenSky, we only threw in
> stand-alone vendor code there. Stuff like Symfony2, Doctrine, Zend,
> swiftmailer, Twig and the like. Any third-party bundles we used went
> under src/Bundles, which I now expect would be src/Company and sit
> right next to our own bundles in src/OpenSky.
The suggestion is to keep third-party bundles in /vendor/VendorName
rather than in the src/ directory at all.
Nils
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
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
