[jira] Commented: (MAVENUPLOAD-2141) Updated version of JSON Java code from www.json.org
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141324#action_141324 ] Michael Tamm commented on MAVENUPLOAD-2141: --- Because I downloaded the source code and created the bundle on 8th of July 2008. But I also see your point, so I just created the another bundle with the version 20080701. You can download it here: http://www.michaeltamm.de/downloads/json-20080701-bundle.jar > Updated version of JSON Java code from www.json.org > --- > > Key: MAVENUPLOAD-2141 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2141 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Tamm > > There have been some changes since the last release: > http://repo1.maven.org/maven2/org/json/json/20070829 -- 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
[jira] Commented: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141330#action_141330 ] Mikael Grev commented on MAVENUPLOAD-2116: -- rsync supports automatic login using password with the "--password-file=FILE" argument, that is why I thought it would work. I will see if I can turn SSH on on my Netgear NAS. Or if I can turn off the password altogether. > Please add MigLayout to the auto rsynced list. > -- > > Key: MAVENUPLOAD-2116 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mikael Grev >Assignee: Carlos Sanchez > > "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael > Grev,[EMAIL PROTECTED],, > The password is "maven". > MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being > added to SWT and #10 RFE for being added to the Java SDK. > I own MiGInfoCom AB which owns MigLayout. > Cheers, > Mikael Grev -- 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
[jira] Closed: (MPIR-118) Equalize links to project web site for artifactId
[ http://jira.codehaus.org/browse/MPIR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-118. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 Fixed in r675547, snapshot deployed > Equalize links to project web site for artifactId > -- > > Key: MPIR-118 > URL: http://jira.codehaus.org/browse/MPIR-118 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies, dependency-convergence, > dependency-management, plugin-management >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > Actually, only the "Project Plugin Management" report has a link in > artifactId column to its project web site. It should be great to add be > default a link to the project Artifact, if it is specified of course. -- 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
[jira] Created: (WAGON-226) filePermissions and directoryPermissions are not set correctly.
filePermissions and directoryPermissions are not set correctly. --- Key: WAGON-226 URL: http://jira.codehaus.org/browse/WAGON-226 Project: Maven Wagon Issue Type: Bug Components: wagon-ftp Affects Versions: 1.0-beta-3, 1.0-beta-2, 1.0 Reporter: Matthieu Leclercq Attachments: wagon-ftp-beta-2.patch, wagon-ftp.patch file permissions and/or directory permissions are not set correctly the "SITE" ftp command that is executed is not correct (the file name is missing). The attached patches fix the issue on trunk and on 1.0-beta-2 release. -- 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
[jira] Created: (MAVENUPLOAD-2145) Mockito 1.4 upload request
Mockito 1.4 upload request -- Key: MAVENUPLOAD-2145 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2145 Project: Maven Upload Requests Issue Type: Wish Reporter: Igor Czechowski http://mockito.googlecode.com/svn/branches/1.4/maven/mockito-all-1.4-bundle.jar http://code.google.com/p/mockito/ http://code.google.com/u/iczechowski/ I'm a project member in Mockito, please upload this bundle, which has no external dependencies. -- 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
[jira] Commented: (MAVENUPLOAD-2124) javaparser-1.0.0-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141407#action_141407 ] Carlos Sanchez commented on MAVENUPLOAD-2124: - http://maven.apache.org/guides/mini/guide-central-repository-upload.html The groupId will identify your project uniquely across all projects, so we need to enforce a naming schema. For projects with artifacts already uploaded to the Central Repository it can be equal to the one used previously, but for new projects it has to follow the package name rules, what means that has to be at least as a domain name you control, and you can create as many subgroups as you want. There are a lot of poorly defined package names so you must provide proof that you control the domain that matches the groupId. Provide proof means that the project is hosted at that domain or it's owned by a member, in that case you must give the link to the registrar database (whois) where the owner is listed and the page in the project web where the owner is associated with the project. eg. If you use a com.sun.xyz package name we expect that the project is hosted at http://xyz.sun.com. Look at More information about package names . Check also the guide about Maven naming conventions . Examples: * www.springframework.org -> org.springframework * oness.sf.net -> net.sf.oness > javaparser-1.0.0-bundle.jar > --- > > Key: MAVENUPLOAD-2124 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2124 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alexandr Liahushevich > Attachments: javaparser-1.0.0-bundle.jar, > javaparser-1.0.0-bundle.jar, javaparser-1.0.1-bundle.jar > > > From: Julio Gesser [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 2:38 PM > To: Alexandr Liahushevich > Subject: Re: Java 1.5 Parser - request to put sources into the maven > repository > > Helo Alexandr, > yes, you can put this distribution there, but I think you need to put the > license too. > best regards, > Júlio Vilmar Gesser > 2008/6/24 Alexandr Liahushevich <[EMAIL PROTECTED]>: > One more question please. > We are using Maven technology for our projects. > Is it ok for you and your team that we want to put your > javaparser_2008-06-19.jar file in the http://repo1.maven.org/maven2/ central > maven repository? -- 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
[jira] Created: (MNG-3661) Cargo deployment issues when used with clover
Cargo deployment issues when used with clover - Key: MNG-3661 URL: http://jira.codehaus.org/browse/MNG-3661 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Reporter: Matt Wringe The clover plugin is setting the classifier for the dependencies as being 'clover', this causes issues when cargo wants to deploy an artifact as the classifiers for the dependencies no longer match. -- 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
[jira] Created: (MPMD-84) Maven PMD plugin does not honour exclude-pattern in PMD rulesets
Maven PMD plugin does not honour exclude-pattern in PMD rulesets Key: MPMD-84 URL: http://jira.codehaus.org/browse/MPMD-84 Project: Maven 2.x PMD Plugin Issue Type: Bug Components: PMD Affects Versions: 2.4 Reporter: Denis Cabasson According to PMD documentation, exclude-patterns should be independendant on the program running PMD : http://pmd.sourceforge.net/howtomakearuleset.html But Maven scans through all the files, not taking into account the exclude-patterns and thus including files that shouldn't be. THose file should be filtered out by the maven plugin -- 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
[jira] Reopened: (MAVENUPLOAD-1989) Add Xalan 2.7.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened MAVENUPLOAD-1989: --- Hi Folks, I reopen the issue because I can see nothing here : http://repo1.maven.org/maven2/xalan/xalan/. Carlos do you need a bundle for this or it's the xalan team job ? Thanks, -- Olivier > Add Xalan 2.7.1 > --- > > Key: MAVENUPLOAD-1989 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1989 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Daniel Kulp >Assignee: Carlos Sanchez > > Please add xalan 2.7.1 to the maven repos. It fixes a couple of nasty bugs > that we're encountering and would like to be able to use it. -- 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
[jira] Updated: (MNG-3639) Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9
[ http://jira.codehaus.org/browse/MNG-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3639: --- Assignee: John Casey Fix Version/s: (was: 2.0.11) 2.0.10 John, this looks like a possible regression introduced in 2.0.9, as such, we should take another look for 2.0.10 > Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9 > -- > > Key: MNG-3639 > URL: http://jira.codehaus.org/browse/MNG-3639 > Project: Maven 2 > Issue Type: Bug > Components: Ant tasks >Affects Versions: 2.0.8 >Reporter: Niall Pemberton >Assignee: John Casey > Fix For: 2.0.10 > > Attachments: mvn-2.0.8-output.txt, mvn-2.0.9-output.txt, pom.xml > > > Apache Commons has a maven ant plugin (called commons-build-plugin[1]) which > has a dependency on Ant 1.7.0 and uses the loadresource task (which was added > to Ant in version 1.7.0). The plugin works fine for maven 2.0.8, but after > upgrading to 2.0.9 fails with the message "Could not create task or type of > type: loadresource." (see attached output). > This has been raised on the maven dev list in the following thread: > http://markmail.org/message/tv37c37fjyzx6l6k > I am attaching a simple pom.xml that reproduces this problem with the > following command: > mvn commons:jira-page > (N.B. create either a "xdocs" or "src/xdoc" directory in the project) > [1] > http://svn.apache.org/viewvc/commons/proper/commons-build-plugin/tags/commons-build-plugin-1.0/ -- 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
