I am installing the orion pep proxy but I think that I have not downloaded the correct version and I am having errors when using a local instance of KeyRock to validate and generate tokens.
I know that the latest version is 0.6.0 but i do not know how to complete the following command to obtain the last version:
./create-rpm.sh
Which is the difference between version and number?
Could you help me with this?
Thanks in advance
The idea of having those two numbers is to help the Release Engineer in debugging their releases, or changes they make to the packagin process itself. The "release number" indicates the version of the package, not the one of the software. E.g.: if you are packaging version 0.6.0, you usually will use release number 1; but, if you find out that you want to add some dependencies for the spec, or you want to update the package to change part of the packaging process, for example, and you try to replace the installed version with a new one, the system will claim the package is up-to-date; in that case, you increase the release number (as the software itself, that is, the Node.js files that constitute the PEP Proxy) hasn't change.
Hope this clarifies the behavior.
Related
I'm trying to initiate astro. When i don't choose a framework i get this error although i have git installed and fully working. Any help will be highly appreciated.
√ Which frameworks would you like to use? »
> Copying project files...
could not find commit hash for latest
This seems to be an issue with degit. Please check if you have 'git' installed on your system, and install it if you don't have (https://git-scm.com).
If you do have 'git' installed, please file a new issue here: https://github.com/withastro/astro/issues
It depends on your OS and environment.
For instance, withastro/astro issue 2144 reports the exact same error message, but on Windows, using Linux on WSL2 (Ubuntu 20.04.3 LTS).
Double-check your %PATH%/$PATH in your execution environment.
Update Oct. 2022, ten month later: withastro/astro issue 2144 is reported closed with the workaround by Matej Bunček:
As I was researching this seems to be a general issue with NPM for those who uses SSH.
There's an open issue here: npm/cli#2610 which is still far from being resolved and it's a huge thread.
Some folks might be interested in these workarounds to get it working.
git config --global url."https://github.com/".insteadOf git#github.com:
git config --global url."https://".insteadOf git://
Also I've tried yarn, npm and pnpm, all of them seems to have same problem so I believe it's core problem of node.
Also both npm 6 and 7 are not working.
Not a direct solution to your error message, but a general solution for those kinds of errors:
I would recommend doing the development inside docker containers, so called devcontainers.
Since you will develop in separate and isolated environments containing only the project's minimum dependencies and tools, it is a lot less likely to face OS specific issues in general.
Here are some resources to get started:
https://code.visualstudio.com/docs/remote/containers
https://microsoft.github.io/code-with-engineering-playbook/developer-experience/devcontainers/
https://github.com/microsoft/vscode-dev-containers
Currently I am going to verify FIWARE.
Release 7.5 was announced, but there are components whose version is lower in the core component.
cygnus
Release7.4 : version2.0.0
Release7.5 : version1.9.0
sth-comet
Release7.4 : version2.4.0
Release7.5 : version2.3.0
I want to know the reason why the version of the component is going down.
With regards to Cygnus, the short history is that FIWARE wrongly used "Cygnus" as software name in FIWARE 7.4 for a component that in FIWARE 7.5 was renamed to "Draco". Cygnus stills existing of course but release 2.0.0 has not come yet. Last Cygnus available version in the moment of writting this is Cygnus 1.10.0, to be included as part of FIWARE release 7.5.1.
With regards to STH, probably FIWARE releases are still using this fork as reference, when it should be using the original one. Note the original repository is the most updated and the one which uses version 2.4.0 at the present moment.
#fgalan is correct, some elements were inconsistently labelled in release 7.4 and 7.5. A patch release has finally corrected this.
As of 7.5.1, the following versions are correct:
cygnus 1.10.0
sth-comet 2.5.0
draco FIWARE_7.5
The new draco generic enabler had been initially released as cygnus 2.x which was incorrect.
I'm trying to replicate the installation guide to integrate Wirecloud 1.0.1 with the latest version of IDM Keyrock.
I'd like to understand if the guide in the documentation is valid again for this version of WC.
Thanks in advance for the answers.
As you suspected, the linked documentation is not valid for WireCloud v1.0.1, you linked to the latest branch of the documentation, that is the documentation for the development version of WireCloud.
The documentation on how to configure WireCloud v1.0.1 to use the IdM can be found in this link.
We know that is not clear that the latest branch is the one used for document the development version, but Read The Docs does not allow us to rename (or we do not know yet how to do it) this branch using a more meaningful name (e.g. develop). The default branch is stable (pointing to the documentation of the latest stable version of WireCloud) but it has proben to not be enough. We have created a ticket for improving this aspect.
I'm trying to implement a continuous deployment system and I seem to not be able to find a good answer for our problem.
We use Jenkins to run a maven build to generate our artifacts and deploy them to Nexus. I see a few projects that bundle up everything into a single war or tar file, extract one file per request from Nexus by name and deploy it to an application server, but this requires them to know beforehand what versions they have available.
My project has quite a few jars/wars/binaries among other artifacts, which don't get deployed using an application server. What we want to do is be able to do is pull any snapshot or release revision of the software out of nexus and either generate an install package or deliver it directly to a remote server.
Clarification: I want QA or development to be able to select a version from Jenkins; where Jenkins will poll Nexus for the available versions, then perform an automated deploy to a server from Nexus.
Is there an easy nexus/maven way to get software out to a testing system?
So, is there a way to poll nexus to determine what revisions are available through ant/ivy, Jenkins, maven, gradle? I'll write in something else if it helps.
I see that a similar question was asked here: How do I choose an artifact from Nexus in a Hudson / Jenkins job?, but it is as of yet unanswered 9 months later.
Nexus gives you a standard HTTP browsing capability. You could browse the repository through HTTP and see what is available.
I still don't understand your Use Case though. If you know which versions of the project you want then what is the problem?
The easiest would be to write an installer pom.xml that has in it a ${} placeholder for the version you want for the artifacts then invoke mvn with mvn package -Dproduct.version=1.0.0
If you use a container, PAX has plugins that allow you to specific artifacts like mvn:myGroup/myArtifact/myVersion and it will auto pull from Maven.
Nexus isn't doing any magic. It's all well known paths on a URL of groups/artifactId/versions
I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.