11:43 a.m.
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
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
7:58 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-751:
-------------------------------
Fix Version/s: 4.2.0.BETA1
Complexity: Low
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.BETA1
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
8:23 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Work on ISPN-751 started by Manik Surtani.
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.BETA1
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
8:35 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani resolved ISPN-751.
--------------------------------
Resolution: Done
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.BETA1
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
7:15 a.m.
New subject: [JBoss JIRA] Reopened: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani reopened ISPN-751:
--------------------------------
The format of the string in Version.java has changed and the regexps in the release script
don't match anymore :(
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
7:15 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-751:
-------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.BETA1)
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
10:31 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
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
9:13 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani resolved ISPN-751.
--------------------------------
Resolution: Done
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
10:39 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Trustin Lee commented on ISPN-751:
----------------------------------
Could we generate Version.java during the build process? For example:
http://fisheye.jboss.org/browse/Netty/trunk/pom.xml?r=HEAD#l320
Then the only property we need to update manually will be the code name.
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
5:12 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs
[
https://jira.jboss.org/browse/ISPN-751?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani commented on ISPN-751:
------------------------------------
It is updated via the build process. At least the micro.patch bits are. Major.minor are
still done by hand because that may involve registering new marshallers, wire formats,
etc.
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
5138
days inactive
5151
days old
infinispan-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Paul Ferraro (JIRA)
-
Trustin Lee (JIRA)