cancel
Showing results for 
Search instead for 
Did you mean: 

Activiti 5.0.beta2 Library Dependencies

limcheekin
Champ on-the-rise
Champ on-the-rise
Hi,

I am on the way to upgrade libraries of Grails Activiti Plugin from Activiti 5.0.beta1 to Activiti 5.0.beta2. I have problem to figure out which jar files should I included for the plugin as I have no idea which one is mandatory/optional given beta2 release has introduced so many additional jar files. Some more I need to make sure that if the library exists in Grails Framework, it should not included in the plugin.

I'm currently relied on libs-runtime and libs-test directory of examples/activiti-engine-examples and examples/activiti-spring-examples to figure out the dependencies, but I think this approach is error-prone.

Is there any document I can refer for Activiti 5.0.beta2 Library Dependencies? It will be great and helpful for deployment if there is a document specified the purpose of included library, runtime/test/compile, mandatory/optional, etc.

Please advice.

Regards,
Chee Kin
6 REPLIES 6

frauke
Champ in-the-making
Champ in-the-making
Hi,

I also have a problem with the library dependencies. The example projects do not compile because the test jars are missing. Could it be that they are not installed with the examples.get.libs targets in the ant script?
How else can I get them?

Best regards
Frauke

tombaeyens
Champ in-the-making
Champ in-the-making
why do you think indicating the lib dependencies like we do in the examples is error prone?

the main purpose of the different examples is to show which dependencies you need for different use cases.  mostly people will use the activiti-engine, then they will need the examples/activiti-engine-examples/libs-runtime/*.jar at rumtime and the additional examples/activiti-engine-examples/libs-test/*.jar during test.

i thought this would make it easy, no?  maybe i overlooked something. 
would it be fixed by better documentation?

an aspect that also played was that now, all of this in the distro really comes from the poms, and that is how the developers manage the dependencies.  which means that it should not be possible for us to make mistakes.

you can create simple maven based text descriptions of the dependencies by doing a mvn dependency:tree

saatsch
Champ in-the-making
Champ in-the-making
Hey
first of all, thank you for doing activiti.

I checked beta2 today and did not get the installation to complete. Loads of maven stuff was not found.
I then decided to add http://maven.alfresco.com/nexus/content/groups/public/
as a repository to our repository manager.

Now I successfully installed activiti and it woks very good as far as I can tell by now.

But sadly it had the effect, that ALL our internal builds broke.

Please take a look at:

http://maven.alfresco.com/nexus/content/groups/public/org/apache/maven/plugins/maven-scm-plugin/mave...

Here, maven-scm-plugin 1.5-SNAPSHOT is mentioned, but it does not exist. This is why our builds broke.
Luckily it is Friday afternoon and most of our devs already went home.

Nice weekend everybody
Greets
Saatsch

limcheekin
Champ on-the-rise
Champ on-the-rise
Hi Tom,

why do you think indicating the lib dependencies like we do in the examples is error prone?

the main purpose of the different examples is to show which dependencies you need for different use cases.  mostly people will use the activiti-engine, then they will need the examples/activiti-engine-examples/libs-runtime/*.jar at rumtime and the additional examples/activiti-engine-examples/libs-test/*.jar during test.

i thought this would make it easy, no?  maybe i overlooked something. 
would it be fixed by better documentation?
I think you misunderstood my meaning, I means the way I upgrade the library is error-prone as I am not sure which jar files are mandatory (Sorry, if my writings is not clear enough). At the moment, I just relied on the examples to find out the dependencies, can I assumed that all jar files under examples/activiti-engine-examples/libs-runtime are mandatory for activiti-engine?

an aspect that also played was that now, all of this in the distro really comes from the poms, and that is how the developers manage the dependencies.  which means that it should not be possible for us to make mistakes.

you can create simple maven based text descriptions of the dependencies by doing a mvn dependency:tree
Thanks. I will try it out. I think it is helpful to include a short description for library dependencies in the documentation as not all developers familiar with maven, just my 2 cents. I doesn't aware about this command "mvn dependency:tree".

Also, I downloaded the source of Activiti and cd to distro directory then run "ant clean distro" to build it, so far the build process was never success in my local machine. Did I missed out anything?

Regards,
Chee Kin

user
Champ in-the-making
Champ in-the-making
Hi,

i installed the beta2 version.

and i stop at these point in the user guide:
Library dependencies
http://activiti.org/userguide/index.html#librarydependencies

How do i install these dependencies?

I hope you can help me.

i try with comands like:
ant examples.get.libs.all

in the build xml

bye

user
Champ in-the-making
Champ in-the-making
oh i m sorry…
i saw my mistake… i m was not in the correkt root…