• Post Reply Bookmark Topic Watch Topic
  • New Topic

Framework Dependencies - where to begin?  RSS feed

Martin White
Posts: 4
Mac Netbeans IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I'm not really sure where to post this, so I've plumped for here!

For almost the last 2 years I've been working on a product that was inherited from an acquisition. Probably the first 6 months was spent just working out how on earth to build it and get a product from it, so they don't count, and to put things in perspective, I'm forever being pulled from one task to another, and to infrastructure, networking etc. etc. - so those 2 years should probably really have been six months.

Anyway, this product is a beast. It's around 480,000 lines of code (though that includes POM files). It dates back to around about 2008. It does use Maven, but from day one (actually several months in!), I discovered there was a dependency issue preventing it from building, and not being familiar with it I never could work it out, so the only way I could get it to build was to ensure the repository was in offline mode. That's been fine to date, but more and more, there are issues cropping up where I know that it's because things are so out of date we need newer versions. For instance, in the web interface there are rendering problems in Chrome and Safari. On investigation, I find that it's because our solution pre-dates the inclusion of Chrome / Safari support in one of the frameworks. And I can solve the problem by updating that framework, but it breaks loads of other stuff.

SO, what would anyone suggest as to how would I go about beginning to tackle bringing this thing up to date. I'm not going to be able to put it off forever and I feel the longer it's being put off, the worse the problem is getting.

As a rough guide, we're at least talking about the following and the versions we're currently on...

JBoss - 4.2.2
Hibernate - 3.2.1 ?
Spring - 2.5.4 ?
jBPM - ?
Seam - 2.0.1

etc. - the list goes on forever!

I'm mostly aware of the fact that Maven should handle a lot of the inter-dependency stuff for me when it comes to the smaller libraries, but I have in the back of my mind somewhere that when it comes to the bigger things like JBoss (I know not a library!), Seam and Hibernate, there are specific version combinations that must be met.

Any pointers on unravelling this would be most welcome. Apart from the obvious one of finding another job

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!