[
https://issues.apache.org/jira/browse/PIVOT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036046#comment-13036046
]
Edvin Syse commented on PIVOT-744:
--
My patch is NOT changing the behavior you describe, my
[
https://issues.apache.org/jira/browse/PIVOT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036079#comment-13036079
]
Raffaele Borrelli commented on PIVOT-737:
-
Thanks Sandro and Greg, I was having the
[
https://issues.apache.org/jira/browse/PIVOT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036120#comment-13036120
]
Greg Brown commented on PIVOT-744:
--
Was this patch actually applied? It doesn't look like
[
https://issues.apache.org/jira/browse/PIVOT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036146#comment-13036146
]
Sandro Martini commented on PIVOT-744:
--
No, to avoid side effects (before yesterday's
[
https://issues.apache.org/jira/browse/PIVOT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036155#comment-13036155
]
Greg Brown commented on PIVOT-744:
--
OK. If you do apply this patch and it works correctly,
[
https://issues.apache.org/jira/browse/PIVOT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036160#comment-13036160
]
Sandro Martini commented on PIVOT-744:
--
Ok, today I'll make some other tests and
In ApplicationContext there is a getJVMVersion() that returns a
Version structure. I'm looking for something that gives me the Pivot
version number (Version object) in a similar fashion and I can't find
it. Is there such a method? If not, do you think it would be useful?
Could it be set somehow
You can get this information from the JAR manifests but it is pretty ugly. Best
thing to do would probably be to add build.properties or something like it to
the generated JARs so it would be available on the classpath.
On May 19, 2011, at 3:42 PM, Roger L. Whitcomb wrote:
In
Would it be worth adding this to the build? Would it then also be worth
adding an API to load and parse this as a Version structure?
Roger Whitcomb | Architect, Engineering | roger.whitc...@ingres.com |
Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 |
USA +1 650-587-5596 |
Would it be worth adding this to the build? Would it then also be worth
adding an API to load and parse this as a Version structure?
Yes, I think so.
Add API to return Version of Pivot retrieved from build.properties
Key: PIVOT-746
URL: https://issues.apache.org/jira/browse/PIVOT-746
Project: Pivot
Issue Type: New
[
https://issues.apache.org/jira/browse/PIVOT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Whitcomb updated PIVOT-746:
-
Attachment: version.patch
Here is a patch that implements this feature.
Add API to return
[
https://issues.apache.org/jira/browse/PIVOT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-746.
--
Resolution: Fixed
Patch applied. Thanks!
Add API to return Version of Pivot retrieved from
13 matches
Mail list logo