Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Voicetools » Deploying VTP updates - but need a little direction
Deploying VTP updates - but need a little direction [message #15899] Tue, 05 September 2006 15:11 Go to next message
Stan Rivera is currently offline Stan Rivera
Messages: 36
Registered: July 2009
Member
I am in the process of adding some customization to the VTP development
environment. My changes involve adding an <extension> to the
org.ecilpse.vtp.editor.vxml.ui plug-in (i.e., making changes to the
plugin.xml and plugin.properties files) and the exension point is
org.eclipse.wst.common.snippets.SnippetContributions, since I am adding
some VXML custom snippets. I seem to have that working (and will be
sending an email to vtp-dev for future reference), but now need a little
direction on my next step and had a few questions.

1) For this extension to the org.ecilpse.vtp.editor.vxml.ui plug-in, how
do I package up my new changes? I'm thinking I will use the Project
Wizard, but I wasn't sure which project-type to pick under Plug-in
Development section?
2) When I check stuff out from the repository that will not be checked-in
since they are for internal usage only, do you ever have to check it in?
3) Is there a away to uncheck-out stuff from the repository, or is that
necessary?

Thanks,
Stan
Re: Deploying VTP updates - but need a little direction [message #15916 is a reply to message #15899] Tue, 05 September 2006 15:50 Go to previous messageGo to next message
Eclipse User
Originally posted by: bdmetz.us.ibm.com.spam

Hi,

Good to hear things are going well. When you create the plug-in project, you
should just be able to create one with the defaults and be ok. Once the
plugin is created you'll need to edit its plugin.xml and plug in whatever
code/snippets you need to. In terms of dealing with the checked out source
code, you are fine -- it doesn't need to be checked in or permanently
checked out.

"Stan Rivera" <stan.rivera@verizonbusiness.com> wrote in message
news:cc45d74a1c2846c65eff1680f5b2591d$1@www.eclipse.org...
>I am in the process of adding some customization to the VTP development
>environment. My changes involve adding an <extension> to the
>org.ecilpse.vtp.editor.vxml.ui plug-in (i.e., making changes to the
>plugin.xml and plugin.properties files) and the exension point is
>org.eclipse.wst.common.snippets.SnippetContributions, since I am adding
>some VXML custom snippets. I seem to have that working (and will be
>sending an email to vtp-dev for future reference), but now need a little
>direction on my next step and had a few questions.
> 1) For this extension to the org.ecilpse.vtp.editor.vxml.ui plug-in, how
> do I package up my new changes? I'm thinking I will use the Project
> Wizard, but I wasn't sure which project-type to pick under Plug-in
> Development section?
> 2) When I check stuff out from the repository that will not be checked-in
> since they are for internal usage only, do you ever have to check it in?
> 3) Is there a away to uncheck-out stuff from the repository, or is that
> necessary?
>
> Thanks,
> Stan
>
Re: Deploying VTP updates - but need a little direction [message #15934 is a reply to message #15916] Tue, 05 September 2006 17:17 Go to previous messageGo to next message
Stan Rivera is currently offline Stan Rivera
Messages: 36
Registered: July 2009
Member
Thanks for your comments. If I may further clarify:
1) So, to incorporate my updates (i.e., updates to the
org.ecilpse.vtp.editor.vxml.ui plug-in), the way to do it is to create a
plug-in project or is this the only way to do it?
2) The reason I ask question 1) is because currently I have the plug-in
checked out and have my current changes in the plug.xml file. I thought
another option was to now right-click on the plug-in in the Project
Explorer and export it as on of the options under the Plug-in Development
folder (Deployable feature, Deployable plug-ins and fragments or Eclipse
product).

