On 7/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
When you have time I'd like to hear your thoughts on the release
process.  For such a short checklist, it sure seems like a lot of
work.  After the last two I wondered if I was making it harder than
necessary.

The process seems just fine. The current *circumstances* are
challenging, in that we are trying to go from one monolithic JAR to
seven lighterr JARs, reflect that division in the website
documentation, accomodate other changes in the overall project
infrastructure, and build a *fleet* of example applications. But, the
process seems fine.

I tried to clarify the StrutsMavenRelease a bit. I think if we trust
SVN (and the committer) to tag the right revision, the process becomes
agile. Otherwise, the only real stumbling block would be pre-testing
the assembly before a tag, and then doing it all over again against a
fresh checkout of the tag. Of course, even that problem would go away
if we had automated tests for the application suite.


I'm a little concerned because Maven rebuilds the jars during the
install phase, so the jars in the assembly are not going to be the
same ones that finally get deployed to the m2 repo. (But since there
is no date in the manifest, there is a chance they'll match exactly.)

We're working against a tag, so these types of binary consistencies
can be corrected if we can get a end-to-end run.


When you say you reset your repository, did you delete the whole
thing, or just org/apache/struts?  What you're describing sounds like
the typical 'first build' that fails several times until all of the
transitive dependencies get downloaded to the local repo.

Yes, StrutsMavenRelease was ambigous, so I removed the entire
repository. I put it back and just removed the o.a.s folder, and the
build ran better. But, then a test failed

[INFO] Surefire report directory: C:\projects\Apache\STRUTS_1_3_5\integration\ap
ps-it\target\surefire-reports

-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.struts.apps.AppsTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.951 sec <<< FA
ILURE!

Results :
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:555)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
       at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
       at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

       at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures
.
       at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugi
n.java:403)
       at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
       ... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19 minutes 56 seconds
[INFO] Finished at: Mon Jul 17 08:55:29 EDT 2006
[INFO] Final Memory: 34M/63M
[INFO] ------------------------------------------------------------------------

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to