You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <te...@gmail.com> on 2005/09/02 13:11:18 UTC
Re: 1.3.0 Release - Next Steps
$ maven build-all
from buid/ is working for me, but
$ maven multiproject:site
from site/build is not. It fails with
----
test:test:
[junit] Running org.apache.struts.tiles.TestI18nFactorySet
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.235 sec
[junit] [ERROR] TEST org.apache.struts.tiles.TestI18nFactorySet FAILED
[junit] Running org.apache.struts.tiles.TestTilesPlugin
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.187 sec
BUILD FAILED
File...... C:\Documents and Settings\ted_2\.maven\cache\maven-multiproject-plugi
n-1.3.1\plugin.jelly
Element... maven:reactor
Line...... 103
Column.... 9
Unable to obtain goal [site] -- C:\Documents and Settings\ted_2\.maven\cache\mav
en-test-plugin-1.6.2\plugin.jelly:181:54: <fail> There were test failures.
Total time: 3 minutes 34 seconds
Finished at: Fri Sep 02 06:35:22 EDT 2005
----
I tried again after running clean-all and build-all again, but no joy.
Meanwhile, the Shale site looks great! I'll use that as a template for
the other subprojects, so that everything will work the same way.
Though, one change might be that the "Struts" link should go to
"http://struts.apache.org/" since we don't know what they might have
built locally.
Obviously, the Shale site build works for me, so next I'll try doing
the same thing for Core.
My hope would be to have the patches to the website finished this
weekend, so that we can at least post that part of the puzzle.
* http://wiki.apache.org/struts/StrutsWebsiteConversion
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
On 9/2/05, Wendy Smoak <ja...@wendysmoak.com> 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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ja...@wendysmoak.com>.
Ted Husted wrote:
> $ maven multiproject:site
> from site/build is not. It fails with
Typo? It should be /current/site (not /current/site/build).
> BUILD FAILED
> Unable to obtain goal [site] -- C:\Documents and
> Settings\ted_2\.maven\cache\mav
> en-test-plugin-1.6.2\plugin.jelly:181:54: <fail> There were test failures.
Can you tell what subproject is doing it? (And did it just start
happening?) You can run with -Dmaven.test.skip (or
possibly -Dmaven.test.failure.ignore) to temporarily get around that.
> Meanwhile, the Shale site looks great! I'll use that as a template for
> the other subprojects, so that everything will work the same way.
One thing to think about is the directory structures... right now the Struts
Flow website is http://struts.apache.org/flow, but if you move the content
under the /current/flow/xdocs and do nothing else, the URL will change to
http://struts.apache.org/struts-flow .
(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>.
> Though, one change might be that the "Struts" link should go to
> "http://struts.apache.org/" since we don't know what they might have
> built locally.
Fixed.
> Obviously, the Shale site build works for me, so next I'll try doing
> the same thing for Core.
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):
echo "------ build multiproject site (head) ------"
cd /svn/struts/current/site/
maven multiproject:site
echo "------ build multiproject site (head - Shale) ------"
cd /svn/struts/current/shale/
maven multiproject:site -Dmaven.test.skip=true
cp -r target/docs/* ../site/target/docs/shale
echo "------ build multiproject site (head - Sandbox) ------"
cd /svn/struts/current/sandbox/
maven multiproject:site
cp -r target/docs/* ../site/target/docs/sandbox
echo "------ build multiproject site (head - Sandbox - Ti) ------"
cd /svn/struts/current/sandbox/ti
maven multiproject:site
cp -r target/docs/* ../../site/target/docs/sandbox/struts-ti
... then publish from site/target/docs/
> My hope would be to have the patches to the website finished this
> weekend, so that we can at least post that part of the puzzle.
> * http://wiki.apache.org/struts/StrutsWebsiteConversion
Sounds good. I'll be here all weekend doing homework. The website will be
a welcome diversion, so let me know if you need anything. :)
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).
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org