Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] Status of Virgo 3.7 support in Virgo Tools
Hi Dani,

The old nature id was part of my personal PDE2Virgo project not related to Eclipse Virgo. In other words, it was not a feature offered out-of-the-box by the Virgo tools, so I am not really breaking compatibility here, just adding a new feature.

This said, I am also fine with a 2.0 version if we agree that's the right number, but it's not really a big leap from 1.1. The new features since 1.1 are:
  • Bug fixes in the tools
  • Some improvements in the Virgo Server Editor
  • PDE support
Does this look enough for a 2.0 version?

Whichever the version number. the key point for me is to have a stable build officially published because several people now believe that the Virgo Tools are unmaintained and I would like to pass a different message. Maybe 1.5 would be better than 1.2 in this sense.

Giamma.

On Wed, Feb 10, 2016 at 9:30 AM Daniel Marthaler <DMarthaler@xxxxxxx> wrote:
Hi GianMaria,
 
Perfect, thank you for the insights.
Regarding the versioning, wouldn't it be better to go for 2.0 instead of 1.2? As you changed the name of the project nature.
 
I hope I will be able to invest some time for Virgo and the Tooling during February, then I will test the Tooling and start solving some of the reported issues on Bugzilla.
Also I want to try out the way you described to work with PDE/VirgoTooling/Maven/Tycho, as this could be a possibility how we will do projects when using Virgo in future.
 
Regards,
Dani
 
Gesendet: Dienstag, 09. Februar 2016 um 09:27 Uhr
Von: Giamma <gm.romanato@xxxxxxxxx>
An: "Virgo Project" <virgo-dev@xxxxxxxxxxx>
Betreff: Re: [virgo-dev] Status of Virgo 3.7 support in Virgo Tools
Hi Dani,
 
a migration action is in my TODO list, it's just lower priority than other items.
I still have to:
  • sort out the installation issue on Mars
  • bump the version number in master. By the way, we should decide the new version number. I think we are currently at 1.1,  so it should probably be 1.2.
  • update user documentation
  • merge everything into master once you guys confirm me that the java7 support branch is working properly
  • add the migration action
  • evaluate the possibility of converting the kernel-tools project into an Eclipse plug-in for inclusion in the IDE feature. Do you know whether the Virgo Runtime uses kernel-tools or is it only used by the IDE?
GianMaria.
 
 
On Tue, Feb 9, 2016 at 7:31 AM Daniel Marthaler <DMarthaler@xxxxxxx> wrote:
Hi GianMaria
 
This sounds great.
Would it also be possible to support a migration scenario for "old" Virgo/PDE2Virgo Projects to the new project nature you've introduced in the feature/329198 branch.
 
Regards,
Dani
 
Gesendet: Sonntag, 07. Februar 2016 um 22:33 Uhr
Von: Giamma <gm.romanato@xxxxxxxxx>
An: "“virgo-dev@xxxxxxxxxxx”" <virgo-dev@xxxxxxxxxxx>
Betreff: [virgo-dev] Status of Virgo 3.7 support in Virgo Tools
 
Dear all,
 
I made the following changes in accordance with the decision to name the Java 7 profile file as "java-server.profile".
 
kernel-tools
I changed org.eclipse.virgo.kernel.tools.internal.SystemPackageFilteringRepository in org.eclipse.virgo.kernel-tools repository to now look for "java-server.profile" and fall back to "java6-server.profile" if not found. This change is pushed to master of the kernel-tools repository.

ide
I built kernel-tools master from the command line using the included ant + ivy scripts and committed the binary JAR and the source JAR into the lib folder of the org.eclipse.virgo.ide.manifest.core bundle (this is just an update, the manifest.core bundle already contained the kernel-tools JARs) in the "support-java-7-profile" branch. In the same branch, I changed the initial implementation of Virgo37Provider written by Florian to now use the $VIRGO_HOME/lib/.version file to detect the Virgo version.
Based on my tests, the Virgo tools in branch "support-java-7-profile" seem now to support properly Virgo 3.7 as long as the profile file is named as we agreed. However, since I could not find a Virgo 3.7 build already containing the profile file with name "java-server.profile", to test that everything worked as expected I took the latest Virgo 3.7 build and copied the java7-server.profile file into java-server.profile.
 
Notes about branches:
I'll wait for the profile name to be changed as discussed in the runtime, then I'd like to merge everything into master. It would be great if you could test to the support-java-7-profile branch.
 
GianMaria.
 
 
 
_______________________________________________ virgo-dev mailing list virgo-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________ virgo-dev mailing list virgo-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev

Back to the top