head	1.2;
access;
symbols
	v20070921-0-7-0:1.2
	STP-0_6_0:1.2
	v200706250300:1.2
	v20070530-0-5-0:1.2
	v200704202100:1.1;
locks; strict;
comment	@# @;


1.2
date	2007.05.04.08.16.15;	author aboisvert;	state Exp;
branches;
next	1.1;
commitid	75ca463aeb864567;

1.1
date	2006.12.04.11.35.52;	author hmalphett;	state Exp;
branches;
next	;
commitid	24be457408164567;


desc
@@


1.2
log
@changes regarding the DnD, a lot of changes
@
text
@<projectDescription>
  <name>org.eclipse.stp.bpmn.validation</name>
  <comment/>
  <projects/>
  <buildSpec>
    <buildCommand>
      <name>org.eclipse.jdt.core.javabuilder</name>
      <arguments/>
    </buildCommand>
    <buildCommand>
      <name>org.eclipse.pde.ManifestBuilder</name>
      <arguments/>
    </buildCommand>
    <buildCommand>
      <name>org.eclipse.pde.SchemaBuilder</name>
      <arguments/>
    </buildCommand>
  </buildSpec>
  <natures>
    <nature>org.eclipse.pde.PluginNature</nature>
    <nature>org.eclipse.jdt.core.javanature</nature>
  </natures>
</projectDescription>@


1.1
log
@validation plugin. BPMN connection rules are implemented.
validation is in batch mode.
batch validation can be called via a builder.

the builder and its nature are actually created lazyly when a bpmn diagram is created.
@
text
@a0 1
<?xml version="1.0" encoding="UTF-8"?>
d2 22
a23 26
	<name>org.eclipse.stp.bpmn.validation</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.pde.ManifestBuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.pde.SchemaBuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.pde.PluginNature</nature>
		<nature>org.eclipse.jdt.core.javanature</nature>
	</natures>
</projectDescription>
@

