slachiewicz commented on PR #145:
URL: https://github.com/apache/maven-wagon/pull/145#issuecomment-2563669283
ok, moved to target subdir
--
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 specif
elharo commented on PR #145:
URL: https://github.com/apache/maven-wagon/pull/145#issuecomment-2563641101
Whatever's going on the build should not be creating new artifacts in the
root directory
--
This is an automated message from the Apache Git Service.
To respond to the message, please
slachiewicz commented on PR #145:
URL: https://github.com/apache/maven-wagon/pull/145#issuecomment-2563640451
This is not in the integration test but while creating artefacts for
wagon-http
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
elharo commented on PR #145:
URL: https://github.com/apache/maven-wagon/pull/145#issuecomment-2563637933
> Maybe reporting to maven-shade-plugin / update docs there should be a good
way to go?
Is that what's creating the problem here? I haven't dug into it and am not
sure what the ro
slachiewicz commented on PR #145:
URL: https://github.com/apache/maven-wagon/pull/145#issuecomment-2563615552
Maybe reporting to maven-shade-plugin / update docs there should be a good
way to go?
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
