Should Maven generate JAXB java code or just use Java code from source control?
We’re trying to plan how to mash together a build server for our shiny new Java backend. We use a lot of JAXB XSD code generation and I was getting into a heated argument with whoever cared that the build server should:
Should Maven generate JAXB java code or just use Java code from source control?
We’re trying to plan how to mash together a build server for our shiny new Java backend. We use a lot of JAXB XSD code generation and I was getting into a heated argument with whoever cared that the build server should:
If a dependency is not in the maven repository should I add it to source control?
One of the jar files that I use in my code is not in the maven repository(and yes I tried to avoid using it). I have installed it locally so when I build the project it gets picked up by maven. I also put instructions in my README so anyone who wants to build my code can see how to add the jar to their local repository.
Should jars that are only gonna be used in one project be deployed to Nexus server [closed]
Closed 9 years ago.
Should jars that are only gonna be used in one project be deployed to Nexus server [closed]
Closed 9 years ago.
Continuous Integration for different languages [closed]
Closed 9 years ago.
Continuous Integration for different languages [closed]
Closed 9 years ago.
Continuous Integration for different languages [closed]
Closed 9 years ago.
Sharing dependency configuration over multiple projects (Maven)
From a big SVN repository we want to switch to Maven/Gradle for handling dependencies so that programmers can work with a single project without checking out the whole thing.
Haskell build and artifact environment similar to Maven
I used to be a Java developer for a long time, but recently, I joined a Haskell team.
In the java world, if you have a large project,
with several teams working on it, a common approach is to use an artifact server such as Maven to ease and speed-up the development.
Numerous build tools, such as Ant, Maven, Gradle, can build the project and
upload a jar file to the artifact server that can be used by the rest of the team
without pain.
Therefore,
by splitting the project into smaller sub-projects, the build time is also drastically reduced.