Eclipse.org provides us with an excellent download infrastructure and mirroring system, so it's probably simplest to use that. It would make bundling the JARs and maintaining dependencies Mylar's responsibility. Anything extra you would need (i.e. the poms) would be best as a contribution you make to the Ant build script. Would that work?
Note that 0.6.0 is not ready for being used in this way because it has the Tasks API in the mylar.tasklist, which is coupled into the UI. Bug for that is: 149981: extract tasks framework from mylar.tasklist https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981 Mik > -----Original Message----- > From: Tomasz Pik [mailto:[EMAIL PROTECTED] > Sent: Friday, July 07, 2006 1:45 AM > To: Mik Kersten > Cc: [EMAIL PROTECTED]; Maven Developers List > Subject: Re: Common API for issue tracking systems > > On 7/7/06, Mik Kersten <[EMAIL PROTECTED]> wrote: > > > Could you please create a bug report for us to indicate how you want to > get > > this API, e.g. have a downloadable bin+src JAR, separate JARs, build > from > > source? http://www.eclipse.org/mylar/bugs.php > > Ideally I'd like just to define, that my code depends on mylar libraries > and maven will download them from ibblio mirrors. > But this comes down to disussion about maintaining libraries on > ibiblio, I don't know if mylar team is interested in providing jars > and poms in a needed form. > Please, let me know this, otherwise I'll try to prepare such set > based on mylar 0.6.0 distribution and open an issue for adding them > to ibiblio (perhaps asking Mylar team to review dependencies and other > things first). > > Regards, > Tomek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
