Re: Searching for a repo1.maven.org administrator
http://maven.apache.org/guides/mini/guide-central-repository-upload.html http://maven.apache.org/guides/mini/guide-maven-evangelism.html there's a list of automatically synced repos at https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv On Wed, Mar 18, 2009 at 6:08 AM, Bond, Timothy wrote: > Ran into #1 a few weeks ago, there is claim of a bad class file noted > here: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=28069 > > -- Tim > > -Original Message- > From: Costin Caraivan [mailto:ccarai...@axway.com] > Sent: Wednesday, March 18, 2009 8:58 AM > To: users@maven.apache.org > Subject: Searching for a repo1.maven.org administrator > > > Hello, > > I would like to contact the administrators of repo1.maven.org for a > corrupted jars and some incorrect poms on repo1. Or at least, I want to > get > some pointer about who to contact so we can fix the problems. > > A short list of the problems: > 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a > project having this dependency makes Proguard crash. Other versions > don't > have this problem, just the jar on repo1. > 2. bouncycastle:bcprov-jdk13:132 is missing. > org.apache.rampart:rampart-project:1.4 requires this dependency, which > can't > be found. I know about exclusions, but I'd rather fix the problem > directly > where it should be fixed. This might be something related to our > corporate > mirror, I'll double check that later. > 3. All the org.eclipse poms are broken. They use version ranges which > can't > be resolved by Maven. BTW, this is the second time I'm reporting this... > > I would file bugs for these, but I don't know under which *category* to > file > them. > > Thank you, > Costin. > > PS: Don't tell me about fixing the problems in the local repository, I'm > willing to help to get them fixed, I just need a contact person. To fix > them > the *right* way. > -- > View this message in context: > http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22 > 578599p22578599.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Searching for a repo1.maven.org administrator
Ran into #1 a few weeks ago, there is claim of a bad class file noted here: https://issues.apache.org/bugzilla/show_bug.cgi?id=28069 -- Tim -Original Message- From: Costin Caraivan [mailto:ccarai...@axway.com] Sent: Wednesday, March 18, 2009 8:58 AM To: users@maven.apache.org Subject: Searching for a repo1.maven.org administrator Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22 578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Costin Caraivan wrote: > > > Stephen Connolly-2 wrote: >> >> If I establish to the repo1 maintainers that I own the mycompany.com, >> then I >> am responsible for all artifacts with com.mycompany as the group Id. >> repo1 >> will not stop me pushing "bad" artifacts... >> >> Note I'm not saying that this is the way it should be... >> >> > > Thanks for the reply. > > However, couldn't some minimap checks be made? Like checking that all the > dependencies can be found on the repo or the repos specified in the poms? > Sorry, that was supposed to be *minimal* :) -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22579520.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Stephen Connolly-2 wrote: > > If I establish to the repo1 maintainers that I own the mycompany.com, then > I > am responsible for all artifacts with com.mycompany as the group Id. > repo1 > will not stop me pushing "bad" artifacts... > > Note I'm not saying that this is the way it should be... > > Thanks for the reply. However, couldn't some minimap checks be made? Like checking that all the dependencies can be found on the repo or the repos specified in the poms? -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22579516.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
If I establish to the repo1 maintainers that I own the mycompany.com, then I am responsible for all artifacts with com.mycompany as the group Id. repo1 will not stop me pushing "bad" artifacts... Note I'm not saying that this is the way it should be... 2009/3/18 Costin Caraivan > > I know that some stuff is just pulled in from elsewhere, but do you want to > tell me that things get uploaded there with 0 review? > > :| > > > Stephen Connolly-2 wrote: > > > > AFAIK, There is no single point of contact. > > > > for #1 try contacting ibm > > for #2 try contacting bouncycastle > > for #3 try contacting eclipse > > > > 2009/3/18 Costin Caraivan > > > >> > >> Hello, > >> > >> I would like to contact the administrators of repo1.maven.org for a > >> corrupted jars and some incorrect poms on repo1. Or at least, I want to > >> get > >> some pointer about who to contact so we can fix the problems. > >> > >> A short list of the problems: > >> 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a > >> project having this dependency makes Proguard crash. Other versions > don't > >> have this problem, just the jar on repo1. > >> 2. bouncycastle:bcprov-jdk13:132 is missing. > >> org.apache.rampart:rampart-project:1.4 requires this dependency, which > >> can't > >> be found. I know about exclusions, but I'd rather fix the problem > >> directly > >> where it should be fixed. This might be something related to our > >> corporate > >> mirror, I'll double check that later. > >> 3. All the org.eclipse poms are broken. They use version ranges which > >> can't > >> be resolved by Maven. BTW, this is the second time I'm reporting this... > >> > >> I would file bugs for these, but I don't know under which *category* to > >> file > >> them. > >> > >> Thank you, > >> Costin. > >> > >> PS: Don't tell me about fixing the problems in the local repository, I'm > >> willing to help to get them fixed, I just need a contact person. To fix > >> them > >> the *right* way. > >> -- > >> View this message in context: > >> > http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html > >> Sent from the Maven - Users mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578774.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Searching for a repo1.maven.org administrator
I know that some stuff is just pulled in from elsewhere, but do you want to tell me that things get uploaded there with 0 review? :| Stephen Connolly-2 wrote: > > AFAIK, There is no single point of contact. > > for #1 try contacting ibm > for #2 try contacting bouncycastle > for #3 try contacting eclipse > > 2009/3/18 Costin Caraivan > >> >> Hello, >> >> I would like to contact the administrators of repo1.maven.org for a >> corrupted jars and some incorrect poms on repo1. Or at least, I want to >> get >> some pointer about who to contact so we can fix the problems. >> >> A short list of the problems: >> 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a >> project having this dependency makes Proguard crash. Other versions don't >> have this problem, just the jar on repo1. >> 2. bouncycastle:bcprov-jdk13:132 is missing. >> org.apache.rampart:rampart-project:1.4 requires this dependency, which >> can't >> be found. I know about exclusions, but I'd rather fix the problem >> directly >> where it should be fixed. This might be something related to our >> corporate >> mirror, I'll double check that later. >> 3. All the org.eclipse poms are broken. They use version ranges which >> can't >> be resolved by Maven. BTW, this is the second time I'm reporting this... >> >> I would file bugs for these, but I don't know under which *category* to >> file >> them. >> >> Thank you, >> Costin. >> >> PS: Don't tell me about fixing the problems in the local repository, I'm >> willing to help to get them fixed, I just need a contact person. To fix >> them >> the *right* way. >> -- >> View this message in context: >> http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578774.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Oh, and before I forget, you will not be able to get the bad artifacts fixed... only superceded with newer versions... once an artifact is in repo1 it's there for good 2009/3/18 Stephen Connolly > AFAIK, There is no single point of contact. > > for #1 try contacting ibm > for #2 try contacting bouncycastle > for #3 try contacting eclipse > > 2009/3/18 Costin Caraivan > > >> Hello, >> >> I would like to contact the administrators of repo1.maven.org for a >> corrupted jars and some incorrect poms on repo1. Or at least, I want to >> get >> some pointer about who to contact so we can fix the problems. >> >> A short list of the problems: >> 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a >> project having this dependency makes Proguard crash. Other versions don't >> have this problem, just the jar on repo1. >> 2. bouncycastle:bcprov-jdk13:132 is missing. >> org.apache.rampart:rampart-project:1.4 requires this dependency, which >> can't >> be found. I know about exclusions, but I'd rather fix the problem directly >> where it should be fixed. This might be something related to our corporate >> mirror, I'll double check that later. >> 3. All the org.eclipse poms are broken. They use version ranges which >> can't >> be resolved by Maven. BTW, this is the second time I'm reporting this... >> >> I would file bugs for these, but I don't know under which *category* to >> file >> them. >> >> Thank you, >> Costin. >> >> PS: Don't tell me about fixing the problems in the local repository, I'm >> willing to help to get them fixed, I just need a contact person. To fix >> them >> the *right* way. >> -- >> View this message in context: >> http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
Re: Searching for a repo1.maven.org administrator
AFAIK, There is no single point of contact. for #1 try contacting ibm for #2 try contacting bouncycastle for #3 try contacting eclipse 2009/3/18 Costin Caraivan > > Hello, > > I would like to contact the administrators of repo1.maven.org for a > corrupted jars and some incorrect poms on repo1. Or at least, I want to get > some pointer about who to contact so we can fix the problems. > > A short list of the problems: > 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a > project having this dependency makes Proguard crash. Other versions don't > have this problem, just the jar on repo1. > 2. bouncycastle:bcprov-jdk13:132 is missing. > org.apache.rampart:rampart-project:1.4 requires this dependency, which > can't > be found. I know about exclusions, but I'd rather fix the problem directly > where it should be fixed. This might be something related to our corporate > mirror, I'll double check that later. > 3. All the org.eclipse poms are broken. They use version ranges which can't > be resolved by Maven. BTW, this is the second time I'm reporting this... > > I would file bugs for these, but I don't know under which *category* to > file > them. > > Thank you, > Costin. > > PS: Don't tell me about fixing the problems in the local repository, I'm > willing to help to get them fixed, I just need a contact person. To fix > them > the *right* way. > -- > View this message in context: > http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >