RE: [stp-dev] WTP-based PolicyEditor contribution: some additionalquesti

[<Andrei.Shakirin@xxxxxxxxxxxxxxx>]

Hi Oisin,

 

1: ok

2: it is our code (common utilities, code for policy generation and basic validation). We just build and use them as normal jars, not plugin bundles.

ok, I will prepare bugzilla entry.

 

Regards,

Andrei.

---

From: stp-dev-bounces@xxxxxxxxxxx [mailto:stp-dev-bounces@xxxxxxxxxxx] On Behalf Of Oisin Hurley
Sent: Donnerstag, 4. Oktober 2007 13:36
To: STP Dev list
Subject: Re: [stp-dev] WTP-based PolicyEditor contribution: some additionalquestions

1. Is it necessary also to create and attach ant build scripts in bugzilla entry for policy editor?

Adrian may correct me here, but I don't think so - we just need the code.

Once the code is in, we will be updating the existing STP build system to 

take it into account.

2. At the moment policy editor contains five modules: two Eclipse plugins (bundles: org.eclipse.stp.policy.wtp.editor_1.0.0 and org.eclipse.stp.policy.wtp.validation_1.0.0) and three modules builded as normal jars.

   These jars are packaged into plugins bundles at the build step.
   Is it OK from point of view of STP build system? Do you have some rules/limitations in this sense?

What are the 'normal' jars?  If they are third party elements, they will need 

to go into the Orbit project after they have been approved, if they are not,

then they should probably moved into a 'library' plugin. But don't worry about

that for the moment, we can do any necessary reorganization when we 

are creating the subcomponent.

 best regards

   Oisin

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland