agentsoz / bdi-abm-integration

BDI ABM Integration
GNU Lesser General Public License v3.0
8 stars 13 forks source link

abm-jadex layer compile failure #79

Closed oemer95 closed 1 year ago

oemer95 commented 3 years ago

Hi there,

I would like to connect matsim with jadex agents, so therefore I installed the layers bdi-abm, bdi-matsim and consequently abm-jadex layer. But during mvn clean install of the abm-jadex layer, I get the terminal output below. Could you please help?

(In the abm-jadex pom-file, I used the jadex version 2.3, which is deprecated and the bdi-abm snapshot 3.0.1)


$ mvn clean install [←[1;34mINFO←[m] Scanning for projects... [←[1;34mINFO←[m] Inspecting build with total of 1 modules... [←[1;34mINFO←[m] Installing Nexus Staging features: [←[1;34mINFO←[m] ... total of 1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin [←[1;34mINFO←[m] [←[1;34mINFO←[m] ←[1m--------------------< ←[0;36mio.github.agentsoz:abm-jadex←[0;1m >--------------------←[m [←[1;34mINFO←[m] ←[1mBuilding ABM Jadex Integration 3.0.1-SNAPSHOT←[m [←[1;34mINFO←[m] ←[1m--------------------------------[ jar ]---------------------------------←[m [←[1;34mINFO←[m] [←[1;34mINFO←[m] ←[1m--- ←[0;32mmaven-clean-plugin:2.5:clean←[m ←m←[m @ ←[36mabm-jadex←[0;1m ---←[m [←[1;34mINFO←[m] Deleting C:\Users\Oemer\Documents\GitHub\bdi-abm-integration-master\integrations\abm-jadex\target [←[1;34mINFO←[m] [←[1;34mINFO←[m] ←[1m--- ←[0;32mlicense-maven-plugin:2.0.0:update-project-license←[m ←m←[m @ ←[36mabm-jadex←[0;1m ---←[m [←[1;34mINFO←[m] Adding a license repository jar:file:/C:/Users/Oemer/.m2/repository/org/codehaus/mojo/license-maven-plugin/2.0.0/license-maven-plugin-2.0.0.jar !/META-INF/licenses [←[1;34mINFO←[m] register GNU Free Documentation License (FDL) version 1.3 [←[1;34mINFO←[m] register GNU General Lesser Public License (LGPL) version 3.0 [←[1;34mINFO←[m] register GNU Affero General Public License (AGPL) version 3.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 3.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 2.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 1.0 [←[1;34mINFO←[m] register Apache License version 2.0 [←[1;34mINFO←[m] register Eclipse Public License - v 2.0 with Secondary License [←[1;34mINFO←[m] register Eclipse Public License - v 2.0 [←[1;34mINFO←[m] register Eclipse Public License - v 1.0 [←[1;34mINFO←[m] register Eclipse Public + Distribution License - v 1.0 [←[1;34mINFO←[m] register COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0 [←[1;34mINFO←[m] register GNU General Lesser Public License (LGPL) version 2.1 [←[1;34mINFO←[m] register MIT-License [←[1;34mINFO←[m] register BSD 2-Clause License [←[1;34mINFO←[m] register BSD 3-Clause License [←[1;34mINFO←[m] register European Union Public License v1.1 [←[1;34mINFO←[m] [←[1;34mINFO←[m] ←[1m--- ←[0;32mlicense-maven-plugin:2.0.0:update-file-header←[m ←m←[m @ ←[36mabm-jadex←[0;1m ---←[m [←[1;34mINFO←[m] Adding a license repository jar:file:/C:/Users/Oemer/.m2/repository/org/codehaus/mojo/license-maven-plugin/2.0.0/license-maven-plugin-2.0.0.jar !/META-INF/licenses [←[1;34mINFO←[m] register GNU Free Documentation License (FDL) version 1.3 [←[1;34mINFO←[m] register GNU General Lesser Public License (LGPL) version 3.0 [←[1;34mINFO←[m] register GNU Affero General Public License (AGPL) version 3.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 3.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 2.0 [←[1;34mINFO←[m] register GNU General Public License (GPL) version 1.0 [←[1;34mINFO←[m] register Apache License version 2.0 [←[1;34mINFO←[m] register Eclipse Public License - v 2.0 with Secondary License [←[1;34mINFO←[m] register Eclipse Public License - v 2.0 [←[1;34mINFO←[m] register Eclipse Public License - v 1.0 [←[1;34mINFO←[m] register Eclipse Public + Distribution License - v 1.0 [←[1;34mINFO←[m] register COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0 [←[1;34mINFO←[m] register GNU General Lesser Public License (LGPL) version 2.1 [←[1;34mINFO←[m] register MIT-License [←[1;34mINFO←[m] register BSD 2-Clause License [←[1;34mINFO←[m] register BSD 3-Clause License [←[1;34mINFO←[m] register European Union Public License v1.1 [←[1;34mINFO←[m] Will search files to update from root C:\Users\Oemer\Documents\GitHub\bdi-abm-integration-master\integrations\abm-jadex\src [←[1;34mINFO←[m] Will search files to update from root C:\Users\Oemer\Documents\GitHub\bdi-abm-integration-master\integrations\abm-jadex\target\generated-source s [←[1;34mINFO←[m] Scan 47 files header done in 237,198ms. [←[1;34mINFO←[m]

dhixsingh commented 3 years ago

@oemer95, the error would be because the bdi-abm 3.* API is incompatible with the abm-jadex integration version. The abm-jadex code is quite old as you can tell, and we haven't ported it to the newer Jadex programming model since we haven't had any users wanting it. Your best bet would be to try with bdi-abm 2.0.2.

oemer95 commented 3 years ago

@dhixsingh Thanks a lot for your help, I'll try out your advice. I wonder if there's an application example provided, where Jadex is connected to MatSim? In fact, I'm working on connecting both together and I would like to know, what you would recommend. Should I modify a given example like "bushfire" or implement a new one from scratch? Thanks a lot!

dhixsingh commented 2 years ago

Unfortunately we never had the integration updated for the “newer” Jadex programming model, as there were no users needing it, so the jadex-abm integration needs to be upgraded first before building any applications with it.

oemer95 commented 2 years ago

@dhixsingh Thank you very much for your response. My problem is to build a connection between the current JadeX (4.0) and MatSim (13.0) and as far as I'm aware, your work is the most similar to this. I would prefer to use your work and update it for JadeX. Since the abm-jadex layer has to be upgraded, I would like to know whether it is done with that or whether I need further changes in the bdi-matsim layer (Edit: or in the bdi-abm layer) ? I would also like to know whether you could provide any help, what essentially changed between the single bdi-abm layer 2.0.1 and the current bdi-abm layer.

Thank you very much for your help!