10-01-2010 02:01 AM
10-01-2010 04:48 AM
10-01-2010 05:37 AM
10-01-2010 10:43 AM
10-02-2010 01:01 AM
why do you think indicating the lib dependencies like we do in the examples is error prone?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?
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.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".
you can create simple maven based text descriptions of the dependencies by doing a mvn dependency:tree
10-04-2010 04:55 AM
10-04-2010 05:06 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.