[
http://jira.codehaus.org/browse/MGWT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202717#action_202717
]
Daniel Scott commented on MGWT-131:
-----------------------------------
Sorry, this still doesn't make much sense to me:
1. If your dependency (src/main/webapp) files are just normal resources
(HTML/CSS/JS etc) then they don't need to be in a war project at all, you can
just copy them into the right place.
2. If your dependency is java code, then you can just put it into a jar file
and then include this as a dependency in the war project.
Is there a particular reason why you need 'library' wars? I didn't think that
wars were supposed to be used in this way.
> Plugin attempts to compile projects with 'pom' packaging
> --------------------------------------------------------
>
> Key: MGWT-131
> URL: http://jira.codehaus.org/browse/MGWT-131
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Fedora 11, Java 1.6.0_16, Maven 2.2.1, GWT 1.7.1
> Reporter: Daniel Scott
> Assignee: nicolas de loof
> Priority: Minor
> Fix For: 1.2
>
>
> When the GWT compile goal is enabled for projects which have the 'pom'
> packaging type, maven attempts to compile the project and fails because no
> source code is available. The compilation should be disabled by default for
> projects which have the 'pom' packaging type.
--
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
