The fact that I chose the name "modules" is really a coincidence - the structure of /trunk was created before I had started learning Maven, and "modules" was selected because I envisioned the individual pieces being similar to Axis2 modules. They are not .mar files yet, but perhaps one day they will be.
Right now my main focus (if you could call it that) with Maven is "how do we better incorporate the sample web projects" - these kind of projects are the chief means of testing, but I do not know how we can use Maven to run tests against something that needs to be deployed on Tomcat or OSGi. Andrew had a plan for developing our test harness[1], but both of us have been busy and this has fallen on the back burner. If we could create a POM that built the WARs, deployed them on Tomcat, and ran the test clients, that would be great; I know that Maven has a way to build WARs, and automatically run test apps, but I don't know about deployment. Progress on this front would be a great reason to revist the top-level structure and POM. For the web site I am just editing the site files in /site, committing, and doing a SVN update from minotaur.apache.org. This was quicker for me than learning another markup meta-language (Forrest) and doing the extra steps necessary to re-generate the site. Right now we're mostly adding to the front page News and Releases section, so it's not bad; soon I'll add a new tutorial node, which should also be self-contained. The only problem comes if we want to redesign the major UI components of the site, which I have no plans of doing in the foreseeable future. ;) Dan [1] http://marc.theaimsgroup.com/?l=muse-dev&m=115143926500357&w=2 Nathan Sowatskey <[EMAIL PROTECTED]> wrote on 07/17/2006 02:57:45 PM: > Ah! > > It is not where I expected it to be :-) > > Normally the top level pom.xml is in the top level directory that > contains the modules directory, not in the same directory as the modules > themselves. > > It needs to be in the top level directory so that the site docs for the > whole project can be built in the appropriate place. > > Did you *really* want to have it where it is, or was that just a Maven > thing that wasn't fully understood? > > Regards > > Nathan > > Daniel Jemiolo wrote: > > looks like it's there: > > > > http://svn.apache.org/viewvc/webservices/muse/trunk/modules/ > > > > did you get any of the other updates? > > > > > > > > Nathan Sowatskey <[EMAIL PROTECTED]> wrote on 07/17/2006 02:07:48 PM: > > > >> Hi > >> > >> I can't see the pom.xml in trunk after I update. Should it be there yet? > >> > >> Thanks > >> > >> Nathan > >> > >> Dan Jemiolo (JIRA) wrote: > >>> [ http://issues.apache.org/jira/browse/MUSE-42?page=all ] > >>> > >>> Dan Jemiolo closed MUSE-42. > >>> --------------------------- > >>> > >>> Resolution: Fixed > >>> > >>> Fixed: http://svn.apache.org/viewvc?view=rev&revision=422728 > >>> > >>>> Update /trunk/modules and build-all.bat to support a top-level Maven2 > > POM for Muse > > ---------------------------------------------------------------------------------- > >>>> Key: MUSE-42 > >>>> URL: http://issues.apache.org/jira/browse/MUSE-42 > >>>> Project: Muse > >>>> Issue Type: Improvement > >>>> Components: Build - Maven, Dependencies, and Optimizations > >>>> Affects Versions: 2.0.0 M1 > >>>> Reporter: Dan Jemiolo > >>>> Assigned To: Dan Jemiolo > >>>> Priority: Minor > >>>> Fix For: 2.0.0 M2 > >>>> > >>>> Attachments: pom.xml > >>>> > >>>> > >>>> It is possible to create a top-level POM for Maven2 that will loop > > through > >> the individual module POMs and build all of them. This will allow us to > > have a > >> completely-Maven2-based build, with much less in the .bat/.sh files. We > > have a > >> proposed solution, we just need the POM file submitted and licensed in > > JIRA. > >>>> Original request and proposal is here: http://marc.theaimsgroup.com/? > >> l=muse-dev&m=115269144619791&w=2 > >> -- > >> Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk > >> +34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco - > >> [EMAIL PROTECTED] > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk > +34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco - > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
