[ http://issues.apache.org/jira/browse/YOKO-68?page=all ]
Lars Kühne resolved YOKO-68.
----------------------------
Resolution: Fixed
Darrent cleared this up on the dev list: Only the C++ Orbacus ORB uses the
version information to change the behaviour. No further code changes are
necesary for yoko.
> Incorrect version number in o.a.y.orb.OB.Version
> ------------------------------------------------
>
> Key: YOKO-68
> URL: http://issues.apache.org/jira/browse/YOKO-68
> Project: Yoko - CORBA Server
> Issue Type: Bug
> Reporter: Lars Kühne
> Assigned To: Lars Kühne
> Fix For: 1.0-incubating-M1
>
>
> Current output is "Yoko for Java 4.3.1 [GA release]".
> The output should reflect the version number in the pom. One technique to
> find the version is described in
> http://mail-archives.apache.org/mod_mbox/maven-users/200605.mbox/[EMAIL
> PROTECTED]
> A numerical version number (4030100) is also in the Version class, it is sent
> as a ServiceContext. Not sure how to generate such numbers from the pom
> version which might include additional textual info like "SNAPSHOT" or
> "Incubator". I can't see any uses for sending the version Context, except
> logging the version of the communication partner. Maybe this functionality
> should be removed completely?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
