DCA11Y-1222 config changes for releasing to Atlassian repository #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With these mentions, the `mvn clean source:jar javadoc:jar install` command fails with ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork (attach-sources) on project frontend-plugin-core: Presumably you have configured maven-source-plugn to execute twice times in your build. You have to configure a classifier for at least on of them. -> [Help 1] ``` Without them, it executes fine, and in the local Maven repository I see the `-javadoc.jar` and `-sources.jar` generated, for both frontend-maven-plugin and frontend-plugin-core, so I consider removing it to be correct.
We don't want to publish to that repository.
Even though it doesn't matter (there's a redirect from atlassian/fmp to attlassian-forks/fmp), it's worth it.
Per https://hello.atlassian.net/wiki/spaces/OSP/pages/791250012/HOWTO+Publish+an+open+source+project+on+Maven+Central, we can publish something to Maven Central only if groupId starts with `com.atlassian` or `io.atlassian`.
|
Superseded by #11 |
arymasheusky-atl
deleted the
issue/master/DCA11Y-1222-release-for-use-in-aui
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In order to make our changes to the fork available for use in Atlassian projects, we want to publish to the Atlassian package repository.
This PR adds and modifies necessary configuration for that.
I followed this internal guide from the local machine and tried until the deployment succeeded.
Another helpful guide: https://hello.atlassian.net/wiki/spaces/OSP/pages/791250012/HOWTO+Publish+an+open+source+project+on+Maven+Central
{com|io}.atlassianprefixes for that.mvn source:jar javadoc:jar install) didn't work with them: that plugin was being called twice and didn't like thatskip=trueconfig to the deploy task. I hold a quaint notion that when a guy issues the "deploy" command, he expects the "deploy" command to execute.Tests and Documentation