Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Oomph Version Management - How to ?(How do you manage your plugin versions in Eclipse Manifest file ?)
Oomph Version Management - How to ? [message #1714041] Mon, 09 November 2015 14:08 Go to next message
ilke Muhtar is currently offline ilke MuhtarFriend
Messages: 47
Registered: September 2015
Member
Hi,

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."

I want to version the plugins in manifest file by the help of eclipse. I learned there is Eclipse PDE API Tooling but it helps for only exported packages at Runtime tab of plugins. How do you version the plugins in eclipse 'by hand' or do you use Eclipse PDE API Tools like tool?

Do you have any idea about this tool and how to deal with service segment ? How is this done in eclipse plugins ?

How can I use Oomph Version Management for versioning my plugins ?

ilke
Re: Oomph Version Management - How to ? [message #1714262 is a reply to message #1714041] Wed, 11 November 2015 08:31 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
Ilke,

We use the version tool with Oomph itself and I use it for EMF. But
there is effectively zero documentation, so explaining how to use it
would involve much investment in documentation. And we don't have time
for that right now. :-(

On 09/11/2015 3:08 PM, ilke Muhtaroglu wrote:
> Hi,
>
> 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."
>
> I want to version the plugins in manifest file by the help of eclipse.
> I learned there is Eclipse PDE API Tooling but it helps for only
> exported packages at Runtime tab of plugins. How do you version the
> plugins in eclipse 'by hand' or do you use Eclipse PDE API Tools like
> tool?
>
> Do you have any idea about this tool and how to deal with service
> segment ? How is this done in eclipse plugins ?
>
> How can I use Oomph Version Management for versioning my plugins ?
>
> ilke


Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Oomph Version Management - How to ? [message #1714276 is a reply to message #1714262] Wed, 11 November 2015 09:33 Go to previous messageGo to next message
ilke Muhtar is currently offline ilke MuhtarFriend
Messages: 47
Registered: September 2015
Member
I see. So how do people manage the plugin versions in eclipse community ?

I learned that we can use Eclipse PDE API Tools for managing exported packages of a plugin. Do you use it ?

So from your email I learned that you use, Oomph Version Management.

I installed the eclipse plugin of oomph. There under preferences tab there is Version Management. There is a table with Release and check mode ? Any idea about how to start using it ? I can read the source code as well if it helps. Can you please point a starting point ? Does people manage plugin version numbering 'by hand' ?
Re: Oomph Version Management - How to ? [message #1714284 is a reply to message #1714276] Wed, 11 November 2015 11:27 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
Ilke

Comments below.

On 11/11/2015 10:33 AM, ilke Muhtaroglu wrote:
> I see. So how do people manage the plugin versions in eclipse community ?
Different approaches are used. Some people just increment the minor
version of all bundles at the start of a new development cycle. Others
use API tools, but it's slow and a long of work. It's good for managing
major and minor version numbers and for ensuring binary compatibility.
>
> I learned that we can use Eclipse PDE API Tools for managing exported
> packages of a plugin. Do you use it ?
No, not even for EMF. I'm just very careful what I change...
>
> So from your email I learned that you use, Oomph Version Management.
Yes it helps me make sure I increment the minor version when I make a
change, and to ensure that this increment bubbles up to all features the
contain the bundles.
>
> I installed the eclipse plugin of oomph. There under preferences tab
> there is Version Management. There is a table with Release and check
> mode ? Any idea about how to start using it ?
Yes, you can add the version management nature via the Configure of the
context menu. The basic idea is that it computes a digest as well as
version information in at the start of a development cycle. So if you
change the content, it knows the version service must be incremented;
generally I change the minor version instead in the master branch and
the service version in the maintenance branch.
> I can read the source code as well if it helps. Can you please point a
> starting point ?
I really don't have the capacity to provide all the help that I think
will be necessary. :-(
> Does people manage plugin version numbering 'by hand' ?
Lots do, and then forget, or use brute force approaches (increment all
minor versions).


Ed Merks
Professional Support: https://www.macromodeling.com/
Previous Topic:Eclipse installation Java version
Next Topic:Importing projects with different Java-Version
Goto Forum:
  


Current Time: Sat Dec 14 13:42:04 GMT 2024

Powered by FUDForum. Page generated in 0.07355 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top