Closed chrisco484 closed 5 years ago
The codes and libraries are too old. Some code files aren't even remotely related to "polling" - too many unrelated files. I would suggest using Spring Integration instead or use the jpoller as is.
We have a ban on Spring* :)
From our experience with client projects once Spring gets introduced to a project it ends up on a one way train to 'bloatware' land and needs much more cloud resources to run it effectively compared to simple POJO apps that do stuff without all the CPU zapping 'under the hood' reflection that occurs. Not many devs tend to worry about it though because most don't ever look under the hood to see how that stuff works and they aren't the ones paying the massive cloud costs to run it :)
From: Karl San Gabriel [mailto:notifications@github.com] Sent: Wednesday, 5 December 2018 11:52 PM To: Turreta/turreta-jpoller Cc: Chris Colman; Author Subject: Re: [Turreta/turreta-jpoller] Convert to maven? (#1)
The codes and libraries are too old. Some code files aren't even remotely related to "polling" - too many unrelated files. I would suggest using Spring Integration instead or use the jpoller as is.
- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Turreta/turreta-jpoller/issues/1#issuecomment-444474 451 , or mute the thread https://github.com/notifications/unsubscribe-auth/AA6iP79K79EQFLXvjwcsm VvUITF2-jw0ks5u18FigaJpZM4Y9UXn . https://github.com/notifications/beacon/AA6iP9npgs7R_nLjadGjYXoArb7O4W6 Oks5u18FigaJpZM4Y9UXn.gif
I have been in touch with the original developer Cristiano Sadun. He is pretty busy with other stuff now but I suggested he create an 'official' JPoller GitHub repo and he has now down this: https://github.com/crsadun/jpoller
I am in the process of importing the current code base from SourceForge and then I plan to mavenize it and then get it deployed to a public maven repo so people can simply add it to their pom.xml for inclusion.
One issue might be the sadun utils library that it uses - he still has access to all that as well but maybe we could make a cut down version of that util library that only includes what is needed by JPoller.
I realize that you have opinions on how hard it will be to mavenize but maybe if we both put out heads together on it we can make it happen.
From: Karl San Gabriel [mailto:notifications@github.com] Sent: Wednesday, 5 December 2018 11:52 PM To: Turreta/turreta-jpoller Cc: Chris Colman; Author Subject: Re: [Turreta/turreta-jpoller] Convert to maven? (#1)
The codes and libraries are too old. Some code files aren't even remotely related to "polling" - too many unrelated files. I would suggest using Spring Integration instead or use the jpoller as is.
- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Turreta/turreta-jpoller/issues/1#issuecomment-444474 451 , or mute the thread https://github.com/notifications/unsubscribe-auth/AA6iP79K79EQFLXvjwcsm VvUITF2-jw0ks5u18FigaJpZM4Y9UXn . https://github.com/notifications/beacon/AA6iP9npgs7R_nLjadGjYXoArb7O4W6 Oks5u18FigaJpZM4Y9UXn.gif
Would you like a hand converting the project to maven?