Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I created a new Spring web app, and I’d very much like to use Maven to handle builds/dependencies. My problem is that the project depends on some existing local projects, and mavenizing them is not currently an option. Is it possible to depend on these projects without mavenizing them?
No and you shouldn’t try that. Maven’s main goal is to have a standardized build. This is what makes Maven so easy to use: Exceptions aren’t be the norm. That’s why Maven requires that all dependencies are in the typical Maven format (POM + jar).
When you say “mavenizing them is not currently an option”, you basically say “Maven is not currently an option”. In my experience, converting an existing project to Maven just takes a couple of minutes … unless said project uses a messy, unreliable build process in which case you really should convert it to Maven ASAP just to stop wasting even more of your precious time. 🙂
If everything else fails, use a build server to produce JAR files from the dependent projects and deploy them to a company wide repository server or just to your local machine.