Stuart McCulloch wrote:
2009/2/17 Sahoo <[email protected]>
Currently the default value of <Private-Package> is empty. Should it by
default not include all the classes of the current project?
hehe, see http://issues.apache.org/jira/browse/FELIX-912
A coincidence.
The latest 1.5.0-SNAPSHOT now sets the default Export-Package /
Private-Package based on the actual project source (if you set _either_
Export-Package or Private-Package then these defaults are not used).
The distribution of packages is as follows: all packages with source files
(ie. *.java) in the current project are exported, except for packages with
"impl" or "internal" or the default package (".") which are kept as private.
I think it will be better not to have any default value for
Export-Package. If we can't break backward compatibility, then let's
just retain the default value of Export-Package and introduce a new rule
for Private-Package which would be that everything in the project source
that's not already part of Export-Package.
The one remaining question is what to do if only Export-Package is set... we
could set Private-Package based on the actual project source which would
guarantee all your local classes will be in the bundle, but what if you
don't actually want these packages included...
Any thoughts on this last point?
In this case, user has to use empty value for Private-Package if they
don't like our default. BTW, I don't see why someone would compile some
code if they don't want it to be part of the bundle. Do you have a use
case for this? Since I don't think this is a typical case, IMO, it is
fair for the default rule to not be applicable for them.
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
