[
https://jira.codehaus.org/browse/MJSIMP-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298700#comment-298700
]
Christopher Hunt commented on MJSIMP-2:
---------------------------------------
JS Import expects (needs) resource files to drive the dependency substitution
process i.e. it takes a ${} reference in a script src attribute value and
replaces it with the required file and its dependencies.
Perhaps you do not require the JS Import plugin?
I would think that many Maven plugins would similarly fail if src/main/java did
not exist (just guessing here though).
> js packaging fails with non.existing src/main/resources
> -------------------------------------------------------
>
> Key: MJSIMP-2
> URL: https://jira.codehaus.org/browse/MJSIMP-2
> Project: Mojo JavaScript Import Maven Plugin
> Issue Type: Bug
> Reporter: Martin Eisengardt
> Assignee: Christopher Hunt
>
> For non-existing src/main/resources there is a failure:
> [ERROR] Failed to execute goal
> org.codehaus.mojo:js-import-maven-plugin:1.0.1-SNAPSHOT:generate-html
> (default-generate-html) on project web-lib-js-core: Execution
> default-generate-html of goal
> org.codehaus.mojo:js-import-maven-plugin:1.0.1-SNAPSHOT:generate-html failed:
> basedir
> C:\dev\ws\r_p\xworlds\xworlds-parent\projects\xworlds-web-lib\branches\0.0.1-SNAPSHOT\web-lib-js-core\src\main\resources
> As soon as you create an empty folder it works. However this is bad. Compared
> to maven java support the javascript-tools should silently ignore if
> src/main/resources are not existing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
