[
https://jira.codehaus.org/browse/MOJO-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Hunt updated MOJO-1703:
-----------------------------------
Description:
The plugin presently allows for globals to identify js files to pull in. In
addition @import can be used to pull in pom declared artifacts.
It may also be useful to bring in js files that have been declared within the
project that do not declare any globals. One instance of this was a file we had
that extended the inbuilt Date object. This file wasn't something declared to
the pom (as it was part of the project), and had no globals (it simply declared
Date.prototype properties).
Any @include could specify the project relative path of the file to include e.g.
/**
* @include "extensions/Date.js"
*/
For now, the work-around is to have the Date.js file declare a global named
"DateExtension" and then declare that that as the dependency.
was:
The plugin presently allows for globals to identify js files to pull in. In
addition @import can be used to pull in pom declared artifacts.
It may also be useful to bring in js files that have been declared within the
project that do not declare any globals. One instance of this was a file I had
that extended the inbuilt Date object. This file wasn't something declared to
the pom (as it was part of the project), and had no globals (it simply declared
Date.prototype properties).
Any @include could specify the project relative path of the file to include e.g.
/**
* @include "extensions/Date.js"
*/
For now, the work-around is to have the Date.js file declare a global named
"DateExtension" and then declare that that as the dependency.
> [js-import-plugin] @include would be useful
> -------------------------------------------
>
> Key: MOJO-1703
> URL: https://jira.codehaus.org/browse/MOJO-1703
> Project: Mojo
> Issue Type: New Feature
> Reporter: Christopher Hunt
> Priority: Minor
>
> The plugin presently allows for globals to identify js files to pull in. In
> addition @import can be used to pull in pom declared artifacts.
> It may also be useful to bring in js files that have been declared within the
> project that do not declare any globals. One instance of this was a file we
> had that extended the inbuilt Date object. This file wasn't something
> declared to the pom (as it was part of the project), and had no globals (it
> simply declared Date.prototype properties).
> Any @include could specify the project relative path of the file to include
> e.g.
> /**
> * @include "extensions/Date.js"
> */
> For now, the work-around is to have the Date.js file declare a global named
> "DateExtension" and then declare that that as the dependency.
--
This message is automatically generated by JIRA.
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
