ICEfaces
  1. ICEfaces
  2. ICE-8935

Publish Weekly snapshot builds to our Maven2 repository

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.2
          • Fix Version/s: 3.3
          • Component/s: Release
          • Labels:
            None
          • Environment:
            ICEfaces 3, Maven2

            Description

            In order to facilitate early-access to development snapshot builds by the community we should add a capability to publish at will a nightly build of icefaces3/trunk to our maven2/snapshots repository.

            The idea is that we would generally publish one of these each week, after successful regression testing was completed. If the build is generally unstable, it would not be published that week.

            This would provide the community with easy access to the latest development code via Maven.

              Activity

              Hide
              Permalink
              Deryk Sinotte added a comment -

              Couple of things that needed to be done.

              One was to modify to the top-level pom so to avoid a known bug with Maven's antrun plugin where it uses the JRE instead of the JDK. This causes a problem on non-Mac systems when you want to compile (i.e. run javac) because it can't find the tools.jar. The bug is described here:

              http://jira.codehaus.org/browse/MANTRUN-20

              and a version of the workaround that I employed is found here:

              http://docs.codehaus.org/display/MAVENUSER/Running+ant+tasks+that+use+the+JDK

              Once Jenkins could run the Maven build from the top, we next needed to send the resulting snapshot artifacts to our own Maven repository. We currently us subversion to hold these files which is generally not recommended from what I read in many spots. In any case, I was eventually able to determine how to do it use a Google plugin that does pretty much what we want. So I created a new Jenkins job specifically to do a deploy. In addition to modifying the top-level pom file, I had to create a /home/builder/.m2/settings.xml file to hold the new credentials I created for the Jenkins build so that the job could check stuff into the repository. A test run made it all the way through and successfully checked the artifacts in.

              Show
              Deryk Sinotte added a comment - Couple of things that needed to be done. One was to modify to the top-level pom so to avoid a known bug with Maven's antrun plugin where it uses the JRE instead of the JDK. This causes a problem on non-Mac systems when you want to compile (i.e. run javac) because it can't find the tools.jar. The bug is described here: http://jira.codehaus.org/browse/MANTRUN-20 and a version of the workaround that I employed is found here: http://docs.codehaus.org/display/MAVENUSER/Running+ant+tasks+that+use+the+JDK Once Jenkins could run the Maven build from the top, we next needed to send the resulting snapshot artifacts to our own Maven repository. We currently us subversion to hold these files which is generally not recommended from what I read in many spots. In any case, I was eventually able to determine how to do it use a Google plugin that does pretty much what we want. So I created a new Jenkins job specifically to do a deploy. In addition to modifying the top-level pom file, I had to create a /home/builder/.m2/settings.xml file to hold the new credentials I created for the Jenkins build so that the job could check stuff into the repository. A test run made it all the way through and successfully checked the artifacts in.

                People

                • Assignee:
                  Deryk Sinotte
                  Reporter:
                  Ken Fyten
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: