Ben Alex wrote:

Documentation generation is about the only thing I can think of. Just to put it up on iBiblio requires only the jar file produced by the ant build, you don't need Maven for that...



OK, will we be uploading as per
http://maven.apache.org/repository-upload.html? In that case, what do we put
in the project.xml?


They never used to asked for the POM file (project.xml). As a first step, I would just submit it with a license and the jar files. There's plenty of libs up on iBiblio without POMs (Spring itself, for example).

It's not a very big deal to make a project.xml file, I did it for 15-20 odd projects while I was playing around with Maven. But if you're not building with Maven in the first place, it's somewhat hard to actually validate it, and at this point Maven _does not_ support transitive dependencies, so I would probably not bother producing a POM for it until it actually does...

Colin




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Acegisecurity-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer

Reply via email to