@Obreh Winfrey I'm curious why new potential devs aren't diving into crypto and defi ?
Is it the volatility ? lack of security ?
Is it the volatility ? lack of security ?
Software Development and Programming Careers (Official Discussion Thread)
- Thread starter Blackking
- Start date
-
- Tags
- careers programming
Do you mean students/people learning to program or people with experience but not in crypto?
as an experienced dev - whay do you think other experienced devs arent making the leap ?
Probably isn't on their radar. I don't think I've seen a lot of those type of job postings when I've been looking. Some people probably are reluctant to chase it without having worked with it before - a chicken and egg problem. In top of that, Data Science is still the buzzword right now.
null
...
Somebody pray for me. I have to turn this codebase with 200+ potential modules into a Maven project. No documentation on how this shyt is built or put together. I'm betting this is going to take me 3 or 4 weeks at least, not including trying to run the application and see if it will even work
null
...
which language(s)?
All Java so far, J2EE. I know how to get things in format of a Maven project, I did it on a personal project. But making sure things don't just explode
null
...
All Java so far, J2EE. I know how to get things in format of a Maven project, I did it on a personal project. But making sure things don't just explode
at least it is Java rather than c/c++ ...
no notes at all is rough as slight version differences can cause all sorts of subtle runtime issues.
i don't know how complicated your environment is but good luck
Vaselclean
Pro
Right click "Convert to Maven project". Easy as that!All Java so far, J2EE. I know how to get things in format of a Maven project, I did it on a personal project. But making sure things don't just explode
Yeah, a future of frustration awaits. I remember I couldn't get a Maven project to build because the Spring Boot version (2.4) I had in the pom file was too new. Turns out Spring Boot 2 does not support anything lower than Java 8. It's little things like that that are going to be extremely annoying. Hopefully there not too many dependencies on other projects/jars or else you may get the "circular dependency" issue. Fun.
I also had a minor weird issue where I had to run the Maven build/install command twice every time to get the project to build successfully.
Last edited:
I'm already running into issues where they have standalone jars as dependencies but I can't get it to recognize them on compile. I have it where I define it as a system dependency in the dependencies section and give it a path to the jar, it even shows up in the classpath during compilation, but it still says it can't find the package. I know that for at least one of them in the module, I can define the regular dependency and let Maven handle it, but I'm weary to make changes like that in case it breaks something at runtime. I may be able to stick it into eclipse or something and include it that way, then see if it'll compile.Right click "Convert to Maven project". Easy as that!
Yeah, a future of frustration awaits. I remember I couldn't get a Maven project to build because the Spring Boot version (2.4) I had in the pom file was too new. Turns out Spring Boot 2 does not support anything lower than Java 8. It's little things like that that are going to be extremely annoying. Hopefully there not too many dependencies on other projects/jars or else you may get the "circular dependency" issue. Fun.
I also had a minor weird issue where I had to run the Maven build/install command twice every time to get the project to build successfully.
null
...
how are you building? can you turn up the build verbosity and look to check that the classpath in the failing build step includes the "missing one". also make sure it isn't picking up a similarly named file which appears somewhere before the "missing one" in the classpath. as a hack just to divide the problem search space put the "missing one" in the root of the build step and see if it builds. it if isn't doing anything exotic in the build you can just cut&paste the build step command, cd to the right directory and run it manually.
yeah I agree that you shouldn't change the project build structure before eliminating other methods of fixing it.
All command line right now, mvn clean install. I set up the directory structure, move things into place, then set up the POM in VS Code. I did run a classpath command and it showed the path to the local jar, so I'm pretty sure the compiler knows it's there. In this instance I'm not tripping too hard because it's a javax.xml dependency and not something custom, but if I hit this problem again, I'll have to sit down and really give it thought. I think one of the only good things about this project is that there's a classpath file in each of the sub directories, so I'm able to understand the inter dependencies without much trouble. I've been making steady progress this morning.