Unable to release without auto-staging #265
Comments
reckart
added a commit
that referenced
this issue
Jan 12, 2023
- Move staging-related configurations into the auto-staging profile
reckart
added a commit
that referenced
this issue
Jan 12, 2023
…out-auto-staging Issue #265: Unable to release without auto-staging
reckart
added a commit
that referenced
this issue
Jan 13, 2023
…ntation-from-website-into-maintainer-guide * main: Issue #265: Unable to release without auto-staging Issue #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+ Issue #268: UIMA components log and then re-throw exceptions which usually leads to errors being logged twice Issue #272: select on FSArray seems broken Issue #275: Improved error message made it even more misleading Issue #266: Unable to install UIMA 3.3.1 Eclipse Plugins in Eclipse 2022-09
reckart
added a commit
that referenced
this issue
Jan 16, 2023
…ipse-plugins-during-release-builds * main: Issue #265: Unable to release without auto-staging Issue #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+ Issue #268: UIMA components log and then re-throw exceptions which usually leads to errors being logged twice Issue #272: select on FSArray seems broken Issue #275: Improved error message made it even more misleading Issue #266: Unable to install UIMA 3.3.1 Eclipse Plugins in Eclipse 2022-09
reckart
added a commit
that referenced
this issue
Jan 20, 2023
…-a-PEAR-context * main: (91 commits) Issue #283: Update issue report generation Issue #283: Update issue report generation [UIMA-6436] Move maintainer documentation from website into maintainer guide [UIMA-6436] Move maintainer documentation from website into maintainer guide [UIMA-6436] Move maintainer documentation from website into maintainer guide Issue #265: Unable to release without auto-staging Issue #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+ Issue #268: UIMA components log and then re-throw exceptions which usually leads to errors being logged twice Issue #275: Improved error message made it even more misleading Issue #266: Unable to install UIMA 3.3.1 Eclipse Plugins in Eclipse 2022-09 No issue: Remove Jira line from PR template - we do not use Jira anymore. #270 - Update dependencies #270 - Update dependencies #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+ No issue. Adjust jira legacy module version. Issue #252: Potential failure to look up FsGenerator3 in OSGI-like contexts Issue #225: Improve deployment in OSGi environments Issue #226: Provide SPI interfaces to locate descriptors and JCas classes Issue #226: Provide SPI interfaces to locate descriptors and JCas classes Issue #247 - RelativePathResolver should consider TCCL ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When trying to run a release without auto-staging, the build fails because the UIMAJ POM contains references to
${staging-folder}and friends which are only defined by the parent POM when the auto-staging profile is not disabled.To Reproduce
Expected behavior
All logic that is related to auto-staging in the UIMAJ build should be in the corresponding profile.
Please complete the following information:
The text was updated successfully, but these errors were encountered: