Local gradle pulbish and project refactoring into packages

natanieljr commented 7 years ago

Dear Nikolaus,

In that commit I did the following changes:

Added a local Gradle instance (as recommended by the developers): Prevents conflicts and remove Gradle installation requirement
Put all classes in packages (at.unisalzburg.aapted. to follow java standards
Added option do publish on mavenLocal (I haven’t uploaded to mavenCentral, but would be great), allowing it to be easily used in other Gradle/Maven projects (details on how to do it are on the readme file)

The main benefit of these changes is to improve easiness to use. Currently, to be used in another project, AAPTED JAR has to be copied to a folder and linked to the project as a dependency. With my change, once you deploy it locally, Gradle can handle the dependency management.

Regards,

Nataniel

mateuszpawlik commented 6 years ago

I've commented on the pull request #6. It also contains packaging changes. When we're done with it, I come back here.

mateuszpawlik commented 6 years ago

Please see the last changes in the master branch and let me know what would be still missing to fix. I think that's only the Maven part. Is that correct?

natanieljr commented 6 years ago

Yes,

All that is missing is the maven plugin to deploy it to a local maven repository.

mateuszpawlik commented 5 years ago

We're discontinuing this repository. Is this pull request still interesting to resolve?

Have a look at our new C++ Tree Similarity library.

DatabaseGroup / apted

Local gradle pulbish and project refactoring into packages #2