I don't really use minitest in my Ruby projects.
How can I exclude it from being shown in autocompletion options?
Unfortunately it is impossible to remove minitest dependency from Gemfile because it is part of activesupport's list of dependencies.
Related question:
JetBrains Idea: exclude package & classes from autocomplete
At the moment it's not possible, please follow the corresponding issues:
your particular case
https://youtrack.jetbrains.com/issue/RUBY-21335
general approach improvement
https://youtrack.jetbrains.com/issue/RUBY-21334
Related
Greetings,
This question is about vscode itself, the Microsoft build. I would
like to know all the dependencies it does have, recursively until I
hit the transitive closure. I also need to know the version/license of
each one of these dependencies. By dependencies I mean any piece of
software it does require to run, whether is something you install at
the OS level with, a bundled component/library, a nodejs/yarn package,
a vscode internal extension, etc. Essentially, I want to know all the
dependencies regardless of the "layer" at which these dependencies get
used.
I guess we can start with the OSS dependencies, given the commercial
build will have a superset of those. In that regard, I see at least 4
files on the github repo which look like partial views of this total
set of dependencies:
https://github.com/microsoft/vscode/blob/main/ThirdPartyNotices.txt
https://github.com/microsoft/vscode/blob/main/package.json
https://github.com/microsoft/vscode/blob/main/cglicenses.json
https://github.com/microsoft/vscode/blob/main/cgmanifest.json
The first question I would have is whether any of the files above is
already recursive, meaning it also includes the dependencies of the
dependencies of the dependencies ... etc. The second question would be
how to assemble the total list of dependencies/version/licenses I am
craving for.
Thank you in advance and kudos for the great tool.
I want to use doxygen with my project to generate documentation.
All "normal" dependencies of my project are managed by vcpkg and I was hoping that I can use doxygen this way as well, although it is not a lib that I link against, but a tool that I process my files with.
There seems to be some need for this, as this issue seems to be posted and some solution is merged.
When I dig further I found that there is a function called vcpkg_find_acquire_program that can specifically be called with doxygen argument. However, all examples are using portfile.cmake which my project does not have.
In my project I use:
vcpkg.json that acts as a manifest file. I specify the project name, version, dependencies. But I cannot put doxygen in the dependency list, because there is no doxygen portfile
CMakeLists.txt where I can specify that I require doxygen, but cmake won't manage downloading/installing it for me. It's vcpkg's job.
CMakeSettings.json where I specify build configurations
...and that is about it in terms of project configuration. So, where should I put that vcpkg_find_acquire_program? Or is there a different way?
I consider migrating a project to Apache Jena but can't get my mind around Jena's architecture. In this example...
https://github.com/apache/jena/tree/master/jena-permissions/src/example/java/org/apache/jena/permissions/example
... we make use of the "permissions" package.
But when I try to imitate what they do in the example using Eclipse and importing the *.jar files from apache-jena-3.1.1 as dependencies, the package org.apache.jena.permissions seems to be missing or inaccessible. Other packages such as org.apache.jena.rdf.model are accessible.
How can I access this package? Thank you very much.
--
Okay, I found the package at Maven: https://jena.apache.org/download/maven.html
Is this the only way to get it, even if you do not use Maven?
mvnrepository.com is usually a better place to search for a Java package:
If you still want to include JARs by hand (the link above is highlighted), don't forget to manually resolve the JARs that jena-permissions depends on:
P.S. I side with #AndyS that learning a dependency management system is 100% worth the effort.
I found the download link on my own. You need to go here to get the package: https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-permissions/
I've noticed that in eclipse if you Right click on a project -> Grails Tools -> You have the option to 'Download Source Jars'.
What is the point of this and what are some common reasons as to why you would want to do this?
Grails 2.2.3
Edit:
I'm not even sure what grails does instead of that.
Many (most) libraries (JARs, "artifacts" in the Maven terminology) publish a sources archive alongside their binary artifacts in the repositories. This can be useful for Eclipse to show you the Javadoc and source code when you're using the library in your projects. As #JonSkeet commented above, it's very useful to have source code available directly in the IDE when using a library.
By default, Grails does not download the sources for artifacts; this option triggers it to do so and attach the sources to the binary JARs.
Agreed with E-Riz.
Here are the reasons I use the sources:
i want to have a deeper understanding of how the library works when debugging my own depending code
i want to find a possible bug in the library, so I can fork it and apply my own patch. i will possibly share this with the maintainers as a pull request if I'm willing to spend that much time on it.
i want to find out what logging systems it uses that might be poorly documented, so I can see better what their code is doing during runtime, to troubleshooting complicated problems.
I have a project where I'd like to use https://www.nuget.org/packages/Bootstrap.Datepicker/, so being a good modern developer I tell VS to add that nuget package. Which is cool. But along with it comes Bootstrap 2.3.1, which I know is a dependency of that package. But my project already has the Bootstrap Less Source (3.2.0.1) package installed, and I'm concerned about having two different "instances" of the "same" package in my project. Another developer on my team has pointed out that any and all Nuget packages that are based on bootstrap probably will require the default one, not the less source package we're using, even though that works best for us.
Is there some way in nuget to tell it to ignore dependencies, or convince it that instead of the dependency it's expecting, it's been met in another way?