Date:
04/02/11 20:55
|
Submitted by:
B_Fristensky
|
Assigned to:
umhameld
|
Category:
Getbirch
|
Priority:
3
|
Ticket group:
Bug
|
Resolution:
Resolved
|
Summary:
Detection of an existing BIRCH install during an update
|
Original submission:
The first thing Getbirch does when installing an update is to delete the current BIRCH core. This is fine, except in the case where the install fails for some reason. For example, if the bin or framework files fail to download, say, for a short network hiccup.
If you try to rerun getbirch.jar, there is no longer a BIRCH system to detect, so it will refuse to allow you to do an update.
Soo the detection of an existing BIRCH install has to be done by detecting something in the local directory. Perhaps local/admin/BIRCH.properties?
|
Please log in to add comments and receive followups via email.
|
Followups
Comment
|
Date
|
By
|
Change landed with commit 66e0d2f83474682bbaf64019a739ed2e2b00889f
tested and verified fix on albacore.
|
04/07/11 22:24
|
umhameld
|
|
No results for "Dependent on ticket"
|
No results for "Dependent on Task"
|
No other tickets are dependent on this ticket
|
Ticket change history
Field
|
Old value
|
Date
|
By
|
status_id
|
Open |
04/07/11 22:24
|
umhameld
|
resolution_id
|
Not Resolved |
04/07/11 22:24
|
umhameld
|
close_date
|
12/31/69 19:00 |
04/07/11 22:24
|
umhameld
|
status_id
|
Pending |
04/02/11 20:56
|
B_Fristensky
|
priority
|
5 |
04/02/11 20:56
|
B_Fristensky
|
assigned_to
|
unset |
04/02/11 20:56
|
B_Fristensky
|
resolution_id
|
Unset |
04/02/11 20:56
|
B_Fristensky
|
|