Skip to content

Conversation

@ronanbrowne
Copy link
Contributor

@ronanbrowne ronanbrowne commented Mar 26, 2025

  • Publish default jar for both subprojects , which has a full dependencies block in pom.xml
  • We will only use this for the purpose of security scanning in the downstream release pack project.
    • This will only scan these Jars and not package them for publishing
  • "standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change

@ronanbrowne ronanbrowne marked this pull request as ready for review March 26, 2025 11:12
@ronanbrowne ronanbrowne merged commit e1a83f8 into release/os/4.9 Mar 26, 2025
1 check passed
@ronanbrowne ronanbrowne deleted the ronanb/shell-jar-4.9-OS branch March 26, 2025 13:53
ronanbrowne added a commit that referenced this pull request Mar 26, 2025
…acks (#121)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
ronanbrowne added a commit that referenced this pull request Mar 26, 2025
…acks (#121) (#123)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
ronanbrowne added a commit that referenced this pull request Mar 26, 2025
…acks (#121)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
ronanbrowne added a commit that referenced this pull request Mar 26, 2025
…acks (#121) (#124)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
ronanbrowne added a commit that referenced this pull request Mar 27, 2025
…acks (#121) (#124)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
ronanbrowne added a commit that referenced this pull request Mar 27, 2025
…acks (#121) (#124) (#129)

Publish default jar for both subprojects , which has a full dependencies block in pom.xml
We will only use this for the purpose of security scanning in the downstream release pack project.
This will only scan these Jars and not package them for publishing
"standard" shadow jar is unaffected, so as far as external consumers are concerned this is a non-functional change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants