i want to add APM as a custom open tracer in wso2am version 4.0.0 but i can't find anything about custom tracing in the documentation. in the previous version of wso2am i.e 3.2.0 there was a section which explained how to add custom tracer. it sounds like that section has been removed in the latest version. any idea how can i add elastic APM as custom tracer?
Please find the same section in here for APIM 4.0.0.
https://apim.docs.wso2.com/en/latest/observe/api-manager/traces/monitoring-with-opentracing/#using-the-custom-tracer-implementation
Related
I'm working with several repositories, but now I need to download the lastest version of some artifacts from a generic repository. Following wiki instructions I created a new layout like this.
Layout description
After that, I have added a new repository with this layout and deployed several artifacts according the layout as you can see.
Artifacts in repository
So, according this documentation: https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-ArtifactLatestVersionSearchBasedonLayout
I expected to download the latest version using this:
http://my-artifactory/distributable-example/OrgExample/moduleX/[RELEASE]/installer/example1-[RELEASE].exe
Instead of that I only get a 404 error. So, how can I get the lastest version?
I have a doubt at this moment.. I'm wondering how to know what is the latest stable version in Github repository of symfony? Any help?
Using symfony new project_name it says it is 2.7.3, but how to know it in Github to fork it?
In GitHub you can look for tags. Only stable realeases are marked by tags with only version in name. Sometimes Symfony have Beta-versions. These versions are marked with tags too but always have appendix: BETA.
So for now the actual stable version is 2.7.4. You can see it in screenshot:
You could check the symfony road map.
http://symfony.com/roadmap
I made a plugin, made revisions to it, and commited it again, yet in the admin area under plugins, I do not see under my plugin that an update is available.
So I had, say, version 1.2.0 , and now I made a new version 1.9.0 and I commited it, and on the wordpress site if you click the download button you WILL get the 1.9.0 version, but people that already have version 1.2.0 installed won't see an update option.
Also, on the wordpress site, it always says "Download version 1.0", even though the current version is 1.9.5 (that's what it says in the readme.txt under the stable tag)
How to fix this?
It sounds like your trunk/stable tag setup is off. This is the way WordPress recommends releasing plugin updates on their site, and what I use for publishing new version of my plugins.
Make changes to your plugin and commit to /trunk
When you are ready to release a new version update your main plugin PHP file under /trunk with the new version number in the plugin header.
Update /trunk/readme.txt to include the new changelog info and set the stable tag to the same version as in #2
Create a tag of /trunk using the same version number specified in the stable tag
The new version of your plugin should not be automatically delivered to anyone who has your plugin installed.
Does anyone know where to find MeteorJS documentation for past versions? There does not seem to be an option on the website to switch to an older version like there is on other documentation sites.
You can download the tag for the version you want and run the app in the /docs directory.
The docs directory is a meteor app. All you need to do is meteor inside of it.
E.g for version 0.7.2:
git clone git#github.com:meteor/meteor.git
cd meteor
git checkout release/0.7.2
cd docs
meteor
open localhost:3000
One way is to dig in through the GitHub repo history for MeteorJS https://github.com/meteor/meteor/commits/devel/docs
Sorry to revive this thread a year in. But for users of the current Meteor 1.3 release it might be reassuring to know that you can get at least access to the Meteor 1.2 guide directly on guide.meteor.com via the small drop-down menu on top. Just switch it from "1.3" to "1.2".
For getting the full API docs or even older versions of the guide the currently accepted answer still applies, of course.
You can read it in plain text (with no sourcecode examples) at:
src meteor docs 0.6.5
src meteor docs 0.7.2
So it seems that giving Nexus a version of "LATEST" will tell it to redirect to latest version of the specified build product.
Where in the docs is this actually documented?
The FAQ contains detailed explanation:
https://docs.sonatype.com/display/SPRTNXOSS/Nexus+FAQ#NexusFAQ-Q.HowcanIretrieveasnapshotifIdon%27tknowtheexactfilename%3F
But also the REST API doco (bundled with every Nexus instance) contains it too. Just login as Admin, go to Administration, Plugin Console, select Core Documentation plugin in grid, and client on the "Core API" link on lower panel.