🌐 US-Proxy
class="logged-out env-production page-responsive" style="word-wrap: break-word;" >
Skip to content

Fix Windows launcher classpath - #3373

Merged
baev merged 4 commits into
mainfrom
fix-classpath
Jun 8, 2026
Merged

Fix Windows launcher classpath#3373
baev merged 4 commits into
mainfrom
fix-classpath

Conversation

@baev

@baev baev commented Jun 5, 2026

Copy link
Copy Markdown
Member

Context

After #3309, the generated Windows launcher for Allure Commandline uses an explicit jar-by-jar classpath instead of a short wildcard classpath.

In Allure Commandline 2.42.0, bin/allure.bat contains a single set CLASSPATH=... line that repeats %APP_HOME% once per jar. The current line is about 2127 chars before expansion and contains 51 %APP_HOME% entries.

On Windows, cmd.exe has an effective command line limit of 8191 characters. After %APP_HOME% expansion, the launcher can exceed that limit when Allure is installed under a long path.

Approximate formula for 2.42.0:
text
expanded_length = 1617 + 51 * length(APP_HOME)

So the launcher becomes risky once APP_HOME is around 129+ characters.

Checklist

@baev baev added the pr:bug Something isn't working label Jun 5, 2026
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

Allure Report Summary

Name Duration Stats New Flaky Retry Report
Allure 2 – Pull request #3373 12m 15s Passed tests 381   Skipped tests 1 3 0 0 View

@baev
baev merged commit 2973672 into main Jun 8, 2026
29 checks passed
@baev
baev deleted the fix-classpath branch June 8, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr:bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants