Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Assets are not recognized in Maven projects

Open
#528 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

Start by reproducing the issue with a manually created Maven project containing the required jMonkeyEngine dependencies, then compare asset handling with projects created from the Gradle and Ant templates. Focus on why the SDK does not open .j3m and .j3o files in the Maven case. Done means those asset types open correctly in Maven projects without regressing Gradle or Ant projects.

Written by the indexing model from the issue text.

Description

I know Maven very well and don't want to learn Gradle at the moment. I manually created a Maven project with all required JME dependencies but SDK can't open "j3m" and "j3o" files which I've took from examples. There is no problem to open those files when project created from Gradle or Ant template.

Dominant language
Java
Stars
349
Forks
104
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jMonkeyEngine/sdk

All issues in jMonkeyEngine/sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.