On job as freelancer working with Java, JDK17+, Jenkins, Maven, Docker, K3S, Git, In my spare time I'm trying to blog about something useful(?) or try to hack on things I like.
Can you please be more specific about Their website sucks IMHO,? file in a jira issue ? Suggest the issues you see or even greater would be to offer a pull request?
The next part: it could welcome YAML as more compact alternative format, while YAML has a lot of disadvantages compared to XML ...yes I know XML is a bit verbose...in Maven 4 there is done a lot of foundation work to improve the format later on...
First off, thanks for the feedback. I'm glad to see someone caring about maven.
Can you please be more specific about Their website sucks IMHO?
Well, IMHO it should start with a getting started section, explaining how a basic pom.xml looks like and building it with the command line. That would be a fair introduction. On the other hand, their front page contains either advanced or useless stuff. Just by looking at it, I think most people would go away. Putting something like this, (not trivial to find) on the front page would have been much more useful IMHO. Besides the front page with a tutorial, I'd offer 4 sections: "pom.xml reference", "CLI reference", "Plugins", "Advanced" and "Community / contributing". The current left menu is cluttered while not containing what you look for.
file in a jira issue ?
Well, that is the next problem. Nowadays everybody has GitHub accounts. Just by requiring people to create an account and use another ticketing system, it looses feedback and contributions. You don't want to create accounts for every lib or tool you use.
YAML has a lot of disadvantages compared to XML
While YAML is not perfect, I think a lot of users would welcome a more lightweight way of wrting the configs
The last thing I'd like to add is that some things are also uselessly difficult to do, like packaging a fat/executable jar. Some comfort stuff like a goal to check for CVEs or update all dependency versions should also be included by default.
Yeah, I noticed that too. But it requires you to explicitly search for it, to download, install and configure the plugin. Basically, it's defying the purpose of making your life easier. Whether the plugin works properly and how your dev tools integrate it is another matter.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can you please be more specific about
Their website sucks IMHO,? file in a jira issue ? Suggest the issues you see or even greater would be to offer a pull request?The next part:
it could welcome YAML as more compact alternative format,while YAML has a lot of disadvantages compared to XML ...yes I know XML is a bit verbose...in Maven 4 there is done a lot of foundation work to improve the format later on...First off, thanks for the feedback. I'm glad to see someone caring about maven.
Well, IMHO it should start with a getting started section, explaining how a basic pom.xml looks like and building it with the command line. That would be a fair introduction. On the other hand, their front page contains either advanced or useless stuff. Just by looking at it, I think most people would go away. Putting something like this, (not trivial to find) on the front page would have been much more useful IMHO. Besides the front page with a tutorial, I'd offer 4 sections: "pom.xml reference", "CLI reference", "Plugins", "Advanced" and "Community / contributing". The current left menu is cluttered while not containing what you look for.
Well, that is the next problem. Nowadays everybody has GitHub accounts. Just by requiring people to create an account and use another ticketing system, it looses feedback and contributions. You don't want to create accounts for every lib or tool you use.
While YAML is not perfect, I think a lot of users would welcome a more lightweight way of wrting the configs
The last thing I'd like to add is that some things are also uselessly difficult to do, like packaging a fat/executable jar. Some comfort stuff like a goal to check for CVEs or update all dependency versions should also be included by default.
There is polyglot-maven project that allows you to write build scripts in different languages. including Yaml
Yeah, I noticed that too. But it requires you to explicitly search for it, to download, install and configure the plugin. Basically, it's defying the purpose of making your life easier. Whether the plugin works properly and how your dev tools integrate it is another matter.