Gordon, On Thursday November 16 2006 4:26 am, Gordon Sim wrote: > Daniel Kulp wrote: > > On Wednesday November 15 2006 2:23 pm, Carl Trieloff wrote: > >> This is key as for most projects. everything that we use might > >> not/will not be in a maven repository. How is this best handled with > >> maven? > > > > Get the artifacts into the repository. From an apache standpoint, > > all the licenses for stuff we're allowed to use allow for the > > artifacts to be published to the maven repository. Follow the > > instructions at: > > http://maven.apache.org/guides/mini/guide-central-repository-upload.h > >tml > > Dan, > > thanks for the info. I have had a brief read of that document. The > quoted section below raised one more question in my mind: > > "you must provide proof that you control the domain that > matches the groupId. Provide proof means that the project > is hosted at that domain or it's owned by a member, in > that case you must give the link to the registrar database > (whois) where the owner is listed and the page in the > project web where the owner is associated with the project. > eg. If you use a com.sun.xyz package name we expect that > the project is hosted at http://xyz.sun.com."; > > Can we put third party artifacts (whose license is acceptable to ASF) > into a maven repository? > > E.g. if we wanted to use evs4j for clustering > (http://freshmeat.net/projects/evs4j/, apache license 2.0), can we > upload that to a maven repository so we can use it as a dependency for > qpid? Could we use net.freshmeat.evs4j as the group id?
Yep. Basically, we would create a pom.xml that accurate describes the jar. The pom would have to include the licenses section, URL, proper dependencies (if any) and stuff like that. You would then zip up the pom.xml, the jar, and preferrably a sources jar and javadoc jar (more on that in a sec), stick the zip on a public HTML site (your apache ~/public_html dir works), and create a MAVENUPLOAD jira request pointing at it. Most of the "legal mumbo jumbo" is to help Carlos. Carlos has a script that runs on the maven upload things. If all the legal stuff is met, the script runs automatically and he doesn't have to do anything. If the script cannot verify things through the automatic routines (example: com.sun.xyz not mapping to http://xyz.sun.com), then Carlos needs to do a bit of manual work to verify things are really there. That all said, it can take a couple days (I think Carlos processes stuff twice a week). Thus, if you are interested in using that, it might be best to start getting it uploaded sooner wrather than later. The only things we really cannot get added to central via this method is other incubating dependencies. That's because Apache doesn't want incubating things on the mirrors. However, Apache has it's own maven repository for incubating projects (where the qpid artifacts would also go). We would just need to work with the other incubating project to help them get the artifacts uploaded. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED]
