On Thu, May 29, 2008 at 9:18 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > Probably network issues or some such, then.
I don't think so, I think maven cached something it shouldn't have. Before downloading the correct jar-files, maven outputted this today, which it didn't yesterday. [INFO] snapshot org.apache.tapestry:tapestry-core:5.0.12-SNAPSHOT: checking for updates from tapestry.snapshots Anyhow, deleting ~/.m2 probably would have solved my problems yesterday as well. :) -- regards, Robin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
