![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
It Must Be Time For a Vacation
It is clearly time for me to take some vacation days. Most everyone else is at work. :)
We use Gradle for our builds and to automate a number of tasks. One of those tasks is fetching the project files for JDeveloper from our Artifactory, which has the advantage of keeping developers who are less familiar with how things *ought* to work from accidentally checking in changes. Unfortunately, this gave me a problem over the last few days, because I am working on a big, ugly merge. I had loaded the JDeveloper files for the combined project, but the merge had left me with a ton of compile errors and JDeveloper was doing its little trick of "I can't see this perfectly good code over here" during the compile, even after I fixed things.
I decided that the right thing to do was to switch to the JDeveloper files that just look at my group's source code, get that fixed, and then go back to the integrated project. It was a great idea.
Except that Gradle would insist on compiling the code on the branch before it would let me download the JDeveloper files. That would fail (which was not a surprise; it was why I was trying to get the JDev files downloaded) and when that failed the process was done and the JDeveloper files were not downloaded.
Swearing ensued. Asking the build team for a fix ensued, but our U.S. guy is on vacation in India and the rest of the build team is in India as well and didn't seem to grasp the problem. I eventually sent one guy a screenshot of the directory listing showing that I did not actually *have* the JDeveloper files on my machine in this directory. This didn't get me a solution to the problem, but it made me feel better.
I figured I would take most of today off if I didn't get a solution. And I didn't. I answered some emails, went out for a nice lunch with Gretchen, came home, and went upstairs to take care of a few things.
And then I started researching Gradle, because I really know very little about it.
I figured out that what I needed to do was to tell Gradle to pretty please, don't run a compile when running this particular task. I still haven't figured out how to put this in the build.gradle file, but I did figure out how to get the files downloaded by changing my command line options. To wit:
"gradlew loadJDevFiles -x compileJava"
And look! I got my files.
I sent an email with the solution and went off to spend the rest of the day in the studio, because I deserve a vacation.
Starting now. :)
(More about the studio later...)
We use Gradle for our builds and to automate a number of tasks. One of those tasks is fetching the project files for JDeveloper from our Artifactory, which has the advantage of keeping developers who are less familiar with how things *ought* to work from accidentally checking in changes. Unfortunately, this gave me a problem over the last few days, because I am working on a big, ugly merge. I had loaded the JDeveloper files for the combined project, but the merge had left me with a ton of compile errors and JDeveloper was doing its little trick of "I can't see this perfectly good code over here" during the compile, even after I fixed things.
I decided that the right thing to do was to switch to the JDeveloper files that just look at my group's source code, get that fixed, and then go back to the integrated project. It was a great idea.
Except that Gradle would insist on compiling the code on the branch before it would let me download the JDeveloper files. That would fail (which was not a surprise; it was why I was trying to get the JDev files downloaded) and when that failed the process was done and the JDeveloper files were not downloaded.
Swearing ensued. Asking the build team for a fix ensued, but our U.S. guy is on vacation in India and the rest of the build team is in India as well and didn't seem to grasp the problem. I eventually sent one guy a screenshot of the directory listing showing that I did not actually *have* the JDeveloper files on my machine in this directory. This didn't get me a solution to the problem, but it made me feel better.
I figured I would take most of today off if I didn't get a solution. And I didn't. I answered some emails, went out for a nice lunch with Gretchen, came home, and went upstairs to take care of a few things.
And then I started researching Gradle, because I really know very little about it.
I figured out that what I needed to do was to tell Gradle to pretty please, don't run a compile when running this particular task. I still haven't figured out how to put this in the build.gradle file, but I did figure out how to get the files downloaded by changing my command line options. To wit:
"gradlew loadJDevFiles -x compileJava"
And look! I got my files.
I sent an email with the solution and went off to spend the rest of the day in the studio, because I deserve a vacation.
Starting now. :)
(More about the studio later...)