Commits on Oct 24, 2017
  1. 526432: Virgo tools do not remove unit letter when making repository...

    giamma committed Oct 24, 2017
    The Tools now force the unit to null when making a path relative.
  2. Merge branch 'feature/510327'

    giamma committed Oct 24, 2017
Commits on May 16, 2017
  1. 510327: Virgo server reports on Windows 10

    giamma committed May 16, 2017
    Temporarily revert Virgo Server P2 repository change as it prevents
    installation on Neon due to uses-conflict on slf4j.
Commits on Apr 19, 2017
  1. 510327: Virgo server reports on Windows 10

    giamma committed Apr 19, 2017
    Tentatively change from win32 to "Windows 8"
  2. #513489 Wrong P2 repository in pom.xml

    giamma committed Apr 19, 2017
    Change pom.xml to use 3.7.0.RELEASE Virgo Server repo.
Commits on Feb 24, 2017
Commits on Feb 23, 2017
Commits on Feb 20, 2017
  1. Build against neon.

    giamma committed Feb 20, 2017
    Tentative change to work around failing test on jenkins.
  2. Add null check.

    giamma committed Feb 20, 2017
Commits on Feb 4, 2017
  1. #511687: ResourceException below ServerProject.deleteWorkspaceProject

    giamma committed Feb 4, 2017
    (thrown in Resource.delete) 
    Add null check to prevent NPE.
Commits on Jan 27, 2017
  1. Error reporting improvements.

    giamma committed Jan 27, 2017
Commits on Jan 9, 2017
  1. Organize imports

    giamma committed Jan 9, 2017
Commits on Jan 5, 2017
  1. 486353: Virgo 3.7 and 3.6.x does not support native library on Windows

    giamma committed Jan 5, 2017
    8.1 and Windows 10 
    Change Virgo35Provider to set system property on Windows
Commits on Jan 2, 2017
  1. 509809: Remove SpringSource Enterprise Bundle Repository browser from

    giamma committed Jan 2, 2017
    Server Editor 
    SpringSource repository browser removed from editor.
Commits on Jan 1, 2017
  1. 509803: Runtime wizard should use relative paths when updating

    giamma committed Jan 1, 2017
    repository properties file 
    Originally the Virgo tools where adding new folders to the repository
    properties file as absolute path.
    Now the tools use paths relative to the Virgo home when possible.
Commits on Dec 8, 2016
  1. Merge branch 'feature/499979'

    giamma committed Dec 8, 2016
Commits on Oct 31, 2016
  1. 499979: Deployment of nested plans fails

    giamma committed Oct 31, 2016
    Re-apply some lost changes.
Commits on Oct 27, 2016
  1. 499979: Deployment of nested plans fails

    giamma committed Oct 27, 2016
    UI improvements:
    - add plan file name validation
    - open newly created plan file in editor when wizard closes
Commits on Oct 26, 2016
  1. 499979: Deployment of nested plans fails

    giamma committed Oct 26, 2016
    Tentative fix:
    - change ServerModuleDelegate to properly recurse into children
    - change Server to properly compute IModuleResource(s) 
    - add a new wizard for creating plan project and plan file
Commits on Aug 21, 2016
  1. 499979: Deployment of nested plans fails

    giamma committed Aug 21, 2016
    Originally, if a top-level plan referred to another plan the deployment
    of the top-level plan would fail because the tooling did not take into
    account the nested plan when deploying the top-level plan.
    Now nested plans are supported:
    - JmxServerDeployCommand parses the top-level plan to look for
      references to nested plans
    - If found, nested plans are copied to the stage directory before
      deploying the top-level plan
    Implementaiton details
    The code tries to deal with the case that plans are distributed across
    the workspace in multiple projects. If the top-level plan is contained
    in a Java project and such Java project depends on other Java projects,
    the project dependencies will be scanned in the proper class-path order
    when looking for nested plans and in case of duplicates, the first
    matching plan found in the cass-path will be used.
    If the project containing the top-level project is not a Java project,
    nested plans will be searched only within the top-level project.
    While the tooling do their best to support plans, please not that the
    above only accounts for the most typical use cases and that certain
    corner cases won't be optimally managed. For example, if a nested plan
    is changed the server will not be able to detect this and auto-publish
    the nested plan and refresh the top-level plan. The user who changed the
    nested plan will have to un-deploy and re-deploy the top-level plan to
    see the change. The modified nested plan will however be picked at the
    next server restart.
    This limitation exists because currently the Tools do not create a WST
    module for the whole project containing the plan, but rather a WST
    module for the plan file only. This design choice implies that the WST
    infrastructure will be tracking workspace changes related to the
    top-level plan file only. To change this behavior a significant rewrite
    would be required and the effort is in my opinion not worth the benefit.
Commits on Jun 15, 2016
Commits on Jun 14, 2016
Commits on Jun 13, 2016
  1. Merge branch 'feature/495981'

    giamma committed Jun 13, 2016
  2. Add Neon Launch configuration

    giamma committed Jun 13, 2016
Commits on Jun 11, 2016
Commits on May 29, 2016
  1. Update tooling documentation.

    giamma committed May 29, 2016
Commits on Apr 17, 2016
  1. Bug #491869 Action for converting PDE plug-in projects to Virgo...

    giamma committed Apr 17, 2016
    Improve action visibility and enablement conditions.