Home » Eclipse Projects » DTP » Ecore ODA provider packaging
|
Re: Ecore ODA provider packaging [message #32476 is a reply to message #32406] |
Tue, 10 July 2007 19:57 |
Linda Chan Messages: 845 Registered: July 2009 |
Senior Member |
|
|
Jeff,
I think the "org.eclipse" prefix would apply only when the source
contribution are ready to go thru the Eclipse process of review and
approval. Eclipse requires certain process, including IP legal review, for
any source contribution and may take a while. In the mean time, it can be
distributed under the non-eclipse name by contributor's own download site
and/or source repository. DTP welcomes different levels of contribution
from the community, and will be happy to post them in DTP's community page:
http://www.eclipse.org/datatools/community.html .
It is thus a good idea to first use a non-eclipse name for your oda
extension id in the interim. Renaming the plugin and package names with
the IDE are quite straight-forward anyway.
After the name is changed, to avoid changing your product that consumes the
interim name, you can simply add a thin plugin that implements the
oda.consumer.driverBridge extension point to bridge the interim oda
extension id to the renamed extension id.
For the eventual source contribution to DTP, it would fall in the DTP
Enablement sub-project category:
http://www.eclipse.org/datatools/project_enablement/index.ht ml .
And all the ODA enablement plugins distributed by DTP use the prefix
"org.eclipse.datatools.enablement.oda." , e.g.
org.eclipse.datatools.enablement.oda.ecore .
Linda
"Jeff Ramsdale" <jeff.ramsdale@gmail.com> wrote in message
news:f70hld$p5q$1@build.eclipse.org...
> As mentioned in another thread, I'm attempting to write an Ecore ODA
> provider. While this may be overly ambitious of me and I don't want to be
> presumptuous concerning it's future at the Eclipse Foundation, I do want
> to package it appropriately for consideration, assuming I'm successful. I
> also want to remove references to the client whose project this serves
> (with their blessing, of course).
>
> As such, should I attempt to follow the FlatFile pattern and use
> 'org.eclipse.datatools.connectivity.oda.ecore' as my plugin name? Or is
> the expectation that I provide it under my own nomenclature and after
> acceptance it is repackaged for inclusion?
>
> Jeff
|
|
|
Re: Ecore ODA provider packaging [message #32580 is a reply to message #32476] |
Wed, 11 July 2007 00:05 |
Jeff Ramsdale Messages: 122 Registered: July 2009 |
Senior Member |
|
|
I've read up a bit on the contribution process, so this was my
expectation. Thanks for clarifying!
-Jeff
Linda Chan wrote:
> Jeff,
>
> I think the "org.eclipse" prefix would apply only when the source
> contribution are ready to go thru the Eclipse process of review and
> approval. Eclipse requires certain process, including IP legal review, for
> any source contribution and may take a while. In the mean time, it can be
> distributed under the non-eclipse name by contributor's own download site
> and/or source repository. DTP welcomes different levels of contribution
> from the community, and will be happy to post them in DTP's community page:
> http://www.eclipse.org/datatools/community.html .
>
> It is thus a good idea to first use a non-eclipse name for your oda
> extension id in the interim. Renaming the plugin and package names with
> the IDE are quite straight-forward anyway.
> After the name is changed, to avoid changing your product that consumes the
> interim name, you can simply add a thin plugin that implements the
> oda.consumer.driverBridge extension point to bridge the interim oda
> extension id to the renamed extension id.
>
> For the eventual source contribution to DTP, it would fall in the DTP
> Enablement sub-project category:
> http://www.eclipse.org/datatools/project_enablement/index.ht ml .
> And all the ODA enablement plugins distributed by DTP use the prefix
> "org.eclipse.datatools.enablement.oda." , e.g.
> org.eclipse.datatools.enablement.oda.ecore .
>
> Linda
|
|
|
Re: Ecore ODA provider packaging [message #586413 is a reply to message #32406] |
Tue, 10 July 2007 19:57 |
Linda Chan Messages: 845 Registered: July 2009 |
Senior Member |
|
|
Jeff,
I think the "org.eclipse" prefix would apply only when the source
contribution are ready to go thru the Eclipse process of review and
approval. Eclipse requires certain process, including IP legal review, for
any source contribution and may take a while. In the mean time, it can be
distributed under the non-eclipse name by contributor's own download site
and/or source repository. DTP welcomes different levels of contribution
from the community, and will be happy to post them in DTP's community page:
http://www.eclipse.org/datatools/community.html .
It is thus a good idea to first use a non-eclipse name for your oda
extension id in the interim. Renaming the plugin and package names with
the IDE are quite straight-forward anyway.
After the name is changed, to avoid changing your product that consumes the
interim name, you can simply add a thin plugin that implements the
oda.consumer.driverBridge extension point to bridge the interim oda
extension id to the renamed extension id.
For the eventual source contribution to DTP, it would fall in the DTP
Enablement sub-project category:
http://www.eclipse.org/datatools/project_enablement/index.ht ml .
And all the ODA enablement plugins distributed by DTP use the prefix
"org.eclipse.datatools.enablement.oda." , e.g.
org.eclipse.datatools.enablement.oda.ecore .
Linda
"Jeff Ramsdale" <jeff.ramsdale@gmail.com> wrote in message
news:f70hld$p5q$1@build.eclipse.org...
> As mentioned in another thread, I'm attempting to write an Ecore ODA
> provider. While this may be overly ambitious of me and I don't want to be
> presumptuous concerning it's future at the Eclipse Foundation, I do want
> to package it appropriately for consideration, assuming I'm successful. I
> also want to remove references to the client whose project this serves
> (with their blessing, of course).
>
> As such, should I attempt to follow the FlatFile pattern and use
> 'org.eclipse.datatools.connectivity.oda.ecore' as my plugin name? Or is
> the expectation that I provide it under my own nomenclature and after
> acceptance it is repackaged for inclusion?
>
> Jeff
|
|
|
Re: Ecore ODA provider packaging [message #586438 is a reply to message #32476] |
Wed, 11 July 2007 00:05 |
Jeff Ramsdale Messages: 122 Registered: July 2009 |
Senior Member |
|
|
I've read up a bit on the contribution process, so this was my
expectation. Thanks for clarifying!
-Jeff
Linda Chan wrote:
> Jeff,
>
> I think the "org.eclipse" prefix would apply only when the source
> contribution are ready to go thru the Eclipse process of review and
> approval. Eclipse requires certain process, including IP legal review, for
> any source contribution and may take a while. In the mean time, it can be
> distributed under the non-eclipse name by contributor's own download site
> and/or source repository. DTP welcomes different levels of contribution
> from the community, and will be happy to post them in DTP's community page:
> http://www.eclipse.org/datatools/community.html .
>
> It is thus a good idea to first use a non-eclipse name for your oda
> extension id in the interim. Renaming the plugin and package names with
> the IDE are quite straight-forward anyway.
> After the name is changed, to avoid changing your product that consumes the
> interim name, you can simply add a thin plugin that implements the
> oda.consumer.driverBridge extension point to bridge the interim oda
> extension id to the renamed extension id.
>
> For the eventual source contribution to DTP, it would fall in the DTP
> Enablement sub-project category:
> http://www.eclipse.org/datatools/project_enablement/index.ht ml .
> And all the ODA enablement plugins distributed by DTP use the prefix
> "org.eclipse.datatools.enablement.oda." , e.g.
> org.eclipse.datatools.enablement.oda.ecore .
>
> Linda
|
|
|
Goto Forum:
Current Time: Thu May 02 20:48:19 GMT 2024
Powered by FUDForum. Page generated in 0.03382 seconds
|