Updated project structure #2
Conversation
|
Jag har skapat en development |
|
Tja Jag tog ut en ny fork I helgen, vet inte om du såg det, eftersom det blev lite för många ändringar på en gång på den förra så det var inte bakåtkompatibelt...vilket känns lite tråkigt. Sent from my HTC ----- Reply message ----- Jag har skapat en development Reply to this email directly or view it on GitHub: |
|
De menar att du gjort mer ndringar n de som kom in nu? Kan vi inte merga 2011/10/17 Nils Olsson <
|
…ecution time for all jobs in a view
…tus, otherwise the model can get the wrong status (e.g. when using a exception strategy that never fail the execution of a model)
…ion is not found, the graphwalker plugin will fail due to a IllegalArgumentException. The exception is thrown when the plugin try to execute "nothing", a check is added to make sure we have something to execute before we do it.
… ModelContext that will be used when executing a model.
Added build badge from Travis-CI
Fix: "The log length has exceeded the limit of 4 Megabytes (this usually means that test suite is raising the same exception over and over)." from travis
Copy and paste typo
No code changes only the project structure has been transformed into a multi-module maven project.
graphwalker-parent - handles dependencies and plugins versioning, also gives all inheriting modules basic functionality like different kind of report generation.
graphwalker-core - contains the GraphWalker code, this module can later on be split up into several modules eg. gui and webservice modules.
graphwalker-standalone - builds the executable standalone jar file, the reason for this being done in a separate module is due to the fact that each maven project only should have one build artifact.
Run "mvn clean install", in each module to compile and install the artifact generated by the module in the local repository, add -Dmaven.test.skip to omit the tests. This is true for all modules except graphwalker-parent, who will instead build the entire project.