While developing the data module I recognized that there are some
"missing"
API methods in the core system. When we depend only on "released"
libraries
in the maven repository this might be very painful.
As Nicolas pointed out, you will be able to use current snapshots or
patched versions. Currently the most of the module developers are
core devs too and can commit to the trunk.
If this is not the case, a module developer will make a JIRA task.
Since all the devs are very interested in the progress of the module
development, I think those issues will get handled with an extra
priority. Esspecially if you attach an applicable patch to the issue,
it will bet done very quickly.
In addition all the module and core developers would get write access
to our maven repository, so that they can provide patched versions
any now and then.
I already made a request to get a maven repository outside of of
sourceforge (since the disk space is limited there). It will be
reachable under http://maven.magnolia.info.
On the other hand we could create a master plan and whatever is
missing
afterwards will never come. Then we would have a very stable API
but no
I don't like to loose the flexibility we have currently. I think the
team is still small enough to work agile.
We need to think about such a procedure if the number of hosted
magnolia modules increases a lot.
Philipp
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
