More info:
After a fresh mvn install the changes are now reflected in Tomcat. So
it _seems_ like the Magnolia running in TC would somehow access the
local maven repository?! Is there something in the "trunk" project I
should know about?
Regards,
will
On 16.09.2008, at 10:21, Will Scheidegger wrote:
Sorry to bother you guys with this, but I've already showed it to
someone else and we both could not find what's causing the trouble:
- I've downloaded and built the latest magnolia (mvn install, then
copied the war from magnolia-empty-webapp/target to Tomcat and let
it bootstrap)
- After everything was up and running I stoped TC, changed some code
in magnolia-core, built it, copied the jar to the magnolia instance
and started TC again
- But magnolia does not reflect the changes!
Things I tried:
- clean, build copy again
- search the whole computer for other copies of the jar
- Printed out the location of the jar that was being used by
magnolia with
ItemType.class.getProtectionDomain().getCodeSource().getLocation()
- Unpacked the Jar
- Decompiled the class
=> The modified code is _in_ the Jar, still Magnolia does not
reflect the changes.
=> When I test the same bit of code from a scriptlet, I _do_ see the
changes!!!
=> What the heck am I doing wrong?!
It's like my code would be overwritten by some old copy of the code
although magnolia claims to be using the modified jar. I'm totally
puzzled and do warmly appreciate any ideas where to look next!
Regards,
will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
