Menu

#135 Make Workspace Setup work with Subclipse

open-fixed
5
2009-09-29
2009-09-26
jfirechief
No

DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
https://www.jfire.org/modules/bugs/view.php?id=1252
ORIGINAL REPORTER: Marc

Discussion

  • jfirechief

    jfirechief - 2009-09-26

    ORIGINAL COMMENT BY Marc, VIEW IT HERE:
    https://www.jfire.org/modules/bugs/view.php?id=1252

    Hi Marius.

    You already told me that you are working on this. Having a look at the project org.nightlabs.eclipse.sdk.adapter.svn.subclipse I saw that you are on the wrong way.

    The org.nightlabs.eclipse.sdk.adapter.svn.ISVNAdapter concept was used in the *old* Initialize Workspace process. And for that, an implementation for Subclipse was never needed as Subclipse connects existing projects automatically using the .svn meta data.

    In the new process, Eclipse's Import Project Set feature is used. Both, Subversive and Subclipse implement this feature - but in a slightly different way and for other team provider ids.

    However, the Subversive project set file (which is generated by the Product Hive) is more or less compatible to the Subclipse format. What needs to be done is to implement the extension point "org.eclipse.team.core.repository" and connect the new implementation to the project set id "org.eclipse.team.svn.core.svnnature" using the canImport attribute. The project set file must then be rewritten to the Subclipse format and the Subclipse importer can be called.

     
  • jfirechief

    jfirechief - 2009-09-26
    • labels: --> NightLabs SDK
     
  • jfirechief

    jfirechief - 2009-09-29
    • assigned_to: nobody --> onlynuwanda
    • status: open --> open-fixed
     
  • jfirechief

    jfirechief - 2009-09-29

    ORIGINAL COMMENT BY Marc, VIEW IT HERE:
    https://www.jfire.org/modules/bugs/view.php?id=1252

    Hi Marius.

    You already told me that you are working on this. Having a look at the project org.nightlabs.eclipse.sdk.adapter.svn.subclipse I saw that you are on the wrong way.

    The org.nightlabs.eclipse.sdk.adapter.svn.ISVNAdapter concept was used in the *old* Initialize Workspace process. And for that, an implementation for Subclipse was never needed as Subclipse connects existing projects automatically using the .svn meta data.

    In the new process, Eclipse's Import Project Set feature is used. Both, Subversive and Subclipse implement this feature - but in a slightly different way and for other team provider ids.

    However, the Subversive project set file (which is generated by the Product Hive) is more or less compatible to the Subclipse format. What needs to be done is to implement the extension point "org.eclipse.team.core.repository" and connect the new implementation to the project set id "org.eclipse.team.svn.core.svnnature" using the canImport attribute. The project set file must then be rewritten to the Subclipse format and the Subclipse importer can be called.

     
  • jfirechief

    jfirechief - 2009-09-29

    ORIGINAL COMMENT BY Nuwanda, VIEW IT HERE:
    https://www.jfire.org/modules/bugs/view.php?id=1252

    Created a new Project (org.nightlabs.eclipse.sdk.wssetup.svn.subclipse) that acts as a substitute for the subversive plugin in opening the ProjectSet and converts the input to a SubClipse compatible format.

     

Log in to post a comment.

Monday.com Logo