[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] ModuleAssembler functional change advice
|
This is precisely what I was describing. This seems to be a very old
request that, based on my interpretation of the discussion attached to
the ticket, still has no satisfactory resolution. I'll try to restart
the discussion there.
Thanks for the pointer,
Steven Curtis
On Thu, Feb 19, 2009 at 3:49 PM, Gorkem Ercan <gercan@xxxxxxx> wrote:
> Hi Steven,
> Have you checked this
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=176650 bugzilla entry?
> Is it what you are describing?
> --
> Gorkem
>
> On Thu, Feb 19, 2009 at 9:32 PM, Steven Curtis <sjcurt01@xxxxxxxxx> wrote:
>> I've done a bit of reading regarding exploded EAR deployment and how
>> it relates to Eclipse publishing capabilities. By exploded
>> deployment, I mean publishing an EAR by making a directory containing
>> all required resources available to the application server instead of
>> packaging the resources into an EAR file and then copying it to the
>> deployment directory of the application server. Oracle's OC4J J2EE
>> container supports this type of deployment.
<snip/>
