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.

Sign up for GitHub

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

Jump to bottom

Run tests against release plugin #33

Open
advayDev1 opened this issue Sep 27, 2015 · 0 comments
Open

Run tests against release plugin #33

advayDev1 opened this issue Sep 27, 2015 · 0 comments
Labels
enhancement

Comments

@advayDev1
Copy link
Contributor

We can do this with 2 environment variable values added to our travis matrix that control the classpath of the plugin jar (either from the local submodule or from plugins.gradle.org)
This was referenced Sep 27, 2015
Merged
Closed
@advayDev1 advayDev1 changed the title Run tests against release plugin and HEAD plugin Run tests against release plugin Oct 3, 2015
@advayDev1 advayDev1 self-assigned this Oct 3, 2015
advayDev1 added a commit to madvay/j2objc-common-libs-e2e-test that referenced this issue Oct 3, 2015
@advayDev1
Run against plugin v0.4.3-alpha; fixes j2objc-contrib#33
dbfa36a
advayDev1 added a commit to madvay/j2objc-common-libs-e2e-test that referenced this issue Oct 3, 2015
@advayDev1
Run against plugin v0.4.3-alpha; fixes j2objc-contrib#33
8a8c8df 
Note we still use the submodule for some gradle configs.
@advayDev1 advayDev1 removed their assignment Sep 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@advayDev1