-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get it building #23
Get it building #23
Conversation
Based on maldil@705e59f
We're getting it from the parent pom.
It would seem that the test files are in the normal source directories.
Not sure if it's completely necessary.
The token isn't working.
This reverts commit 5953caf.
I think it is included in the deployment.
Different projects have different build and resource directories.
Buildship seemed to do this automatically.
It's timing out.
This seems to be the project standard.
This reverts commit 9355100. It doesn't seem to work.
Added an m2e property not to set the source folder as a test source. The problem is that Eclipse will not export test source packages, but this package is *both* a test source and normal source.
You may want to review the files by ignoring whitespace. |
Good to go here. I had to skip one test, namely, the |
The J2EE module was not part of the original (automated) build: Lines 24 to 33 in 0543c10
Perhaps this was being test manually in the past. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks fine to me. I will approve with a relatively cursory review since this is a significant improvement over what we had before. I just have one comment to address
CONTRIBUTING.md
Outdated
1. Build and deploy WALA to your local maven repository. This is necessary because the test JARs are not published on Maven Central: `./gradlew publishToMavenLocal`. | ||
1. If you run into [this issue](https://github.com/wala/WALA/issues/1173), try: `./gradlew publishToMavenLocal -x signRemotePublication`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we update these instructions in light of the updates on the corresponding WALA issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but it would be different depending whether the rest JARs are released. Do we have those for 1.5.9 or does a new release need to be cut?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think even for 1.5.9, just running ./gradlew publishLocalPublicationToMavenLocal
should work without requiring signing; see here. Does it work for you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but it would be ideal to have these JARs in maven local instead of building WALA locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but that won't happen until after we fix the relevant issues and cut the next release (timeline unclear). In the meantime, if we want to merge this, we should have the instructions be correct for whatever release works for this repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an issue on http://github.com/wala/WALA that I can track to the test JARs to be released? I'll create an issue on this slide and block on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is wala/WALA#1201. After that is fixed, I would have to cut a release (which should be easy).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yes, I also forgot I had wala/WALA#1171.
Per wala/WALA#1173 (comment), using the `publishLocalPublicationToMavenLocal` task instead of the more obvious `publishToMavenLocal` task.
Per wala/WALA#1173 (comment), usinmg the `publishLocalPublicationToMavenLocal` task instead of the more obvious `publishToMavenLocal` task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's merge
Updating and documenting the build process.