I also had a couple of more questions:
1) I plan on adding a help plug-in and on branding my updates (for
internal and external, i.e., customer facing, usage). Will I be doing a
Feature Project to incorporate my extensions to the snippets and the
corresponding help and branding stuff?
2) In doing what I want to do here (add capabilities to Eclipse for
internal and customer facing usage), do I need to get any special
permission or deal with any licensing issues for this type of branding? I
say this type of branding because the features I am using will only be
valid for users (internal or customer facing) developing against the
VerizonBusiness speech platform.

Thanks again!

Stan
Re: Deploying VTP updates - but need a little direction [message #15952 is a reply to message #15934] Wed, 13 September 2006 19:35 Go to previous messageGo to next message
Eclipse User
Originally posted by: bdmetz.us.ibm.com.spam

Hi Stan,

Sorry for the delay - I was on vacation.

If you modify one of the VTP plugins, you should have it in your workspace
as a plug-in project checked out from CVS, which sounds like what you
currently have. In terms of packaging your changes, I would suggest you
redistribute the entire VTP modified as you need it (ie with plugin changes)
to your userbase and add your new help to a new plugin and a new feature.

The EPL's terms should be read and evaluated internally, but I personally
understand that if you modify any EPL plugins you should contribute the
changes back if you plan to distribute the compiled changes outside of your
corporation. Since the changes are probably specialized to your organization
you can feel free to post a patch to this newsgroup if you ever do so.

"Stan Rivera" <stan.rivera@verizonbusiness.com> wrote in message
news:c18a241aa06e0ff48b19d097ccb6bb03$1@www.eclipse.org...
> Thanks for your comments. If I may further clarify:
> 1) So, to incorporate my updates (i.e., updates to the
> org.ecilpse.vtp.editor.vxml.ui plug-in), the way to do it is to create a
> plug-in project or is this the only way to do it?
> 2) The reason I ask question 1) is because currently I have the plug-in
> checked out and have my current changes in the plug.xml file. I thought
> another option was to now right-click on the plug-in in the Project
> Explorer and export it as on of the options under the Plug-in Development
> folder (Deployable feature, Deployable plug-ins and fragments or Eclipse
> product).
>
> I also had a couple of more questions:
> 1) I plan on adding a help plug-in and on branding my updates (for
> internal and external, i.e., customer facing, usage). Will I be doing a
> Feature Project to incorporate my extensions to the snippets and the
> corresponding help and branding stuff?
> 2) In doing what I want to do here (add capabilities to Eclipse for
> internal and customer facing usage), do I need to get any special
> permission or deal with any licensing issues for this type of branding? I
> say this type of branding because the features I am using will only be
> valid for users (internal or customer facing) developing against the
> VerizonBusiness speech platform.
>
> Thanks again!
>
> Stan
>
Re: Deploying VTP updates - but need a little direction [message #15970 is a reply to message #15952] Wed, 20 September 2006 15:52 Go to previous message
Stan Rivera is currently offline Stan Rivera
Messages: 36
Registered: July 2009
Member
Brent,
Thanks for getting back to me, hope you had a great vacation. Well, I
think I finally figured out what I should be doing, guess that's what
happens once you get your feet wet - :), albeit I was in the process of
getting them wet, just my shoes were very well insulated. I have a few
questions, but first, here's what I have so far:
1) I created a several new plug-ins:
a) com.<company>.speechtools - This plug-in holds all my branding stuff.
b) com.<company>.speechtools.doc - This plug-in holds my documentation
stuff.
c) com.<company>.speechtools.vxml.ui - This plug-in has my Snippet
extension to the SnippetsContribution plug-in which contain custom VXML
that are only applicable to my company's speech platform.
2) I created a feature (com.<company>.speechtools.feature) for these
plug-ins.
3) I created an update site project (com.<company>.speechtools.update) so
users can update these plug-ins from my website.

