I've seen rumors on general portlas of an impending pluto release. I
assume this would be of trunk.
I glanced at the svn tree for a minute and see some things that either
need to be or IMO should be changed before release.
Required....
There needs to be an accurate NOTICE file in svn at the root that
applies to the actual source code you get when you check out from
svn. AFAIK this is just the standard apache NOTICE.
Desirable...
use up to date portals-pom as parent. Hopefully this will be 1.2
clean up pom plugin dependencies -- most of these should be specified
in parents.
I think it might be a good idea to provide osgi metadata by using the
maven-bundle-plugin. On the other hand I'm not prepared to test if it
is accurate yet.
I don't think specifying all dependency versions as properties is
considered good maven practice.
I don't think we necessarily want the KEYS file here. I'd think in a
common location for portals would be better.
I suspect that pluto.xsi is not functional, I don't see any obvious
updates since pluto 1.
I'd really prefer using maven tools rather than ant to assembly the
binary distros including tomcat. Such an assembly would be in an
additional subproject, not the top level pom.
I ran into some unwarranted classloading assumptions in pluto 1, see
PLUTO-555. I think it would be great if we could fix the remaining
one in pluto trunk before release, but I'm not entirely sure what the
correct fix really is. In pluto 1.x I did this in ToolTips.java:
- private static final ResourceBundle BUNDLE =
ResourceBundle.getBundle("ToolTips");
+ private static final ResourceBundle BUNDLE =
ResourceBundle.getBundle("ToolTips", Locale.US,
Thread.currentThread().getContextClassLoader());
but it seems rather unlikely that the Locale.US is appropriate.
Anyone have an idea?
thanks
david jencks
