I think we're talking about two different things here
1) 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.

Paul

On 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?

~Lincoln

On Mon, Sep 19, 2011 at 4:00 PM, Aslak Knutsen <aslak@4fs.no> wrote:
https://github.com/arquillian/arquillian-maven/blob/master/plugin/src/main/java/org/jboss/arquillian/maven/BaseCommand.java#L188

:)

On Mon, Sep 19, 2011 at 8:54 PM, Lincoln Baxter, III
<lincolnbaxter@gmail.com> wrote:
> Yes, we need this. I believe Paul is working on this. Copied forge-dev.
>
> https://issues.jboss.org/browse/SEAMFORGE-284
>
> Where do we get started?
>
> ~Lincoln
>
> On Mon, Sep 19, 2011 at 2:16 PM, Dan Allen <dan.j.allen@gmail.com> 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
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
>



--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"