![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0.1 |
|
Assignee:
|
Unassigned |
|
Attachments:
|
js-import-maven-plugin.patch |
|
Created:
|
21/Jan/13 6:06 AM
|
|
Description:
|
Hi,
I'm working on a project using my own packaging type "js" and want to resolve library dependencies with the help of this plugin using the "@import" notation in JS-Files.
Situation:
- JS-File A has no dependencies -> pom.xml contains no dependencies
- JS-File B depends on JS-File A -> pom.xml contains dependency for JS-File A
- HTML-File references JS-File B -> pom.xml contains dependency for JS-File B
Expected behavior:
- Plugin detects JS-File B and JS-File A as dependencies for HTML-File
Current behavior:
- Only JS-File B is detected and copied for further packaging
Quickfix:
- Adding dependency for JS-File A in HTML-File's pom.xml
-> but this conflicts with my idea of dependency management
Patch:
- I've created a patch to solve my problem (see attachment).
Currently I'm deploying the patched version of the plugin via my own infrastructure but I would appreciate it if the fix could be integrated into the main development and published via Maven Central.
Thanks.
|
|
Environment:
|
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
|
|
Project:
|
Mojo _javascript_ Import Maven Plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Sebastian Dorok
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
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
