[jbosstools-dev] Re: physical bound file names in .settings directories ?
do we still work with users existing workspaces having that file ?
(we
must)
Yes, if that file is found it is used. What is new is that the file can be
removed
without any harm.
do we still work with non-WTP projects ? (we must)
We have already been working with Seam java projects without creating this
file.
What information does org.jbosstools.jst.web.xml represent ?
It is more than just the jar dependencies right?
Yes, it contains information about web modules. First, it was implemented in
Struts,
and our specification required to support references to any location on disk
for
struts-config.xml, module root folders, java src folder, etc. That is why
Struts is so
dependent on our xml file and that is why paths are absolute.
Dialog "Modules Configuration" illustrates the dependency.
Later, when JSF was developed, no support for such an elaborate dependency
was provided, instead, auto-restoring references by analyzing web.xml was
implemented.
That is, JSF implementation was more prepared to dismiss that xml,
by addressing WTP in the algorithm for restoring references.
If struts is completely seperate from this then lets first focus on
JSF -
I haven't seen anyone report back on Struts.
Then, with that stipulation, I think, JBIDE-1714 and JBIDE-1820 are fixed.
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