Thanks a lot for your work on this!
I had a quick look at the pom and was wondering:
- The groupId: we have org.jitsi registered at Sonatype. I realise that ice4j has always been a bit more separated than the other projects, but I think it would be best to put it under org.jitsi anyway. What were your thaughts on this matter?
- Forked dependencies: from my experince so far, other projects put forks under their own groupId, i.e. for us org.jitsi. This way they can be uploaded to Sonatype without having deploy access to the projects' respective groupId. Again, love to hear what you think.
- Packaging: ideally we would directly create OSGi bundles instead of plain jars. There's a build plugin that automatically creates the manifest. See e.g. sdes4j's pom.
This all obviously doesn't really apply if we don't upload our artifacts to Sonatype/Maven Central. But I think we should aim to do that for our libraries.
-- sent from my mobile
On 29.06.2015, at 02:16, Jitsi Jenkins <firstname.lastname@example.org> wrote:
ice4j - Build # 217 - Successful
Started by an SCM change
[email@example.com] Adds Maven support.
No tests ran.
cruisecontrol mailing list
Unsubscribe instructions and other list options: