10000 [3.0] [Bridge] [Swiftmailer] Removed non-existent namespace from composer.json autoload section by paradajozsef · Pull Request #17337 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[3.0] [Bridge] [Swiftmailer] Removed non-existent namespace from composer.json autoload section #17337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

paradajozsef
Copy link
Contributor
Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a

After PR #13046 Symfony\Bridge\Swiftmailer\ ns not exists.

@Tobion
Copy link
Contributor
Tobion commented Jan 12, 2016

👍 should be merged in 3.0

Status: Reviewed

@fabpot
Copy link
Member
fabpot commented Jan 12, 2016

Thank you @paradajozsef.

fabpot added a commit that referenced this pull request Jan 12, 2016
…ace from composer.json autoload section (paradajozsef)

This PR was submitted for the master branch but it was merged into the 3.0 branch instead (closes #17337).

Discussion
----------

[3.0] [Bridge] [Swiftmailer] Removed non-existent namespace from composer.json autoload section

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

After PR #13046 Symfony\Bridge\Swiftmailer\ ns not exists.

Commits
-------

ecf4591 Removed non-existent directory from composer autoload
@fabpot fabpot closed this 6D91 Jan 12, 2016
@paradajozsef paradajozsef deleted the remove-swm-from-comp branch January 12, 2016 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0