I have a few questions regarding jaxme's mavenizing. I'm sure there are
more to come :-)
- Project JaxMe2 has been renamed to JaxMeCore so it doesn't clash with
the top-level project. Any other ideas?
- How do we want to handle subproject's version? All subprojects have
the same version?
- Where do we want the resulting jars to be? Stick with dist?
- Do we want the target directory and dist directory on cvs? IMHO no.
- The checkstyle.xml file used is the same Maven uses. Maybe review to
suit our needs.
- All tests (except for PM - which I haven't started mavenizing) are ran
by maven but VersionTest from JS fails because it is expected to be ran
by ant. Any ideas? Also JS.antlr.test is not a junit test. Should a
junit test be made?
- When building JS's tests the first thing I did was to build the
auxiliary files on a temp directory and then compile with ant the JS.src
and the temp directory all together. The thing is that we'd need
hsqldb.jar and junit.jar on the repository. I was thinking of generating
the auxiliary files (EnumExample, ...) on the JS.src folder with a
different package name: org.apache.ws.jaxme.js.junit.temp (or similar)
so after compilation they can safely be deleted from the JS.src folder.
Any other ideas?
best regards,
nacho
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
