| build path (compile classpath) vs. runtime classpath [message #127613] |
Mon, 15 December 2003 17:20 |
 Keith Donald
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
Our development team would like the capability with our projects in Eclipse
to more clearly distinguish between compile-time (build path) library
dependencies, and those required at run-time (defined within a run
configuration.)
Currently, we lump both compile-time and run-time dependencies into the
project build path for convenience, which ensures the project will compile
AND run from Eclipse with minimal setup. This saves our developers from
having to add-in the necessary run-time dependencies in their own local run
configurations. However, this also mixes compile time stuff with runtime
stuff, which results in a lot of extra classpath variables in the build path
which are not needed.
The workaround we implemented above could be addressed by allowing run
configurations to be saved on a project-by-project basis to a central
repository, similiar to how the build-path information is now. This way we
could keep the distinction between compile time and run-time dependencies
clear. This would also free the users from having to perform additional
local setup of runtime dependencies in order to launch the application from
Eclipse.
Thanks,
Keith Donald
Senior Software Developer
kdonald@csi-inc.com
|
|
|
Powered by
FUDForum. Page generated in 0.03342 seconds
] 
Search
Help
Register
Login
Home
