On Mon, Nov 22, 2010 at 10:23 AM, Chris <crehb...@gmail.com> wrote:

>
> On Nov 19, 7:50 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> > FWIW, I have *no* problem with Eclipse Helios (3.6, updated to SR1)
> > with GPE 1.4.0.v201010280102 and m2eclipse 0.10.2.20100623-1649 on
> > Windows XP Pro SP3
> > (if I understand correctly the issue, when launching DevMode, my
> > index.jsp and other things like that from my "war directory" –$
> > {project.build.directory}/${project.build.finalName}, i.e. target/
> > <webapp maven module name>– would vanish)
>
> Hi,
>
> Its not all files in the build output directory - our HTML files and
> any static resources that are kept in 'src/main/webapp' and copied to
> 'target/<module>' are left alone when starting dev mode.  Our
> particular problem is that we had a separate maven resources project
> that was being deployed to 'target/<module>' during mvn:package, and
> those exploded resources were being deleted when dev mode is starting
> up.
>
> Yes, such resources will be wiped out. What's actually happening here is
that GPE is using WTP's "smart publish" functionality to publish J2EE
modules  to the target/ directory.

So, in the source of launching, GPE performs a WTP publish. The WTP publish
will copy any J2EE modules that it knows about over to the target/
directory, which means that all of your resources in src/main/webapp will be
copied over properly. If you're got Maven's integration with WTP installed,
then the target/WEB-INF/lib directory will contain all of the libraries that
are in the runtime scope which are defined in your pom.xml file.

However, the publish is a "smart" one - so if any resources to be published
already exist in the target/ directory and are unchanged, the copy of that
file is not performed. In addition, if any resources are found in the
target/ directory that the publisher did not mean to create, then they are
deleted.

In the next version of GPE, I think we'll consider either:

1) Allow the user to specify which folders should remain untouched during a
smart publish
2) Switch over to a "full publish" - that will leave resources that are
unknown alone.


> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to