[infinispan-issues] [JBoss JIRA] Commented: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Fri Nov 5 11:31:01 EDT 2010


    [ https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561630#action_12561630 ] 

Galder Zamarreño commented on ISPN-751:
---------------------------------------

Oh, maybe it's due to the addition of major property for ISPN-728 that caused the issue?

You should add a big note on top of the information that changed within Version.java so that whoever makes any change there, it double checks that the release script runs fine (does it have a dry-run option or similar?) 

> Infinispan release reporting itself as a SNAPSHOT in logs
> ---------------------------------------------------------
>
>                 Key: ISPN-751
>                 URL: https://jira.jboss.org/browse/ISPN-751
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.2.0.ALPHA5
>            Reporter: Paul Ferraro
>            Assignee: Manik Surtani
>            Priority: Minor
>             Fix For: 4.2.0.CR1
>
>
> Using infinispan-core-4.2.0.ALPHA5, I see the following in the logs:
> 2010-10-29 12:20:39,557 INFO  [org.infinispan.factories.GlobalComponentRegistry] (RMI TCP Connection(6)-127.0.0.1) Infinispan version: Infinispan 'Ursus' 4.2.0.SNAPSHOT
> It seems the release was built prior to tagging/labelling?
> While this is trivial - it is definitely something you'll want to fix before the final release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list