Which development environment for Activiti itself?

[ogeisser]

Hi,

can someone from the commiters explain which build/development environment is needed for Activiti ?

I have figured out the following on my own and maybe someone can confirm/correct this:

- Source-code: http://svn.activiti.org/repo/activiti/trunk
- Maven: (indicator: pom.xml files)
- IDE: Eclipse (indicator: .project files)
- M2Eclipse plugin (indicator: maven2Nature and maven2Builder in .project files)
- JDK/JRE 5 (indicator: maven-compiler-plugin configuration 1.5/1.5)

I'm not sure about WTP and m2eclipse-extras for WTP. Do you use this?

If the above is correct shouldn't the following work?

Eclipse|New|Others|Maven|Checkout Maven Projects from SCM and the check-out from the above URL.
Note: It's Eclipse EE (which includes WTP) and it is running on JDK 5. M2Eclipse & M2Eclipse WTP extras are installed

Doing this gives me a lot of errors inside of Eclipse.

Thank you for your support.

Olli

[jcosano]

Hello,

I think that all you need you can find here:

http://svn.activiti.org/repo/activiti/trunk/docs/developers.guide.html

I have all code in my eclipse workspace (last revision) without error

[ogeisser]

Hi,

thanks for the info. I found one important detail which makes a difference.

The guide only talks about "check out" and "import existing projects" but there are at least two
different ways in Eclipse to do this.

You can "Checkout project with SVN" and you can "Maven|Checkout existing Maven project from SCM". The later one is only
available with the M2Eclipse plugin installed. The M2Eclipse plugin will also detect sub-projects
and automatically configure new projects and WTP support so there is no need for an additional "import step".

As far as I have tried the "M2Eclipse way" currently does not work very well with the current state of Activiti.
There are some known problems with M2Eclipse and the WTP integration but on the other hand there exist
project which checkout with M2Eclipse without any problems. So I can not tell who is to blame for
the problems with the Activiti/M2Eclipse combination.

I had a better experience with "standard" SVN project checkout and "standard" "project import".
But also following this route gives some minor problems but much less then the former way of doing it.

Following the commits on the project there is a lot of activity in activiti 😉
A lot of stuff is currently moving. For example JDK 5 or 6 usage/support is currently inconsistent
(pom.xml says compiler 1.5/1.5 but code uses @Overrides for interfaces).

Maybe these infos can