-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
Author Message
 Post subject: Reverse-engineering - saving console configurations
PostPosted: Tue Jan 24, 2006 2:20 pm 
Beginner
Beginner

Joined: Tue Jan 24, 2006 1:48 pm
Posts: 20
Location: Stevenage, UK
Question: Does anyone know if it is possible to save console configurations into a file in a project?

Further details
I'm using the Hibernate Tools Eclipse plugin to generate Java code for a some tables in a couple of databases.
I've now got to the point where I'd like to submit everything to CVS.
I have 4 reverse-engineering "launch" configurations (two to generate the .hbm.xml & hibernate.cfg.xml files for each of two databases, and another two to generate the POJO for both databases - i.e. 2 stages x 2 databases).
Each of these "launch" configurations refers to a console configuration.
The first stage (generating the .hbm.xml and hibernate.cfg.xml files) uses consoles which refer to hibernate.cfg.xml files I wrote. The second stage (generating the java) refers to consoles that refer to the hibernate.cfg.xml files generated by the first stage. Hence I've got 4 "launch" configurations, each of which refers to its own console configuration.

However, the toolset appears to save the console configuration in some files in the "workspace" set of directories, and I'd prefer to avoid saving the workspace configuration under CVS. (Everything else is within a single project.)

I've found that it is possible to save a "launch" configuration as a file (instead of having it magically saved away somewhere in the workspace), and hence it's possible to save it as a file in a project (and this is what I've done).
Question is, does anyone know if it is possible to do the same for the console configurations (that these "launch" configurations depend on) and save the console configurations into a file in a project?
If it isn't possible, would folks agree that it should be possible (perhaps even the default) and hence a JIRA enhancement request wouldn't be unreasonable? It would be nice if one could save all the data required by a reverse-engineering project in a nice self-contained fashion.

Thanks,

Peter

Hibernate tools: TOOLS_3_1_0_BETA3


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 24, 2006 3:47 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
sure, put it in jira

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 25, 2006 5:45 am 
Beginner
Beginner

Joined: Tue Jan 24, 2006 1:48 pm
Posts: 20
Location: Stevenage, UK
Ok, I've JIRAed it.

Can I assume from your response that I'm not missing something and there is no workaround (i.e. way of saving the console configurations) other than saving the entire workspace?

Thanks,

Peter


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 25, 2006 5:53 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
yes, all console configurations are saved in the workspace - mimicking how cvs repositories are saved. But i guess that there are a bit too many parameters here, so i'm ok by having it saved inside the project.

_________________
Max
Don't forget to rate


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.