> Hi Mike,
>> I took a look at the 3.0.12 tag in bliki's svn. The pom's configuration
>> is broken. Source and target are different. This might lead to errors.
>> All subsueqents poms are fine. They have 1.5 and 1.5 set. I would
>> recommend to upgrade at least to 3.0.13.
> Provided 3.0.13 (or whatever the latest version is) is Java 5-compatible
> then upgrading to that version sounds like the right solution. I don't
> personally use the Bliki parser, but I've gotten reports from a number
> of users who do so if there are any issues with the upgrade I'm sure
> someone will report it and we can downgrade if needed.
I was to hasty in upgrading Bliki Core to 3.0.15 and JAMWiki failed to
org.jamwiki.parser.bliki.JAMWikiModel is not abstract and does not
override abstract method getNamespace() in info.bliki.wiki.model.IWikiModel
Axel introduced a breaking change in a bugfix version. WTF!
Now you have seen the perfect case which I have depicted in my criticism
of a broken versioning scheme.
I reverted back to 3.0.12 release version, all upstream versions are
broken. Due to my lack of knowledge of the upper shown code spot, I am
not able to fix that easily.
Are you willing to do so or do we want to stick to 3.0.12 for now?