Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12348615&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1686/
https://repository.apache.org/content/repositories/maven-1686/org/apache/maven/archetype/
Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228&version=12344166
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MDEPLOY/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-1685
slachiewicz closed pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubs
dependabot[bot] commented on pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78#issuecomment-1001555337
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor v
dependabot[bot] opened a new pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78
Bumps
[plexus-container-default](https://github.com/codehaus-plexus/plexus-containers)
from 2.1.0 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-conta
Hi,
Even if I get the idea and where you come from, the CVE are basically
moving databases and not something you put in a project - or worse an
artifact - and deploy with it so it sounds like something unrelated to
maven itself but that maven could exploit or host - it is possible to host
such an
Hello,
I hope this is the right place to make this suggestion and to discuss this. If
not, please let me know where to write this instead.
For software projects it is important to know whether vulnerable dependencies
are used as part of the build. Especially the recent Log4j 2 vulnerabilities
