...@lists.oxidforge.org] on behalf of Björn Schotte
> [bjoern.scho...@mayflower.de]
> Sent: Monday, May 19, 2014 11:53 AM
> To: dev-general@lists.oxidforge.org
> Subject: Re: [oxid-dev-general] Proposed composer as module dependency
> management tool
>
> Hi,
>
> On 19.0
ct: Re: [oxid-dev-general] Proposed composer as module dependency
management tool
Hi,
On 19.05.14 11:44, Marco Steinhaeuser wrote:
> I'd propose to discuss it rather here in this mailing list (maybe better
> without the signature ^^):
Why not discuss it in public on GitHub? T
Hi,
On 19.05.14 11:44, Marco Steinhaeuser wrote:
> I'd propose to discuss it rather here in this mailing list (maybe better
> without the signature ^^):
Why not discuss it in public on GitHub? That's what GitHub is for:
preparing a Pull Request which references the tracker id.
I just wanted to
ented.
Cheers
Marco
From: dev-general-boun...@lists.oxidforge.org
[dev-general-boun...@lists.oxidforge.org] on behalf of Björn Schotte
[bjoern.scho...@mayflower.de]
Sent: Monday, May 19, 2014 11:17 AM
To: dev-general@lists.oxidforge.org
Subject: Re: [oxid-dev-general]
Hi Dirk,
On 19.05.14 10:37, Dirk Blößl | superReal GmbH wrote:
> Any ideas on how to proceed? Any comments from other users? ;-)
Further comments on https://github.com/OXID-eSales/oxideshop_ce/issues/140
inviting kermit etc. into the discussion.
Best, Björn
--
Mayflower GmbH
Hi Björn,
we are already using composer with OXID for about 2 years now and also made the
changes to the composer-installers repo.
I’d love to see a deeper integration of composer in the OXID core, so we should
talk about how it could work.
I already tried to set up activation via composer hook
Hi folks,
I just proposed the usage of composer for managing modules:
https://github.com/OXID-eSales/oxideshop_ce/issues/140
It requires the usage of composer/installers which contain install path
maps for oxid modules and themes.
Not sure if I should create a PR, though. Currently exploring
au
