Hi, On Sun, Nov 15, 2009 at 6:56 PM, Karl Heinz Marbaise <[email protected]> wrote: > 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...
We only need to create the release package when cutting a release candidate. There's little benefit of building the release package when you've already downloaded it. The normal package lifecycle is for building the sources and packaging the resulting binaries. > Why is the assembly.xml descriptor not in src/main/assembly folder ? I dislike having folders with just a single file in them, and there does not seem to be any benefit (less configuration, better IDE/build integration, etc.) to putting the file in src/main/assembly. Note that for Tika 0.6 we may want to look at using the new Apache source release assembly descriptor that was recently released by Maven, see http://markmail.org/message/aeblw44n6qam23lp. > 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) There's no need to specify these plugin versions since they're inherited from the parent. > maven-assembly-plugin ! > maven-jxr-plugin ! > maven-pmd-plugin ! > maven-surefire-report-plugin ! Yep, we probably should fix these plugin versions. > [-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..) Do you see these as blockers for the release? I wouldn't mind if Chris wanted to do a second release candidate to fix these issues, but I'd be equally happy to see these issues fixed in time for Tika 0.6 as neither seems to be too critical. BR, Jukka Zitting
