Home » Eclipse Projects » Virgo » Virgo Project wil be archived?
|
Re: Virgo Project wil be archived? [message #1111736 is a reply to message #1111602] |
Wed, 18 September 2013 17:05 |
Miles Parker Messages: 1341 Registered: July 2009 |
Senior Member |
|
|
Hi Eduardo,
I think, sadly, the message speaks for itself. If this technology is truly important for the community then someone in the community needs to step up to see it continue to be supported. So now may be the time for the user community to rise to that occasion..
Note that the level of support does not need to be that great. The fact is that Virgo works quite well for its intended purposes now. The chief need would be to coordinate and maintain builds and ensure that basic bug triage is accomplished -- ideally that would be someone familiar with Eclipse Development Process along with Virgo internals. And then there should be thought given to where the technology evolves to, and what future releases would look like, but I'm sure that there would be a lot of flexibility with respect to that.
cheers,
Miles
[Updated on: Wed, 18 September 2013 17:06] Report message to a moderator
|
|
|
Re: Virgo Project wil be archived? [message #1111795 is a reply to message #1111736] |
Wed, 18 September 2013 18:57 |
Eduardo Frazão Messages: 123 Registered: January 2012 |
Senior Member |
|
|
Hi Miles Parker! Thanks by your answer!
Only by the moviment on the forum, we can conclude that this Technology is import for many. I have 4 products heavy based on Virgo, and the bigger one is comming.
I dont see some Virgo features in any other projects.
- Spring support out of the box, and with Spring OSGi Integration
- Easy AOP support with Equinox Weaving hooks
- Gemini Projects.
- GEMINI WEB! (Goddbye Servlet http service bridges, and other things)
- Blueprint
- DB Access
- JPA Made easy with EclipseLink and Gemini
- And others as naming, etc
- Simplified Deploy Model
- Easy Logging.
- Various flavors for minimal dependencies
- More can be read here: http://www.eclipse.org/virgo/benefits/ (The ideal OSGi Server Runtime?)
Virgo was the light on the end of tunel for Enterprise OSGi Applications. (At least for me).
I think that ARCHIVE a project like that will be a big mistake, after so many efforts to it be what it is today, and right now, when it reaches the desired stability of tooling, etc. We, normal users that belive on this solution, and builds our projects based on, are very very concerned, even more when Spring simple says that they will not release Spring with OSGi metadata anymore. What is going on? . Modularity isn't anymore a concern of enterprise development?
[Updated on: Wed, 18 September 2013 19:07] Report message to a moderator
|
|
| |
Re: Virgo Project wil be archived? [message #1112324 is a reply to message #1112110] |
Thu, 19 September 2013 12:39 |
Eduardo Frazão Messages: 123 Registered: January 2012 |
Senior Member |
|
|
Well. For this point of view, seems like the Virgo, and others of this type is doomed. So... its time to revert our projects to a flat class path model? The problem for me, right now, isn't the flat classpath, but the high modular design of our solutions, totaly built around of plugins, etc.
Maybe it was written to early.
Future proof
Virgo is an open source Eclipse project with a liberal license and active participation from multiple vendors, which positions it ideally for the future.
From: http://www.eclipse.org/virgo/benefits/
[Updated on: Thu, 19 September 2013 12:43] Report message to a moderator
|
|
|
Re: Virgo Project wil be archived? [message #1112381 is a reply to message #1112324] |
Thu, 19 September 2013 15:48 |
Tin N/A Messages: 46 Registered: December 2010 |
Member |
|
|
Eduardo Frazão wrote on Thu, 19 September 2013 14:39Well. For this point of view, seems like the Virgo, and others of this type is doomed. So... its time to revert our projects to a flat class path model? The problem for me, right now, isn't the flat classpath, but the high modular design of our solutions, totaly built around of plugins, etc.
I don't think you need to migrate back if you have the whole system working in modules right now (and expertise to build on it). In the company I work for, we also have Virgo in production (in fact, still using the 3.0 version), and it'll stay in production for quite a few more years with upgrades to the functionalities as needed. Right now, I don't see any new features that we would need from Virgo to keep our system running, so in that sense Virgo really is futureproof - it already provides everything we need for the next few years. And hopefully this will be enough for the rest of the Java world to bridge the gap and the whole modularity concept becomes mainstream.
|
|
|
Re: Virgo Project wil be archived? [message #1112417 is a reply to message #1112381] |
Thu, 19 September 2013 17:06 |
Eduardo Frazão Messages: 123 Registered: January 2012 |
Senior Member |
|
|
Yes. I agree with you. Right now, i'm working on a project that is 60% done. Its is uses Spring (DI, Transaction Management, and other stuff), AOP via LTW, Gemini JPA, Snaps. I can't see this needs, supplied by another OSGi Runtime Server right now, and I cant break development, and start a transition in this moment. My concern is about possible bug fixes, IDE Tooling, etc. Spring will continue its evolution, and Virgo versions will be outdated. Even if we can upgrade minor versions of Spring, how will the major updates be applied?
Will be other Gemini Projects continued? Gemini JPA have some bugs, and Eclipselink is releasing new versions.
|
|
| | | | | |
Goto Forum:
Current Time: Tue Sep 24 06:34:03 GMT 2024
Powered by FUDForum. Page generated in 0.04406 seconds
|