As you can see, I am no longer extending any of the VTP plug-ins. With
that said, I had a couple of questions:
1) I don't if this new approach changes your previous answer about
licensing, but to do what I am showing above, do I need any special
license or approval from the Eclipse foundation?
2) I plan on redistributing this branded version of Eclipse to users
developing speech platform. Am I required to submit my plug-ins to the
VTP repository?
3) Is my version of Eclipse considered a "commercial" release and
therefore needs to comply to the EPL?
4) For my license files, is there a template I need to follow or since
this branded version is free, can I merely put "This product is free." in
the license file?

Any input you might have would greatly appreciated. However, if you need
to redirect me to the proper forum, that would be fine, too.

Thanks again!

Stan
Re: Deploying VTP updates - but need a little direction [message #575425 is a reply to message #15899] Tue, 05 September 2006 15:50 Go to previous message
Eclipse User
Originally posted by: bdmetz.us.ibm.com.spam

Hi,

Good to hear things are going well. When you create the plug-in project, you
should just be able to create one with the defaults and be ok. Once the
plugin is created you'll need to edit its plugin.xml and plug in whatever
code/snippets you need to. In terms of dealing with the checked out source
code, you are fine -- it doesn't need to be checked in or permanently
checked out.

"Stan Rivera" <stan.rivera@verizonbusiness.com> wrote in message
news:cc45d74a1c2846c65eff1680f5b2591d$1@www.eclipse.org...
>I am in the process of adding some customization to the VTP development
>environment. My changes involve adding an <extension> to the
>org.ecilpse.vtp.editor.vxml.ui plug-in (i.e., making changes to the
>plugin.xml and plugin.properties files) and the exension point is
>org.eclipse.wst.common.snippets.SnippetContributions, since I am adding
>some VXML custom snippets. I seem to have that working (and will be
>sending an email to vtp-dev for future reference), but now need a little
>direction on my next step and had a few questions.
> 1) For this extension to the org.ecilpse.vtp.editor.vxml.ui plug-in, how
> do I package up my new changes? I'm thinking I will use the Project
> Wizard, but I wasn't sure which project-type to pick under Plug-in
> Development section?
> 2) When I check stuff out from the repository that will not be checked-in
> since they are for internal usage only, do you ever have to check it in?
> 3) Is there a away to uncheck-out stuff from the repository, or is that
> necessary?
>
> Thanks,
> Stan
>
Re: Deploying VTP updates - but need a little direction [message #575452 is a reply to message #15916] Tue, 05 September 2006 17:17 Go to previous message
Stan Rivera is currently offline Stan Rivera
Messages: 36
Registered: July 2009
Member
Thanks for your comments. If I may further clarify:
1) So, to incorporate my updates (i.e., updates to the
org.ecilpse.vtp.editor.vxml.ui plug-in), the way to do it is to create a
plug-in project or is this the only way to do it?
2) The reason I ask question 1) is because currently I have the plug-in
checked out and have my current changes in the plug.xml file. I thought
another option was to now right-click on the plug-in in the Project
Explorer and export it as on of the options under the Plug-in Development
folder (Deployable feature, Deployable plug-ins and fragments or Eclipse
product).

I also had a couple of more questions:
1) I plan on adding a help plug-in and on branding my updates (for
internal and external, i.e., customer facing, usage). Will I be doing a
Feature Project to incorporate my extensions to the snippets and the
corresponding help and branding stuff?
2) In doing what I want to do here (add capabilities to Eclipse for
internal and customer facing usage), do I need to get any special
permission or deal with any licensing issues for this type of branding? I
say this type of branding because the features I am using will only be
valid for users (internal or customer facing) developing against the
VerizonBusiness speech platform.

Thanks again!

