Skip to content

Commit

Permalink
new portlet for mysql user management
Browse files Browse the repository at this point in the history
  • Loading branch information
kathrinklee committed Mar 12, 2019
1 parent 8366263 commit 4814ed9
Show file tree
Hide file tree
Showing 40 changed files with 18,403 additions and 0 deletions.
28 changes: 28 additions & 0 deletions user-db-portlet/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@

# Eclipse
.classpath
.project
.settings/

# VS Code
.vscode

# Intellij
.idea/
*.iml
*.iws

# Mac
.DS_Store

# Maven
target/

# Some of our applications generate logs, which should be ignored by git
logs/

# Other
**/.factorypath

# compiled Vaadin widgetsets
src/main/webapp/VAADIN/widgetsets
14 changes: 14 additions & 0 deletions user-db-portlet/.travis.settings.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
<settings>
<servers>
<server>
<id>nexus-snapshots</id>
<username>${env.MAVEN_REPO_USERNAME}</username>
<password>${env.MAVEN_REPO_PASSWORD}</password>
</server>
<server>
<id>nexus-releases</id>
<username>${env.MAVEN_REPO_USERNAME}</username>
<password>${env.MAVEN_REPO_PASSWORD}</password>
</server>
</servers>
</settings>
74 changes: 74 additions & 0 deletions user-db-portlet/.travis.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
# Build script for Travis CI
#

# use fast-boot container-based hosts
sudo: false
dist: trusty

# no need to check for oracle's java
language: java
jdk: openjdk8

# speed up builds by caching maven local repository
cache:
directories:
- "$HOME/.m2/repository"

# as agreed in our SOP
branches:
only:
- master
- development

# added to make logs look cleaner, crisper, certified fresh
before_install: unset _JAVA_OPTIONS

# speed up builds by telling Travis that we don't need any special "installation"
install: true

