[jboss-as7-dev] Deployment -- why marker files?

[Jason T. Greene]

Sure. You have a good point here. We need to solve CLI + exploded.

On 4/13/11 3:54 AM, Max Rydahl Andersen wrote:
> yes, but its limited/not-applicable for exploded deployments.
>
> So could we please say "Please use CLI or console for *production* deployments" or make the remote management API support exploded deployments/incremental updates ?:)
>
> /max
>
> On Apr 13, 2011, at 05:43, Jason T. Greene wrote:
>
>> Right, and in fact I think we should promote the CLI over FS. It always
>> does exactly what you tell it to :)
>>
>> On 4/12/11 10:21 PM, Jim Tyrrell wrote:
>>> I will second this, I hope the console has the ability to "tweak" these
>>> settings, I also would think the command line tool should handle them,
>>> from the demo today it looks like it does, or at least does something
>>> around deployment.
>>>
>>> Jim Tyrrell
>>> Senior JBoss Solutions Architect
>>>
>>> Did you see RHT on CNBC's Mad Money?
>>> http://www.cnbc.com/id/39401056
>>>
>>>
>>>
>>> On Apr 12, 2011, at 8:16 PM, Howard Gao wrote:
>>>
>>>> I think managing those mark files with deployment through a tool is the
>>>> right way. If I had such a tool, I don't even care to look into
>>>> /deployments directory for any mark files.
>>>>
>>>> Howard
>>>>
>>>>
>>>> On 04/13/2011 06:57 AM, Max Rydahl Andersen wrote:
>>>>>>> Have you guys talked with Max and the tools team to see what/how this
>>>>>>> effects what they have to do?
>>>>>> Yes, I think hes happy with the eventual outcome. Although I will let
>>>>>> him comment :)
>>>>>
>>>>> Jim, if you look at the forum thread you should see my head show up a
>>>>> tons of times ;)
>>>>>
>>>>> And just to keep it short - I think we found a good balance that
>>>>> solves both sides of the story and the
>>>>> overall idea is good - especially now that just putting archives in
>>>>> the directory will work as you have always
>>>>> been used to. There might be some glitches left in the implementation
>>>>> but that is why its called a Beta and
>>>>> if someone finds issues with it report jira with steps to reproduce.
>>>>>
>>>>> So if you use archives then stuff just works (even with tools), if
>>>>> exploded then you need an explicit marker but
>>>>> that is "easily" done in tools; hardest one is actually Maven but
>>>>> should be easy to implement in Cargo.
>>>>>
>>>>> JBoss Tools trunk supports the notion of .dodeploy files now btw.
>>>>>
>>>>> Our biggest challenge is the remote API which is unfortunately much
>>>>> more shaky at this point than the file deployment....so i'm happy
>>>>> the FS API at least works otherwise we would be rather stuck ;)
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org<mailto:jboss-as7-dev at lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org<mailto:jboss-as7-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> --
>> Jason T. Greene
>> JBoss, a division of Red Hat
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> /max
> http://about.me/maxandersen
>
>
>


-- 
Jason T. Greene
JBoss, a division of Red Hat