Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I don't think the question is trivial. Maven is very complex and confusing at first. The documentation is also quite something. It's not easy to figure out what's going on unless you already know. ...
Answer
#2: Post edited
by
matthewsnyder
·
2023-06-23T02:15:35Z (11 months ago)
- I don't think the question is trivial. Maven is very complex and confusing at first. The documentation is also quite something. It's not easy to figure out what's going on unless you already know. Your question explains a valuable thing.
- My real concern is discoverability:
- * It has nothing to do with docusign API
- * It has nothing to do with your code sample - but the important point is, "the app seems to complain about phantom code that doesn't exist"
- * The errors you quoted are not characteristic - forgetting to update the project is basically a random error generator, and it could be anything
- Based on the logic in [another post I made](https://software.codidact.com/posts/280965/288330#answer-288330), I would say the solution here is to find a question titled something like "What are general troubleshooting steps when a Java program is not working as expected?" (create it if it doesn't exist) and add an item to that list called "make sure you've updated your project".
- This would require first having at least a semi-consensus in the community that it's okay to ask broad, open-ended, collaborative list-style questions.
- I don't think the question is trivial. Maven is very complex and confusing at first. The documentation is also quite something. It's not easy to figure out what's going on unless you already know. Your question explains a valuable thing.
- My real concern is discoverability:
- * It has nothing to do with docusign API
- * It has nothing to do with your code sample - but the important point is, "the app seems to complain about phantom code that doesn't exist"
- * The errors you quoted are not characteristic - forgetting to update the project is basically a random error generator, and it could be anything
- So how would other people who forgot to update the project find this question, instead of reasking? Will it just be an endless cycle of new users asking yet another variation on the same, and power users closing as duplicate?
- Based on the logic in [another post I made](https://software.codidact.com/posts/280965/288330#answer-288330), I would say the solution here is to find a question titled something like "What are general troubleshooting steps when a Java program is not working as expected?" (create it if it doesn't exist) and add an item to that list called "make sure you've updated your project".
- This would require first having at least a semi-consensus in the community that it's okay to ask broad, open-ended, collaborative list-style questions.
#1: Initial revision
by
matthewsnyder
·
2023-06-23T02:14:25Z (11 months ago)
I don't think the question is trivial. Maven is very complex and confusing at first. The documentation is also quite something. It's not easy to figure out what's going on unless you already know. Your question explains a valuable thing. My real concern is discoverability: * It has nothing to do with docusign API * It has nothing to do with your code sample - but the important point is, "the app seems to complain about phantom code that doesn't exist" * The errors you quoted are not characteristic - forgetting to update the project is basically a random error generator, and it could be anything Based on the logic in [another post I made](https://software.codidact.com/posts/280965/288330#answer-288330), I would say the solution here is to find a question titled something like "What are general troubleshooting steps when a Java program is not working as expected?" (create it if it doesn't exist) and add an item to that list called "make sure you've updated your project". This would require first having at least a semi-consensus in the community that it's okay to ask broad, open-ended, collaborative list-style questions.