Community
Participate
Working Groups
When importing lib jars into my project, I find that I'm always going through the same tedious motion to add them to the build path. I'd like to request a checkbox on the import dialog, "add imported items to build path" that would, um, add the imported items to the build path.
there is no need to import JARs you reference them directly on the file system (either as an external JAR or via a variable). Support for a Java aware importer is not planned for 2.0
Just to clarify why I think importing jars from the filesystem is a useful project construction strategy: one of my chief complaints with VisualAge Java was its inability to maintain a common project workspace. That is, each developer was responsible for adding all required projects to the workspace, and for maintaining the correct versions of these projects. Eclipse overcomes this with external .jar (or variable reference). The flaw here comes from a) developers that do not have network access to a lib directory, or b) developers are still responsible for acquiring and maintaining all project- relevant jars. By creating a project /lib directory and importing jars into the project (and maintaining them in source control), the common project organization is kept consistent and complete, and zero time is wasted in configuration.
correct, I'm not against importing JARs and make them managed, but we still have no time for Java aware importer for 2.0
We should not implement a Java aware importer. Instead we should provide an action "Add to Build Path" on Jars that aren't already on the build path. This give use creater flixibility. Consider for 2.1
added 'Add to Build Path' action (in context menu on JARs) > 20021029
