Community
Participate
Working Groups
Build Identifier: 1.14 (CVS) Obviously when installing AMP, a wrong version of log4j is not being detected. This leads to missing options in the New Project wizard. Reproducible: Always Steps to Reproduce: 1. Eclipse environment with installed log4j 1.2.13 2. Install AMP Features 3. Open New Project wizard 4. "Agent Modeling Group" is missing!
Created attachment 178590 [details] Proposed patch to fix log4j problem This patch adds a log4j version constraint to the AMFX-feature. Minimum version of log4j seems to be 1.2.15.
Hi Jonas, Thanks for the patch! These apache dependencies are the bane of Eclipse builds and seems especially to crop up in Xtext/Xpand stuff. The issue is that many people end up needing this and then it gets imported, but if it ends up over-specificed, then Eclipse won't install *any* of your dependencies and the whole thing breaks. Not good. In particular, rather than use Require-Bundle, the best practice seems to be to use Import-Package. But what I've done instead of applying your patch is just get rid of log4j altogether. I'm not too fond of using it as I think it's fiddly and plus it relies on static methods (!). There is just one usage in params and I've commented that out. Would you give it a try and see if that takes care of your issue? You'd have to build it locally as the builds are still fubar'd (but I think I finally figured out the dependency issue there..) Life would be so much simpler if we didn't have to depend on anything else.. :) -Miles
Hi Miles, I think it's a good thing to remove unnecessary dependencies. However, XWT still requires Log4j 1.2.15. But this is fair enough for me. :)
(In reply to comment #3) > I think it's a good thing to remove unnecessary dependencies. However, XWT > still requires Log4j 1.2.15. Yes, and I'll let them worry about that.. :D Let me know if it solves the problem for you. So, are you using e4?
For me, the problem is solved. I'm currently not using E4. But that's just about the next thing we plan to do. Have you already made any experiences with AMP and E4?
(In reply to comment #5) > For me, the problem is solved. > > I'm currently not using E4. But that's just about the next thing we plan to do. > Have you already made any experiences with AMP and E4? OK, marking as resolved. No, but that was definitely on my list.. If you get it working I'd love to see screen shots.
