You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We (@profpantoja, @souzavdj) are preparing a new JaCaMo package that offer a new agent architecture (Hermes). It allows agents of different Multi-Agent Systems to exchange messages using a IoT Gateway. However, our architecture is dependent of the contextnet-2.7, and this middleware, has a specific maven repository. When I put the uses package in the .jcm file, the JaCaMo can't find the dependence.
I see that the file .jcm-deps.gradle include in runtime the package dependency, but as the special maven repository is not included, the gradle can't resolve.
@jomifred, would it be interesting to include an option for it in the .jcm file? Almost like below:
The text was updated successfully, but these errors were encountered:
Hi Nilson, thanks for the detailed report of the issue and the suggestion of improvements.
For the current version of JaCaMo, you have to edit the build.gradle file of your project and add the new repository there.
HTH,
Jomi
Hello everyone,
We (@profpantoja, @souzavdj) are preparing a new JaCaMo package that offer a new agent architecture (Hermes). It allows agents of different Multi-Agent Systems to exchange messages using a IoT Gateway. However, our architecture is dependent of the contextnet-2.7, and this middleware, has a specific maven repository. When I put the uses package in the .jcm file, the JaCaMo can't find the dependence.
I see that the file .jcm-deps.gradle include in runtime the package dependency, but as the special maven repository is not included, the gradle can't resolve.
@jomifred, would it be interesting to include an option for it in the .jcm file? Almost like below:
The text was updated successfully, but these errors were encountered: