Okay, I see what's happening. There is no 'build source package' target for this project. Usually, we use Ant to zip all the relevant files into a .zip and .tz file.
I will see what it takes to add an equivalent mvn target to achieve the same thing. Thanks, Om On Thu, Nov 13, 2014 at 3:52 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > On Thu, Nov 13, 2014 at 3:30 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> 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/ >> <http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-flex-release/> >> >> 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. >> >> > Are we sure that the source-release.zip is actually getting built? I > don't see it in the 'target' directory in the workspace. > I do see a flex-tool-api-1.1.0-SNAPSHOT.jar here[1] which seems to be the > only artifact getting built. > > Thanks, > Om > > [1] > https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastSuccessfulBuild/artifact/flex-tool-api/target/ > > >> -Alex >> >> >
