Skip to content
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

Merged
merged 47 commits into from
Jan 10, 2023
Merged

Get it building #23

merged 47 commits into from
Jan 10, 2023

Conversation

khatchad
Copy link
Collaborator

@khatchad khatchad commented Dec 25, 2022

Updating and documenting the build process.

Buildship seemed to do this automatically.
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.
@khatchad khatchad changed the title Progress on building Get it building Jan 5, 2023
@khatchad
Copy link
Collaborator Author

khatchad commented Jan 5, 2023

You may want to review the files by ignoring whitespace.

@khatchad khatchad marked this pull request as ready for review January 5, 2023 21:49
@khatchad
Copy link
Collaborator Author

khatchad commented Jan 5, 2023

Good to go here. I had to skip one test, namely, the ServerTest. I didn't fix the J2EE stuff, and that test was hanging.

@khatchad
Copy link
Collaborator Author

khatchad commented Jan 5, 2023

The J2EE module was not part of the original (automated) build:

ML/pom.xml

Lines 24 to 33 in 0543c10

<modules>
<module>com.ibm.wala.cast.python</module>
<module>com.ibm.wala.cast.python.jython</module>
<module>com.ibm.wala.cast.python.jython3</module>
<module>com.ibm.wala.cast.python.test</module>
<module>com.ibm.wala.cast.python.jython.test</module>
<module>com.ibm.wala.cast.python.jython3.test</module>
<module>com.ibm.wala.cast.python.ml</module>
<module>com.ibm.wala.cast.python.ml.test</module>
</modules>

Perhaps this was being test manually in the past.

@msridhar msridhar self-requested a review January 8, 2023 17:58
Copy link
Member

@msridhar msridhar left a 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
Comment on lines 33 to 34
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`.
Copy link
Member

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?

Copy link
Collaborator Author

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?

Copy link
Member

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?

Copy link
Collaborator Author

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.

Copy link
Member

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. Done.

Copy link
Collaborator Author

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.

Copy link
Member

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).

Copy link
Collaborator Author

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.
Copy link
Member

@msridhar msridhar left a 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

@msridhar msridhar merged commit 6c85f99 into wala:master Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants