Jeanne Boyarsky wrote:1) Then don't compile it one package at a time. That comment was based on your suggestion. You are going to need to talk to someone on your team about how to build the software.
Jeanne Boyarsky wrote:It's building your product by checking it out of the repository. It wouldn't need a path.
Peter Johnson wrote:1) This is another thing that the Nexus repository would solve. We use Maven to grab all dependencies form Nexus before a compile starts.
Peter Johnson wrote:3) Are you asking where the resulting file is placed? For example, if you Ant script builds a WAR file, are you asking where does that WAR file go? Unless you coded up something to copy the WAR somewhere, it simply stays on the Jenkins build server. In our build environment we use Nexus to maintain a repository of all built artifacts (WARs, JARs, ZIPs, MSIs, etc.) which makes it easy for others to grab the things they need.
Punit Jain wrote:ohh you mean using nexus repository i can look the dependencies, but how? and we are using Ant.
Punit Jain wrote: there i specify path for ClearCase, jdk and Ant not also for that product for which we are doing development, why?