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

JavaScript generation should not generate files in src/main/resources #73

Open
maxleiko opened this issue Jan 15, 2015 · 3 comments
Open

Comments

@maxleiko
Copy link
Collaborator

When you ask the plugin to generate also the JavaScript model using <js>true</js>, it will generate some files in src/main/resources (index.html and model-js-all.js).
This is really not a good idea.

@gnain
Copy link
Collaborator

gnain commented Jan 15, 2015

Could you elaborate a bit ?

@maxleiko
Copy link
Collaborator Author

The generated code looks like a sloppy test. Maybe it should be generated, but it should be placed in, I do not know, let say target/js/examples, not in the project's main folder

@gnain
Copy link
Collaborator

gnain commented Jan 15, 2015

Somehow, yes. It's true. However, the index is generated only if there is no index: it does not override if you changed it.
The *-all.js is generated in resources, next to the index to show what is generated, also because it is linked to the index, and to allow it is embedded in the Jar.
But true, we could generate it elsewhere.

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

No branches or pull requests

2 participants