> It might be need to provide a function for creating an esb
archive
> without WTP deployment, just like export a web War file from File >
> Export > Web > War file, we can provide something like File >
> Export > ESB > ESB archive.
Wouldn't it be better to simply have this
be a function for our WTP
adapter that can export whatever gets deployed to a separate location ?
This is not a special case for ESB, both WAR, EAR, JAR's etc. would be
useful for this.
I.e. a File > Export > Server > Deployed archive or something similar ?
/max
>
> Denny
>> /max
>>> Any documentation?
>>>
>>> Thanks,
>>>
>>> Jeff
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "John Graham" <jgraham(a)redhat.com>
>>> To: "Mark Little" <mlittle(a)redhat.com>, "Mark
Proctor"
>>> <mproctor(a)redhat.com>, "Kris Verlaenen"
<kverlaen(a)redhat.com>,
>>> "Koen Aers" <kaers(a)redhat.com>, "Burr Sutter"
<bsutter(a)redhat.com>,
>>> "Leonard Dimaggio" <ldimaggi(a)redhat.com>, "Kevin
Conner"
>>> <kconner(a)redhat.com>, "Jeffrey Delong"
<jdelong(a)redhat.com>,
>>> "Garvin Dean" <garvin.dean(a)amentra.com>, "Edgar A
Silva"
>>> <edgar.silva(a)redhat.com>, "Prakasha Aradhya"
<paradhya(a)redhat.com>,
>>> "Max Andersen" <manderse(a)redhat.com>, "Trevor
Kirby"
>>> <tkirby(a)redhat.com>
>>> Sent: Thursday, January 8, 2009 12:30:09 PM GMT -07:00 US/Canada
>>> Mountain
>>> Subject: UPDATE: Assistance in testing JBDS with SOA-P
>>>
>>> Following up:
>>>
>>> 1. I should have prefaced the original message with "Please feel
>>> free to
>>> forward to anyone else (internal to RH/JB or under the appropriate
>>> agreements for this sort of internal information) who you might think
>>> would be interested in testing." If you do, please let me know, so
>>> I can
>>> add them into the list of people receiving these email updates.
>>>
>>> 2. Related to (1): Why not just use a mailing list like soa-tools?
>>> There
>>> are a couple of reasons: (a) There is no single list, or small set of
>>> lists, that covers everyone involved (and, no, I am not sending this
>>> request to thecore ;) ), (b) this is a short term, focused request,
>>> (c)
>>> list requests are like talking to a stadium of people, whereas this
>>> subset shows that I am talking to *you* :)
>>>
>>> 3. (Thanks, Len and Trev!) For the SOA-P download please use:
>>>
http://jawa05.englab.brq.redhat.com/released/soa-p-4.3.0.GA/
>>>
>>> 4. (Thanks, Max, Len, and Jeff!) Ignore the "all plug-ins" zips for
>>> the
>>> tooling, and use the installer jar instead. You might find that your
>>> browser attempts to open this jar directly instead of downloading
>>> it, in
>>> which case you'll need to do a "save as" on the installer jar.
Once
>>> downloaded, from the command line issue "java -jar ...." with the
jar
>>> name to start the installer.
>>>
>>> 5. If you test but don't find any problems, still please drop an email
>>> to Max and I saying that you've tried. Since "no response" does
not
>>> mean
>>> "tried it and found no problems to report," these notes will help
Max
>>> and I determine the test coverage in place for this combination.
>>>
>>> 6. Particular importance of this JBDS release: This is the release
>>> that
>>> we'll take to EclipseCon in March, and we'd like to push it hard,
>>> especially in the SOA area. We just need to be sure that what we push
>>> doesn't fall over. :)
>>>
>>> Thanks again!
>>> John
>>>
>>> On Wed, 2009-01-07 at 15:54 -0500, John Graham wrote:
>>>
>>>> As we reach the final stages of the JBoss Developer Studio (JBDS) 2.0
>>>> release, we are seeking help in testing the JBDS/SOA-P
>>>> combination. In
>>>> particular, we're interested in how the jBPM and Drools
distributions
>>>> bundled in the SOA-P product work with JBDS.
>>>>
>>>> So, while testing and feedback at any stage is appreciated, the
>>>> critical
>>>> period for release will be over the next 10 days or so. Any timely
>>>> feedback will help us to improve the tooling offered for this product
>>>> configuration.
>>>>
>>>> The specific builds of each:
>>>>
>>>> * JBDS 2.0: Use
>>>>
http://reports.qa.atl.jboss.com/binaries/RHDS/release/2.0.0.CR1/200812221...
>>>>
>>>> via the installer. (EAP is optional.)
>>>>
>>>> * SOA-P: Use
>>>>
http://jawa05.englab.brq.redhat.com/candidate/soa-4.3.0.GA_IR5/
>>>> (SOA team: this is the link that was provided to JBDS QE a while
>>>> ago; if
>>>> a later build should be used, please let us know in this thread.)
>>>>
>>>> If any questions come up during testing, it probably is best to
>>>> use the
>>>> jbosstools-dev(a)lists.jboss.org mailing list, since that will get the
>>>> most people in the most time zones. (Of course there's always JIRA
>>>> for
>>>> bugs.)
>>>>
>>>> A number of people on thread have tested various milestones of
>>>> this JBDS
>>>> release, and the input has been very valuable. We hope each of you
>>>> can
>>>> spare a few cycles to help us wrap up testing for this product
>>>> combination.
>>>>
>>>> -- John
>>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>