Bill Shannon kirjoitti:
> Petteri Räty wrote:
>> I want to package the deployment-api module from glassfish modules to
>> replace our current fetch restricted binary package. The only question
>> is how should I version it. Looking at project.xml of
>> glassfish-v1_ur1-p01-b02-src.zip we have:
>>
>> betelgeuse_at_pena ~/btdown/glassfish/deployment-api $ grep -i version *
>> build.xml:<?xml version="1.0" encoding="iso-8859-1"?>
>> project.xml:<?xml version="1.0" encoding="UTF-8"?>
>> project.xml: <pomVersion>3</pomVersion>
>> project.xml: <currentVersion>9.0-SNAPSHOT</currentVersion>
>>
>> Probably the version number should include 9.0 and the glassfish release
>> in some way? For example 9.0_pre110102?
>
> For a module representing a Java standard API, wouldn't it be better
> if the version number of the module matched the version number of the
> corresponding Java spec?
>
I see 9.0 comes from Sun Java System Application Server Platform Edition
9 probably so that is not useful indeed.
http://java.sun.com/j2ee/tools/deployment/
It seems the spec is in version 1.1:
http://java.sun.com/j2ee/tools/deployment/downloads/index.html
So probably a good name + versioning compination is:
glassfish-deployment-api-1.1.1.1.01. With Glassfish it should be too
that the bXX number represent some internal builds like with JDK too?
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)
Have you considered using a versioning scheme more standard for the FOSS
world like X.Y.Z?
Regards,
Petteri