Is there a history of changes for JAGS? I've been looking around the JAGS homepage and sourceforge and found nothing.
There is no changelog on web or in the release, one must look directly into the source code:
http://sourceforge.net/p/mcmc-jags/code-0/ci/default/tree/NEWS
Related
It is clear that there has been a lot of updates on the subject, however not much documentation is (yet) available, as far as I'm aware of. I downloaded the most recent commit from the feature/spectatorview branch of MixedrealityToolkit-Unity, and copied the MixedRealityToolkit.Extensions into my MRTK folder.
Now some of the noticable changes has to do with the PlatformSwitcher-holding prefab "SpectatorView - HoloLens". The script is marked as "SpectatorViewOld" and it could be interpreted as this is a deprecated prefab. There's also SpectatorView.ASA.HoloLens/Android, however these prefabs are seemingly having missing scripts, which prevents them from being usable in a project.
My question is, if there's an up-to-date guide on how to implement the SpectatorView, and if so, where can I find this/How do I go about it? Should I stick with an earlier commit?
Update:
We have migrated to a new repository with samples and better documentation, please take a look here: https://github.com/microsoft/MixedReality-SpectatorView.
==================================================
Yes, we currently have a stable branch that matches what we showcased at //BUILD:
https://github.com/microsoft/MixedRealityToolkit-Unity/tree/prerelease/2019.build.spectatorView
And, documentation for it here:
https://github.com/microsoft/MixedRealityToolkit-Unity/blob/prerelease/2019.build.spectatorView/Assets/MixedRealityToolkit.Extensions/SpectatorView/SpectatorView.md
Please give that a try.
We are still in active development as we push towards a V1, and soon will be cleaning up all the deprecated files and polishing of our documentation.
In my Liferay module, I want to use Liferay's SomeConvenientClass.
What is the recommended way to find out what module provides that class?
So that I can quickly add it to my build.gradle.
Ideally it should either:
return the module's group/name/version,
or say with certitude that this class does not exist in Liferay or is not exported.
Until now I go by trial-and-error and copy/paste from build.gradle files found in the wild, but I am looking for a more reliable method.
I have Liferay installed, and the source code of the exact same Liferay version, if that helps.
I tried mvnrepository but it does not seem to return anything, example: https://mvnrepository.com/search?q=AuditMessageProcessor
Have you tried http://search.maven.org/#advancedsearch ?
For example:
http://search.maven.org/#search|ga|1|c:"AuditMessageProcessor"
This is more an option than a real thing, but this is how I normally do:
be familiar with package naming conventions used by liferay and
inside apps: api, service, web...
be familiar with the bundle structure used by liferay, as their
use of resource folders, which are not so obvious sometimes...
With that in mind, normally on github is enough to navigate: portal->(kernel/impl/services/apps)->app service/api/web...
But this is a natural process that comes when you spend your day inside the code.
Normally, online jar locators help, but quite often I just rely on my IDE.
On my IDE I have all set-up with Spring dependency management, after I extracted the dependencies using Gogo shell with a running bundle. With Gogo you will not find classes, but modules and packs will be listed. (Gogo is probably what you are looking for btw, as it is able to list with version numbers)
Bottom line, if you need a list as a picture of a running environment, use Gogo.
With regards to the master code, just do not trust it! When it comes to modularity and bundles versioning Liferay is pretty messy (read The dependency management problem here: https://www.e-systems.tech/blog/-/blogs/liferay-digital-experience-platform-review-7-0-ga4).
For your step 7, you will need to chose an api version and code against it. The apis are more stable. You can impose a limit for compatibility on you bnd file, which will cause the system to issue warnings. On your environment, you can catch api changes earlier, let's say, you can ask gradle to use a module with an version number but any patch (using the "+" sing), when you build with a fresh cache or if you change gradle resolution strategy to download you dependencies more frequently, if the build breaks, well, you will see it.
Helpful start point: https://dev.liferay.com/pt/develop/reference/-/knowledge_base/7-0/using-the-felix-gogo-shell
This is how I do, it is slow and manual, so don't hesitate to suggest other methods.
Download Liferay's source code if you don't have it already.
Run find . -name SomeConvenientClass.java. If nothing is found, you can be sure the class is not part of Liferay.
In the path to the class, find the src folder level, and go just under that, so for instance if it is modules/apps/collaboration/document-library/document-library-web/src/main/java/com/liferay/document/library/web/portlet/action/DLViewMVCRenderCommand.java then go to modules/apps/collaboration/document-library/document-library-web/.
Hopefully there is a bnd.bnd file there, open it.
If the package of the class is not in the Export-Package section, then either give up (duplicate Liferay's code into your module), or use some dark tricks. If you believe the class should be exported, you can explain your case at https://issues.liferay.com/browse/LPS-70480 for future generations to enjoy.
Module name is the value of Bundle-SymbolicName.
Version is the value of Bundle-Version.
Group is probably com.liferay, although sometimes it is com.liferay.portal, not sure how to tell.
Build. Sometimes it fails because Maven repositories are missing a version, for instance com.liferay.document.library.web 1.0.11 is not available despite being used by DXP fix pack 30. Not sure what to do in such cases except choosing a "similar" version and hoping for the best.
I'm writing an app that uses the GitLab API, and I'd like to list the pages in the wiki. I can do something like http://gitlab/username/project/wikis/home.md to get the source of an individual file, and see all pages with http://gitlab/username/project/wikis/pages, but I can't do http://gitlab/username/project/wikis/pages.md due to a 500 error.
Is there a way I can retrieve the list of files in the wiki?
So there's now a GitLab Wiki API available which does everything I need:
https://docs.gitlab.com/ce/api/wikis.html
It can be used something like this:
https://gitlab.example.com/api/v4/projects/:project_id/wikis?with_content=1&private_token=yourtokenhere
Note; if this list is to facilitate a TOC (Table of content) for navigation purpose, you now have GitLab 13.5 (October 2020), which comes with:
Deep-level wiki navigation
In GitLab 13.5, along with the release of group wikis, we have another huge improvement in how to view and navigate the file structure of a wiki.
Currently, it’s very difficult to see where you are or understand the structure of a wiki if you have multiple folder levels. This makes it difficult to navigate, find pages, and mentally map your information.
With this release, we’ve introduced wiki deep nesting in the sidebar so you can see all of your pages and navigate accordingly.
See Documentation and Issue.
Possibly not what you wanted (and a bit late) but if you have modified your Sidebar (i.e. _sidebar) you can make a copy of it and then delete it.
You could also add link:pages[List all pages]
to your home page. That might avoid, somehow, the 500 you get from pages.md
I just upgraded the Typo3 from 6.2.26 to 7.6.10, but the styles at the front page are all missing. Just the content and data from the DB shown on it. I guess maybe it was the loss of.
So, if there somebody met this question too, share your ideas with me. Looking for your advice, many thanks.
First you should check if your JS/CSS files are present in the source code of your page. If they are, there are two possibilities, imo:
your html is cached but the cache files were deleted/moved. Solution: clean your cache (the best is to clean it from the install tool -> "Important actions")
Your baseURL/absRefPrefix is broken. I would advice to use config.absRefPrefix instead of baseURL (https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Config/Index.html)
I am looking for a JIRA plugin that will show the status of issues at a previous date I give it. So if I tell it Monday of last week, I would like all of the issues that existed at that time with their status at that time. I was wondering if such a plugin existed or if there is another way to go about this. Thanks for reading and for any help you provide.
*Note, I made a excel macro to basically do this but it includes a gigantic mysql query that I would not like not to use if such a plugin already exists.
I don't think that such a plugin exists at all because this would involve issue statistics to show how the issue changed over time.
You can post an feature request with the Atlassian JIRA team to see if this is possible or not. They could also include this feature in a future release or a proprietary plugin if they see that there is enough interest.
http://www.atlassian.com/resources/support