[ http://jira.codehaus.org/browse/MAVENUPLOAD-950?page=comments#action_68918 ]
Jeff Jensen commented on MAVENUPLOAD-950: ----------------------------------------- Must be something with m2. We've been running these without problem on Maven 1 FB 1.3 snapshot since you published them. The POMs have been that way for years, except for the increased version numbers I did to 1.0.0 (I just copied the existing ones and changed FB version number). Interesting changes. When prepping 1.3, I wondered about dom4j. I noticed the m1 plugin declares it. I'd like m1 to use the same poms as m2 for future maintenance. Can I just update the m1 plugin's FB dependency group ids, or is there more to it? I see the model version 4 in the m2 ones...makes me think not. If /maven redirects to /maven2, then why does it take days for new things to show up in /maven even though they exist in /maven2? net.sourceforge.findbugs is another example of this. This works: http://www.ibiblio.org/maven2/net/sourceforge/findbugs/findbugs/1.0.0/ This does not work: http://www.ibiblio.org/maven/net/sourceforge/findbugs/findbugs/1.0.0/ This does not work: http://www.ibiblio.org/maven/net.sourceforge.findbugs > Upload new FindBugs 1.0.0 artifacts to ibiblio > ---------------------------------------------- > > Key: MAVENUPLOAD-950 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-950 > Project: maven-upload-requests > Type: Improvement > Reporter: Jeff Jensen > Assignee: Carlos Sanchez > Attachments: annotations-1.0.0-bundle.jar, coreplugin-1.0.0-bundle.jar, > findbugs-1.0.0-bundle.jar, findbugs-ant-1.0.0-bundle.jar, > findbugsGUI-1.0.0-bundle.jar > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
