| Best tooling to replace Texo [message #1854413] |
Wed, 17 August 2022 19:32  |
 Mr Cur
Messages: 35
Registered: September 2014 |
Member |
|
|
Hi,
I use Texo for quite some time to generate JPA classes for UML class models.
It works very well, but unfortunately seems not to be maintained anymore. For example, it can not be installed in recent Eclipse editions, so it requires an old Eclipse install to get it up-and-running. This clumsy, and a pity, because Texo is an excellent tool.
A small product survey by me revealed not an equivalent (commercial) product with similar functionality as Texo. Most products do not include a graphical editor, generate poor code (e.g. bidirectional relationships are not supported), offer only limited control of the code generation process and/or do not allow to add code to the generated code (that will not be overwritten during the next generation process).
Tools I looked at are Jeddict, StarUML/Rebel and JPA-Buddy, but none of them satisfied my requirements completely:
- graphical editor for the class modelling
- full support of JPA 2.1
- generation of high quality code, e.g. correct and safe management of bidirectional relationships
- fine grained control of the generation process
- generation of Jackson annotations, e.g. @JsonSubtype, etc. (nice to have)
My questions:
- are there suggestions for suitable tooling (commercial software is acceptable for us, as long as it fits the requirements)
- did someone manage to build Texo recently? I have checked out the source code, but the build system (buckminster) is unfamiliar to me and seems also to be end-of-live.
Thanks for your answers.
-- Jaap
|
|
|
| Re: Best tooling to replace Texo [message #1854419 is a reply to message #1854413] |
Thu, 18 August 2022 06:47  |
Ed Willink
Messages: 7554
Registered: July 2009 |
Senior Member |
|
|
Hi
I'm sorry that I cannot help with Texo specifically; whenever I have tried to improve my knowledge, I somehow concluded that Texo wasn't relevant for me.
Buckminster is indeed very end of life. Maven-based Tycho is the almost universally adopted replacement. It has distinct differences and is on balance distinctly better but the transition is painful.
However most Eclipse projects have a local build that just happens magically as the JDT builder and possibly other builders do their work. You are able to launch a nested Eclipse and use your build without ever touching Buckminster or Tycho or Maven or Gradle or ...
To allow other users, or yourself in the outer Eclipse to use your semi-interactive build you just need to export the plugins, and then import them again. I regret that it is many years since I did this so I cannot offer precise guidance, but you can probably manage without a Buckminster replacement. There is a File->Export facility. Slightly more advanced, but still simple is to add a feature and build an Update Site. Texo surely provides features so you just need to define the Update Site. Texo is so old that the Update Site may already be there from pre-Buckminster days.
You will of course have to invoke test suites manually and may need to do a little repair to accommodate the mandatory Java 11 for modern Eclipse IDE work.
Regards
Ed Willink
[Updated on: Thu, 18 August 2022 06:49] Report message to a moderator |
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02279 seconds
] 
Search
Help
Register
Login
Home
