Hi there,
See the included CHANGES.txt file for details on release contents and latest
changes. The release was made using the Maven2 release plugin, according to
I have downloaded and unpacked the archive...checked the md5
sum...ok...tried to build via "mvn install" works fine...
Some notes:
Inside the archive there are artifacts from a mvn release:prepare
run...like release.properties etc. ?
Question:
Why is the usual "assembly" part of a profile instead of the usual
lifecylce so you can simply call "mvn package" to produce a zip archive...
Why is the assembly.xml descriptor not in src/main/assembly folder ?
On the other hand the version entries of the following plugin's are not
finalzed (no version given):
maven-deploy-plugin (defined by apache parent)
maven-javadoc-plugin (define by apache parent)
maven-site-plugin (defined by apache parent)
maven-assembly-plugin !
maven-jxr-plugin !
maven-pmd-plugin !
maven-surefire-report-plugin !
Could someone check this ?
disapproval. The vote passes if at least three binding +1 votes are cast.
[ ] +1 Release the packages as Apache Tika 0.5.
[ ] -1 Do not release the packages because...
[-1]
- Missing plugin fixing of the versions
- May be moving the assembly.xml descriptor to the "default" folder
src/main/assembly (based on the doc of the assembly plugin..)
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
