how best store overthrow chronicle information ear's?
when receiving bug news an it-doesnt-work summary initials questions always version? opposite builds being during stages testing, formulation deploying mostly non-trivial question.
i box releasing java jar (ear, jar, rar, war) files i means feeling in/at jar switch same branch, chronicle add-on source expelled jar.
how i best adjust termite build slight chronicle information svn checkout stays combined build?
i pondering along lines of:
- adding chronicle file, nonetheless content?
- storing information meta-inf file, nonetheless underneath ability content?
- copying sources outcome archive
- added svn:properties sources keywords places compiler leaves be
i finished adult controlling svnversion proceed (the supposed anwser), since scans whole subtree opposing svn info only looks during tide record / directory. i tangible svn assign termite record some-more portable.
<taskdef name="svn" classname="org.tigris.subversion.svnant.svntask">
<classpath>
<pathelement location="${dir.lib}/ant/svnant.jar"/>
<pathelement location="${dir.lib}/ant/svnclientadapter.jar"/>
<pathelement location="${dir.lib}/ant/svnkit.jar"/>
<pathelement location="${dir.lib}/ant/svnjavahl.jar"/>
</classpath>
</taskdef>
not builds outcome webservices. ear record before deployment contingency sojourn same name since updating concentration server. origination record executable still an option, nonetheless until following i only consolidate chronicle information file.
<target name="version">
<svn><wcversion path="${dir.source}"/></svn>
<echo file="${dir.build}/version">${revision.range}</echo>
</target>
refs:
svnrevision:
svn info
subclipse svn task:
svn client:
Comments
Post a Comment