Is there a special reason, why xml elements from the metadata (for
instance CoreOutputFormatted.xml) like mfp:example or
mfp:source-code are not parsed, when generating the tagdoc stuff ?
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
Hello:
In base-desktop.xss, we have the following private styles:
!--
Private BIDI Styles: Not sure if these are generally useful, but
if so, these could be made public.
--
style name=FloatStart
property name=floatleft/property
/style
style name=FloatEnd
I'm fine with making these public.
Really, to make these public the minimal thing we should do is to
document these keys in skin-selectors.xml and to change the comment to
say they are public instead of private.
We can also change the name to have it start with 'AF' to be consistent
with the
Ok, I figured out what is going on.
If we want our manifest.mf file in our jar to show the implementation
version, then we need to:
1. Add a manifest.mf file in the META-INF directory that has the
implementation-version in it.
2. Add this configuration element to the pom.xml file:
plugin
