R
Robert Mazur
Robert> Thus, source
Hi Phil. Thanks for the input.
I will just continue my file layout to get Eclipse happy. But ya, I bet
you are correct about Ant, and its ability to build everything exactly
as you tell it to. I can't vouch for that as I don't use Ant, but from
the little I do know, it sound ultra-configurable to handle whatever you
want.
*** Caveat....maybe Ant can do something I am not aware of, that being
controlling how Eclipse internally handles projects...in which case my
explanation to follow may be completely wrong ****
But from what I know, and just so you know what I mean....all I am
saying is for Eclipse to not show little red X's everywhere and yellow
alerts, etc, while you are doing your developing (not the final build
that Ant may do wonderfully as you suggest), files need to be in the
"right" place in the file system. So if I want to call somewhere in my
code:
food.fruits.apples
...I better have my apples class file on the OS file system in:
/food
/food/fruits/
/food/fruits/apples
....rather than just in /apples....or Eclipse will post X's everywhere
and give me errors/alerts that my structure is out of whack, JSP's with
bean tags will be alerted out by Eclipse's editors, etc. With JBuilder
I could have apples.java somewhere crazy and JBuilder wouldn't care so
much, like:
/usr/local/mywork/projects/something_else/some_classes/apples.java
Similarly if I want to move a JSP to a subfolder like:
/one.jsp
....to...
-number_pages
--one.jsp
.....in my *Eclipse project*, the result is it gets moved in the OS file
system such that if I call:
http://www.whatever.com/one.jsp
..... and refresh the browser to view the page, the page will not be
found (because I moved it to a different folder inside Eclipse's
project, it moved in on the file system). You see in JBuilder, you can
sub-folder the heck out of everything for tidiness and convenience, but
it doesn't change the layout of the web app itself. So in the *JBuilder
project*, one.jsp and two.jsp could be found in different folders at:
projectroot/number_pages/watch_these/need_to_edit/one.jsp
projectroot/something_else/work_project/two.jsp
....and I could still call them without any special Ant builds as:
http://www.whatever.com/one.jsp
http://www.whatever.com/two.jsp
That's all I am saying. The build of the project, in the context of my
thread in this newsgroup, is something different, and I bet you are spot
on that Ant can build things anyway I want.
Perhaps Ant w/ Eclipse also handles the project during development to
remove all the red and yellow alerts when source files are in different
places *in the project*? If so, I apologize...I don't know that.
OK, I'll put it all to rest now! ;-p Thanks Phil, and to all, for
their input.
Rob
Robert> files need to be refactored, edited, etc.
If eclipse has ant support (which I know that it does), then I can't
sen how it can stop you from doing this. You write an ant file which
builds the appropriate WAR file structure from however you like your
OS file system.
<snip>
Cheers
Phil
Hi Phil. Thanks for the input.
I will just continue my file layout to get Eclipse happy. But ya, I bet
you are correct about Ant, and its ability to build everything exactly
as you tell it to. I can't vouch for that as I don't use Ant, but from
the little I do know, it sound ultra-configurable to handle whatever you
want.
*** Caveat....maybe Ant can do something I am not aware of, that being
controlling how Eclipse internally handles projects...in which case my
explanation to follow may be completely wrong ****
But from what I know, and just so you know what I mean....all I am
saying is for Eclipse to not show little red X's everywhere and yellow
alerts, etc, while you are doing your developing (not the final build
that Ant may do wonderfully as you suggest), files need to be in the
"right" place in the file system. So if I want to call somewhere in my
code:
food.fruits.apples
...I better have my apples class file on the OS file system in:
/food
/food/fruits/
/food/fruits/apples
....rather than just in /apples....or Eclipse will post X's everywhere
and give me errors/alerts that my structure is out of whack, JSP's with
bean tags will be alerted out by Eclipse's editors, etc. With JBuilder
I could have apples.java somewhere crazy and JBuilder wouldn't care so
much, like:
/usr/local/mywork/projects/something_else/some_classes/apples.java
Similarly if I want to move a JSP to a subfolder like:
/one.jsp
....to...
-number_pages
--one.jsp
.....in my *Eclipse project*, the result is it gets moved in the OS file
system such that if I call:
http://www.whatever.com/one.jsp
..... and refresh the browser to view the page, the page will not be
found (because I moved it to a different folder inside Eclipse's
project, it moved in on the file system). You see in JBuilder, you can
sub-folder the heck out of everything for tidiness and convenience, but
it doesn't change the layout of the web app itself. So in the *JBuilder
project*, one.jsp and two.jsp could be found in different folders at:
projectroot/number_pages/watch_these/need_to_edit/one.jsp
projectroot/something_else/work_project/two.jsp
....and I could still call them without any special Ant builds as:
http://www.whatever.com/one.jsp
http://www.whatever.com/two.jsp
That's all I am saying. The build of the project, in the context of my
thread in this newsgroup, is something different, and I bet you are spot
on that Ant can build things anyway I want.
Perhaps Ant w/ Eclipse also handles the project during development to
remove all the red and yellow alerts when source files are in different
places *in the project*? If so, I apologize...I don't know that.
OK, I'll put it all to rest now! ;-p Thanks Phil, and to all, for
their input.
Rob