Hi Ken,
I am far from fluent in eclipse and I am still struggling to get
eclipse to return me the manifest when we build with the incremental
builder. If you can figure it out that would be great we have already
spent quite a few hours trying to understand why the eclipse class
loader does not return the manifest when we run in debug mode after a
incremental build I know that technically there is no jar but the
package is there and the call loader should return the meta info for it.
What we have working is in ant we build out own custom manifest and
push it into the application jar. It is quite easy to do with ant and
svnant enables you to retrieve the svn version number form the
working copy you are building against.
Pierre
<jar destfile="${build.root}/${project.name}.woa/Contents/Resources/
Java/${project.name}.jar" update="yes" index="no" manifest="$
{build.classes}/META-INF/MANIFEST.MF" />
<target name="global.manifest.application" depends="global.properties">
<echo message="-------------------------------------" />
<echo message="Building Manifest for ${project.name}" />
<echo message="-------------------------------------" />
<mkdir dir="${build.classes}/META-INF" />
<manifest file="${build.classes}/META-INF/MANIFEST.MF">
<attribute name="Built-By" value="${user.name}" />
<attribute name="Specification-Title" value="sPearCat" />
<attribute name="Specification-Version" value="${version.major}.$
{version.minor}" />
<attribute name="Specification-Vendor" value="sPearWay Ltd." />
<attribute name="Package-Title" value="${project.name}" />
<attribute name="Package-Version" value="${version.major}.$
{version.minor}.${version.patch}" />
<attribute name="Package-Vendor" value="sPearWay Ltd." />
<attribute name="Implementation-Version" value="${version.major}.$
{version.minor}.${version.patch}" />
<attribute name="Implementation-Vendor" value="sPearWay Ltd." />
<attribute name="Version-Major" value="${version.major}" />
<attribute name="Version-Minor" value="${version.minor}" />
<attribute name="Version-Patch" value="${version.patch}" />
<attribute name="Version-Build" value="${build.number}" />
<attribute name="Version-Build-Date" value="${build.date}" />
<attribute name="Main-Class" value="${project.principal.class}" />
</manifest>
</target>
On 6-Nov-06, at 10:09 AM, Ken Anderson wrote:
> Pierre,
>
> I would like to get svn revision numbers into my builds, but I
> don't speak "Eclipse" sufficiently yet. Can you give me a few
> pointers, like where the section below should reside and how to
> integrate svnant?
>
> Thanks much,
> Ken
>
> On Nov 6, 2006, at 11:32 AM, Pierre Frisch wrote:
>
>> Hi Mike,
>>
>> If you accept the dependency on svnant you can to it by adding this:
>>
>> <typedef resource="org/tigris/subversion/svnant/svnantlib.xml" />
>> <svn>
>> <wcVersion path="${project.dir}" prefix="svn." />
>> </svn>
>> <property name="build.number" value="${svn.revision.max}" />
>>
>> This is the way I do it with my projects.
>>
>> Pierre
>>
>> On 6-Nov-06, at 8:16 AM, Mike Schrag wrote:
>>
>>> Yeah, I thought I fixed the version # problem last night, but
>>> obviously i just broke it in a different way ... Fixing it now.
>>>
>>> On Nov 6, 2006, at 10:59 AM, Jake Fisher wrote:
>>>
>>>> I just tried to update from http://www.mdimension.com/~wolips/
>>>> update/
>>>> and found that the last build seems to have messed up a bit. The
>>>> last
>>>> build build number is listed as 2.0.0..jar rather than
>>>> 2.0.0.xxxx.jar.
>>>> Can someone fire off a new build when they get a chance?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> ~jake
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Mon Nov 06 2006 - 14:30:16 EST