I am using keytool-maven-plugin to create a PKCS#12 keystore, but skip if it
already exist. This keystore is used with continous builds. Somehow the
resulting self-signed keystore.p12 cannot be used to verify a released JAR
that has been signed with a PKCS12 keystore containing a purchased
certific
Trying to also use http with Nexus site deployment didn't work.
[INFO] --- maven-site-plugin:3.4:deploy (default-deploy) @ MyApp ---
http://maven-vm1:8081/nexus/content/sites/site/MyApp/ - Session: Opened
[INFO] Pushing /home/sverre/workspace/MyApp-R11/target/site
[INFO]>>> to http://maven-v
That was it.
snapshots
http://maven-vm1:8081/nexus/content/repositories/snapshots
releases
http://maven-vm1:8081/nexus/content/repositories/releases
I had to create two servers with both these Id's, then it worked
I decided to start using HTTP/HTTPS instead of SCP for uploading and
downloading artefacts from my Nexus server.
However switching the URL didn't work.
I have created a user in Nexus called build.
In my settings.xml I have the following configuration taken from
http://books.sonatype.com/nexus-book
I tried backtracking some changes I have made since my last successful
release.
It fails when I use Apache Maven 3.2.1 and it works fine when I'm using
Apache Maven 3.0.4
--
View this message in context:
http://maven.40175.n5.nabble.com/Hangs-when-downloading-maven-metadata-xml-tp5791924p5791
Maven hangs when it tries to download the maven-metadata.xml file. However
uploading artifacts works fine.
This happens with both mvn release:perform and mvn deploy
[INFO] Downloading:
scp://build/srv/maven/releases/com/mycomp/myproject/maven-metadata.xml
[INFO] 421/421 B
[INFO] 422/421 B
I could take a look at User Token for the settings.xml if using http for
distribution management is the preferred way. But why is it preferred over
scp?
I'm not using SCP to Nexus. I'm using SCP to upload the artifacts directly
to the storage location where Nexus keeps its releases and snapshots.
I know uploading through SCP is possible. At my previous workplace we
uploaded the artifacts through SCP directly to the server location and not
the web location. I have replicated it right down as I remember it. There
could possible just be some user authentication problem. I could possibly
solve
Building my project with Jenkins. The workspace is on a jenkins slave node.
This slave node happens to be the same server which is running the Sonatype
Nexus Repository.
Jenkins master is running on user called jenkins. The slave node is
configured for the user called build on that slave, but I do
That was it and actually so simple. Never thought it could have anything to
do with JCE. I had disabled all but the 192/256-bit algorithms on my SSH.
Installing the JCE unlimited policy did the trick.
--
View this message in context:
http://maven.40175.n5.nabble.com/Failure-to-deploy-Cannot-con
I am trying to deploy my application.
Before I try to deploy to the actual server, I am using my own computer as
the remote repository.
snapshots
Repository for snapshot versions of company jars
scp://mymachine/srv/maven/snapshot
11 matches
Mail list logo
