This is an automated email from the ASF dual-hosted git repository.
yasith pushed a change to branch cybershuttle-dev
in repository https://gitbox.apache.org/repos/asf/airavata.git
discard 47b06fe91b update airavata distribution module to match deployment
structure
discard 0c6a272b5e fix deprecations, cleanup code. add placeholders for job
monitor email/pw in airavata-server.properties
discard 843edb3c13 fix issues with helix participant and job engine starter
discard cf17a29c07 get hibernate orm to validate against test db. manually
specify catalog for conflicting entities.
discard 668fc39273 migrate openjpa to hibernate, update pool and dbcp deps to
pool2 and dbcp2.
discard 8429960eca parametrize pom versions. add maven-enforcer rule for
dependency convergence and fix version issues.
discard ebdbeabaec regenerated thrift stubs with version 0.21.0 and fix issues
discard f0a8350d1b bump JDK to v17. create devcontainer setup. bump rabbitmq
and proto versions. consolidate maven-compiler plugin versions. migrate openjpa
to 4.0.1. update javax to jakarta. regenerate certs. fix bugs.
add cfc00e5159 updated jupyterhub_config.py
new 55124e8432 bump JDK to v17. create devcontainer setup. bump rabbitmq
and proto versions. consolidate maven-compiler plugin versions. migrate openjpa
to 4.0.1. update javax to jakarta. regenerate certs. fix bugs.
new bfc028ae60 regenerated thrift stubs with version 0.21.0 and fix issues
new 94915ed231 parametrize pom versions. add maven-enforcer rule for
dependency convergence and fix version issues.
new de25688a32 migrate openjpa to hibernate, update pool and dbcp deps to
pool2 and dbcp2.
new 1d96b1db54 get hibernate orm to validate against test db. manually
specify catalog for conflicting entities.
new 713918e389 fix issues with helix participant and job engine starter
new 6e036df49f fix deprecations, cleanup code. add placeholders for job
monitor email/pw in airavata-server.properties
new d7bce90a6d update airavata distribution module to match deployment
structure
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (47b06fe91b)
\
N -- N -- N refs/heads/cybershuttle-dev (d7bce90a6d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../research-hub/compose/jupyterhub_config.py | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
