Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Does unexported packages effect the versioning? (Version Management Tool )

Exported packages are considered as api packages.

Regards,
Vikas
------------------------------------------------------------------------
Eclipse Modeling/ PDE
IBM Rational
EGL D Block - Bangalore, India
Office Phone No : +91 - 80 - 41776506
------------------------------------------------------------------------

Inactive hide details for ilke Muhtaroglu ---11/09/2015 05:39:19 PM---I did it by step 3 : 3) Ensure that some packages are expilke Muhtaroglu ---11/09/2015 05:39:19 PM---I did it by step 3 : 3) Ensure that some packages are exported so that they are treated as API

From: ilke Muhtaroglu <ilke.muhtaroglu@xxxxxxxxx>
To: pde-dev@xxxxxxxxxxx
Date: 11/09/2015 05:39 PM
Subject: [pde-dev] Does unexported packages effect the versioning? (Version Management Tool )
Sent by: pde-dev-bounces@xxxxxxxxxxx




I did it by step 3 :

3) Ensure that some packages are exported so that they are treated as API
( In Manifest file - go to runtime tab and then select packages to export)

But Can't I have other unexported packages effect the versioning ? Or they are neglected because they wont effect the major or minor version.

http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.emf.cdo.releng.version.doc%2Fhtml%2Fguide%2FUnderstanding.html

At this link it tells about Version Management Tool, 

"Unfortunately there's nothing to help manage the micro segment, also referred to as the service segment; its correct management is quite complex. This is where the Version Management Tool, also referred to as the version manager, helps fill the void."

So If I am not exporting the package then API Tools wont help and I have to do the plugin versioning of at least the service segment 'by hand', right ?

Is this the way how you work with plugins ?

ilke

On Mon, Nov 9, 2015 at 1:23 PM, <pde-dev-request@xxxxxxxxxxx> wrote:
    Send pde-dev mailing list submissions to
                pde-dev@xxxxxxxxxxx

    To subscribe or unsubscribe via the World Wide Web, visit
                https://dev.eclipse.org/mailman/listinfo/pde-dev
    or, via email, send a message with subject or body 'help' to
                pde-dev-request@xxxxxxxxxxx

    You can reach the person managing the list at
                pde-dev-owner@xxxxxxxxxxx

    When replying, please edit your Subject line so it is more specific
    than "Re: Contents of pde-dev digest..."


    Today's Topics:

       1. Re: How to set the baseline for developed plugins and to get
          versioning error for them ? (Vikas Chandra)


    ----------------------------------------------------------------------

    Message: 1
    Date: Mon, 9 Nov 2015 15:42:27 +0530
    From: "Vikas Chandra" <    Vikas.Chandra@xxxxxxxxxx>
    To: "Eclipse PDE general developers list." <    pde-dev@xxxxxxxxxxx>
    Subject: Re: [pde-dev] How to set the baseline for developed plugins
            and to get versioning error for them ?
    Message-ID: <    201511091022.tA9AMZY8018543@xxxxxxxxxxxxxxxxxx>
    Content-Type: text/plain; charset="iso-8859-1"


    Hi ilke,

    1) Ensure that the plugin project has api tool set up ( project ->Plugin-in
    Tools-> API Tools Set Up)
    2) Ensure that all api tool preference are set properly preference page
    (  Plugin Development - >API error/warnings  ) . Set error in all relevant
    tabs
    3) Ensure that some packages are exported so that they are treated as API
    ( In Manifest file - go to runtime tab and then select packages to export)
    4) Set the baseline as you have done

    I did 1 to 4 and then I got. Use quickfix ( right click on error and select
    quickfix) to do version management.






    Regards,
    Vikas
    ------------------------------------------------------------------------
    Eclipse Modeling/ PDE
    IBM Rational
    EGL D Block - Bangalore, India
    Office Phone No :     +91 - 80 - 41776506
    ------------------------------------------------------------------------



    From:   ilke Muhtaroglu <    ilke.muhtaroglu@xxxxxxxxx>
    To:     "    pde-dev@xxxxxxxxxxx" <pde-dev@xxxxxxxxxxx>
    Date:   11/09/2015 02:01 PM
    Subject:        [pde-dev] How to set the baseline for developed plugins and to
                get versioning error for them ?
    Sent by:            pde-dev-bounces@xxxxxxxxxxx



    Hi,
    at this link of eclipse

    http://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Ftasks%2Fapi_tooling_compare_to_baseline.htm

    ?it says "
          Click?Browse...?and select the root folder of the Eclipse SDK you
          want to choose as your baseline"



    I want to use API Tools for the plugins I create. I want to easen updating
    the version numbers of plugins. Hence I set the baseline as workspace of
    the plugins. And Eclipse found the plugins I develop and I added it as
    baseline. But it didn't work too. I don't get an version update error for
    plugins when I add a public class with public methods. I use the default
    settings they are set to give error under version tab of PDE Preferences.

    Previously I set the root folder of eclipse as stated at link but that
    didnt help. When I choose the eclipse root folder as baseline I see the
    eclipse plugins and I can set it as baseline. When I go to source folder of
    the plugin and say "compare with" ?"APIbaseline..." and choose the default
    baseline it says "No changes have been found".

    I can attach any screen shot of eclipse if you want. I attached my current
    settings.

    Thanks in advance.

    Sincerely


    (See attached file: EclipsePDE_APITools_APIBaseline.png)
    _______________________________________________
    pde-dev mailing list
    pde-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe
    from this list, visit
    https://dev.eclipse.org/mailman/listinfo/pde-dev
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <    https://dev.eclipse.org/mailman/private/pde-dev/attachments/20151109/d58f9ca6/attachment.html>
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: 0E599249.gif
    Type: image/gif
    Size: 46459 bytes
    Desc: not available
    URL: <    https://dev.eclipse.org/mailman/private/pde-dev/attachments/20151109/d58f9ca6/attachment.gif>
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: graycol.gif
    Type: image/gif
    Size: 105 bytes
    Desc: not available
    URL: <    https://dev.eclipse.org/mailman/private/pde-dev/attachments/20151109/d58f9ca6/attachment-0001.gif>
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: EclipsePDE_APITools_APIBaseline.png
    Type: image/png
    Size: 149977 bytes
    Desc: not available
    URL: <    https://dev.eclipse.org/mailman/private/pde-dev/attachments/20151109/d58f9ca6/attachment.png>

    ------------------------------

    _______________________________________________
    pde-dev mailing list
    pde-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/pde-dev

    End of pde-dev Digest, Vol 122, Issue 7
    ***************************************
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pde-dev

Back to the top