Thanks Snjezana. It sounds like you changes will make the 3.0.1
repository have the correct version numbers and soon the 3.1 workspace
will be updated to contain the new version info. I updated my copy of
3.0.1 and didn't see them so I will look for your commit notification.
Carla
Snjezana Sevo-Zenzerovic wrote:
> Carla,
>
> in 3.0.1 I am actually adding additional update version field right
> now and I'll merge those changes into trunk as soon as possible. Since
> the update version will be empty on the trunk, it will be enough to
> rev up minor version.
>
> You can definitely set version_prefix to empty value in 3.1, it is
> already empty in 3.0.1 branch. version_suffix is currently not used,
> but it may be eventually used by sustaining to append patch version or
> something similar.
>
> Thanks,
>
> Snjezana
>
>
> Carla Mott wrote:
>> Thanks. I will verify. This solves the problem for 3.1 but what
>> about the 3.0.1 release? is the minor version 0.1? What is the
>> version_suffix? BTW do we still want the version_prefix to be 'v'? I
>> thought that we are dropping the 'v' for this release. Is that still
>> the case?
>>
>> Thanks,
>> Carla
>>
>> Jennifer Chou wrote:
>>> I just tried this and looks like it works.
>>>
>>> 1. Change top-level pom.xml
>>>
>>> Index: pom.xml
>>> ===================================================================
>>> --- pom.xml (revision 36721)
>>> +++ pom.xml (working copy)
>>> @@ -122,7 +122,7 @@
>>> <abbrev_product_name>glassfish</abbrev_product_name>
>>> <version_prefix>v</version_prefix>
>>> <major_version>3</major_version>
>>> - <minor_version>0</minor_version>
>>> + <minor_version>1</minor_version>
>>> <version_suffix></version_suffix>
>>> <build.id>${user.name}-private</build.id><!-- on Hudson and
>>> RE, this ge
>>> ts replaced by real build ID -->
>>> <jruby-scripting.version>1.0-b17</jruby-scripting.version>
>>>
>>> 2. After building core or core\branding, you should see inside
>>> GlassFishBranding.java, minor_version = "1".
>>> private String major_version = "3";
>>> private String minor_version = "1";
>>>
>>> In the log file now I see
>>> [#|2010-05-05T11:37:49.515+0100|INFO|glassfishv3.1|null|_ThreadID=25;_ThreadName
>>>
>>> ={felix.fileinstall.poll=5000,
>>> felix.fileinstall.bundles.new.start=true, felix.f
>>>
>>> Jennifer
>>>
>>> On 5/5/2010 1:34 AM, Carla Mott wrote:
>>>>
>>>> Hi,
>>>>
>>>> The version number in the log files is incorrect for the releases
>>>> we are working on. It still reads glassfishv3.0. What is the
>>>> correct API I should use to get the version number so it is always
>>>> updated to the current version?
>>>>
>>>> Thanks,
>>>> Carla
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>