FAQ » History » Revision 6
Revision 5 (Henning Blohm, 08.02.2015 17:35) → Revision 6/7 (Henning Blohm, 08.02.2015 20:10)
h1. FAQ
h2. Development
h3. Why is it not possible to arm my z2 project in Eclipse?
If the Eclipse project does not show a little Z icon as decoration, it is not even recognized as a z2 project. To become a z2 project, the specific entry
<pre><code class="xml">
<classpathentry kind="con" path="ZFabrik.Eclipsoid"/>
</code></pre>
has to be present in the *.classpath* file that is located in the root folder of the project. The right-click context menu of the Eclipsoid plugin offers the option to "Transform into z2 project", which is nothing but modifying the *.classpath* file accordingly.
Arming a z2 module (note that z2 _modules_ are simply eclipse _projects_) is nothing but adding a file called *LOCAL* into its root folder. The Eclipsoid plugin will show the Z decoration with a little green halo for armed projects and without otherwise.
h3. Why are my z2 development projects not picked up by z2?
By definition, all modules recognized by z2 are loaded from _component repositories_. One particular implementation, the so-called _dev repository_ is particularly useful for development scenarios. In particular this implementation
* ... can be configured to discover modules in a number of local file system locations,
* ... loads modules with high priority (and hence overlays remote versions of modules of the same name),
* ... is safe to use during development as it will snapshot module versions at synchronization time.
In order to work the following prerequisites must be met:
h4. The dev repository must be running.
Make sure to list the target state *org.z2env.dev.shared/ready* when running z2.
You should indeed see logging output like this
<pre>
INFO: Starting component repo component:org.z2env.dev.repo/devRepo,repo:org.z2env.dev.repo/devRepo,prio:750,mode:strict, workspaces (1): [/home/hb/org.z2env.svn]
</pre>
h4. Your projects must be located one or two levels deep on the search path of the dev repo
By default the dev repository will search for armed modules (see [[FAQ#Why are my z2 development projects not picked up by z2?|Why are my z2 development projects not picked up by z2?]]) in the parent folder of the z2 <home> location (i.e. modules will be siblings or children of siblings of the <home> folder). Using the system property
*org.z2env.dev.local.workspace*
you can specify a comma-separated list of file system locations to use instead. During start, the dev repository will list the locations ("workspaces") it will search on the console.