Should we or should we not copy what "npm" does with being able to run user defined commands? Some people do seem to like that idea.
We could have:
jpm do <name> - which would execute the command named jpm run - would be an alias for jpm do run, as would jpm compile and jpm test
If I do this I'd go for as dumb an implementation as possible, except perhaps for the fact that I'd like a common way of dealing with paths. So that you can have something like "java -cp deps/*" and have that be turned into "java -cp deps\*" on Windows somehow.
One way would be to automatically detect things that look like paths and convert them and then have a special way to mark things that you don't want converted. Or the opposite where you have to mark paths in a way to convert them.
The other thing would be to have to possibility of inserting the class path (so instead of doing "java -cp deps/*" you could do something like "java -cp {{deps}}", where the path would of course be using OS-compliant separators)
Should we or should we not copy what "npm" does with being able to run user defined commands? Some people do seem to like that idea.
We could have:
jpm do <name>- which would execute the command namedjpm run- would be an alias forjpm do run, as wouldjpm compileandjpm testIf I do this I'd go for as dumb an implementation as possible, except perhaps for the fact that I'd like a common way of dealing with paths. So that you can have something like
"java -cp deps/*"and have that be turned into"java -cp deps\*"on Windows somehow.One way would be to automatically detect things that look like paths and convert them and then have a special way to mark things that you don't want converted. Or the opposite where you have to mark paths in a way to convert them.
The other thing would be to have to possibility of inserting the class path (so instead of doing
"java -cp deps/*"you could do something like"java -cp {{deps}}", where the path would of course be using OS-compliant separators)