that the intention with Sql2Java is that people tailor the templates to their own use, or is the intent that for most people the templates should be used as is.
This I suppose also asks about how updates to the system will happen and how users should go about merging them with their use of the code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right assuming both:
- templates could be used "AS IS"
- templates could be tailored
The second point is giving you the warranty that the generated code will match your company own rules for quality (passing some PMD or CheckStyle rule sets). This is also the way the templates matured... to give most users the ability to assume the first point does apply.
The tailored templates could be posted as attachments in "Bug Reports" or "Feature Request". Some developper will later on catch them and merge them into the source code of the project. As for the "users" of sql2java, they are advised to keep their own version of the templates in their usual code versioning system.
Hope this answer your questions.
Alain.
BTW: if you have some templates for the "Stored Procedure" feature, don't hesitate to post them as a feature request (or as attachment to the already existing request).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As an addition to Alain's post: We are planning to support template packs. These packs will contain a collection of templates and make it possible to create a package for own use. We are also planning to create an online library where new packs can be posted.
But .... This won't happen until the next release of sql2java (greenwade - 3.0). We are still busy implementing lot's of new things inside this new release, the packs being one of them.
So far my 5 cents
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
that the intention with Sql2Java is that people tailor the templates to their own use, or is the intent that for most people the templates should be used as is.
This I suppose also asks about how updates to the system will happen and how users should go about merging them with their use of the code.
You are right assuming both:
- templates could be used "AS IS"
- templates could be tailored
The second point is giving you the warranty that the generated code will match your company own rules for quality (passing some PMD or CheckStyle rule sets). This is also the way the templates matured... to give most users the ability to assume the first point does apply.
The tailored templates could be posted as attachments in "Bug Reports" or "Feature Request". Some developper will later on catch them and merge them into the source code of the project. As for the "users" of sql2java, they are advised to keep their own version of the templates in their usual code versioning system.
Hope this answer your questions.
Alain.
BTW: if you have some templates for the "Stored Procedure" feature, don't hesitate to post them as a feature request (or as attachment to the already existing request).
As an addition to Alain's post: We are planning to support template packs. These packs will contain a collection of templates and make it possible to create a package for own use. We are also planning to create an online library where new packs can be posted.
But .... This won't happen until the next release of sql2java (greenwade - 3.0). We are still busy implementing lot's of new things inside this new release, the packs being one of them.
So far my 5 cents