| a glimpse at I200511162235 [message #147477] |
Thu, 17 November 2005 09:59  |
Eclipse User |
|
|
|
Originally posted by: toby.polley.com
Hi there,
a just tried I200511162235 to decide whether we'll migrate to 1.0M9. I
noticed a few things, but these might be easy for someone who knows
how-to. If not, well...
- The '.deployables' directory is gone. OK, webtools can publish the
modules, every n seconds, too, but using .deployables this was done
instantly. (We would have to change the way we work but people might
wonder..) Pointing tomcat to the old .deployables directory, the changes
made were visible as soon as they were saved. Is there some way to
archive this with a current version? (Or what are the reasons against this?)
- Including other projects (Web Libraries) using the 'J2EE Module
Dependencies' is a _very_ nice feature we have been missing. (We use ant
scripts at the moment.) But, if I am correct, not all classpath entries
(from the project being included) that are marked as 'exported' are
actually copied to the active WEB-INF/lib. This means projects included
by the included project *g* are never found by tomcat (although in
eclipse's classpath) as well as 'first'- (in the first project) or
'second-order' libraries.
- If I have a Dynamic Web Project (called 'A') with a JSP page (a.jsp)
referencing a class called 'test.A' and an _independent_ pure java
project called 'B' containing 'test.A', too, when i rename test.A within
B using the refactoring methods, a.jsp will be changed (altough B is
never referenced by A).
Thanks for your effort (and any comments :),
Toby
|
|
|
| Re: a glimpse at I200511162235 [message #147532 is a reply to message #147477] |
Thu, 17 November 2005 12:07  |
| Eclipse User |
|
|
|
On Thu, 17 Nov 2005 09:59:58 -0500, Tobias Polley <toby@polley.com> wrot=
e:
>
> - If I have a Dynamic Web Project (called 'A') with a JSP page (a.jsp)=
referencing a class called 'test.A' and an
> _independent_ pure java project called 'B' containing 'test.A', too, w=
hen i rename test.A within B using the refactoring
> methods, a.jsp will be changed (altough B is never referenced by A)
Thanks for taking an early look! I can't speak to them all, but for this=
one, I'm not sure if its a
bug or a feature :)
Does the "preview" not even give you a choice to include that change for=
the "never referenced" class?
I suspect we can improve this user experience over time, but at the mome=
nt, am not sure how much
we (in JSP) know about what's referenced and what's not. But .. if we ar=
e really looking in all
other projects! sounds like a good opportunity for performance fixes too=
! :)
|
|
|
| Re: a glimpse at I200511162235 [message #147616 is a reply to message #147532] |
Thu, 17 November 2005 20:18 |
| Eclipse User |
|
|
|
Originally posted by: toby.polley.com
David Williams wrote:
>> - If I have a Dynamic Web Project (called 'A') with a JSP page
>> (a.jsp) referencing a class called 'test.A' and an _independent_
>> pure java project called 'B' containing 'test.A', too, when i
>> rename test.A within B using the refactoring methods, a.jsp will be
>> changed (altough B is never referenced by A)
> Does the "preview" not even give you a choice to include that change
> for the "never referenced" class?
yes. So I am able to unselect the changes in a.jsp.
> I suspect we can improve this user experience over time, but at the
> moment, am not sure how much we (in JSP) know about what's referenced
> and what's not.
yes... Adding another Dynamic Web Project 'A2' with the same JSP file
(named a2.jsp there) does not show a compilation error (since the class
test.A is missing in A2), but code completion is not available for this
missing class. Trying to rename test.A from project B previews changes
a.jsp as well as a2.jsp.
|
|
|
Powered by
FUDForum. Page generated in 0.04389 seconds
Home