> do we still work with non-WTP projects ? (we must)
>
It has not been working without WTP natures before. Because if you add
JSF/Struts capabilities it adds all necessary WTP features.
I'm referring to I can open files in non wtp projects and the editors almost work.
Before I assume it just ignored that there were no .settings info for it and just
want to be sure it now does not assume it will be in an WTP project.
-max
> What information does org.jbosstools.jst.web.xml represent ? It
is more than just the jar dependencies right?
>
>
>> For Struts projects dependency of Studio implementation on this file is rather
strong
>> so that eliminating it would require some extensive refactoring. Do we need to
solve
>> the problem for Struts, nevertheless, or is not it worth efforts?
>>
>
> If struts is completely seperate from this then lets first focus on JSF - I
haven't seen
> anyone report back on Struts.
>
> -max
>
>
>> Slava
>>
>>
>> ----- Original Message -----
>> From: "Max Rydahl Andersen" <max.andersen(a)redhat.com>
>> To: <jbosstools-dev(a)lists.jboss.org>
>> Cc: "Viacheslav Kabanovich" <scabanovich(a)exadel.com>;
<external-exadel-list(a)redhat.com>
>> Sent: Monday, March 17, 2008 8:07 PM
>> Subject: physical bound file names in .settings directories ?
>>
>>
>> I just noticed
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137029#... which
>> asks how users should commit their projects to svn/cvs when our .settings files
contains
>> hardcoded file references.
>>
>> I did not think we still had this so it becomes a very good question.
>>
>> How did Exadel do this with Exadel studio ?
>>
>> /max
>>
>>
>
>
>
>
>