[
http://jira.codehaus.org/browse/MJS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259690#action_259690
]
Christopher Hunt commented on MJS-38:
-------------------------------------
I think that this project's MOJOs should be deprecated in favour of factoring
out useful components into their own MOJOs. Each MOJO should be focused on
specific tooling and use cases, just as they are for other languages such as
Java. Note that there is no monolithic Java plugin.
I have already created two JS MOJOS to this end (1)(2).
To address the existing goals:
javascript:copy-dependencies handles javascript dependencies and unpack them to
your script directory. *** This can be handled better by (1). ***
javascript:compile prepares your scripts to get packaged in the web
application. *** I believe that this can be handled with the assembly plugin.
***
javascript:inplace unpack javascript dependencies to your web application
source, to enable quick development with servlet containers that don't require
a packaging phase. *** I think that (1) can help with this ***
javascript:compress use a configurable javascript compressor to reduce the
weight of js files. *** This should exist as a separate set of plugins -
perhaps one for each flavour of compressor out there ***
javascript:package pack a maven based javascript library as a javascript
archive to get installed/deployed in the repository. *** Not necessary. JS
files intended as libraries can be installed in a repo as js files directly.
Take the jQuery approach (and others) where many js files can be appended
together into the one and then distributed like so. There may be a MOJO already
for this (may be the assembly plugin could be utilised somehow). ***
javascript:attach-compressed pack a javascript archive with compressed version
of the library scripts. *** Wouldn't be necessary ****
I couldn't find the other goals, but I recall their being JSLint reporting and
JSDoc reporting. JSLint reporting is better handled by (2) given that the
developer is better off knowing their coding problems when they save their
file, not when generating site doco. However if a report is required still then
(2) could be expanded to provide such a thing.
JsDoc reporting is certainly worthy of its own MOJO and I'm using it with my
projects.
'hope that this is helpful.
References:
1. http://mojo.codehaus.org/js-import-plugin/
2. http://mojo.codehaus.org/jslint-plugin/
> Review the current status of this project
> -----------------------------------------
>
> Key: MJS-38
> URL: http://jira.codehaus.org/browse/MJS-38
> Project: Maven Javascript Tools
> Issue Type: Task
> Affects Versions: Short Term
> Reporter: Tim Astle
> Assignee: nicolas de loof
>
> This project is due for a review as to it's future. Things to consider are:
> # Should this project continue as is?
> # Should the project be split up?
> # Should the project be discontinued.
> # How do we handle notifying users of any changes in the project plans?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
