aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes A few questions on CI, configuration and integration Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "A few questions on CI, configuration and integration" Watch "A few questions on CI, configuration and integration" New topic
Author

A few questions on CI, configuration and integration

Steven Hicks
Greenhorn

Joined: Nov 06, 2013
Posts: 2
I currently have a system that has a single Maven build. It contains many modules, with only one shared library between all of them. I have it setup where I can do a build of all of the modules at once.

My project is setup as such:

  • Web Application and service end points
  • Shared library
  • Client Project1
  • Client Project2


  • Client Project 2 contains tests that require the web application to be deployed and working. If the web application's test endpoints fail, then I'm ok with the Client-Project2 not to be built.

    [Please forgive me with all of this detail.. I'm a little bit lost on whats the best practice here]

    So the questions I have:
  • How would I build the Java web application and keep a separate configuration? (I can't just store it in the DB, because the DB connection string can change based on where its deployed... and it doesn't fix the configuration deal) I'm also reluctant to hard code the database reference within the build. (Via resource filtering)
  • How would I force a deploy within Maven prior to moving to the next project?


  • Peter Johnson
    author
    Bartender

    Joined: May 14, 2008
    Posts: 5843
        
        7

    Personally, I would have 4 Maven projects, one for each artifact. I would use Jenkins to build them, and if i wanted to force them to always rebuild, I would configure that in Jenkins.

    As to the configuration setting, we use profiles in settings.xml and resource filtering to apply the property values in settings.xml to the filtered properties files. Sometimes that does mean editing the settings.xml file when working with a new host, but that's usually not that big of an issue.


    JBoss In Action
    Steven Hicks
    Greenhorn

    Joined: Nov 06, 2013
    Posts: 2
    Peter Johnson wrote:Personally, I would have 4 Maven projects, one for each artifact. I would use Jenkins to build them, and if i wanted to force them to always rebuild, I would configure that in Jenkins.

    As to the configuration setting, we use profiles in settings.xml and resource filtering to apply the property values in settings.xml to the filtered properties files. Sometimes that does mean editing the settings.xml file when working with a new host, but that's usually not that big of an issue.


    So are you suggeting that the builds will have compiled in settings?
     
    I agree. Here's the link: http://aspose.com/file-tools
     
    subject: A few questions on CI, configuration and integration