[FLOW3-general] Getting started (again)

[Sebastian Kurfürst]

Hey Christian,

> My primary goal is a running setup to execute the unit tests - via cli
> and browser. I'd like to hack on minor things and push to the
> subprojects of a distribution.
The browser-based test runner is deprecated and will most likely be removed.

> Questions:
> - Which distribution should I clone (to get latest development versions
> of flow3)? FLOW3 or Phoenix? It seems the testing package is not
> included in FLOW3 distribution. How do I get it and activate it?
I suggest that you use http://www.wwwision.de/githelper/ and select
Distribution/FLOW3. This will give you the base distribution of FLOW3,
ready to run all FLOW3 unit tests. After executing the commands shown
you will have a fully running FLOW3 instance.

Unit tests require that you have an up-to-date PHPUnit Installation via
PEAR. If you have the "phpunit" command available on your CLI, chances
are good that you are ready to go :-)

Then, to run unit tests, you can do the following (from inside the base
directory), via CLI:
phpunit -c Build/Common/PhpUnit/UnitTests.xml
Packages/Framework/FLOW3/Tests/Unit


> - Are the documents at [1] and [2] still fully valid?
Yeah think so.

> - How are the distributions interweaved with the subprojects? I know
> that hudson always does some 'raised pointer' things, but if I clone one
> of the distributions and checkout the master of flow3 package, is this
> really 'latest version'? What exactly is this pointer thing in hudson
> and how do I work with it? How do I update everything to latest head?

I do the following:

git submodule foreach 'git checkout master; git fetch; git reset --hard
origin/master'

 however this will ERASE ALL CHANGES which are either uncommitted OR
committed in master branch.

The Testing package has been removed.

> outdated (like the Welcome package with it's cli hints). This is really
> complicated for a beginner (with developer aims) and should imho be
> structured better ... A simple overview page, explaining structures and
> resources and 'where to look if you want to do xy', 'how to start' and
> 'we have this list of maintained web resources' would be great! I'm
> currently stuck at this point, don't know which web resources are valid
> and how all this works together. Take old things offline again, so that
> they do not confuse users. Could the documentation be tagged along with
> the flow3 version ('this docu is valid for alpha13, this one for HEAD')?
You are right. We are right now heavily working on stabilizing FLOW3
ready for first beta, and then we will do a sprint heavily focussing on
these documentation issues.

Greets,
Sebastian