I'm working on cleaning up the build (BVAL-58).  Here are a few things I 
suggest changing -- these will be in at least one version of my patch -- and 
some questions.

1. It seems pretty standard nowadays to name bundles such as apache-bval by 
their package name, so it would be <artifactId>org.apache.bval</artifactId>

2. I don't think its worth the trouble to use antrun to figure out the svn 
version.  Maven already creates a property file that includes the project 
version.  If anyone really wants this info, I'd hope they would write an 
scm-plugin mojo to do it.

3. Is anyone interested in using slf4j instead of commons-logging?

4.  For use in osgi, I'm not sure why any packages are exported.  Isn't the 
idea that you create the validator through the spec api and configure it 
through a provided xml file if necessary?   I really doubt exporting everything 
is a good idea.

5. Reading the eclipse documentation at 
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
 it looks to me like the Eclipse-AutoStart header is obsolete and does nothing 
(modern osgi frameworks behave this way by default).

thanks!
david jencks

Reply via email to