Eclipse Community Forums: ServerTools (WTP) » how is .deplyables updated

Home » Language IDEs » ServerTools (WTP) » how is .deplyables updated

how is .deplyables updated [message #145352]

Thu, 27 October 2005 08:26

Eclipse User

Hello,
What causes the .deployables directory to be updated? If I add a jar to the
WEB-INF/lib directory - what triggers it's copying to the .deployables
directory? If I change the context.xml, what triggers its copying?
Thanks,
Zohar

Re: how is .deplyables updated [message #145402 is a reply to message #145352]

Thu, 27 October 2005 14:32

Eclipse User

I think it was either a builder or a resource change listener, however
the entire .deployables has been removed now. Copying is no longer
being done.

Zohar wrote:
> Hello,
> What causes the .deployables directory to be updated? If I add a jar to the
> WEB-INF/lib directory - what triggers it's copying to the .deployables
> directory? If I change the context.xml, what triggers its copying?
> Thanks,
> Zohar
>
>

Re: how is .deplyables updated [message #145609 is a reply to message #145402]

Sun, 30 October 2005 02:06

Eclipse User

removed where? What's the behavior now?

"Sachin Patel" <sppatel2@gmail.com> wrote in message
news:djr6g8$klo$1@news.eclipse.org...
>I think it was either a builder or a resource change listener, however the
>entire .deployables has been removed now. Copying is no longer being done.
>
> Zohar wrote:
>> Hello,
>> What causes the .deployables directory to be updated? If I add a jar to
>> the WEB-INF/lib directory - what triggers it's copying to the
>> .deployables directory? If I change the context.xml, what triggers its
>> copying?
>> Thanks,
>> Zohar

Re: how is .deplyables updated [message #146246 is a reply to message #145609]

Thu, 03 November 2005 15:33

Eclipse User

Zohar wrote:
> removed where? What's the behavior now?

This is my understanding please correct me if I am wrong.

Since 2 weeks I-builds ago work it was removed, it used to be used as a
pre-publishing assembly area. But the operation has now been push into
the wst.server/jst.server publishing tasks.

Before (with .deployables):

* Build process hardwired class output into
project/.deployables/project/WEB-INF/classes/blah.class
* Resource change process copied resource file into
project/.deployables/project/....
* Publish task then did no real work but copy files from
project/.deployables/project/.... into
..metadata/.plugins/org.eclipse.wst.server.core/tmp0/.....

After

* The wst.server publish operation takes the resources directly from
their location in the workspace and copies into
..metadata/.plugins/org.eclipse.wst.server.core/tmp0/..... there is no
longer any double copy.
* There is no longer a hardwired class output directory, you can set it
wherever you like, just like any other prokect.

The .deployables was always internal eclipse implementation detail and
should not be used by any external tools or process.

--
Darryl L. Miles

Previous Topic:	SEVERE: Error filterStart and Context Startup
Next Topic:	What can I use Integration Build (Declared Weekly) for ???

Goto Forum:

-=] Back to Top [=-

Current Time: Mon May 12 17:48:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter