Ah, I thought you also picked up the issue on starting/stopping the container as well, which is linked to this one.
Maybe we should think about the concept of a Deployment API for forge, and what that would mean, but for now, let's just try this out on AS7.
I think we're talking about two different things here1) Deploying to AS7 using Shrinkwrap/Arquillian instead of file copies.2) Downloading and setting up the container (the issue Lincoln linked to).But anyway, I agree we should do this. I will pick this up.PaulOn Sep 19, 2011, at 10:07 PM, Lincoln Baxter, III wrote:Paul,
Does this look like a good starting point? Is this what you were thinking?
~LincolnOn Mon, Sep 19, 2011 at 4:00 PM, Aslak Knutsen <email@example.com> wrote:
On Mon, Sep 19, 2011 at 8:54 PM, Lincoln Baxter, III
> Yes, we need this. I believe Paul is working on this. Copied forge-dev.
> Where do we get started?
> On Mon, Sep 19, 2011 at 2:16 PM, Dan Allen <firstname.lastname@example.org> wrote:
>> I think its very important to switch forge over to the arquillian
>> container module to handle container life cycle and deploy commands in a
>> generic way, rather than the current as7 command. Could you guys catch up so
>> lincoln can get the info he needs about the container apis to get this
>> kickef off? This is a great example of using what we have across projects
>> (to follow up on a theme from the f2f).
>> - Dan Allen
>> Sent from my Android-powered phone:
>> An open platform for carriers, consumers and developers
> Lincoln Baxter, III
> "Keep it Simple"
Lincoln Baxter, III
"Keep it Simple"