10000 Remove everything related to the deprecated AcmeDemoBundle by javiereguiluz · Pull Request #212 · sensiolabs/SensioDistributionBundle · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Jan 6, 2020. It is now read-only.

Remove everything related to the deprecated AcmeDemoBundle #212

Closed

Conversation

javiereguiluz
Copy link
Contributor

The context

AcmeDemoBundle is deprecated because of the new SymfonyDemoApplication. This bundle should no longer appear when creating a project with the Symfony Standard Edition (no matter if you use the Symfony Installer or the Composer installation).

The problem

In the past I tried to remove this bundle (see #198). However, when you install Symfony you still get this annoying bundle, so you cannot get a fresh clean Symfony installation.

The solution

I propose to remove the AcmeDemoBundle for once and for all by removing all its files.

Please note that in the Composer/ScriptHandler.php there are two methods called installAcmeDemoBundle() and patchAcmeDemoBundleConfiguration() which I've emptied but left for BC reasons. @stof do you think we could removed these two methods entirely? Thanks.

@fabpot
Copy link
Member
fabpot commented Jun 5, 2015

I don't think we need to keep BC in the ScriptHandler script.

@fabpot
Copy link
Member
fabpot commented Jun 5, 2015

One way to keep BC would be to bump version to 4.0 for the bundle and update the symfony SE to use the new version for all new versions (including 2.3?).

@javiereguiluz
Copy link
Contributor Author

It's great to hear that. I've created two separate pull requests to remove the AcmeDemoBundle from Symfony Standard too:

@stof
Copy link
Contributor
stof commented Jun 11, 2015

If we remove the methods, we indeed need to bump the major version as it is a BC break for anyone using it in their composer.json. but it is fine IMO

@Pierstoval
Copy link

Is it possible to simply throw a "deprecated" error in the composer script that tells the user to remove the methods in his composer.json file?

@stof
Copy link
Contributor
stof commented Jun 11, 2015

@Pierstoval this is a bad idea. Composer turns all PHP errors into exceptions, including the E_USER_DEPRECATED ones, meaning that it would make the composer installation fail if you trigger it in the script handler (and if you trigger it silenced, it will never be reported as the special error handler of Symfony logging all deprecations even silenced is not registered in Composer runs)

@Pierstoval
Copy link

So what is the best solution then? Show the message simply in the output?

@stof
Copy link
Contributor
stof commented Jun 11, 2015

Well, in 3.x of the bundle, the handler should continue to work (for BC reasons). But we could indeed add a message in the output saying it is deprecated (not sure it is worth it as I'm not sure people will read it).
and in 4.0, we should just remove the methods entirely IMO and document the change in the upgrade instructions (it is an easy upgrade)

@Tobion
Copy link
Contributor
Tobion commented Jun 11, 2015

👍 for removing in 4.0. @javiereguiluz so you need to change the branch alias in composer.json

@fabpot
Copy link
Member
fabpot commented Jun 11, 2015

I've bumped the version of the master branch to 4.0.

@fabpot
Copy link
Member
fabpot commented Jun 11, 2015

Thank you @javiereguiluz.

@fabpot fabpot closed this in 97929c0 Jun 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0