Well, I've had a busy morning. I've done a ton of work on the projects at
Tapestry @ JavaForge.
I've changed the version number of everything to 1.0.0-SNAPSHOT.
Documentation has been updated. Site navigation updated. Look and feel is now aligned with everything else Tapestry.
This was spurred by a comment in the user mailing list about how tapestry-spring doesn't work with prototype beans. It does, but I haven't updated the documentation.
Of course, Maven 2 is letting me down here. It doesn't support site publishing via FTP (just secure FTP and various SSH related options). This adds a manual step to deploying the documentation that I'll roll into a Ruby script next time I publish.
Anyway, tapestry-testng, tapestry-flash and tapestry-spring are release candidates. tapestry-prop may have a few features (already in Tapestry 5) added to it before its final.
9 comments:
Hi, Howard? Does tapestry-spring support Spring 2.0? And how is Tapestry 5 devlopment state now? I just can't wait for T5, specially when the T4-style templates are implemented. :)
Spring is very good about backwards compatibility, so I have no doubts it will work with 2.0. You can check for yourself by downloading the tapestry-spring source and playing with the spring dependency version.
T5 will be ready asap, but that's still a ways off. It will be useable in a limited form fairly soon, with the really impresive JavaScript stuff coming a bit later.
That's a good idea: to release a core version of Tapestry 5, ending the hunger of many (myself included, of course :)), and them another release with all the fancy AJAX stuff. ;)
Howard, You can deploy using FTP if you add this to the build section of your pom.xml.
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ftp</artifactId>
<version>1.0-beta-1</version>
</extension>
</extensions>
Nope, I've tried that before and it doesn't work:
$ mvn -N site:deploy
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Tapestry @ Javaforge
[INFO] task-segment: [site:deploy]
[INFO] ----------------------------------------------------------------------------
[INFO] [site:deploy]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Wagon protocol 'ftp' doesn't support directory copying
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Sat Nov 25 08:14:40 PST 2006
[INFO] Final Memory: 3M/7M
[INFO] ------------------------------------------------------------------------
~/Documents/workspace/tapestry-javaforge
$
Not that it makes the maven plugin's ability to transfer directories over ftp any less troublesome, but I'd have to imagine that enabling an ssh server on your host would be a fairly trivial task to accomplish if one were so inclined. (maybe especially if one had some sort of plesk administrative interface, then it might possibly be enabled by logging in / going to Virtuozzo -> System Services -> checking off sshd and clicking start ....but only if you have such an interface - in theory )
Startlogic doesn't support any kind of login, it's a shared virtual host server. Cheap and reliable, but limited.
The only reason I suggested it was because I use startlogic for opencomponentry.com using a shared virtual server as well. The option is available to me but it could be that I have different options available for some other reason I don't know.
Sorry, works for deploy but I guess not for site:deploy. I don't understand why FTP is not a first class wagon protocol.
Post a Comment