Define binary tarball layout
----------------------------
Key: QI-315
URL: http://issues.ops4j.org/browse/QI-315
Project: Qi4j
Issue Type: Sub-task
Reporter: Niclas Hedhman
The binary tarball should be optimized for users' needs and not as a result of
convention or simple implementation on our side.
Some discussion has taken place on the mailing list, which tend to favor that
modules are somewhat preserved in the distribution, but aggregated enough for
convenience of use. Current suggested layout (living document and up for
suggested alternations);
{code}
$INST/
bin/
install-idea-plugin(.bat)
docs/
<are we starting with non-sitevision documentation??>
javadocs/
core/
<each core part separate, but linked correctly>
// What about Runtime?? should it be included at all?
libraries/
<each library separate, but linked correctly>
extensions/
<each extension separate, but linked correctly>
ide/
idea/
qidea-$VERSION.jar // not really for distro at the moment.
lib/
core/
qi4j-core-api-$VERSION.jar
qi4j-core-spi-$VERSION.jar
qi4j-core-bootstrap-$VERSION.jar
qi4j-core-runtime-$VERSION.jar
qi4j-core-teststupport-$VERSION.jar
libraries/
$LIB/
qi4j-$LIB-$VERSION.jar
<each dependency for such library>
extensions/
$EXT/
qi4j-$EXT-$VERSION.jar
<each dependency for such library>
reports/
cobertura/
<aggregated cobertura report for all>
junit/
<aggregated junit report for all>
samples/
$SAMPLE/
src
pom.xml
pom.xml
src/
<source distro>
tutorials/
$TUT/
src
pom.xml
pom.xml
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
