On 11/13/14, 3:19 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>> >> In fact, when trying to review the potential release candidate, it >>turned >> out to be difficult (impossible?) for Maven to provide the source >>artifact >> on the CI server without actually deploying the artifact to a Maven >> server. > > >Can you please explain what "for Maven to provide the source artifact on >the CI server" means? What are you trying to do? In our new no-RC workflow, we are trying to get Jenkins to post builds with artifacts. For TDF, we have this: http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-flex-re lease/ Click on “Last Successful Artifacts” and somewhere in there is the source package. Over at https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/ We have “Last Successful Artifacts”, but despite my asking several times, Chris was unable to get the build to leave the source-release.zip file there. He said that would require running the “deploy” command which would try to upload the artifacts to the Maven staging server. My takeaway was that Maven didn’t have a “build” command that would just compile artifacts and not deploy them. That’s why I drew the analogy to not being able to get pepperoni on one side and sausage on the other. The Maven assumption is that you would always deploy any built artifacts. -Alex
