[MAGNOLIA-1676] Version can't be parsed during second bootstrap Created: 09/Aug/07  Updated: 23/Jan/13  Resolved: 10/Aug/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: Capitaine Harold Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Eclipse 3.2.2, wtp, jdk 1.5, tomcat 5.0, linux ubuntu 7.04


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In info.magnolia.module.model.Version.java, more specifically in the private constructor.
The version string is parsed to get a short to differentiate the major, the minor and the patch version.
On the first start of Magnolia, as the project is not build with maven or with whatever mecanism, the variable ${project.version} is not set, so Magnolia replaced it with the value (dev). This value is parsed as mentioned previously that's why a numberformat exception raises, so Magnolia can't start.



 Comments   
Comment by Magnolia International [ 09/Aug/07 ]

woops - had not read correctly. will give that a try.

Comment by Magnolia International [ 09/Aug/07 ]

should be fixed now, thanks for reporting and sorry for the hasty closing.

Comment by Magnolia International [ 10/Aug/07 ]

re-fixed by philipp

Generated at Mon Feb 12 03:29:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.