Hi Wayne, I think that it makes sense to discuss a packaging around producing www artifacts more than just js artifacts.
Right now, as well as the import plugin I've proposed, I'm going to be using other plugins e.g. js-test-runner (http://code.google.com/p/jstd-maven-plugin/) and assemble them in a coherent way through my pom. I've got js-ria archetype in the works which lays out a template project for JavaScript RIA development; I see that is where most of the binding of JS related projects and plugins should occur as opposed to monolith plugins. I've also got an assembly file that takes what is presently in my classes folder (I'm using a jar packaging) and archives it taking care of generating .htaccess files and the like. I'm using Server Side Includes so I need to ensure that various html files have their execution bits set etc - the assembly plugin really helps here. I'd reckon that a "www" packaging would be something like this (it could even be this): http://jira.sakaiproject.org/browse/SMP-3 Whatever it is I believe it would be something very similar to the jar packaging lifecycle but without the jar build and perhaps different target folders e.g. "www". Perhaps a www plugin is required here which also managing deploying archives to an http server... perhaps this is already done! Thoughts? Kind regards, Christopher On 23/10/2010, at 2:20 AM, Wayne Fay wrote: >> As you'd know, there are multiple unit test toolkits, multiple compressors >> etc. for JavaScript. I don't think it'd be useful to combine them all into >> one >> plugin. Your thoughts? > > Does it make sense to talk about implementing a new Javascript > lifecycle with bindings at various lifecycle phases (that make sense > for Javascript development) and then attaching various plugins to the > phases? > > I don't do a lot of Javascript development these days so I may be > completely off base... in which case, feel free to ignore me. ;-) > > Wayne > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
