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

Contribution properties files are ignored in favor of stale contributions.txt file on Processing site. #2572

Closed
jdf opened this Issue Jun 8, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@jdf
Copy link
Contributor

jdf commented Jun 8, 2014

http://processing.org/contrib_generate/contributions.txt is not kept up-to-date, and, when a contribution is installed, its properties file is ignored, and overwritten with the stale information in the master list on the processing web site.

@fjenett fjenett added this to the GSOC 14 - Joel/Florian milestone Jun 10, 2014

@joelmoniz

This comment has been minimized.

Copy link
Member

joelmoniz commented Jun 21, 2014

@jdf : Could you please clarify the error for me? The information in the properties file seems to be chosen in preference to contributions.txt when a mode has been installed. For example, consider the screenshot where I modified the .properties file (to simulate a .properties more recent than the contributions.txt). Here's what I got:

properties_vs_contributions

Thanks

@jdf

This comment has been minimized.

Copy link
Contributor

jdf commented Jun 22, 2014

All I can tell you is that for weeks an old "sentence" field was displayed in the Mode Manager.

It's possible that hand simulating an install, such as you did, does not hit the same code path as actually installing.

@joelmoniz

This comment has been minimized.

Copy link
Member

joelmoniz commented Jun 22, 2014

Thanks. I shall work on this.

Update: Ok. I've narrowed down the likely source of this issue to here. I shall work on validating the fields rather than writing the properties file afresh soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment