[jira] Created: (MCHANGELOG-81) Unparseable date exception if the date format is other than yyyy-MM-dd for the date range
Unparseable date exception if the date format is other than -MM-dd for the date range - Key: MCHANGELOG-81 URL: http://jira.codehaus.org/browse/MCHANGELOG-81 Project: Maven 2.x Changelog Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Perforce SCM Reporter: Sudharma Rao Priority: Critical Getting following error if the date format is other than -MM-dd as in case of Perforce SCM Embedded error: An error has occurred during changelog command : Unparseable date: "2008/02/08 01:01:01" Following is the plugin configuration and I'm using Perforce SCM. org.apache.maven.plugins maven-changelog-plugin /MM/dd HH:mm:ss date 2008/02/08 01:01:01 2008/02/01 01:01:01 Cause: The date format is hardcoded to "-MM-dd" at line 572 in org/apache/maven/plugin/changelog/ChangeLogReport.java Solution: The SCM plugin uses ' /MM/dd HH:mm:ss' for the start and end date. The Changelog plugin doesn't use this. Please make it use either 'userDateFormat' or 'dateFormat' for parsing date. -- 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: (MINSTALL-47) Add option to append the file name to the md5/sha1 checksums
[ http://jira.codehaus.org/browse/MINSTALL-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124850 ] Wendy Smoak commented on MINSTALL-47: - Niall, what do these checksums get used for? I'm not opposed to the patch, just curious. The feature to create checksums was added in MINSTALL-9, so we might as well give the user control over what the checksums look like. As far as I can tell, Maven ignores checksums for files that are already in the local repo. (So my question about whether Maven can consume this new format is irrelevant for the _install_ plugin.) > Add option to append the file name to the md5/sha1 checksums > > > Key: MINSTALL-47 > URL: http://jira.codehaus.org/browse/MINSTALL-47 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Niall Pemberton >Priority: Minor > Attachments: maven-install-checksum-append-filename-v1.patch, > maven-install-checksum-patterns-v1.patch > > > Some tools which check checksums expect the sum to be followed by > *filename > http://www.mail-archive.com/[EMAIL PROTECTED]/msg67770.html > It would be good to have a configuration option so that the install plugin > can do this -- 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: (MWAR-146) Better support for skinny wars
[ http://jira.codehaus.org/browse/MWAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124857 ] Jene Jasper commented on MWAR-146: -- Is there also something like packagingIncludes because I do not want to edit the war pom.xml every time a shared library is added? > Better support for skinny wars > -- > > Key: MWAR-146 > URL: http://jira.codehaus.org/browse/MWAR-146 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Jene Jasper >Assignee: Stephane Nicoll > Attachments: MWAR-146-maven-war-plugin-2.0.2.patch > > > Added a warLibIncludes element to include only the specified list of jars > because the warSourceExcludes is never finished when you add new dependencies > to a project. -- 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: (MWAR-146) Better support for skinny wars
[ http://jira.codehaus.org/browse/MWAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124858 ] Stephane Nicoll commented on MWAR-146: -- yes > Better support for skinny wars > -- > > Key: MWAR-146 > URL: http://jira.codehaus.org/browse/MWAR-146 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Jene Jasper >Assignee: Stephane Nicoll > Attachments: MWAR-146-maven-war-plugin-2.0.2.patch > > > Added a warLibIncludes element to include only the specified list of jars > because the warSourceExcludes is never finished when you add new dependencies > to a project. -- 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: (MWAR-146) Better support for skinny wars
[ http://jira.codehaus.org/browse/MWAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124859 ] Stephane Nicoll commented on MWAR-146: -- No. The include is based on the resources and the includes/excludes settings. > Better support for skinny wars > -- > > Key: MWAR-146 > URL: http://jira.codehaus.org/browse/MWAR-146 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Jene Jasper >Assignee: Stephane Nicoll > Attachments: MWAR-146-maven-war-plugin-2.0.2.patch > > > Added a warLibIncludes element to include only the specified list of jars > because the warSourceExcludes is never finished when you add new dependencies > to a project. -- 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: (MWAR-146) Better support for skinny wars
[ http://jira.codehaus.org/browse/MWAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MWAR-146: - Comment: was deleted > Better support for skinny wars > -- > > Key: MWAR-146 > URL: http://jira.codehaus.org/browse/MWAR-146 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Jene Jasper >Assignee: Stephane Nicoll > Attachments: MWAR-146-maven-war-plugin-2.0.2.patch > > > Added a warLibIncludes element to include only the specified list of jars > because the warSourceExcludes is never finished when you add new dependencies > to a project. -- 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: (MAVENUPLOAD-1917) Upload beans binding 1.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1917. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload beans binding 1.2.1 > -- > > Key: MAVENUPLOAD-1917 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1917 > Project: maven-upload-requests > Issue Type: Task >Reporter: Steve Taylor >Assignee: Carlos Sanchez > Attachments: beansbinding-1.2.1-bundle.jar > > > The bundle isn't publicly accessable, but it's attached here. Hope that's ok. -- 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-1892) SableCC 3.2 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124863 ] Carlos Sanchez commented on MAVENUPLOAD-1892: - use 3.2-1 as version, previous times that there were problems that was the schema used > SableCC 3.2 upload > -- > > Key: MAVENUPLOAD-1892 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1892 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Paul Donohue >Assignee: Carlos Sanchez > > http://psd.umd.edu/sablecc-3.2-bundle.jar > http://www.sablecc.org/ > I am not a developer for SableCC. > SableCC 3.1 is currently in the repository. > SableCC 3.2 was released ~3 years ago, and is still the latest stable version > (the unstable version 4.0 is still under active development). -- 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: (MAVENUPLOAD-1944) Sync. net.sf.fck-faces repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1944. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync. net.sf.fck-faces repository > - > > Key: MAVENUPLOAD-1944 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1944 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ingo Düppe >Assignee: Carlos Sanchez > Attachments: net.sf.fck-faces.sh > > > Please synchronize http://fck-faces.sf.net/maven2/ repository to the central > maven repository. > I'm a member of the developer team. -- 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-3418) Inclusion of Wagon Webdav component in 2.0.9 distribution
Inclusion of Wagon Webdav component in 2.0.9 distribution - Key: MNG-3418 URL: http://jira.codehaus.org/browse/MNG-3418 Project: Maven 2 Issue Type: Wish Components: Deployment Affects Versions: 2.0.9 Reporter: James William Dumay I propose the inclusion of Wagon Webdav component for the 2.0.9 release. This helps by not having to have a pom when using deploy:deploy-file to load the Wagon dav component or sourcing the correct dependencies to put in Mavens classpath. -- 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-3418) Inclusion of Wagon Webdav component in 2.0.9 distribution
[ http://jira.codehaus.org/browse/MNG-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3418: --- Fix Version/s: 2.0.9 > Inclusion of Wagon Webdav component in 2.0.9 distribution > - > > Key: MNG-3418 > URL: http://jira.codehaus.org/browse/MNG-3418 > Project: Maven 2 > Issue Type: Wish > Components: Deployment >Affects Versions: 2.0.9 >Reporter: James William Dumay >Assignee: Brian Fox > Fix For: 2.0.9 > > > I propose the inclusion of Wagon Webdav component for the 2.0.9 release. > This helps by not having to have a pom when using deploy:deploy-file to load > the Wagon dav component or sourcing the correct dependencies to put in Mavens > classpath. -- 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: (MNG-3418) Inclusion of Wagon Webdav component in 2.0.9 distribution
[ http://jira.codehaus.org/browse/MNG-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124879 ] Brett Porter commented on MNG-3418: --- please note the discussion in http://jira.codehaus.org/browse/MNG-2664 if we can successfully use shade to avoid the problems in there then I'm all for it. > Inclusion of Wagon Webdav component in 2.0.9 distribution > - > > Key: MNG-3418 > URL: http://jira.codehaus.org/browse/MNG-3418 > Project: Maven 2 > Issue Type: Wish > Components: Deployment >Affects Versions: 2.0.9 >Reporter: James William Dumay >Assignee: Brian Fox > Fix For: 2.0.9 > > > I propose the inclusion of Wagon Webdav component for the 2.0.9 release. > This helps by not having to have a pom when using deploy:deploy-file to load > the Wagon dav component or sourcing the correct dependencies to put in Mavens > classpath. -- 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-1892) SableCC 3.2 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124889 ] Paul Donohue commented on MAVENUPLOAD-1892: --- Updated ... http://psd.umd.edu/sablecc-3.2-1-bundle.jar Thanks! > SableCC 3.2 upload > -- > > Key: MAVENUPLOAD-1892 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1892 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Paul Donohue >Assignee: Carlos Sanchez > > http://psd.umd.edu/sablecc-3.2-bundle.jar > http://www.sablecc.org/ > I am not a developer for SableCC. > SableCC 3.1 is currently in the repository. > SableCC 3.2 was released ~3 years ago, and is still the latest stable version > (the unstable version 4.0 is still under active development). -- 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
