On Sat, Aug 14, 2010 at 9:52 AM, Dennis Lundberg <denn...@apache.org> wrote:
> On 2010-08-12 09:26, Stephane Nicoll wrote: > > +1 > > > > While we're discussing the war plugin, if anyone is interested to work on > it > > a bit more, it would be much appreciated: users have reported a lot of > > issues and some of them are quite old. One theme for 2.2 would be to > > finalize the caching system (with a fix for the XStream thing) but we > still > > have very old request like MWAR-9 and MWAR-33. > > I'm interested in working on the plugin in general, but I haven't got a > clue about the caching system though. > We can chat together if you're interested. Roughly, the cache stores the state of the war file (i.e. the dependencies) in an xml file placed in the target directory. In a next run (mvn package for instance), the idea is to compare the latest state provided by the cache with the actual dependencies tree of the project. We're suppose to deal with the following: * Remove a dependency from WEB-INF/lib if the dependency has been removed meanwhile (a clean would do but the cache is there to provide the same level without cleaning your whole target directory) * Replace a SNAPSHOT version following an update (since the SNAPSHOTs are unique, you easily end up with duplicated jar without a clean) This helps users who have an exploded war and want to refresh it without too much IO operations. Of course, this is not enough. The next steps would be to deal with jar files buried in an overlay for instance but it will have to use some heuristics to determine the version. Not sure how far we should go. > As you've seen by the JIRA e-mails I've been going through some issues, > closing the ones that lack proper problem descriptions or where the > reporter has not answered our follow-up questions. > Right, It's been a while since I haven't done this so thanks again for that :) > > There are still ~50 open issues in JIRA and that's too much to handle. I > think we should add components in JIRA to be able to group related > issues together. > > We should agree on a suitable set of components. Here's a proposal from > me. Please comment on it. > > - cache > - exploded goal > - inplace goal > - manifest (meaning not just the goal, but any issue involving the > creation/copying of manifests) > - multi module > - overlays > - war goal > The components thing is actually a very good idea. I'll give it some thoughts and get back to you. Thanks, S. > > > > Thanks for doing this by the way. > > Sure thing > > > S. > > > > --- > > [image: Linkedin] <http://www.linkedin.com/in/snicoll>[image: > > Twitter]<http://twitter.com/snicoll> > > > > > > On Thu, Aug 12, 2010 at 12:02 AM, Dennis Lundberg <denn...@apache.org > >wrote: > > > >> Hi > >> > >> I'm going to try to push out a release of the WAR Plugin soonish. If > >> anyone has something to add to it, now is the time to do it (or ask for > >> more time). > >> > >> Current release is 2.1-beta-1 and trunk is labeled 2.1-beta-2-SNAPSHOT. > >> Having looked at the 4 issues slated for 2.1 in JIRA, I'd like to push > >> those issues to 2.2 and release what we have now as 2.1 (no beta). WDYT? > >> > >> -- > >> Dennis Lundberg > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
