|It is more practical to develop and build that way. The classes go into
|ejxjboss.jar anyway (not jboss.jar). Note that the package naming would
|still place it in the org.jboss core.
That is just because you work on the GUI. Please keep the class files under
the main tree. People who look at the container want to know where the
metadata comes from. You had it in the GUI before and it was no good.
Please learn.
|I do not want the normal users to be in no-mans-land during this
|phase, so I
|will figure out how to do CVS branches first. That will allow this to be
|done in parallel and merged in at the last possible point in time.
sounds good, a tag would have done it since I trust you can put good code in
there.
|We are not going to release a version in a week so tags are OK.
|Indeed. As above, the classes are in org.jboss, but not in JBoss
|core CVS. I
That is a mistake, the convenience of your gui BUILD should not impact the
the convenience of browsing and building for all developers of the
container.
|might move these classes to JBoss core when it is done though, although I
|think the only reason would be to "keep them together". From a practical
|point of view it is better to keep it in the EJX CVS module, as motivated
|above.
no rickard building the JBoss core then becomes complicated because we move
the stuff in the GUI and the metadata and we have to move the files etc etc.
We were there before remember? Develop the GUI as you wish but it will not
impact the container, ok?
marc
|
|regards,
| Rickard
|
|
|
|
|
