[#255] - Framework Dependency Handling (Fix #115)
- Closed
- 12 Dec 2013
- Medium
- Build: master
- # 255
- Diff
- joomla:JFWdeps
- Success default The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Per #115, this lists out all packages for the Framework we're actually depending on. Since we're using so much of it, Composer is still installing the full Framework, but this better gauges what we are actually using. I've also removed the use of the Framework's Event and Log packages (Event was actually unused totally aside from loading the dispatcher and Log replaced with our using Monolog).
Other dependencies are updated as well with the composer update
drmmr763
- 
Isn't DI a separate package ?Filesystem is used in the CLI app, but that could (or should) be refactored to use DirectoryIterators.
The with() method lives in the PHP package.
Otherwise: Big
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2013-12-12 13:43:34 |
I think we need to figure out what to do if we need a dev-master version of any of the framework packages - and I'm pretty sure we will...
Until then, this will look good when we release our 1.0 
I switched the joomla/github package to dev-master, did a clean install with the following result:
- Installing joomla/framework (1.0)
Loading from cache
- Installing joomla/joomla-framework (dev-master 1e5c9a1)
Cloning 1e5c9a192167d285da30b705157ffa7eb0649811
autoload_namespaces.php
'Joomla' =>
array(
$baseDir . '/src', $vendorDir . '/joomla/framework/src',
$vendorDir . '/joomla/joomla-framework/src'),
Files
├── vendor
│ ├── joomla
│ │ ├── framework
│ │ └── joomla-framework
pretty messy I guess...
Hmm @eddieajau or @dongilbert can comment on this? ;)
Composer dependency resolution within our packages is messed up somewhere. Should be fixed soon with the release of 1.1. We've added some new features and fixed some things. I think it warrants an update.