Stan
Re: Deploying VTP updates - but need a little direction [message #575504 is a reply to message #15934] Wed, 13 September 2006 19:35 Go to previous message
Eclipse User
Originally posted by: bdmetz.us.ibm.com.spam

Hi Stan,

Sorry for the delay - I was on vacation.

If you modify one of the VTP plugins, you should have it in your workspace
as a plug-in project checked out from CVS, which sounds like what you
currently have. In terms of packaging your changes, I would suggest you
redistribute the entire VTP modified as you need it (ie with plugin changes)
to your userbase and add your new help to a new plugin and a new feature.

The EPL's terms should be read and evaluated internally, but I personally
understand that if you modify any EPL plugins you should contribute the
changes back if you plan to distribute the compiled changes outside of your
corporation. Since the changes are probably specialized to your organization
you can feel free to post a patch to this newsgroup if you ever do so.

"Stan Rivera" <stan.rivera@verizonbusiness.com> wrote in message
news:c18a241aa06e0ff48b19d097ccb6bb03$1@www.eclipse.org...
> Thanks for your comments. If I may further clarify:
> 1) So, to incorporate my updates (i.e., updates to the
> org.ecilpse.vtp.editor.vxml.ui plug-in), the way to do it is to create a
> plug-in project or is this the only way to do it?
> 2) The reason I ask question 1) is because currently I have the plug-in
> checked out and have my current changes in the plug.xml file. I thought
> another option was to now right-click on the plug-in in the Project
> Explorer and export it as on of the options under the Plug-in Development
> folder (Deployable feature, Deployable plug-ins and fragments or Eclipse
> product).
>
> I also had a couple of more questions:
> 1) I plan on adding a help plug-in and on branding my updates (for
> internal and external, i.e., customer facing, usage). Will I be doing a
> Feature Project to incorporate my extensions to the snippets and the
> corresponding help and branding stuff?
> 2) In doing what I want to do here (add capabilities to Eclipse for
> internal and customer facing usage), do I need to get any special
> permission or deal with any licensing issues for this type of branding? I
> say this type of branding because the features I am using will only be
> valid for users (internal or customer facing) developing against the
> VerizonBusiness speech platform.
>
> Thanks again!
>
> Stan
>
Re: Deploying VTP updates - but need a little direction [message #575531 is a reply to message #15952] Wed, 20 September 2006 15:52 Go to previous message
Stan Rivera is currently offline Stan Rivera
Messages: 36
Registered: July 2009
Member
Brent,
Thanks for getting back to me, hope you had a great vacation. Well, I
think I finally figured out what I should be doing, guess that's what
happens once you get your feet wet - :), albeit I was in the process of
getting them wet, just my shoes were very well insulated. I have a few
questions, but first, here's what I have so far:
1) I created a several new plug-ins:
a) com.<company>.speechtools - This plug-in holds all my branding stuff.
b) com.<company>.speechtools.doc - This plug-in holds my documentation
stuff.
c) com.<company>.speechtools.vxml.ui - This plug-in has my Snippet
extension to the SnippetsContribution plug-in which contain custom VXML
that are only applicable to my company's speech platform.
2) I created a feature (com.<company>.speechtools.feature) for these
plug-ins.
3) I created an update site project (com.<company>.speechtools.update) so
users can update these plug-ins from my website.

As you can see, I am no longer extending any of the VTP plug-ins. With
that said, I had a couple of questions:
1) I don't if this new approach changes your previous answer about
licensing, but to do what I am showing above, do I need any special
license or approval from the Eclipse foundation?
2) I plan on redistributing this branded version of Eclipse to users
developing speech platform. Am I required to submit my plug-ins to the
VTP repository?
3) Is my version of Eclipse considered a "commercial" release and
therefore needs to comply to the EPL?
4) For my license files, is there a template I need to follow or since
this branded version is free, can I merely put "This product is free." in
the license file?

Any input you might have would greatly appreciated. However, if you need
to redirect me to the proper forum, that would be fine, too.

Thanks again!

Stan
Previous Topic:Deploying VTP updates - but need a little direction
Next Topic:Auto-generated VXML from creating "new" VXML file incorrect
Goto Forum:
  


Current Time: Tue Sep 16 09:45:22 GMT 2014

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

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