That would be awesome! But I wouldn't bother setting up the Ant based builds, though; the focus should be on getting the Maven based things to work. A wrinkle is you might have to be a bit adaptable on the assembly stuff, as we're not quite done creating that. And, that actually raises a question about what MyFaces is doing on the topic of sample applications (as well as to solicit advice from other folks here as well).
I will try to take a look tomorrow night and see where things stand with the maven build. Even if we don't get things running completely the main thing is to get continuum up and running. Also, it will be good to build the jars at a minimum just to make sure everything is compiling and things are running smoothly. We can add the assembly and publish stuff later.
For maximum user benefit, it's nice to ship sample apps "ready to run", with all their dependent jars included. But with four apps already, that would mean lots of jar files duplicated -- which would really bloat an all-in-one download. For the Ant based builds, I took the tack of creating several kinds of artifacts: * A zip of the framework itself (library jars, sources, javadocs)
Certainly very easy to do with maven.
* A zip of the dependencies (which Maven will eliminate the need for * A war file for each example (ideally with a buildable source module and javadocs for the application classes included inside). What do you think of this kind of strategy for Maven based builds as well?
Hmmm good idea. This would come in handy with MyFaces now that you mention it. Of course you have to weigh the possible confusion of "missing" dependencies vs. the bandwith you save. How are existing shale users responding on the user list? (I'm not currently monitoring that one.)
Craig
Sean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
