[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836696#comment-16836696
]
Davide Grandi commented on DERBY-6645:
--------------------------------------
Upon suggestion of [~rhillegas] I've attached a pdf map of current (revision
1859039) trunk's build.xml (build.xml.dot.pdf).
The map has been generated by a short XSLT stylesheet that navigate build.xml
archive spitting out a "build.xml.dot" file.
With Graphviz this dot file is transformed in a map connecting Ant targets with
their prerequisites (with an index on the arc).
The arcs are drawn in bold for antcall dependencies and in red for exec ones.
I've attached a zipped script (for windows and linux - build2dot.zip) that run
the XSLT stylesheet, with 2 samples : one for JTOpen and one for Derby.
To run you should :
- set the JAVA_HOME env var
- launch it with
build2dot.sh build.xml
- then run Graphviz with
dot -Tpdf -O build.xml.dot
- view the generated build.xml.dot.pdf file with, e.g., "evince"
evince build.xml.dot.pdf
Best regards,
Davide Grandi
> Switch to Maven for building Apache Derby
> -----------------------------------------
>
> Key: DERBY-6645
> URL: https://issues.apache.org/jira/browse/DERBY-6645
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.10.2.0
> Reporter: Moritz Hoffmann
> Priority: Major
> Attachments: DERBY-6645_v1.patch, build.xml.dot.pdf, build2dot.zip
>
>
> For a new user building Derby is very hard. It does not follow established
> Java project structures and requires a lot of prior knowledge. Also the
> documentation is rather short. Especially running the tests is non-intuitive
> at the beginning. Thus, I propose that Derby switches to building using Maven
> and restructures its components in a cleaner way. Testing should be revised
> to produce reproducible results. This would make development and testing much
> easier and more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
