Copied from briandealwis/cram#5: @student-06 asked

It would be great if we can supply auth creds for registry using parameters since it removes the dependency on credential helpers.

My exact use case is: We are setting up a CI system for UI projects, where we need to push docker images (without daemon) to a local registry which has auth.

The tool generates code that causes PMD UnnecessaryModifier warnings for generated enums .
(https://pmd.github.io/latest/pmd_rules_java_codestyle.html#unnecessarymodifier)
It might make sense to change the autogenerated code not to have

    private SomeEnum(String value) {
        this.value = value;
    }

but

SomeEnum(String value) {
    this.value = value;
}

Thank you for this project!

I have been struggling to work out how best to configure a CI for using DependencyCheck.

For example, I'd like to use the caching feature of GitHub actions with DependencyCheck to avoid redownloading all the CVEs on each build.

1. Is there a shared cache I can refer to?
2. If not; what's the "right" way to set up a shared cache for my project?

Ideally, this

New feature: Prevent header timestamp in git.properties to allow for reproducible builds.

The git.properties file output includes the current time as a timestamp in a commented header. This prevents reproducible builds because each build will include a different timestamp.

A feature fix would prevent this timestamp from being written as a comment header.

Note1: For reproducible builds th

I can not make the eclipse stop at a breakpoint to debug..
Does anyone know how to do this?

I already tried this:
https://blog.jooq.org/2015/06/23/how-to-debug-your-maven-build-with-eclipse/

http://answerforqa.weblog.to/archives/1039022150.html

When I use the gradle plugin with Gradle 6, I get the following deprecation warning.

> Task :generateTypeScript
Running TypeScriptGenerator version 2.21.588
The compile configuration has been deprecated for resolution. This will fail with an error in Gradle 7.0. Please resolve the compileClasspath configuration instead. Consult the upgrading guide for further information: https://docs.grad

As discussed in the last Call, this issue should be used to discuss the possibility of using the Reporter to extract documentation for the bnd.bndtools.org page automatically.

We should try to experiment with it and find out, what would be necessary to incorporate this in the bnd build.

@stbischof As you have invested quite a bit of work in the reporter, what do you think would be necessary

Sorry, i've tried to use <dirmode> without any success:

<data>
	<src>${project.external-resources}</src>
	<type>directory</type>
	<includes>*.conf, *.webfilters</includes>
	<mapper>
		<type>perm</type>
		<filemode>666</filemode>
                <dirmode>777</dirmode>
		<strip>1</strip>
		<prefix>/usr/lib/${project.name.camel}/examples</prefix>
	</mapper>
</data>

Could yo

I get the feeling that the Wiki doesn't really get read too much and is not as easy to find as the website. I'm going to suggest that we move all wiki content to the website and then close down the Wiki portion of the repo.

The website is using markdown with GitHub Pages so it should largely be a cut and paste job with some minor tweaking.

The 1.8.0 release initially failed because of javadoc errors, most of which are fixed now. To make sure we spot these earlier next time, we should enable doclint and javadoc production in CI

Add 'since' information to plugin configuration parameters by inspecting the commit history.

Now we usually simply call .name() or .toString() in config selections, which may be confused and there are too many options, we should use more friendly name in display and reduce the options.

Currently, the headless scanner extension expects an XML based configuration file and this works ok. But, making the XML is cumbersome and also requires that most of the request URLs be wrapped in CDATA blocks.

IMHO, this would be much simpler, cleaner and much more concise in JSON than in XML, Also, the configuration files for Burp itself seem to be JSON based. So, this move will make it sor

The XML report for dependency updates contains typos. It would be nice to fix:

• nextVersionAlailable to nextVersionAvailable (fixed with #341 )
• nextIncremetalAvailable to nextIncrementalAvailable (still open)

Best regards

Matthias

The executable files permissions are removed by this plugin, under macOS or Linux OS.
The files permissions "0755" are correctly set by the maven-assembly-plugin but are removed by this appbundle plugin, so all the embedded binaries are not working as expected with this DMG package generated.

Can the bars in features, tags, steps summary pages be made clickable so the link opens to the details page directly.
So it goes from pages/tag-summary.html to pages/tag-scenarios/tag_TagOver.html when the TagOver bar is clicked.
Saves the time for scrolling and searching for the desired tag, feature or step in the section below.