On 9/2/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Can you tell what subproject is doing it? (And did it just start > happening?)
Tiles. It wasn't happening earlier this week. > You can run with -Dmaven.test.skip (or > possibly -Dmaven.test.failure.ignore) to temporarily get around that. Yep, that did the trick. > (Based on experimentation in shale/use-cases/project.xml,) Maven uses the > <artifactId> from project.xml as the directory name. Since flow has none, I > think it's using the <id>. Maybe James can comment on what else is affected > by <id> and <artifactId>. We'd want to do the simplest, most consistent thing. If published as an artifact, Struts Flow would resolve to struts-flow, and so that's where the website should be. Every subproject should have an artifact id. > How are you bulding the Shale site? It is another multiproject site on its > own. I haven't been able to get Maven to cooperate and do the whole thing > automatically, so "building the Struts site" currently consists of (adapted > from build/maven-nightly.sh.current): Once we get past this initial hump, I don't think doing them all at once will be particularly important. Worst case, we can use a batch file or shell script to run each subproject in progression. Then, if a subproject needs to be a multiproject of its own, it can. In regular practice, it will be more important to be able to do each subproject on its own. People will tend to work on one subproject or another, and then post only those changes, rather than do all at once. > Have we decided what to do about the Struts 1.2 docs? There was talk of > putting them under http://struts.apache.org/docs/1.2 (like HTTPD) or > http://struts.apache.org/struts-1.2-doc/ (like Tomcat). For consistency, we might want to treat the docs like they were an artifact, which would imply a third form, "struts-doc-1.2" :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
