Tips and tricks

Some tips and tricks for maintaining Across.

Maven problems with Across snapshots

If you run into more (seemingly unexplainable) errors with Maven and Across snapshots, a good option is to brute-force clean your local Maven repository of all artifacts in any com.foreach.* group:

rm -rf ~/.m2/repository/com/foreach

I assume you are a power user, and are smart enough to not wipe out your entire home directory, by accidentally putting a space after the ~/ in that previous command :-)

ax-exec.sh

You can use this script to run a command in each of the 7 repositories, for instance:

ax-exec.sh git status
ax-exec.sh git fetch -p
ax-exec.sh git pull --ff-only

Danger zone: If you want to “undo” everything in all 7 repositories:

ax-exec.sh git reset --hard

ax-set-snapshot-versions.py

This script looks at the current branch of each of the 7 repositories, and updates the pom.xml files of each repository to use the right snapshot version for that repository, and its dependencies. E.g. if your current branches are:

across-framework.version:            5.4
across-autoconfigure.version:        2.4
across-base-modules.version:         4.4
across-entity-admin-modules.version: 4.4
across-user-auth-modules.version:    4.4
across-media-modules.version:        6.4
across-platform.version:             5.4

Then the script will propose this:

across-framework.version=5.4-SNAPSHOT
across-autoconfigure.version=2.4-SNAPSHOT
across-base-modules.version=4.4-SNAPSHOT
across-entity-admin-modules.version=4.4-SNAPSHOT
across-user-auth-modules.version=4.4-SNAPSHOT
across-media-modules.version=6.4-SNAPSHOT
across-platform.version=5.4-SNAPSHOT
Are you sure you want to set the above -SNAPSHOT versions? [y/N]:

There are two use cases for this: