Max Rydahl Andersen wrote:

For JSF projects, solving  JBIDE-1714, I have eliminated file /.settings/org.jbosstools.jst.web.xml
so it is not a problem anymore.


okey...then I have questions for that:

do we still work with users existing workspaces having that file ? (we must)

I suppose we do. But I need Slava to confirm that.

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.

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@redhat.com>
To: <jbosstools-dev@lists.jboss.org>
Cc: "Viacheslav Kabanovich" <scabanovich@exadel.com>; <external-exadel-list@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#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