You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kirill Kovalenko (JIRA)" <di...@incubator.apache.org> on 2005/10/06 15:20:47 UTC
[jira] Created: (DIREVE-271) Proposed change to the vendorVersion attribute format.
Proposed change to the vendorVersion attribute format.
------------------------------------------------------
Key: DIREVE-271
URL: http://issues.apache.org/jira/browse/DIREVE-271
Project: Directory Server
Type: Wish
Components: server main
Versions: 0.9.2
Reporter: Kirill Kovalenko
Assigned to: Alex Karasulu
Priority: Trivial
I just have a suggestion for the vendorVersion attribute format that you use. Now it's something like this: $Rev: 123456. For many people subversion revision number is meaningless and says nothing. I suggest something more standard like 'major.minor.revison.build'. For example - '0.9.3.123456'. Such approach allows people that have no idea of subversion revision to identify server version easily.
--
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
[jira] Resolved: (DIREVE-271) Proposed change to the vendorVersion
attribute format.
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-271?page=all ]
Alex Karasulu resolved DIREVE-271:
----------------------------------
Fix Version: 0.9.4
Resolution: Fixed
Now the maven 2 filters a properties file that contains the pom version which the build incorporates into the jar file. This properties file is loaded and the version is read. Just fixed this in revision:
http://svn.apache.org/viewcvs?rev=366630&view=rev
> Proposed change to the vendorVersion attribute format.
> ------------------------------------------------------
>
> Key: DIREVE-271
> URL: http://issues.apache.org/jira/browse/DIREVE-271
> Project: Directory Server
> Type: Wish
> Components: server main
> Versions: 0.9.2
> Reporter: Kirill Kovalenko
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 0.9.4
>
> I just have a suggestion for the vendorVersion attribute format that you use. Now it's something like this: $Rev: 123456. For many people subversion revision number is meaningless and says nothing. I suggest something more standard like 'major.minor.revison.build'. For example - '0.9.3.123456'. Such approach allows people that have no idea of subversion revision to identify server version easily.
--
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
[jira] Closed: (DIRSERVER-294) Proposed change to the vendorVersion
attribute format.
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-294.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> Proposed change to the vendorVersion attribute format.
> ------------------------------------------------------
>
> Key: DIRSERVER-294
> URL: https://issues.apache.org/jira/browse/DIRSERVER-294
> Project: Directory ApacheDS
> Issue Type: Wish
> Affects Versions: pre-1.0
> Reporter: Kirill Kovalenko
> Assigned To: Alex Karasulu
> Priority: Trivial
> Fix For: 1.0-RC1
>
>
> I just have a suggestion for the vendorVersion attribute format that you use. Now it's something like this: $Rev: 123456. For many people subversion revision number is meaningless and says nothing. I suggest something more standard like 'major.minor.revison.build'. For example - '0.9.3.123456'. Such approach allows people that have no idea of subversion revision to identify server version easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.