- This topic has 9 replies, 3 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Hi, I’ve almost forgotten this idea: I’ve seen that ME (2.7RC2) adds it’s own library set (J2EE) to the IDE, besides the existing JRE/JDK library set. We’ve tested ME with one existing project (among others ) having _lots_ of libraries. The plain Eclipse drove me nuts because I had to scroll permanently in the package explorer, just to jump over those libraries.
Now I’d like to see a posibility to define my own library sets (definiton saved into workspace or project) like the lib set ME provides. A extension could be the option to export/import the definition of user defined library sets. This would considerably ease in larger project teams the redistribution of modified project settings. (iirc JBuilder has this feature)
Victor
Victor, great suggestion; we definately look into this!
If you don’t need persistent src/javadoc attachment for your libraries, I found a decent plugin for this a while back… I don’t remember where though.
Victor, I think this is exactly what you are looking for:
http://www.javango.net/eclipse/userlib.htmlI will bring up the possibility of integrating this into ME to the ME team.
Thanks for the tip, I was wondering about this issues myself. I was going to suggest a Struts library set instead of all the files showing up in the package explorer, but this more generic case of user definable library sets would be much better. If they would maintain their links to source and documentation accross projects that would be truly ideal.
Roy Wells
Riyad, thanks! The plugin you mentioned is in the right direction.
Now… the more I’m thinking and playing with it… I’d really like to see this not at not at IDE level, but at project level, with paths relative to the project root. In the biggest project I tested with ME, I have 19 (nineteen) jar files in the …/WEB-INF/lib, no joke. These, together with the JRE/JDK and TOMCAT (packaged in a user lib) libs occupy about 1/3 of the package explorer (even slightly more), and this with a small IDe font and 1600×1200 resolution…wow that’s sizeable loss of realistate just to JARs… you can try and filter them using the package filtering, but using a plugin like this might help more.
Can you give an example of where having this plugin at a project level is more beneficial? I think this plugin really benefits the crowd that uses a lot of projects with the same technology (i.e. struts). If you wanted to use this plugin within a project, it would effectively (in my opinion) create the same effect as simply filtering out “*.jar” from your package explorer… so I’m not quite sure I see the value here, maybe you can point it out?
The problem of the Javango plugin is, that you have to add each .jar library at once, using a _full_ filesystem path.
But the .jar files I mean are already in the project directory tree, and when I’m passing the project tree & config files to someone else, the .jar files are already there, in the tree. The whole configuration is relative to the project root directory, _except_ the Javango library set, which is external and needs to be redefined for _each_ workspace used. I’m dreaming of having the library set definition saved into the project configuration -not IDE configuration-, with paths relative to the prj root dir. Or at least the ability to use a variable as the root of the library set.I’ll try tomorrow to filter the .jar files out of the tree, let’s see how it looks like.
VictorHmm yes I see waht you mean. Can you try and see if you like the filter method AND if its saved in the project such that when you pass it off, others see the filter too?
I did the following: filter “*.jar” and “referenced libraries”. This frees the tree a lot. Thanks for the good idea.
The filter settings are afaics workspace bound. But I can live with that.Thanks again,
Victor
