Howard Lewis Ship schrieb:
I don't want to introduce non-backwards compatible solutions, plus I
generally like having the resources in the same virtual folder as the
classes.
resources could have the same package structure as your classes. If you
want to have them next to your classes, then you could fix your build
script to do the packacking of src/main/resources/foo/bar/anyImage to
the correcct target folder
META-INF/resources/foo/bar/bazz.png
I know I was very unhappy when I upgraded an app from 5.1 to 5.2 and
stuff was broken. I want to avoid that. We're not talking about
subtle API changes only used by a handful for inner-circle hard-core
devs ... it's basic stuff and third party libraries that suddenly
break, and the majority of users won't have the skills to figure out
what broke and how to fix it.
I agree that we should strive for backwards compatitibility but this is
something else then striving only for backward compatitiblity. If we
break something that this is mainly a communication problem for us and
informing users about this what be very useful.
We could add a setting which does protect all resources by default.
Disabling let you switch back.
We could document that the default behaviour will change in 5.3 and in
the interim time let this be an optional setting.
A dedicated folder is by far easier to handle than to mark everything as
to be delivered.
All technologies including JSF, JBoss Seam need to break things fromtime
to time or let old code not interoperate with new code. There is no
innovation with zero change.
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-----
Software Developer and Trainer for Hibernate / Java Persistence
http://www.laliluna.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
