Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Hello, and questions about preparing a bundle for orbit


> And I have a question about the version number, in the original
> library, version number is not obvious and could be related to "2007.10.20
> beta ". For instant I put "0.1.0.qualifier", but I would like to
> have a confirmation that I am in the good way. And because it is a
> beta version,


I think 0.1.0.qualifier would be good, under the circumstances. You might work with that project, and encourage them to adopt an OSGi friendly versioning .... or, if they intend to always use the timestamp approach. For example, you might ask them how their version number would signify "new function" vs. "service" vs. "breaking API change". Perhaps you can help "educate" them on the merits of OSGi versioning? :)

> I would like to know if I need to put "Incubation" in
> bundle's name as required for eclipse projects.

No. But a "note" needs to be made in the IP Log xml file (I forget if its a separate element, or literally in the note element, but hopefully you'll see an example, with that hint).

> Another question about the namespace, originally it is only
> "prefuse", I would like to keep it as it is only for packages for
> backward compatibility, however I would prefer to name the bundle
> project "org.prefuse"

I think the conventions would dictate "prefuse". Again, you might work with the project authors, and ask why they picked such a non-standard package naming pattern. If they plan to stick with that, I'd stay with "prefuse". If, for example, they say in next release they plan to use "org.prefuse", then I think it'd be ok to use that as the bundle name now, even though wouldn't match current packages.

HTH





From: GBarbier@xxxxxxxxxxxxxxxx
To: orbit-dev@xxxxxxxxxxx
Date: 02/17/2010 10:05 AM
Subject: [orbit-dev] Hello, and questions about preparing a bundle for orbit
Sent by: orbit-dev-bounces@xxxxxxxxxxx





Hello guys,

In the process of "orbitization" for a third party library, I have filled a CQ for the Prefuse visualization toolkit (see
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=3702).
It has been accepted for the parallel IP process and I'm building the bundle for it.


And I have a question about the version number, in the original library, version number is not obvious and could be related to "
2007.10.20 beta ". For instant I put "0.1.0.qualifier", but I would like to have a confirmation that I am in the good way. And because it is a beta version, I would like to know if I need to put "Incubation" in bundle's name as required for eclipse projects.
Another question about the namespace, originally it is only "prefuse", I would like to keep it as it is only for packages for backward compatibility, however I would prefer to name the bundle project "org.prefuse"


I guess you would like to have more details about this library and its usage in our project:

So, Prefuse provides optimized data structures for tables, graphs, and trees. It is in Swing, but could be easily embed into SWT editors (as we did). The original project website =
http://prefuse.org/

The project I am working as committer is the MoDisco project, our purpose is to provide a framework to get models of legacy applications, and to address in general the modernization problem (refactoring, migration, reverse documentation, etc.) See more on
project site or wiki.
We use Prefuse to get cool and sexy graph to represent method calls, inheritance tree, etc.


Regards,
Gabriel Barbier
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev



Back to the top