In VSCode we can exclude some files from being shown by adding the following to settings.json:
"files.exclude": {
"**/*.exe": true
},
How do I do this in Fleet?
Related
There are several standard Java dependencies that have forks with the same maven coordinates and a "redhat-xxx" suffix in their version number, for example
commons-configuration:common-configuration
org.eclipse.microprofile.config:microprofile-config-api
javax.enterprise:cdi-api
My question is
(How) can I configure renovate to exclude all dependencies whose version matches /redhat-\d+$/ ?
There is a similar question here, but that asks for a more restricted set of dependencies. If I were to define a packageRule like
{
"packageRules": [
{
"groupName" : "Exclude all redhat-xyz versions"
"matchPackagePatterns": [".*"],
"allowedVersions": "!/redhat-\\d+$/"
}
]
}
It would group all dependencies into one giant pull request which isn't helpful.
Try to set registryUrls to standard Maven repo so that Redhat dependencies and such are not checked:
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["config:base"],
"packageRules": [{
"matchManagers": ["maven"],
"registryUrls": ["https://repo.maven.apache.org/maven2"],
}]
}
or use your given config and add "enabled": false
What should be in "pattern": of Artifactory downloadSpec file to include or skip sub folder
repo / folderA / folderB / *.xml
repo / folderA / *.xml
So I need to download xmls from folderA or from specific subfolder of folderA
Normally I would write :: "pattern": "repo/folderA/**/*.xml" but this pattern cant find artifacts under folderA
In case you have a small amount of folders under folderA, you can use the "excludePatterns" feature. For example:
{
"files": [
{
"pattern": "repo/folderA/*.xml",
"excludePatterns": ["folderA/folderC/*","folderA/folderd/*"]
}
]
}
You can read more about exclude patterns on JFrog CLI File Specs documentation or JFrog CI servers File Specs documentation (use the one that relevant for you).
If you have too many folders under folderA or the folders name will be changed in future, use two fileSpacs for download:
{
"files": [
{
"pattern": "repo/folderA/*.xml",
"recursive": false
},
{
"pattern": "repo/folderA/folderB/*.xml",
"recursive": false
}
]
}
I want the auto-generated package.json to be configured in a way that it points to the Kotlin generated JavaScript file. This is my current gradle configuration:
apply plugin: 'kotlin-platform-js'
apply from: "$project.rootDir/gradle/deploy.gradle"
dependencies {
expectedBy project(":")
// Compile/implementation dependencies
implementation "org.jetbrains.kotlin:kotlin-stdlib-js:$kotlin_version"
}
apply plugin: 'org.jetbrains.kotlin.frontend'
compileKotlin2Js {
kotlinOptions.metaInfo = true
kotlinOptions.sourceMap = true
kotlinOptions.moduleKind = 'commonjs'
}
kotlinFrontend {
sourceMaps = true
npm {
dependency("kotlin")
replaceVersion("kotlin-js-library", "1.1.0")
}
define "PRODUCTION", true
webpackBundle {
bundleName = "${project.name}"
sourceMapEnabled = true
}
}
This outputs both a myProject.js file located in $project.builDir.path/classes/nain which is what I hoped would be reflected in the generated package.json file. But the outputted package.json file (located in the project's build directory) is like this:
{
"name": "myProject",
"version": "1.2.0-10-SNAPSHOT",
"description": "simple description",
"main": "myProject",
"dependencies": {
"kotlin": "*"
},
"devDependencies": {
"webpack": "*",
"webpack-dev-server": "*",
"source-map-loader": "*",
"karma": "*",
"qunitjs": "1.23.1",
"karma-qunit": "*",
"karma-sourcemap-loader": "*",
"karma-phantomjs-launcher": "*",
"phantomjs-prebuilt": "*",
"karma-webpack": "*"
}
}
The problem is this, the "main" attribute in the package.json does not point to the bundle file located in classes/main/myProject.js. I tried looking through the documentation to find how to set the main attribute to the to a specific directory and js file but could not find it. I can only change the name by setting bundleName property in webpackBundle portion of the gradle file. Thanks for the help in advance!
So I found a work around to be able to use gradle to publish to npm. I added the following bit to my code:
apply plugin: "com.moowork.node"
//Must copy the output javascript file
//to the location that the package.json expects it to be
//This is semi-workaround since I have not found a way to
//configure the outputted package.json file
task copyJSFile(type: Copy){
from "$project.buildDir.path/classes/main/"
into "${project.buildDir}"
include "*.js"
}
//We publish our project to npm
task npmPublish(dependsOn: copyJSFile, type: NpmTask) {
description = "publishes the project to npm"
workingDir = file("${project.buildDir}")
args = ['publish']
}
What this does is copy the outputted JavaScript generated files to a place where the package.json is configured when you call the npmPublish gradle task.
I want to compile all .scss files in my sass folder to a single .css file
E:\SassToCss
\sass
\style1.scss
\style2.scss
\Want to have the compiled style.css in project root directory.
I tried the followings
sass: {
dist: {
files: {
'style.css' : 'sass/*.scss'
}
}
}
This is generating css for the first file only & ignoring rest of the files.
sass: {
dist: {
files: [{
expand: true,
//cwd: 'styles',
src: ['*.scss'],
//dest: '../public',
ext: '.css'
}]
}
}
This not generating my .css file. What's the correct way of doing so
Create a scss file, for example "style.scss" and use the #import tag for including other sass files.
Your sass compiler should take only style.scss to compile it in css
sass: {
dist: {
files: {
'style.css' : 'sass/style.scss'
}
}
}
See here for examples and better explanation: http://sass-lang.com/guide
i would like to compile all SCSS files that are inside scss folder and are not imported ( file names do not start with _ ) each into separate CSS files( that has the same name as SCSS file ).
that kind of functionality that can be found in Prepros.
is it possible to do it with grunt-sass?
i tried this but it doesn't work:
sass: {
dist: {
files {
'css/*.css': 'scss/*.scss',
}
}
}
You can try:
sass: {
dist: {
files: [{
expand: true,
cwd: 'styles',
src: ['*.scss'],
dest: '../public',
ext: '.css'
}]
}
}
You need to build your file object dynamically, see here:
http://gruntjs.com/configuring-tasks#building-the-files-object-dynamically