Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » static profiles with model libraries
static profiles with model libraries [message #477429] Fri, 23 May 2008 14:54 Go to next message
Eclipse UserFriend
Originally posted by: huascar.espinoza.cea.com

Hi all,

I'm building a static profile that imports a model library. The model
library has been implemented in a separated file/model. I was wondering
about the best way to organize the static profile taking into account that
the imported model library has some packages that apply the profile itself!
There is not a circular reference at package level, but the files (profile
and model library) are mutually dependent.

More concretely, I'd like to know from experienced people on static profiles
the best organization to avoid conflicts. Separated
projects/plugins/packages for the profile and the library?

Thank you in advance,



--

Huascar ESPINOZA, Ph.D.

CEA LIST

Model-Driven Engineering for Real-Time Embedded Systems

91191 GIF/YVETTE CEDEX

Phone/Fax: +33 1 69 08 45 87 / 20 82

FRANCE
Re: static profiles with model libraries [message #477457 is a reply to message #477429] Wed, 28 May 2008 14:08 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Huascar,

I think you will be on the cutting edge in terms of using static profile
definition so you may not receive many replies to your posting.

If I understand the configuration of your project, you have some profile
(for which you are generating code), then you have a library which uses the
profile (that library would be reused elsewhere). You also mention that
the profile and model library are mutually dependent.
It's difficult to speculate on how best to arrange such a project. You
might consider splitting the dependency if it is causing you issues and
separating out sections of the profile (although I'm not sure if creating 2
profiles would make sense in your case ).


I'm eager to hear how this is working out for you and your experiences.
Please let us know if you discover any pitfalls or errors that you cannot
get around.

Cheers,
- James.


"Huascar Espinoza" <huascar.espinoza@cea.com> wrote in message
news:g16lqt$d8p$1@build.eclipse.org...
>
> Hi all,
>
> I'm building a static profile that imports a model library. The model
> library has been implemented in a separated file/model. I was wondering
> about the best way to organize the static profile taking into account that
> the imported model library has some packages that apply the profile
> itself! There is not a circular reference at package level, but the files
> (profile and model library) are mutually dependent.
>
> More concretely, I'd like to know from experienced people on static
> profiles the best organization to avoid conflicts. Separated
> projects/plugins/packages for the profile and the library?
>
> Thank you in advance,
>
>
>
> --
>
> Huascar ESPINOZA, Ph.D.
>
> CEA LIST
>
> Model-Driven Engineering for Real-Time Embedded Systems
>
> 91191 GIF/YVETTE CEDEX
>
> Phone/Fax: +33 1 69 08 45 87 / 20 82
>
> FRANCE
>
>
Re: static profiles with model libraries [message #626639 is a reply to message #477429] Wed, 28 May 2008 14:08 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Huascar,

I think you will be on the cutting edge in terms of using static profile
definition so you may not receive many replies to your posting.

If I understand the configuration of your project, you have some profile
(for which you are generating code), then you have a library which uses the
profile (that library would be reused elsewhere). You also mention that
the profile and model library are mutually dependent.
It's difficult to speculate on how best to arrange such a project. You
might consider splitting the dependency if it is causing you issues and
separating out sections of the profile (although I'm not sure if creating 2
profiles would make sense in your case ).


I'm eager to hear how this is working out for you and your experiences.
Please let us know if you discover any pitfalls or errors that you cannot
get around.

Cheers,
- James.


"Huascar Espinoza" <huascar.espinoza@cea.com> wrote in message
news:g16lqt$d8p$1@build.eclipse.org...
>
> Hi all,
>
> I'm building a static profile that imports a model library. The model
> library has been implemented in a separated file/model. I was wondering
> about the best way to organize the static profile taking into account that
> the imported model library has some packages that apply the profile
> itself! There is not a circular reference at package level, but the files
> (profile and model library) are mutually dependent.
>
> More concretely, I'd like to know from experienced people on static
> profiles the best organization to avoid conflicts. Separated
> projects/plugins/packages for the profile and the library?
>
> Thank you in advance,
>
>
>
> --
>
> Huascar ESPINOZA, Ph.D.
>
> CEA LIST
>
> Model-Driven Engineering for Real-Time Embedded Systems
>
> 91191 GIF/YVETTE CEDEX
>
> Phone/Fax: +33 1 69 08 45 87 / 20 82
>
> FRANCE
>
>
Previous Topic:Re: Amalgamate Models
Next Topic:Creating an AssociationClass
Goto Forum:
  


Current Time: Wed Sep 19 07:28:23 GMT 2018

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

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

Back to the top