ant plugin only looks for jar files in directory named "target"
Metadata
Current evaluation
Request to make the ant plugin's jar search directory configurable (hardcoded to 'target'). 10-year-old feature request with zero comments and no maintainer interaction; repo has since been heavily restructured.
Suggested action: needs triage
Reason: The issue carries 'bitesize' and 'plugin' labels but has 0 comments, no maintainer response, and no assignee, so it shows no sign of having been assessed or prioritized. It is a legitimate feature request (configurable jar location) rather than a support question, but I could not confirm via tools whether the ant plugin still exists in the current codebase, so I am not confident enough to close it as stale or irrelevant.
Impact:
20
Quick Win:
15.0
Staleness:
95
Complexity:
25
Confidence:
55
Support Request:
15
Issue body
I have the following build.xml for use with the ant plugin in snapcraft :
<project name="HelloWorld" basedir="." default="main">
<property name="src.dir" value="src"/>
<property name="build.dir" value="build"/>
<property name="classes.dir" value="${build.dir}/classes"/>
<property name="jar.dir" value="lib"/>
<property name="main-class" value="oata.HelloWorld"/>
<target name="clean">
<delete dir="${build.dir}"/>
</target>
<target name="compile">
<mkdir dir="${classes.dir}"/>
<javac srcdir="${src.dir}" destdir="${classes.dir}"/>
</target>
<target name="jar" depends="compile">
<mkdir dir="${jar.dir}"/>
<jar destfile="${jar.dir}/${ant.project.name}.jar" basedir="${classes.dir}">
<manifest>
<attribute name="Main-Class" value="${main-class}"/>
</manifest>
</jar>
</target>
<target name="run" depends="jar">
<java jar="${jar.dir}/${ant.project.name}.jar" fork="true"/>
</target>
<target name="clean-build" depends="clean,jar"/>
<target name="main" depends="clean,run"/>
</project>
After building the part which uses the ant plugin I get the error :
"Failed doing build for hello: could not find any built jar files for part".
If I change the line :
<property name="jar.dir" value="lib"/>
to
<property name="jar.dir" value="target"/>
the error goes away.
It would be useful to have a way to configure the location the ant plugin looks in for jar files.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
15.0
Staleness:
95
Complexity:
25
Confidence:
55
Support Request:
15
|
needs triage | Request to make the ant plugin's jar search directory configurable (hardcoded to 'target'). 10-year-old feature request with zero comments and no maintainer interaction; repo has since been heavily restructured. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Request to configure the output directory for Snapcraft's ant plugin instead of hardcoding target. Issue is over 9 years old with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Feature request to configure the output directory for snapcraft's ant plugin instead of hardcoding target. Issue is over 9 years old with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Feature request to configure the jar output directory for the snapcraft ant plugin, which currently hardcodes target. Issue is over 10 years old with no maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
10
|
close stale | Snapcraft ant plugin hardcodes JAR discovery to the target directory, preventing custom build.xml configurations. Unassigned, inactive for years, and needs implementation to support configurable output paths. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.