Re: [epf-dev] When does EPF create a new resource

[Ricardo Balduino <balduino@xxxxxxxxxx>]

Hi,  

EPFC stores name, presentation name,
brief description, and relationships of elements in the corresponding plugin.xmi
file.
When you add text to any other field,
such as main description, etc, then a <element_name>.xmi file
is created for that element in order to store the additional text.

Process elements (capability patterns
and delivery processes) have a different file structure. There can be up
to 3 files per process element: model.xmi, content.xmi, and diagram.xmi
files.

For more information, see "Using
EPF Composer with a version control system", section 1 "Overview
of EPF Composer files", on 
http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.epf/docs/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?cvsroot=Technology_Project&content-type=text/htm

Ricardo.




From:      
 Onno van der Straaten
<onno.van.der.straaten@xxxxxxxxx>
To:      
 hwintjen@xxxxxxxxxxxxxxxxxxx,
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
Date:      
 10/09/2010 05:10 AM
Subject:    
   Re: [epf-dev]
When does EPF create a new resource
Sent by:    
   epf-dev-bounces@xxxxxxxxxxx

---

Hi Hauke,
When you add more than only a presentation name a file is created. If you
check the contents of the plugin.xmi you'll see that it contains the presentation
names of elements of your plugin. All other fields are stored outside plugin.xmi
in a separate file. 
Best regards,
Onno

Op 8 okt 2010 10:42 schreef "Hauke Wintjen" <hwintjen@xxxxxxxxxxxxxxxxxxx>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear EPF Team.

I recently started using EPF(1.5.1) to author a method plugin / method library.

What currently wonders me is when does EPF create a new resource (file on disk) when I create a new task / practice.
Some tasks seem to reside in the plugin.xmi and others reside on disk as a new resource named after the name.
But as it looks to me they were defined by me with the same properties.

Any hints on this?

Kind regards

Hauke

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJMrtlDAAoJECTbT0NB+ctidroIAMXsx+IuezDeuGfiNAZvlP9y
HnmIAfTpiwsjoF4A/WS0URVCFWHLx1Y3wZM27dh5gFTDJC2JvYnoxFSeOdXxDY4H
Rhjjtxi5StTv8N6P6Ml1nxOA6x3bT6tHMxMfEMEFzOsmIX428I+vNTjCzVUIDFSj
5JwuwB85ebUuipYg1VKvHuYsRLRS4yvf2PPcbbeNuiW7Q1Kj/vXPmRbnyNru2kmG
xLmxfByhlaPjqEMyyCHIHrm8lu2PIru9az9wG2P8HAHnEe0Z/4atosddn7BBWs+l
3T7hxl+fHqonUSUOjLLxwuCpFl+X4sCjGPr6F8CS1VMeSkL/Z21T8Lu7sRfM7qA=
=yP6w
-----END PGP SIGNATURE-----

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev