|Re: [virgo-dev] Wrong bugzilla entry and other questions|
Regarding the update to Java 8 I can't see any need for a change in Virgo Tools so far. But if needs arise I will contact you asap.
I share your opinion for the Java 7 API level and that Virgo should provide a Java 7 profile. I'm currently at the point that Virgo compiles using Java 8 with source and target set to 1.8. I will check what is required to provide the Java 7 profile this week.
What could be improved on the Virgo Tooling is an integration with build tools like Gradle or Maven. I personally prefer Gradle but Maven is nowadays the most used build tool among the Java community.
At work we develop bundles using the Eclipse PDE tooling together with your PDE2Virgo plugin and Virgo Tools. This works most of the time and is nice when you wish to be able to work in a fully IDE integrated manner. But we also maintain a Gradle build script for building our bundles on our CI server.
We also looked at Bndtools but we find this to intrusive and the Manifest generation for Spring context XML files is also not working. I know such an integration would mean a huge amount of work so having your PDE2Virgo plugin integrated in the next release as you described it would be a very good starting point.