Elasticsearch Ingest-Attachment Plugin - Where to get zip distribution - repository

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.

Related

I want virtocommerce in my own local repository.(include storefront, platform and modules). How to setup all of these in my solutions?

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.

What's the recommended way to get the latest sakai code to test against?

My standard route has been to go to confluence, find the docs sections, then navigate through to the install docs for the version, e.g. sakai 10:
https://confluence.sakaiproject.org/x/iYGLBQ
Through one means or another I happened across the source route to this too, so starting here....
http://source.sakaiproject.org/release/
You get redirected to the latest stuff, and appended version numbers to that url gives you other docs, e.g. adding 2.8.2 or 10 to the end of the url
But the links to what I should download are quite often not there, at the time of writing the 10 tar ball and zip in the confluence links are dead and the source.sakaiproject links doesn't have the 10 docs yet (redirects to 2.9.3) presumably this is because v10 is not released yet....
So, I'd like to evaluate a new version of a sakai source install, what's the best way to do this? (considering the official documentation for install is still being formed)
Do I download the latest SVN, or the latest RC or the latest beta or??? How do I know what's best to test against without being "too" bleeding edge? Is there a recommended tar ball/zip link to test against? Is there a "latest good" SVN branch?
The latest code is always in the Sakai trunk (currently svn):
https://source.sakaiproject.org/svn/sakai/trunk/
That code may very well not be stable though as it is where things are being actively developed. If you are not actively developing then you should stick to the releases as indicated on the project website here:
http://sakaiproject.org/current-release
If you want to use something in between (say an upcoming release) then you can grab the most recent tag or maybe use a recent branch (both currently in svn, latest shown below at the time I write this):
https://source.sakaiproject.org/svn/sakai/branches/sakai-10.x/
https://source.sakaiproject.org/svn/sakai/tags/sakai-10-rc02/
The reality of the situation is that if you want to use something other than the release then you should really participate in the dev community for Sakai. Joining the mailing lists and the weekly calls will provide the information you are asking about and much more.

Original sources of org.eclipse.jface_3.2.2

I have google a lot and also download the Eclipse-Version 3.2.2 to get the source.
The plugin folder did'nt contain the sources.
Do somebody know where i can find/download them?
Did you try JFACE FOR ECLIPSE PAGE
http://wiki.eclipse.org/JFace

How to browse Metacello repositories in Pharo Smalltalk?

I have downloaded Pharo 1.2.2 #12353 and wanted to install some packages in a easier way than going through Monticello Browser. I do not want to copy and paste scripts to install packages. After I opened the Menu, Tools, Configuration Browser a new window is shown with 3 ConfigurationOf...
ConfigurationOfFFI
ConfigurationOfMagma
ConfigurationOfVistaCursors
There is no help or description of what's the purpose of the Configuration Browser. What's one supposed to do with that?
there is no way to select a repository of configurations
there is no menu option to add a ConfigurationOf
there is no way to browse the Configurations from that window
Besides, is that the right tool to browse a "Metacello Repository" like http://www.squeaksource.com/MetacelloRepository.html ?
There is a custom browser to Metacello? Why isn't included in the release by default?
You can give MetacelloBrowser a try. It is aimed at providing a Metacello-centric interface for managing your project. The browser is still in development, but can be used for many tasks quite nicely.
If you decide to take it for a spin, please submit any issues here. Join the Metacello mailing list if you have any questions or comments.
Dale
Please report an issue about the Configuration Browser at http://code.google.com/p/pharo/issues/list and post your difficulties to the Pharo list. I played with the tool too and couldn't understand it either.
see
http://lists.gforge.inria.fr/pipermail/pharo-project/2011-December/057409.html
and for its origins:
http://code.google.com/p/pharo/issues/detail?id=2752
The ideas is that we have an own Squeaksource repo (universe) for a
specific Pharo version where we have a copy all the ConfigurationOfXXX
that are known to work in this specific Pharo version.
Since nobody (yet) mainted the one for Pharo 1.3 the browser is just empty.
I will try to find the time to fill the repo for Pharo 1.3

Using Maven for project distribution

I have an Project that I distribute by sending out large packages. I'd like to know if there is a user friendly way of using Maven to distribute updates of the project? I'd need something like what is done for updating softwares like Firefox or Acrobat Reader. Check a respository, warn user of an update, download and reconfigure. All within a simple and friendly interface. Alternative open source java projects are welcome.
If your project is a library: You need to set up a public maven repository (or use Maven Central). This way, your users can fetch the latest version of your library by updating their POM.
If your project is something else, you can use a Maven repository to keep the packages in a place for easy deployment for you (and easy download for everyone else). Next, you'll need to point your software to the site and download the file "maven-metadata.xml" once in a while. Maven will create and manage this file for you when you say "mvn deploy". The file contains the latest version numbers.
All you have to do is to download this small file and examine it. If there is a new version, open a dialog for your user so they can decide to download it. I suggest to offer "Only download" and "Download and upgrade" as separate options because users like to download some time in the background and then install between two projects. They don't like nagging dialogs ("New version available. Download and ruin your day now?" ... "I asked five minutes ago. Download now!" ... "Downloading anyway. Credit card details found on your hard drive. Selecting other important software you need. Purchasing now. Have a nice day!" ;) ).
I don't think maven has any standard way of providing this functionality. Maven does have notion of "release" and "deploy", but these don't apply to the scenario you are describing.