Hi people,

Just was checking the plugins release and I noticed a couple of things that 
could be improved (this
is not specifically about the release, but more technical).

A couple of things were missing from the release, which could be handled a 
different way :

- The parent pom of trinidad plugins could org.apache/apache/3 (think that is )
  This fixes the license things automatically.
- if you put a NOTICE.txt and LICENSE.txt in every "root" of an artifact 
(plugins can be used
individually, so I think they need to be there anyway), you can simply use the 
resources plugin to
include them from the root of the plugin, instead of having them in 
src/main/resources. In any case,
the NOTICE could be different for every plugin (eg could imagine adding javacc 
to the notice of the
javacc plugin)
- The current signing of the plugin (when doing releases) is uncommented. You 
can also put that in a
profile, so you don't have to change the pom each time (probably could also be 
done in a
profiles.xml, but to be honest, I never used that)
- Add some documentation how a release are made by the trinidad project (also 
for the non plugin
releases). (if it is already there, sorry didn't look too close :)


If I can find some time I can do some of the changes myself and send patches / 
commit myself
(whatever is preferred, in the commit myself scenario I will give myself karma 
for trinidad).
I can also do it in a branch, so you can review if you are happy with the 
changes I have in mind..

Mvgr,
Maritn

Reply via email to