You are right. There isn't a process project anymore. However an ant-task to deploy the process definition is supplied. There should also be an ant script around which also creates the jar with the java classes used in the process definition. Deploying is not really comfortable right now. AFAIK making deployment easier and more convient is work in progress.
I personally don't like the fact that the process definition is deployed directly to the database. It's inconvient where the database server is normally not accessible directly from the developer workstation.
What was actually the reason to drop the process project? IMHO it would be convient to have a project again whose standard behaviour is creating a *.bar with the process definition, the process image and the implementation classes and the option to deploy it.
Thank you Sebastian for letting me know that process project really doesn't exist for jBPM 4. I agree that it would be convenient to have a standard process project. I'll use the ant tasks instead.
The processproject did not do much besides adding jars to the classpath and creating some files.
The option to deploy it was something on the designer part, not the process project.
Would be better if it becomes a process nature... The process images is also created now by the GPD, no difference there
Thank you very much for the additional information.