# as agreed in our SOP, build everything (don't deploy, just try to 'mvn install' locally, which covers all phases)
script: mvn --quiet --activate-profiles !development-build,!release-build --settings .travis.settings.xml clean cobertura:cobertura install
# upload code coverage report, generate maven site (javadocs, documentation, static code analysis, etc.)
after_success:
- bash <(curl -s https://codecov.io/bash)
- mvn --quiet --activate-profiles !development-build,!release-build --settings .travis.settings.xml site

# upload to maven
deploy:
# as agreed in our SOP, builds on development branch will deploy to our maven repository after validating
# the artifact has a proper SNAPSHOT version
# artifact will be installed in our testing instance if it is a .war file
- skip_cleanup: true
provider: script
script: echo "development deployment" && mvn --quiet --activate-profiles development-build,!release-build --settings .travis.settings.xml deploy
on:
branch: development
condition: '"$TRAVIS_EVENT_TYPE" = "push"'
# as agreed in our SOP, tagging a commit on the master branch will upload to our maven repository
# after validating the artifact has a proper release version
# artifact will be installed in our testing instance if it is a .war file
- skip_cleanup: true
provider: script
script: echo "master deployment" && mvn --quiet --activate-profiles !development-build,release-build --settings .travis.settings.xml deploy
on:
branch: master
condition: '"$TRAVIS_EVENT_TYPE" = "push"'

# change according to your needs, but we recommend to deactivate email notifications
# for now, we configured Travis to send a notification to the #travis-ci channel
notifications:
email:
on_success: never
on_failure: never
slack:
on_success: never
on_failure: always
# edit the following section if you want to get slack notifications
rooms:
- secure: "***"

# encrypted variables
env:
global:
- secure: "LlC638W4guO/Jv8mFTl2ifQG9iFLqkCCjqKrDZkKzWd2KdZBDFygB1dSXVWgORYhzOonfpURiXAiddmKor2w6yO/t9o9MxJ3iN9l6qZCQurNyCb91WhGHKAPy502Ig407rJk8aLPIHgwNVu8PtFJmQFOH5W24YyoVDCjvG5u8hOmNaqdsc7WSkTBThGQsElR16Vm+LA9EbFVBSdhu/QN0slLiqoA2D7MgUFc3Jsxv1PYXrOWUQ5uHZ6VRAdmcYVp1Qt07nuu1QcMr0TEOvCgmyUD8B1FTAuXPYJxLbqvQ8VdgXS99bbbsAC0cxJl/aLjFYeOiJNv79MdG7DM1cbnJwx2pQMvCiFiuukz2NOsffDeR+9M5QbMo3QbjBvzJeQqPm1Ecqk8B7VN0dWpyHlkLzR0qNVOMs6dzfAVpXvLNF7fXf0pZKPE/EzuSxIDLrJtJlKXdyxs0gd8vz2YTtTalwlA6Fr5OZel6pIj3BvphYt4/14PxtNQXL3NDF4r4h0IvjzMYv2SUa2v/hyxORB7P1zgujq8Cf6xG1jz31D5uC3c/g4mOxfY6+b/6Dkbwk5liylOMNNKSknr6IkcfO5NL90BzcE08V7hExci8D1MyMvSNmHnDCxKYySnUeaadOzEXUyZoL5BvMOGi4t2wM1SXvF9K6IKnWu68ooPYNUjeFs="
- secure: "AeLiIp7pkGAiokeyTPdVBpVUj1Cp+o/1vWQbvOr4vvOGUJl5hqahRU/A4sWWVb+oPrVbAVt5U/PxPpevTz/27f/rIfYx3jB2YNjgrJ8VE2JfPlBw2bnvnF8YOcimDPmgqHvnNdF319JzdGvv4acucEfbIhj/yfgGsjCi0/7zlDyhJojobyhjF196VsZfxQQNTJCURPbgTU9XciE4JX1dxkpv3Hht/XiJ/WWNUcMsgwWiuVlyeScc64i8giWvpOYmcj11Q0PQFNRwRJ/K4sbRV7GaNhBXTbkmOENGlGapA1MfOQ1726VT/SCzC88DUQLjfVXoOs215VjdSU13B1J6fVN0WJrJcyt6ZjigoaRhrMtFGsuEpegdZGTZn2uo6bJxGY4XPfzy1eshaAx892IfWMC358F+/a89a22v6LmlVQIWtJkos0bQRbvPYMt+eQalwdXAnt4ljL5llxuf7240jAjj0hM2WVRxkgxwIJpfrK7Q4vBGkFQ2Crlrjk3g+TqH4i2zelON5FzhrTSS2N+wu6Zp1+7dhgOm5KSyZTguKmsXKN+gu7BIrVvza0ZDuEQjrgCAZ0kBDtoEAxTdLh3NAf3l2XqkvAlHnsfYA7nJSDkB+Y6mIduRVRsyrr2QazDW6F6jPZzALdNP6BaZbEzbGMCEFnpBeqlJNJtlxNf94sU="
46 changes: 46 additions & 0 deletions user-db-portlet/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at info@qbic.uni-tuebingen.de. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
21 changes: 21 additions & 0 deletions user-db-portlet/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2018, QBiC.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
14 changes: 14 additions & 0 deletions user-db-portlet/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# User Database Portlet

[![Build Status](https://travis-ci.com/qbicsoftware/user-db-portlet.svg?branch=development)](https://travis-ci.com/qbicsoftware/user-db-portlet)[![Code Coverage]( https://codecov.io/gh/qbicsoftware/user-db-portlet/branch/development/graph/badge.svg)](https://codecov.io/gh/qbicsoftware/user-db-portlet)

User Database Portlet - User DB Tools Portlet enables users to add people and affiliations to the SQL user database.

## Author

Created by Andreas Friedrich (andreas.friedrich@qbic.uni-tuebingen.de).

## Description

## How to Install

81 changes: 81 additions & 0 deletions user-db-portlet/pom.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>life.qbic</groupId>
<artifactId>portlet-parent-pom</artifactId>
<version>1.3.0</version>
</parent>
<artifactId>user-db-portlet</artifactId>
<version>1.2.0-SNAPSHOT</version>
<name>User Database Portlet</name>
<url>http://github.com/qbicsoftware/user-db-portlet</url>
<packaging>war</packaging>
<!-- we only need to tell maven where to find our parent pom and other QBiC
dependencies -->
<repositories>
<repository>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
<id>nexus-snapshots</id>
<name>QBiC Snapshots</name>
<url>https://qbic-repo.am10.uni-tuebingen.de/repository/maven-snapshots</url>
</repository>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>nexus-releases</id>
<name>QBiC Releases</name>
<url>https://qbic-repo.am10.uni-tuebingen.de/repository/maven-releases</url>
</repository>
</repositories>
<!-- To avoid inconsistencies across projects, plase check which librares
are already contained before adding new ones under <dependencies>. You can
use the following maven command to generate a dependency tree and list all
maven artifacts (libraries) that are available: $ mvn dependency:tree Check
your IDE's documentation to display maven's dependency tree. -->
<dependencies>
<dependency>
<groupId>life.qbic</groupId>
<artifactId>portal-utils-lib</artifactId>
<version>1.3.0</version>
</dependency>
<dependency>
<groupId>life.qbic</groupId>
<artifactId>openbis-client-lib</artifactId>
<version>1.1.4</version>
</dependency>
<dependency>
<groupId>life.qbic</groupId>
<artifactId>data-model-lib</artifactId>
<version>1.2.0</version>
</dependency>
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
</dependency>
<dependency>
<groupId>org.vaadin.addons</groupId>
<artifactId>filteringtable</artifactId>
<version>1.0.0.v7</version>
</dependency>
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.6</version>
</dependency>
</dependencies>
</project>
Loading

0 comments on commit 4814ed9

Please sign in to comment.