Daniel Fagerstrom wrote:
I'll talk to Upayavira, and see if we can take care about it.
I saw that you had changed the Cocoon group id to org.apache.cocoon from
apache-cocoon in the main pom and the core pom but nowhere else. What is
your plane for this? Should we just start to change group id to
org.apache.cocoon in all poms?
The "unofficial" groupId policy from the maven ppl states that one
should try to use a package based groupId ie org.apache.cocoon rather
than just apache-cocoon. I'll see about getting our poms changed unless
you beat me to it.
Jorg
