Develop Reference

When I created a repository on GitHub, it kept showing quick setup page. How should I remove that page and proceed?

When I created a repository on GitHub, it kept showing quick setup page, how should I remove that page and proceed?

The quick setup page only shows when there's nothing in your repository yet. What you need to do is follow the instructions and push something to your repository, then the setup page will disappear.
If for some reason the instructions aren't showing you how to do this, you have two options:
Option 1: clone it based on the regular naming scheme
git clone git#github.com:username/repository.git
Replace username and repository with your username and the repository name, respectively. If the repository is owned by an organization, replace username by the organization name.
Option 2: create a repository locally and setup a remote
git init
git remote add origin git#github.com:username/repository.git
touch README.md
git commit -a -m "Created README"
git push -u origin master
Again, replace username and repository with your username and the repository name, respectively. If the repository is owned by an organization, replace username by the organization name.

When creating a new repository you can check 'Initialize this repository with a README' and you will be taken to the normal github repository view.

Spring Cloud config authentication with AWS Code Commit

I'm novice to use spring cloud config server, so is first time for me and i hope i can receive help, thanks in advance for this.
What i can try to do is to configure Spring cloud Configuration Server as central server for configurations among all Microservices.
We are using AWS CodeCommit as SCM repository.
The problem is that i receive always the same error once i try to inve an existing file on AWS CC.
I suppose is a problem of authentication, but i'm not sure
Error screenshot
This is the bootstrap configuration on Spring CSC
server.port=9090
management.security.enabled=false
logging.level.org.springframework.web: TRACE
spring.application.name=config-service
spring.cloud.config.server.git.uri: https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/ServiceLayer
This is the file in my SCM repository that i'm trying to call:
configuration:
projectName: ms-login
server:
port: 8000
message:
greeting: Hello from the configuration
I've make a several try:
Placed the AWS GIT Credential (NOT the AWS Secret key) in bootstrap properties, but without result. Example:
spring.cloud.config.server.git.username: sergio.greco-at-682088819034
spring.cloud.config.server.git.password: xxxxxxx
Placed the AWS Secret Key \ Identity ID as java parameter once start, as follow:
-Daws.accessKeyId=xxxxxxxxYNOA -Daws.secretKey=xxxxxxxxxxxxxxxx
Set environment variables AWS_ACCESS_KEY_ID \ AWS_SECRET_ACCESS_KEY.
Can someone help me?

You need has the AWS SDK in the classpath.
Relevant documentation on this: http://cloud.spring.io/spring-cloud-static/spring-cloud-config/1.3.1.RELEASE/
Search for “Authentication with AWS CodeCommit”.
Note: The aws-java-sdk-core jar is an optional dependency. If the aws-java-sdk-core jar is not on your classpath, then the AWS Code Commit credential provider will not be created regardless of the git server URI.

Gradle build is failing [Could not resolve all dependencies for configuration ':compile'.]

I am trying for so many days to resolve this exception , followed many blogs and couldn't find solution. when I run a bundle.gradle by giving jettyRun as command
I am getting an exception
**FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all dependencies for configuration ':compile'.
> Could not resolve javax.servlet:servlet-api:2.5.
Required by:
:1-SimpleServlet:unspecified
> Could not GET 'http://repo1.maven.org/maven2/javax/servlet/servlet-api/2.5/servlet-api-2.5.pom'.
> Connection to http://repo1.maven.org refused
> Could not resolve org.apache.commons:commons-io:1.3.2.
Required by:
:1-SimpleServlet:unspecified
> Could not GET 'http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom'.
> Connection to http://repo1.maven.org refused**

