profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dirkey/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Dirk Hoffmann dirkey asado GmbH Frankfurt

dirkey/buildship 0

The Eclipse Plug-ins for Gradle project.

dirkey/code 0

A place for all the cool JavaFX code from fxexperience.com blog

dirkey/flow 0

Flow is a Java framework binding Vaadin web components to Java. This is part of Vaadin 10+.

dirkey/flow-viritin 0

Viritin inspired project for Vaadin Flow

dirkey/Froxlor 0

The server administration software for your needs - The official Froxlor development Git repository

dirkey/intellij-community 0

IntelliJ IDEA Community Edition

dirkey/jfxtras 0

A supporting library for JavaFX, containing helper classes, extended layouts, controls and other interesting widgets.

dirkey/masonite 0

The Modern And Developer Centric Python Web Framework. Be sure to read the documentation and join the Slack channel questions: http://slack.masoniteproject.com

dirkey/picard 0

MusicBrainz Picard

dirkey/redmine_bbb 0

Integrate BigBlueButton server with redmine

issue commentgzm55/project-settings-maven-extension

Credentials for mirror

Yes, exactly! You need manual tasks to do so. Some projects even checkin the settings.xml in the repo, with the part to copy and paste to the users settings.xml. But why! Why we need this manual task, where there is the authentication known in the company anyway. It should only deny access from the outer world. Please consider: This should only be for a user to read the repository (not deploy)! If the ignore is mention to be a security feature, you should stop the build if these settings are present. Ignore don't stop developer to add them anyway.

Dichotomia

comment created time in 25 days

issue commentgzm55/project-settings-maven-extension

Credentials for mirror

I think it's not a good idea to ignore any setting. There are some use cases where it makes total sense. Most enterprises host a dedicated or a shared repo. Reading and Deploying needs authentication. Clearly, you should never commit your credentials which got deploy capabilities. On the other hand, the reading authentication is shared over the wiki or email anyways. In our case: I wish I could provide a settings file with the credentials for accessing the repo. The build server overwrites it with the -s ci_settings.xml file. So, no harm involved. If the developer got the rights to clone the project, he don't need to change any files at all.

Dichotomia

comment created time in 25 days