From: Alex O'R. <spy...@gm...> - 2014-04-16 00:26:04
|
Hi I have a project that needs a specific version of JCommon which is not in the maven repo. Is it possible for someone to publich 1.0.18 (someone else on the form asked for 1.0.16 too)? I was considering opening a sonatype ticket to get it published but i don't want to cause any synchronization issues |
From: Martin H. <ma...@xs...> - 2014-04-16 07:08:42
Attachments:
signature.asc
|
On 15 Apr 2014, Alex O'Ree wrote: > Hi I have a project that needs a specific version of JCommon which is not > in the maven repo. Is it possible for someone to publich 1.0.18 (someone > else on the form asked for 1.0.16 too)? JFreeChart still uses ant, unfortunately. I tried to publish current versions to maven central for the last view years but missed some (no time). If new versions come out I'll try to upload them ASAP but I'm not going to start uploading old versions. So your best option would be to just use a local repo-manager (like nexus or archiva) as suggested by the maven guys anyway, and upload the missing artifacts there. It will save you time in the end and is really not much work. > I was considering opening a sonatype ticket to get it published but i don't > want to cause any synchronization issues Don't do this. This only reaches Sonatype who is not responsible for this job and they won't upload anything. - martin |
From: Alex O'R. <spy...@gm...> - 2014-04-16 12:47:42
|
Sonatype has a mechanism to get stuff added to maven central. https://maven.apache.org/guides/mini/guide-central-repository-upload.html, see the section on Sonatype OSS. Are you really against this? I'm willing to do the leg work to get this uploaded. JCommon, at least 1.0.18 has a pom already, it just needs to be uploaded. On Wed, Apr 16, 2014 at 2:45 AM, Martin Hoeller <ma...@xs...> wrote: > On 15 Apr 2014, Alex O'Ree wrote: > > > Hi I have a project that needs a specific version of JCommon which is not > > in the maven repo. Is it possible for someone to publich 1.0.18 (someone > > else on the form asked for 1.0.16 too)? > > JFreeChart still uses ant, unfortunately. I tried to publish current > versions to maven central for the last view years but missed some (no > time). If new versions come out I'll try to upload them ASAP but I'm not > going to start uploading old versions. > > So your best option would be to just use a local repo-manager (like nexus > or archiva) as suggested by the maven guys anyway, and upload the missing > artifacts there. It will save you time in the end and is really not much > work. > > > I was considering opening a sonatype ticket to get it published but i > don't > > want to cause any synchronization issues > > Don't do this. This only reaches Sonatype who is not responsible for this > job and they won't upload anything. > > - martin > |
From: Martin H. <ma...@xs...> - 2014-04-16 13:06:42
Attachments:
signature.asc
|
On 16 Apr 2014, Alex O'Ree wrote: > Sonatype has a mechanism to get stuff added to maven central. > https://maven.apache.org/guides/mini/guide-central-repository-upload.html, > see the section on Sonatype OSS. I know, that's what we do with new releases and it's even documented in the wiki: http://sourceforge.net/apps/mediawiki/jfreechart/index.php?title=Developer_Information#Deploy_a_release_to_the_Maven_Central_Repository > Are you really against this? No, this is great! But actually it's some work when ant is the primary used build-tool. You need to checkout the old version, generate javadocs, signatures and upload all this staff via maven. Maven can do all of this automatically, but as it's not the primary build-tool, sometimes problems arise when performing this task which makes it a bit time consuming. (When everyhing works ok, it's less than 15min of work, but it can be an hour or two if something goes wrong.) > I'm willing to do the leg work to get this > uploaded. JCommon, at least 1.0.18 has a pom already, it just needs to be > uploaded. You don't have permission to upload, so I would have to do it anyway. And for uploading it via maven (what is the recommended way), I need the artifacs, javadocs, poms and all correctly signed in my local repo. So the leg work you offer to do won't help me much :( But you sould do it anyway and just deploy it to your lokal or remote repository manager and that's the least work for everybody. If you are kind, you could document the process and post it here or in the forum to help others. hth, - martin > On Wed, Apr 16, 2014 at 2:45 AM, Martin Hoeller <ma...@xs...> wrote: > > > On 15 Apr 2014, Alex O'Ree wrote: > > > > > Hi I have a project that needs a specific version of JCommon which is not > > > in the maven repo. Is it possible for someone to publich 1.0.18 (someone > > > else on the form asked for 1.0.16 too)? > > > > JFreeChart still uses ant, unfortunately. I tried to publish current > > versions to maven central for the last view years but missed some (no > > time). If new versions come out I'll try to upload them ASAP but I'm not > > going to start uploading old versions. > > > > So your best option would be to just use a local repo-manager (like nexus > > or archiva) as suggested by the maven guys anyway, and upload the missing > > artifacts there. It will save you time in the end and is really not much > > work. > > > > > I was considering opening a sonatype ticket to get it published but i > > don't > > > want to cause any synchronization issues > > > > Don't do this. This only reaches Sonatype who is not responsible for this > > job and they won't upload anything. > > > > - martin > > -- Martin Höller | mar...@xs... *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 |
From: Martin H. <ma...@xs...> - 2014-04-16 13:13:31
Attachments:
signature.asc
|
On 16 Apr 2014, Martin Hoeller wrote: > On 16 Apr 2014, Alex O'Ree wrote: > > > Sonatype has a mechanism to get stuff added to maven central. > > https://maven.apache.org/guides/mini/guide-central-repository-upload.html, > > see the section on Sonatype OSS. > > I know, that's what we do with new releases and it's even documented in > the wiki: > http://sourceforge.net/apps/mediawiki/jfreechart/index.php?title=Developer_Information#Deploy_a_release_to_the_Maven_Central_Repository > > > Are you really against this? > > No, this is great! But actually it's some work when ant is the primary > used build-tool. You need to checkout the old version, generate javadocs, > signatures and upload all this staff via maven. Maven can do all of this > automatically, but as it's not the primary build-tool, sometimes problems > arise when performing this task which makes it a bit time consuming. > (When everyhing works ok, it's less than 15min of work, but it can be an > hour or two if something goes wrong.) > > > I'm willing to do the leg work to get this > > uploaded. JCommon, at least 1.0.18 has a pom already, it just needs to be > > uploaded. > > You don't have permission to upload, so I would have to do it anyway. And > for uploading it via maven (what is the recommended way), I need the > artifacs, javadocs, poms and all correctly signed in my local repo. So > the leg work you offer to do won't help me much :( > > But you sould do it anyway and just deploy it to your lokal or remote > repository manager and that's the least work for everybody. If you are > kind, you could document the process and post it here or in the forum to > help others. Here are some links that might help understanding Maven repositories: https://maven.apache.org/repository-management.html http://stackoverflow.com/questions/5692256/maven-best-way-of-linking-custom-external-jar-to-my-project?lq=1 http://stackoverflow.com/questions/442230/how-to-manually-install-an-artifact-in-maven-2?lq=1 hth, - martin |