I've been wondering this for a while and never asked. When you create a
transformation project all of the tag libraries are autoimported except
for the workspace tag library. It's manually imported in the generated
main.jet file. What's the reason for this? I guess a good reason would
be since it's main functionality is for the workspace and would mainly be
used in the main template it's not used anywhere else and therefore,
memory could be saved, but I don't believe it's much at all.
Another reason to add to your point is that JET can also be executed from
the a standalone project which necessarily be a Eclipse based project ,
the concept is that all OSGI bundles can be executed from anywhere , if
thats the case then lots of Workspace related pre initializations could
potentially result in errors and plugins will not be loaded properly.
The same reason could be though from the Project - Link to File System
JET experts please correct me if I am wrong on my perception.
The thought was that the WS tags are generally used by a small number of
templates (main.jet and those it directly includes), and that it would be
bad practice to use them in templates that create content. So, the decision
was made to made those tags a little harder to get at.
In general, setting auto-import to true means you can avoid writing @taglib
directives in each template. Including a tag lib import with auto-import set
to false does nothing - a @taglib directive will pull in any tag library,
whether it is mentioned on plugin.xml or not.