Thursday, October 13, 2016

Re: best practices for modular GWT app


On 12 Oct 2016, at 19:38, Kirill Prazdnikov <pkirill@gmail.com> wrote:

I do not completely understand which problems do you have, but we dont have any issues working with SDM with modules I described above.

maybe was something wrong in my project layout. Now I made another test, and in the submodule I revert the packaging to "jar" and added back this:

<build>
    <resources>
        <resource>
            <directory>src/main/java</directory>
            <includes>
                <include>**/*.java</include>
                <include>**/*.gwt.xml</include>
                <include>**/*.ui.xml</include>
            </includes>
        </resource>
    </resources>
</build>

and in the main GWT pom.xml file I need to have this to work it correctly:

<dependency>
    <groupId>${project.groupId}</groupId>
    <artifactId>WebMetabase-module-user</artifactId>
    <version>${project.version}</version>
    <classifier>sources</classifier>
</dependency>

otherwise without the classifier-sources I didn't get a recompile when I refresh the browser.
As I posted yesterday the system is also working using the other GWT-Maven plugin, but I think is a "clear" way to add extra modules to the project, I'm right?


No comments:

Post a Comment