|"Java Build Path / Order and Export" propery [message #540753]
||Thu, 17 June 2010 09:22
| vlad.balan Missing name
Registered: June 2010
could somone show an example scenario when the "Order and Export" is useful? The Export part of it.
Doc says "Source folders are always exported, and can not be deselected". This is pretty clear: when this project is added in another project's build path it contributes its classes to that project's classpath. This is the expected behaviour of adding this project to the other's classpath.
But also says that "Exported entries are visible to projects that require the project."
So what happens if checking other entries in this list, besides the projects source folder. Like for example, checking here some other projects that this project depends on, not only its source folders.
When could it be useful?
Is this kind of checking useful when this project is referenced by Java, Web or EAR projects?
And how it should be referenced for the expected effect to happen? As a Java Build Path entry, as a Project References entry or as a Java EE Module Dependecy entry?
[Updated on: Thu, 17 June 2010 09:26]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03619 seconds