| [Bug?] Eclipse Unable to nest output folders [message #200826] |
Tue, 24 February 2004 08:07  |
Eclipse User |
|
|
|
Hello All,
After spending some time with individual output folders for different
source directories, I feel that eclipse's inability to nest output
folders is very annoying (for J2EE developers) and a possible area of
improvement.
If eclipse was able to nest output folders, I can do a J2EE project
completely without writing a make file or an ANT script.
consider this use case, I want to write an EJB. So I create a directory
my directory structure like
src
|
|--com.abhi.blalba.*
|
config
|
|-- ejb -> *.xml
Now I want to set the output directory of the src folder to bin/MyEjb
and config/ejb to bin/MyEjb/META-INF folders.
presently I cannot do this because META-INF is nested inside bin/MyEjb
(OK if my project has only one EJB then I can choose bin/MyEjb/META-INF
as the default output folder and work around the problem of nesting ...
but if the project has two ejbs then the workaround fails)
The reason given in one of previous threads is that eclipse doesn't know
where the files are coming from (in case of nesting) ... but why doesn't
it know? because when I map a source folder to an output folder I
clearly specify both the source and the target.
If I could have nested output folders, then I can simple save java/xml
files and the new version gets copied in its appropriate output folder.
Then I could simple do a directory based deployment of the app. If the
deployment is done in debug mode most app servers will reload the class
and resource files as soon as they change.
Meaning that without repeatedly running ant script or make file or
recreating the jar/ear I can do development. I simple save the file and
it gets deployed. Once testing is finished I can do a "jar -cvf" and
that's it I get my EAR file.
It frees me from writing complex and large ANT scripts or make files.
and running the ant script repeatedly every time I change the code.
regards,
Abhishek.
|
|
|
| Re: [Bug?] Eclipse Unable to nest output folders [message #200930 is a reply to message #200826] |
Tue, 24 February 2004 11:31  |
| Eclipse User |
|
|
|
If you are wanting to sync resources as they are added/changed/deleted,
you probably want use an IResourceChangeListener for your plugin. When you
get a resource change event, you can make the approriate change in the
application directory of the appserver. I'm pretty sure that is how other
J2EE environments like Lomboz and MyEclipse do it.
Derek
Abhishek Srivastava wrote:
> Hello All,
> After spending some time with individual output folders for different
> source directories, I feel that eclipse's inability to nest output
> folders is very annoying (for J2EE developers) and a possible area of
> improvement.
> If eclipse was able to nest output folders, I can do a J2EE project
> completely without writing a make file or an ANT script.
> consider this use case, I want to write an EJB. So I create a directory
> my directory structure like
> src
> |
> |--com.abhi.blalba.*
> |
> config
> |
> |-- ejb -> *.xml
> Now I want to set the output directory of the src folder to bin/MyEjb
> and config/ejb to bin/MyEjb/META-INF folders.
> presently I cannot do this because META-INF is nested inside bin/MyEjb
> (OK if my project has only one EJB then I can choose bin/MyEjb/META-INF
> as the default output folder and work around the problem of nesting ...
> but if the project has two ejbs then the workaround fails)
> The reason given in one of previous threads is that eclipse doesn't know
> where the files are coming from (in case of nesting) ... but why doesn't
> it know? because when I map a source folder to an output folder I
> clearly specify both the source and the target.
> If I could have nested output folders, then I can simple save java/xml
> files and the new version gets copied in its appropriate output folder.
> Then I could simple do a directory based deployment of the app. If the
> deployment is done in debug mode most app servers will reload the class
> and resource files as soon as they change.
> Meaning that without repeatedly running ant script or make file or
> recreating the jar/ear I can do development. I simple save the file and
> it gets deployed. Once testing is finished I can do a "jar -cvf" and
> that's it I get my EAR file.
> It frees me from writing complex and large ANT scripts or make files.
> and running the ant script repeatedly every time I change the code.
> regards,
> Abhishek.
|
|
|
Powered by
FUDForum. Page generated in 0.33426 seconds
Home