I am trying to use the nexus API, in order to retrieve a maven artifact.
The problem is that I want in a first step to propose the user to chose the version number. To do so, I thought I could use the REST API, but regarding the documentation, it seems that it is not possible.
Any idea?
You need to use the alternative REST API provided by the Nexus Indexer Lucene Plugin
The following example retrieves details of the available log4j artifacts:
https://repository.sonatype.org/service/local/lucene/search?g=log4j&a=log4j
Related
How to take artifactory package builds details thru api. I have only the artifact(package), with this i need to find the builds details which is available under in builds tab...
Please help...
If you mean 'Build Info' then you can use the get Build Info REST API:
https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-BuildInfo
I'm looking for a way to install the ingest-attachment plugin in offline mode.
So to do it i first need download the zip distribution of this plugin.
Official documentation (https://www.elastic.co/guide/en/elasticsearch/plugins/master/ingest-attachment.html) provides a non working link on their artifact repository
Would anyone have an idea where to download a stable/released zip version of this plugin ?
Many thanks.
Ok seems like the link they propose is broken cause the version does not exist anymore in their artifact repository.
I had to get a previous version (5.1.1) instead. It's just a shame they do not track any dead link in their documentation for massive indexation / analytics products company... or at least propose a clear URL to browse all available versions.
I want virtocommerce in my own local repository.
storefront is a solution that will configure it according to the following link:
Storefront Source Code Getting Started
And it works.
But I want to have a solution For platforms and modules,
Like the link below:
vc-integrations
But I need the platform and modules to be connected to the github for the latest changes.
I've studied the link below:
Source Code Getting Started
but I do not understand how should I configure for my goals (one solution for platfrom and modules and fork, clone ,upstream for all for get latest versions of them)
We've used to have a single repository and single solution for Virto Commerce Manager and modules (vc-integrations). It was difficult to maintain and release often. That's why the single repository was split into many "1 module per repository" pieces.
We consider that in most cases having only Virto Commerce Manager configured should be sufficient. What's your scenario? Check "Manual module installation from source code" section in Source Code Getting Started to get started.
Are there any plugins available for this? Does SoapUI offer plugins/addins anyway?
Thank.
It is not clear what you are asking.
SoapUI generates a soapui.log by default in the current working directory. Basic information is available in the official documentation, under the heading "Tip 7) Read the Log".
As for plugins: yes there are plugins available, and described in the official documentation as well.
Update:
If you are after logs of all the calls you made, then you need to launch the test runner with the -a or -A switch. As always official documentation is available for launching from the GUI or CLI.
Don't actually know if SOAPUI has any kind of plugins. But you could create your own reporting structure, which would be really cool because you can customize it however you want to. In our project, we write the expected and update the actual values into the data sink and write the test status into the same, all using the groovy script :)
I have an MVC App which uses Azure AD, it works very well using the WindowsAzure.AD.Graph.2013_04_05 helper project that Microsoft made available. This project is now outdated, but looking at the new Nuget Package, the two require code changes.
I have two questions, How long can I use the old one before I find myself locked out of my own app. Second, has anyone migrated between them?
What I have is very simple, its just an Auth Filter which checks if a user is in one or more groups.
You should have at least a year from the announcement of a REST version being deprecated; a REST version is not the same as a NuGet package version, so you'll need to understand the underlying version in use.
Please refer to this Microsoft support policy on Azure-related REST APIs and libraries: http://support.microsoft.com/gp/azure-cloud-lifecycle-faq