- Having well defined variables is more readable than configuring
everything in MAVEN_CUSTOM_OPTS
- Do not provide a default admin password value : people deploying on
Heroku for testing or demonstration purpose would likely forget to
customize this password, which would be a security flaw
- reduce Heroku specific impacts on existing pom.xml
This eases up suggested initatives from http://mantis.tokeek.de/view.php?id=649
Allows longer term also to store translation maps for the htroot files
in standardized/reuseable xliff format ( http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html ).
+ added test case creating and comparing xliff file with internal custom prop file.
(currently the introduced class is not used in core code)
This allows to use libbuild/pom as main maven project to build all needed
libs to compile and run YaCy, including YaCy itself.
Furthermore, maven is well supported by Netbeans IDE so we can discontinue
to maintaine Netbeans IDE specific project settings (in directory nbproject,
which lack config for debug anyway, nbproject can be deleted and NB will
compile YaCy via maven).
Additionally adjusted pom's project name to match the name in the repository.
to create the release archive only if profile is activated (speeding up normal compilation)
- bind install of the 2 jar's not available in repository to validate phase (was clean)
to automatically add these to local repository (with disadvantage it's done every time)
reger