Home » Archived » Tigerstripe » Several questions as starting to use Tigerstripe
|
| Re: Several questions as starting to use Tigerstripe [message #10056 is a reply to message #10033] |
Wed, 28 May 2008 16:25   |
 Eric Dillon
Messages: 103
Registered: July 2009 |
Senior Member |
|
|
Hi Jerome,
See my comments inline.
Eric
On 5/27/08 7:18 PM, in article g1ifds$5vf$1@build.eclipse.org, "Jerome
Magnet" <jeromem@nortel.com> wrote:
> Hi All,
>
> I started using the latest Tigerstripe workbench as part of the TMF
> Interface
> Program(org.eclipse.tigerstripe.workbench.base_0.3.0.M200805 061422_incubation)
>
> I have the following questions :
>
> - Is the Eclipse Tigerstripe Help aligned with the latest version
> (Tigerstripe Workbench 2.x)?
> For example, it says TS comes with three default basic plug-ins. It was true
> before but I don't see that now.
> It seems that it does not reflect the latest TS architecture changes? I also
> still see many references to OSS/J. I thought they had been removed to make
> TS generic?
There has been few posts already in this group about this. No, the Doc is
still aligned with the old commercial version. We are working on the changes
but they won't be in place until mid-june.
I particular, the basic plugins are gone. They were VERY OLD non-compliant
OSSJ plugins.
The TS changes to remove OSSJ stuff are being done as we speak too. We are
working on the 0.3 release stream (check out the dates/details at
http://wiki.eclipse.org/Tigerstripe_0.3_stream ). Most of these changes we
implemented in the 0.3M2 drop as of yesterday. (looks like you're still on
the 0.3M1).
The goal is indeed to make TS generic.
>
> - Failing to access plugin project global properties from a template in a
> test model project using $pluginRef.Properties.getProperty.
> Template is in Refer to plug-in and test model project in TMF GForge TIP SVN
> repository at respectively : Teams\Framework\TIDE\xml_plugin and
> Teams\Framework\TIDE\xml_plugin\templates\wsdl\wsdl.vm.
I'll differ this to Richard who is the plugin guru :-).
>
> - Failing to define stereotypes to artifact, methods, parameters. The
> stereotype selection is empty. I can't find in the help pages where, how to
> create stereotypes?
When definining stereotypes you need to assign a scope of applicability to
them. By default (probably needs to be the other way around) stereotypes are
not in scope for anything, you need to explicitly select what they will be
applicable to.
When defining a stereotype, look at the details, scroll down a little and
you'll see a lot of checkboxes to define where they should be applicable.
Once you've updated this, save your profile and "activated it again" to
apply the changes, the stererotypes should be offered then.
>
> Thanks,
> Jerome
>
>
|
|
|
| Re: Several questions as starting to use Tigerstripe [message #10103 is a reply to message #10056] |
Thu, 29 May 2008 09:16 |
Richard Craddock
Messages: 31
Registered: July 2009 |
Member |
|
|
Hi Jerome.
>>
>> - Failing to access plugin project global properties from a template in a
>> test model project using $pluginRef.Properties.getProperty.
>> Template is in Refer to plug-in and test model project in TMF GForge TIP SVN
>> repository at respectively : TeamsFrameworkTIDExml_plugin and
>> TeamsFrameworkTIDExml_plugintemplateswsdlwsdl.vm.
> I'll differ this to Richard who is the plugin guru :-).
The $pluginref object in the context has been renamed to be $pluginConfig
- that should enable you to get these properties.
>>
>> - Failing to define stereotypes to artifact, methods, parameters. The
>> stereotype selection is empty. I can't find in the help pages where, how to
>> create stereotypes?
Before you get to Eric's point below, you need to define the stereotypes
in a Workbench Profile, and then apply that to your session.
http://wiki.eclipse.org/Tigerstripe_Profile_Tutorial - iss out of date
:-(, but gives the concepts. In the tutorial, the Steroetypes are called
annotations. (We have put in place a true "annotation" mechanism, so have
given the stereotypes a more meaningful name.)
> When defining stereotypes you need to assign a scope of applicability to
> them. By default (probably needs to be the other way around) stereotypes are
> not in scope for anything, you need to explicitly select what they will be
> applicable to.
> When defining a stereotype, look at the details, scroll down a little and
> you'll see a lot of checkboxes to define where they should be applicable.
> Once you've updated this, save your profile and "activated it again" to
> apply the changes, the stererotypes should be offered then.
>>
Cheers,
Richard
|
|
|
| Re: Several questions as starting to use Tigerstripe [message #563216 is a reply to message #10033] |
Wed, 28 May 2008 16:25 |
Eric Dillon
Messages: 103
Registered: July 2009 |
Senior Member |
|
|
Hi Jerome,
See my comments inline.
Eric
On 5/27/08 7:18 PM, in article g1ifds$5vf$1@build.eclipse.org, "Jerome
Magnet" <jeromem@nortel.com> wrote:
> Hi All,
>
> I started using the latest Tigerstripe workbench as part of the TMF
> Interface
> Program(org.eclipse.tigerstripe.workbench.base_0.3.0.M200805 061422_incubation)
>
> I have the following questions :
>
> - Is the Eclipse Tigerstripe Help aligned with the latest version
> (Tigerstripe Workbench 2.x)?
> For example, it says TS comes with three default basic plug-ins. It was true
> before but I don't see that now.
> It seems that it does not reflect the latest TS architecture changes? I also
> still see many references to OSS/J. I thought they had been removed to make
> TS generic?
There has been few posts already in this group about this. No, the Doc is
still aligned with the old commercial version. We are working on the changes
but they won't be in place until mid-june.
I particular, the basic plugins are gone. They were VERY OLD non-compliant
OSSJ plugins.
The TS changes to remove OSSJ stuff are being done as we speak too. We are
working on the 0.3 release stream (check out the dates/details at
http://wiki.eclipse.org/Tigerstripe_0.3_stream ). Most of these changes we
implemented in the 0.3M2 drop as of yesterday. (looks like you're still on
the 0.3M1).
The goal is indeed to make TS generic.
>
> - Failing to access plugin project global properties from a template in a
> test model project using $pluginRef.Properties.getProperty.
> Template is in Refer to plug-in and test model project in TMF GForge TIP SVN
> repository at respectively : Teams\Framework\TIDE\xml_plugin and
> Teams\Framework\TIDE\xml_plugin\templates\wsdl\wsdl.vm.
I'll differ this to Richard who is the plugin guru :-).
>
> - Failing to define stereotypes to artifact, methods, parameters. The
> stereotype selection is empty. I can't find in the help pages where, how to
> create stereotypes?
When definining stereotypes you need to assign a scope of applicability to
them. By default (probably needs to be the other way around) stereotypes are
not in scope for anything, you need to explicitly select what they will be
applicable to.
When defining a stereotype, look at the details, scroll down a little and
you'll see a lot of checkboxes to define where they should be applicable.
Once you've updated this, save your profile and "activated it again" to
apply the changes, the stererotypes should be offered then.
>
> Thanks,
> Jerome
>
>
|
|
|
| Re: Several questions as starting to use Tigerstripe [message #563266 is a reply to message #10056] |
Thu, 29 May 2008 09:16 |
Richard Craddock
Messages: 31
Registered: July 2009 |
Member |
|
|
Hi Jerome.
>>
>> - Failing to access plugin project global properties from a template in a
>> test model project using $pluginRef.Properties.getProperty.
>> Template is in Refer to plug-in and test model project in TMF GForge TIP SVN
>> repository at respectively : TeamsFrameworkTIDExml_plugin and
>> TeamsFrameworkTIDExml_plugintemplateswsdlwsdl.vm.
> I'll differ this to Richard who is the plugin guru :-).
The $pluginref object in the context has been renamed to be $pluginConfig
- that should enable you to get these properties.
>>
>> - Failing to define stereotypes to artifact, methods, parameters. The
>> stereotype selection is empty. I can't find in the help pages where, how to
>> create stereotypes?
Before you get to Eric's point below, you need to define the stereotypes
in a Workbench Profile, and then apply that to your session.
http://wiki.eclipse.org/Tigerstripe_Profile_Tutorial - iss out of date
:-(, but gives the concepts. In the tutorial, the Steroetypes are called
annotations. (We have put in place a true "annotation" mechanism, so have
given the stereotypes a more meaningful name.)
> When defining stereotypes you need to assign a scope of applicability to
> them. By default (probably needs to be the other way around) stereotypes are
> not in scope for anything, you need to explicitly select what they will be
> applicable to.
> When defining a stereotype, look at the details, scroll down a little and
> you'll see a lot of checkboxes to define where they should be applicable.
> Once you've updated this, save your profile and "activated it again" to
> apply the changes, the stererotypes should be offered then.
>>
Cheers,
Richard
|
|
|
Goto Forum:
Current Time: Tue Apr 23 13:38:07 GMT 2024
Powered by FUDForum. Page generated in 0.03480 seconds |
] 
Search
Help
Register
Login
Home