The real error is this:
Connection to http://repo1.maven.org refused
Gradle needs to download the dependencies listed in the error message to be able to compile the project.
You're probably behind a firewall or your Internet connection isn't working. You need to make sure Gradle can access http://repo1.maven.org.
Note: Maven Central (http://repo1.maven.org) can be accessed with a browser. If you see the message "Browsing for this directory has been disabled" that means your browser could connect to the server (the error is a special message my Maven Central, not a standard HTTP error message).
If you see this but Maven or Gradle fail, then you need to check your browser's/OS's proxy settings and configure your tool accordingly.
Related:
How do I use Maven through a proxy?
Gradle proxy configuration

Using --refresh-dependencies switch with gradle, helped me to resolve this issue.

In my case the problem was resolved when I changed my gradle version from 4.6 to 4.7.

#Aaron Digulla said I have firewall problem.
I was having problem with GSON dependency, (hope it will solve other dependecy problems also) and this answer solved the problem. Stack Overflow Could not resolve all dependencies for configuration ':classpath'
#Kangars post :
This is what i have in my gradle.build for build script and allprojects
buildscript {
repositories {
jcenter {
url "http://jcenter.bintray.com/"
}
}
}
allprojects {
repositories {
jcenter {
url "http://jcenter.bintray.com/"
}
}
}

This is because of slow internet connection or you haven't configure proxy settings correctly. Gradle needs to download some dependencies , if it cant access the repository it fires this error. All you have to do is check your internet connection and make sure gradle can access the maven repository.

The root cause
Connection to http://repo1.maven.org refused
indicates that the build is failing as gradle is not able to fetch some dependencies from the repository.
Here is a list of causes and corresponding resolutions you might want to try:
Internet connectivity issues - Have a good internet speed and connectivity
Firewall (system or third party) - Ensure firewall is not blocking access to the repository
Working behind a proxy - Gradle proxy configuration
Firewall or some random application meddling with proxy application1 - Kill the process meddling with the proxy application
The proxy application causes certificate problems2 - Import proxy application's certificate
References:
Telerik forum's answer on how to fix internet connectivity issue while using Fiddler
Telerik forum's answer on secure connection issue while using Fiddler

It looks like you don't have a working internet connection or haven't configured your proxy/firewall.
Please check if you can access repo1.maven.org from commandline or a browser.

I used the steps below to fix it.
Go to command prompt and set the java opts.
SET JAVA_OPTS=-Dhttp.proxyHost=your_proxy_server_name -Dhttp.proxyPort=your_proxy_port -Dhttp.nonProxyHosts=127.0.0.1
Then build your Gradle application and all the connection refused errors no longer appear.
gradle clean build distZip

For my case it was a poor connection issue so the IDE couldn't get resources online

Using Nexus as feature repository

Is there a way to add a secured Nexus repository as feature repository to Apache Karaf?
I tried to run the command:
karaf#root()> feature:repo-add http://<user>:<password>#<my-repository>
But I get the following error:
Adding feature url http://<user>:<password>#<my-repository> Error executing command: Server returned HTTP response code: 401 for URL: http://<user>:<password>#<my-repository>
I'm using Apache Karaf 3.0.0.
Thanks,
Mickael

The solution is simple.
Install Maven on the server on which Karaf is running and configure it. Generally, you will configure it through the file settings.xml present in ~/.m2. The credentials for accessing the Nexus repository are indicated in the file.
Finally, instead of using an HTTP URL for referencing your feature, use a Maven URL of the form:
mvn:<groupId>/<artifactId>/<version>/xml/features
The feature will be resolved through Maven.

You can add your own Maven repository to org.ops4j.pax.url.mvn.repositories.
config:edit org.ops4j.pax.url.mvn
config:property-set org.ops4j.pax.url.mvn.repositories http://your.nexus.repo/here
config:update

maven build doesnot consider new repository url

We had to change the repository location in the Pom.xml but when I run Maven(from within IntelliJ IDE) I notice in the logs that it still points to the old URL.
The maven repository in our organization has recently been moved to a new URL. The old URL is not valid anymore and hence I get connection timeout errors in the logs. I verified that all the instances of old URL has been updated in the POM.xmls.
Here is the excerpt of the logs. I do not find any references of the old URL anywhere on my machine.
[Proj Guard] Skipping disabled repository central
[Proj Guard] snapshot com.XYZ.Proj:Proj-libraries-conflict-guard:4.trunk-SNAPSHOT: checking for updates from mvnnexus
[Proj Guard] Checking for pre-existing User-Agent configuration.
[Proj Guard] Adding User-Agent configuration.
[Proj Guard] Connecting to repository: 'mvnnexus' with url: 'http://ABC.XYZ.corp:8081/nexus/content/groups/public'.
[Proj Guard] repository metadata for: 'snapshot com.XYZ.Proj:Proj-libraries-conflict-guard:4.trunk-SNAPSHOT' could not be retrieved from repository: mvnnexus due to an error: Error transferring file: Connection timed out: connect
org.apache.maven.wagon.TransferFailedException: Error transferring file: Connection timed out: connect
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:546)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:443)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97)
at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65)
at org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:63)
at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:55)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:145)
The URL has been changed from(example) http:// ABC.XYZ.corp:8081/nexus/content/groups/public
to http:// nexus.Test.corp/nexus/content/groups/public but it does not seem to be picking.
Am I missing anything?
Please help me figure this out, let me know if you need any further info.