e

eclipse-toolsupport

defacto they client test developed become introduce lead every until software bpel when recently activities these chunks services consequences however lacked support frameworks such code undesired include that language example this small other development allow have easily methodologies programming composing side written bpelunit standard rolled important into nearly junit framework developers defects therefore unit exists java testing closing
Files download
File Operation
eclipse-toolsupport-1.6.0.jar download
eclipse-toolsupport-1.6.0.pom download
Apache Maven 
<dependency>
  <groupId>net.bpelunit</groupId>
  <artifactId>eclipse-toolsupport</artifactId>
  <version>1.6.0</version>
  <type>eclipse-plugin</type>
</dependency>
Gradle Groovy 
implementation 'net.bpelunit:eclipse-toolsupport:1.6.0'
Gradle Kotlin 
implementation("net.bpelunit:eclipse-toolsupport:1.6.0")
Scala SBT 
libraryDependencies += "net.bpelunit" % "eclipse-toolsupport" % "1.6.0"
Groovy Grape 
@Grapes(
  @Grab(group='net.bpelunit', module='eclipse-toolsupport', version='1.6.0')
)
Apache Ivy 
<dependency org="net.bpelunit" name="eclipse-toolsupport" rev="1.6.0" />
Leiningen 
[net.bpelunit/eclipse-toolsupport "1.6.0"]
Apache Buildr 
'net.bpelunit:eclipse-toolsupport:jar:1.6.0'
Dependencies 
<parent>
  <groupId>net.bpelunit</groupId>
  <artifactId>bpelunit-tycho-parent</artifactId>
  <version>1.6.0</version>
</parent>

compile

|-- net.bpelunit:framework