4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Ken in nashua
Can someone resolve this please and repost new binaries to the release ? Eclipse complains that 4.1.6-SNAPSHOT remains in the classpath. This occurs after I delete tapestry from my local repo and perform a fresh install off the remote repo where 4.1.6 is released on. Tapestry-4.1.6 release

Re: 4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Martin Strand
Works fine here, are you sure you're not still using 4.1.6-SNAPSHOT? Martin On Tue, 16 Sep 2008 17:05:04 +0200, Ken in nashua [EMAIL PROTECTED] wrote: Can someone resolve this please and repost new binaries to the release ? Eclipse complains that 4.1.6-SNAPSHOT remains in the classpath.

Re: 4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Kalle Korhonen
Works fine here as well. Kalle On Tue, Sep 16, 2008 at 8:38 AM, Martin Strand [EMAIL PROTECTED] wrote: Works fine here, are you sure you're not still using 4.1.6-SNAPSHOT? Martin On Tue, 16 Sep 2008 17:05:04 +0200, Ken in nashua [EMAIL PROTECTED] wrote: Can someone resolve this

RE: 4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Ken in nashua
1. My eclipse has no libraries defined 2. My repo is purged/deleted prior to build 3. All eclipse projects are being re-generated with the maven-eclipse-plugin from maven 4. There are no references to any 4.1.6-SNAPSHOT within my webapp 5. I tried 4.1.6 as released 6. I tried 4.1.6

Re: 4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Martin Strand
Yeah, it seems pom.xml in the svn tag has the wrong version number (4.1.6-SNAPSHOT) But if you get the published files from maven's repo they're all ok: http://repo1.maven.org/maven2/org/apache/tapestry/ On Tue, 16 Sep 2008 19:05:08 +0200, Ken in nashua [EMAIL PROTECTED] wrote: 1. My

RE: 4.1.6 remains unusable for eclipse runtime

2008-09-16 Thread Ken in nashua
Folks, Thanks for the gracious and helpfuyl feedback. I remained persistent on this one because I was unsure of the svn references to 4.1.6-SNAPSHOT As it turns out I had commented out several project builds who's projects I was importing into eclipse. I was under the impression that