On 4/12/06, Don Brown <[EMAIL PROTECTED]> wrote: > So can we say we have an assembly building and can restart the nightlies?
All 25MB of it. :) Example: http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/ The procedure here should work the same for nightlies as releases. You can change 'deploy' to 'install' to avoid publishing the snapshots to maven-snapshot-repository. http://wiki.apache.org/struts/StrutsMavenRelease > What remains before releasing 1.3.2 from a build perspective? The website? I rearranged struts/site, and the FAQs aren't working. I might just be a missing 'id' attribute, though. (See followup post commenting on r393500.) The main site and menu need to be re-worked to reflect the simplified Action/Shale/Tiles organization. I think Struts Action needs a 'top level' site: struts/action/trunk/src/site/*. If that were published to s.a.o/struts-action, then struts-core, struts-taglib, etc., could go below it. (For example: http://struts.apache.org/struts-shale/shale-tiger/ ). We may have to publish each module separately, I have a feeling the changes that make site aggregation work in m2 are not yet released. Each pom needs a <distributionManagement>/<site> section with the correct path. (See struts/pom/pom.xml for an example.) I'd like to move the src/conf and conf/java files into src/main/resources and remove the <resource> tags from the pom, also. This page should capture everything a developer needs to know to work with the build, so please add to it as you discover things, or even add empty sections with questions if you have any. http://wiki.apache.org/struts/StrutsMaintenanceMaven Thanks, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
