Hi, Nacho,
Nacho G. Mac Dowell wrote:
Do you mean we'll be able to reverse jaxb's behaviour? This would definitely attract a lot more users!
No idea, what you mean. :-) The idea is, that the user may supply his own data beans (that do not generate an interface or something similar) and that JaxMe generates the marshalling and unmarshalling code only. A bridge to Betwixt, in other words.
All I've recently done is try to mavenize jaxme.
I have absolutely no idea about Maven. What are the advantages?
I will probably need assistance on the build process.
No problem. As far as I am concerned, I would only ask, that the clean separation between api, xs, js, jaxme core, and pm is kept.
Maven is the only way I can imagine to include the plugin (because of eclipse's dependencies). any ideas?
If it is for the plugin only, that's no problem. As we can and will not distribute the Eclipse jar files (license issues), one has to add them manually to the build directory. In other words, it is not a necessity, that it can be built out of the box. It is quite fine to specify "Get that jar file from there, put it in some directory and create a property foo with the directory path. Then the build will work." or something similar.
Should I commit JAXME-47's patch? It's about default values handling. I'm still quite scared of committing anything... :-[
Go on. :-) If you want to do things good, add a unit test, that demonstrates the bug and proofs that you did indeed fix it.
Can you explain a little bit jaxme's versions and branches? I get confused...
There's nothing special. We have a maintenance branch (0.3) and the HEAD. As far as I am concerned, we'll cut a new maintenance branch for 0.4 at some point. Maintenance branch means nothing more, than that only bug fixes should go into the branch. Features etc. go into HEAD.
Jochen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
