[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-628) Updated conf&all to reflect new version

Mircea Markus (JIRA) jira-events at lists.jboss.org
Tue Sep 7 12:17:52 EDT 2010


     [ https://jira.jboss.org/browse/ISPN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus resolved ISPN-628.
--------------------------------

    Resolution: Done


I've updated all the pom.xml to reflect that. Also VAM.java and Version.java

> Updated conf&all to reflect new version
> ---------------------------------------
>
>                 Key: ISPN-628
>                 URL: https://jira.jboss.org/browse/ISPN-628
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 4.2.0.BETA1, 4.2.0.CR1, 4.2.0.Final
>
>
> You shoudl also create JIRAs to make sure you update version numbers in Version.java and in the XML schema headers to 4.2.0 (from 4.1.0)
> [11:47] manik: otherwise if we forget wqe end up with a weird release.  
> [11:47] mmarkus: manik: doesn't the release script do that?
> [11:48] manik: Sorry, yes, it does it for Version.java
> [11:48] manik: but not for the schema generators
> [11:48] manik: Nor for the marshaller layer
> [11:48] manik: (VersionAwareMarshaller)
> [11:49] manik: since those 2 components only care about major.minor versions, not major.minor.micro.modifier 
> [11:49] manik: (if you know what I mean(
> [11:49] manik: Anyway just create a JIRA to check these before any release
> [11:49] manik: otherwise you will have broken stuff

-- 
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