[jira] Created: (MAVENUPLOAD-713) easymock 2.0
easymock 2.0 Key: MAVENUPLOAD-713 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-713 Project: maven-upload-requests Type: Task Reporter: Alexandre Poitras Attachments: easymock-2.0-bundle.jar The bundle comes as an attachment http://www.easymock.org/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-713) easymock 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-713?page=all ] Alexandre Poitras updated MAVENUPLOAD-713: -- Attachment: easymock-2.0-bundle.zip easymock 2.0 Key: MAVENUPLOAD-713 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-713 Project: maven-upload-requests Type: Task Reporter: Alexandre Poitras Attachments: easymock-2.0-bundle.jar, easymock-2.0-bundle.zip The bundle comes as an attachment http://www.easymock.org/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-713) easymock 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-713?page=all ] Alexandre Poitras updated MAVENUPLOAD-713: -- Attachment: easymock-2.0-bundle.jar easymock 2.0 Key: MAVENUPLOAD-713 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-713 Project: maven-upload-requests Type: Task Reporter: Alexandre Poitras Attachments: easymock-2.0-bundle.jar, easymock-2.0-bundle.jar, easymock-2.0-bundle.zip The bundle comes as an attachment http://www.easymock.org/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (WAGON-36) An exception is throwed when the http response code is 201
An exception is throwed when the http response code is 201
--
Key: WAGON-36
URL: http://jira.codehaus.org/browse/WAGON-36
Project: wagon
Type: Bug
Versions: 1.0-alpha-6
Reporter: Alexandre Poitras
Priority: Minor
The put method of the LightweightHttpWagon class throw an exception whener the
http response code is 201. The 201 code indicate the PUT method has completed
successfully in a WebDav environment.
The problem comes from here :
if ( putConnection.getResponseCode() != HttpURLConnection.HTTP_OK )
{
throw new TransferFailedException(
Unable to transfer file. HttpURLConnection returned the
response code: +
putConnection.getResponseCode() );
}
An exception is thrown whenever the Http code is different from 200 wich is not
good.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-748) Upload request for ldaptemplate
Upload request for ldaptemplate --- Key: MAVENUPLOAD-748 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-748 Project: maven-upload-requests Type: Task Reporter: Alexandre Poitras Attachments: ldaptemplate-1.0-rc1-bundle.jar attached http://sourceforge.net/projects/ldaptemplate/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MECLIPSE-37) eclipse:eclipse should execute in a later phase than generate-sources
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=comments#action_59318 ] Alexandre Poitras commented on MECLIPSE-37: --- I don't like the eclipse:eclipse goal to be automatically linked to a phase, because I can't generate my projets when the source code doesn't compile. How about not giving one by default but give the option to specify it in the plugin configuration section. eclipse:eclipse should execute in a later phase than generate-sources --- Key: MECLIPSE-37 URL: http://jira.codehaus.org/browse/MECLIPSE-37 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.0 Reporter: Mark Donszelmann Assignee: fabrizio giustina the eclipse:eclipse goal should run in a later phase than it currently does (generate-sources) as user defined plugins may add to the compileSourceRoots and testCompileSourceRoots. If it runs later, added paths will be written correctly to the .classpath. Suggested phase is test -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-349) Hibernate 3.1.2 transaction API dependency has a wrong scope
Hibernate 3.1.2 transaction API dependency has a wrong scope Key: MEV-349 URL: http://jira.codehaus.org/browse/MEV-349 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras Hibernate 3.1.2 transaction API dependency (javax.transaction.jta) has no scope defined. It should be provided since it is an official J2EE api and I don't want it to be included in my archive. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRELEASE-81) The site hasn't been republished since October 16th
The site hasn't been republished since October 16th --- Key: MRELEASE-81 URL: http://jira.codehaus.org/browse/MRELEASE-81 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-4 Reporter: Alexandre Poitras Priority: Trivial Fix For: 2.0-beta-3 The site hasn't been republished since October 16th so all the scm url's are wrong. People who want the last version will have a hard time figuring where are the sources. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRELEASE-81) The site hasn't been republished since October 16th
[ http://jira.codehaus.org/browse/MRELEASE-81?page=comments#action_59567 ] Alexandre Poitras commented on MRELEASE-81: --- Forget the fix version, my mistake. The site hasn't been republished since October 16th --- Key: MRELEASE-81 URL: http://jira.codehaus.org/browse/MRELEASE-81 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-4 Reporter: Alexandre Poitras Priority: Trivial Fix For: 2.0-beta-3 The site hasn't been republished since October 16th so all the scm url's are wrong. People who want the last version will have a hard time figuring where are the sources. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSITE-96) SiteMojo generate an unclosed div class=section tag.
SiteMojo generate an unclosed div class=section tag. Key: MSITE-96 URL: http://jira.codehaus.org/browse/MSITE-96 Project: Maven 2.x Site Plugin Type: Bug Reporter: Alexandre Poitras Priority: Minor SiteMojo generate an unclosed div class=section tag. Yann Le Du seems to have located the problem, I'll copy his answer here : I think your problem is with the About page (index.html). This page is generated in maven-site-plugin. In SiteMojo.java [2] , generateIndexPage(), there is indeed a div class=section generated by section1() that is not closed with section1_() . The generated html is not valid xhtml. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-354) Spring-dao has an invalid dependency on jta
Spring-dao has an invalid dependency on jta --- Key: MEV-354 URL: http://jira.codehaus.org/browse/MEV-354 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The jta dependency doesn't have any version so it doesn't get include in the build process : dependency groupIdjavax.transaction/groupId artifactIdjta/artifactId /dependency -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-354) Spring-dao has an invalid dependency on jta
[ http://jira.codehaus.org/browse/MEV-354?page=comments#action_59930 ] Alexandre Poitras commented on MEV-354: --- I would like to submit a patch but for some obscure reasons, I can't connect to the SVN repository. Anyway, the version should be version1.0.1B/version and in my opinion the scope should be provided. Spring-dao has an invalid dependency on jta --- Key: MEV-354 URL: http://jira.codehaus.org/browse/MEV-354 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The jta dependency doesn't have any version so it doesn't get include in the build process : dependency groupIdjavax.transaction/groupId artifactIdjta/artifactId /dependency -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-354) Spring-dao has an invalid dependency on jta
[ http://jira.codehaus.org/browse/MEV-354?page=comments#action_60343 ] Alexandre Poitras commented on MEV-354: --- Weird, it solves the problem when I had the version number. It seems the version number is not herited. I'll try to narrow the problem. Spring-dao has an invalid dependency on jta --- Key: MEV-354 URL: http://jira.codehaus.org/browse/MEV-354 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras Assignee: Carlos Sanchez The jta dependency doesn't have any version so it doesn't get include in the build process : dependency groupIdjavax.transaction/groupId artifactIdjta/artifactId /dependency -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-285) Erase JAXME package since it is now located in org.apache.ws
Erase JAXME package since it is now located in org.apache.ws Key: MEV-285 URL: http://jira.codehaus.org/browse/MEV-285 Project: Maven Evangelism Type: Improvement Components: Invalid POM Reporter: Alexandre Poitras Having jaxme located at the repository root and in the org.apache.ws is confusing. Plus, the pom files in the /jaxme package don't have any dependencies in it, everyone should use the org.apache.ws.jaxme package. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-286) Erase top Spring package since the real ones are in org.springframework
Erase top Spring package since the real ones are in org.springframework --- Key: MEV-286 URL: http://jira.codehaus.org/browse/MEV-286 Project: Maven Evangelism Type: Improvement Components: Invalid POM Reporter: Alexandre Poitras The top spring package is confusing and the poms updated are located in org.springframework package. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-287) Spring beans 1.2.5 jar is corrupted
Spring beans 1.2.5 jar is corrupted --- Key: MEV-287 URL: http://jira.codehaus.org/browse/MEV-287 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras Some headers seem to be corrupted. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-289) Spring-full doesn't have any jars and there is already a Spring artifact.
Spring-full doesn't have any jars and there is already a Spring artifact. - Key: MEV-289 URL: http://jira.codehaus.org/browse/MEV-289 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras Spring-full seems useless because there's already a Spring artifact wich is the complete Spring jar. It should be deleted since it is confusing. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-286) Erase top Spring package since the real ones are in org.springframework
[ http://jira.codehaus.org/browse/MEV-286?page=comments#action_55541 ] Alexandre Poitras commented on MEV-286: --- Cool! What is a relocation pom or is there any documentation on the subject? Erase top Spring package since the real ones are in org.springframework --- Key: MEV-286 URL: http://jira.codehaus.org/browse/MEV-286 Project: Maven Evangelism Type: Improvement Components: Invalid POM Reporter: Alexandre Poitras Assignee: Carlos Sanchez The top spring package is confusing and the poms updated are located in org.springframework package. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-290) Spring beans 1.2.5 jar is corrupted
Spring beans 1.2.5 jar is corrupted --- Key: MEV-290 URL: http://jira.codehaus.org/browse/MEV-290 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras I get a jar bad header error whenever I attempt 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-290) Spring beans 1.2.5 jar is corrupted
[ http://jira.codehaus.org/browse/MEV-290?page=comments#action_1 ] Alexandre Poitras commented on MEV-290: --- Sorry I didn't search before, my bad I taught if it was already reported it would have been fixed by now. I'll search before creating any issues. Spring beans 1.2.5 jar is corrupted --- Key: MEV-290 URL: http://jira.codehaus.org/browse/MEV-290 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras Assignee: Carlos Sanchez I get a jar bad header error whenever I attempt 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-291) Easymock 2.0 isn't present in the repository
[ http://jira.codehaus.org/browse/MEV-291?page=all ] Alexandre Poitras updated MEV-291: -- Attachment: pom.xml Easymock 2.0 isn't present in the repository Key: MEV-291 URL: http://jira.codehaus.org/browse/MEV-291 Project: Maven Evangelism Type: New Feature Components: Missing POM Reporter: Alexandre Poitras Attachments: pom.xml There's a new version of EasyMock. Here's the link : http://prdownloads.sourceforge.net/easymock/easymock2.0.zip I also attached a pom.xml file with this issue. The other easymock libraries groupId value is easymock wich isn't good, so I think this new version should be put in org.easymock -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-291) Easymock 2.0 isn't present in the repository
Easymock 2.0 isn't present in the repository Key: MEV-291 URL: http://jira.codehaus.org/browse/MEV-291 Project: Maven Evangelism Type: New Feature Components: Missing POM Reporter: Alexandre Poitras Attachments: pom.xml There's a new version of EasyMock. Here's the link : http://prdownloads.sourceforge.net/easymock/easymock2.0.zip I also attached a pom.xml file with this issue. The other easymock libraries groupId value is easymock wich isn't good, so I think this new version should be put in org.easymock -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-290) Spring beans 1.2.5 jar is corrupted
[ http://jira.codehaus.org/browse/MEV-290?page=comments#action_55683 ] Alexandre Poitras commented on MEV-290: --- Sorry about that, we had some network issues... Spring beans 1.2.5 jar is corrupted --- Key: MEV-290 URL: http://jira.codehaus.org/browse/MEV-290 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras Assignee: Carlos Sanchez I get a jar bad header error whenever I attempt 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-287) Spring beans 1.2.5 jar is corrupted
[ http://jira.codehaus.org/browse/MEV-287?page=comments#action_55684 ] Alexandre Poitras commented on MEV-287: --- Weird, I tried three times and it didn't work. I was always having a -49 bad jar header or something like that. By the way, I was using the eclipse plugin. I'll try again tomorrow, thank for your effort and sorry for all the troubles! Spring beans 1.2.5 jar is corrupted --- Key: MEV-287 URL: http://jira.codehaus.org/browse/MEV-287 Project: Maven Evangelism Type: Bug Reporter: Alexandre Poitras Assignee: Carlos Sanchez Some headers seem to be corrupted. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVADOC-63) The project name can't have any spaces
The project name can't have any spaces
--
Key: MPJAVADOC-63
URL: http://jira.codehaus.org/browse/MPJAVADOC-63
Project: maven-javadoc-plugin
Type: Bug
Versions: 1.7
Reporter: Alexandre Poitras
If you put space in your project name in your pom.xml file, there is an error
during the javadoc generation.
In my opinion, it looks like the plugin doesn't use string quotes on the
javadoc command line for the doctitle argument, wich default value is
${project.name} ${project.version} API.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1406) Possibility to aggrates sources from other modules
Possibility to aggrates sources from other modules -- Key: MNG-1406 URL: http://jira.codehaus.org/browse/MNG-1406 Project: Maven 2 Type: New Feature Components: maven-assembly-plugin Reporter: Alexandre Poitras It would be nice if it was possible to aggregate the sources of the other sibling modules instead of having to archive different jar files containing the sources. I would like also to be able to do that with Javadoc but I think it's already in the scope of the javadoc 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1406) Possibility to aggrates sources from other modules
[ http://jira.codehaus.org/browse/MNG-1406?page=comments#action_49855 ] Alexandre Poitras commented on MNG-1406: I got a crazy idea but maybe it could be a nice feature. What if every submodule of a pom module could define an archive fragment in their configuration and then running assembly:assembly goal on the parent project would aggregate all this fragments in one archive. It would solve all the issues raised about multiprojects aggregation right now. Just my two cents. Possibility to aggrates sources from other modules -- Key: MNG-1406 URL: http://jira.codehaus.org/browse/MNG-1406 Project: Maven 2 Type: New Feature Components: maven-assembly-plugin Reporter: Alexandre Poitras It would be nice if it was possible to aggregate the sources of the other sibling modules instead of having to archive different jar files containing the sources. I would like also to be able to do that with Javadoc but I think it's already in the scope of the javadoc 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1389) The project name can't have any spaces
[ http://jira.codehaus.org/browse/MNG-1389?page=comments#action_49917 ]
Alexandre Poitras commented on MNG-1389:
Sorry, the problem is not with spaces but with having quotes.
The project name can't have any spaces
--
Key: MNG-1389
URL: http://jira.codehaus.org/browse/MNG-1389
Project: Maven 2
Type: Bug
Reporter: Alexandre Poitras
If you put space in your project name in your pom.xml file, there is an error
during the javadoc generation.
In my opinion, it looks like the plugin doesn't use string quotes on the
javadoc command line for the doctitle argument, wich default value is
${project.name} ${project.version} API.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-171) MyFaces is complete mess
Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MyFaces is complete mess -- Key: MEV-171 URL: http://jira.codehaus.org/browse/MEV-171 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The dependencies should be like that. I don't know how to clean the dependencies for the standalone myfaces composants (jsf-api,jsf-impl, tomahawk, ..). Note that I haven't tested that yet, (I will as soon as I deploy my app). The dependencies added there are based on the informations found on the page http://myfaces.apache.org/gettingstarted.html. dependencies dependency groupIdmyfaces/groupId artifactIdmyfaces/artifactId version1.0.9/version /dependency dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3.0/version /dependency dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.1/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.7/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency dependency groupIdcommons-fileupload/groupId artifactId commons-fileupload/artifactId version1.0/version /dependency dependency groupIdcommons-lang/groupId artifactId commons-lang/artifactId version2.1/version /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency dependency groupIdcommons-validator/groupId artifactIdcommons-validator/artifactId version1.1.4/version /dependency dependency groupIdjakarta-oro/groupId artifactIdjakarta-oro/artifactId version/ /dependency dependency groupIdoro/groupId artifactIdoro/artifactId version2.0.8/version /dependency !-- this one is tricky, it is said to use jsp-2.0.jar from tomcat but I can't find it -- !-- we can use provided as scope here but wouldn't be compatible for those without a J2EE 1.4 container -- dependency groupIdtomcat/groupId artifactIdjsp-api/artifactId version5.0.18/version /dependency dependency groupIdjstl/groupId artifactIdjstl/artifactId version1.1.2/version /dependency dependency groupIdjstl/groupId artifactIdportlet-api/artifactId version1.1.2/version /dependency dependency groupIdservlet-api/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency !-- only for tiles support -- dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.7/version /dependency dependency groupIdtaglibrarydoc/groupId artifactIdtlddoc/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2.3/version /dependency dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymock/artifactId version1.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymockclassextension/artifactId version1.1/version scopetest/scope /dependency dependency groupIdcargo/groupId artifactIdcargo/artifactId version0.6/version scopetest/scope /dependency /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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-171) MyFaces is complete mess
In-Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [ http://jira.codehaus.org/browse/MEV-171?page=comments#action_49943 ] Alexandre Poitras commented on MEV-171: --- Whoops get ride of the first dependecy please : dependency groupIdmyfaces/groupId artifactIdmyfaces/artifactId version1.0.9/version /dependency MyFaces is complete mess -- Key: MEV-171 URL: http://jira.codehaus.org/browse/MEV-171 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The dependencies should be like that. I don't know how to clean the dependencies for the standalone myfaces composants (jsf-api,jsf-impl, tomahawk, ..). Note that I haven't tested that yet, (I will as soon as I deploy my app). The dependencies added there are based on the informations found on the page http://myfaces.apache.org/gettingstarted.html. dependencies dependency groupIdmyfaces/groupId artifactIdmyfaces/artifactId version1.0.9/version /dependency dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3.0/version /dependency dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.1/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.7/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency dependency groupIdcommons-fileupload/groupId artifactId commons-fileupload/artifactId version1.0/version /dependency dependency groupIdcommons-lang/groupId artifactId commons-lang/artifactId version2.1/version /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency dependency groupIdcommons-validator/groupId artifactIdcommons-validator/artifactId version1.1.4/version /dependency dependency groupIdjakarta-oro/groupId artifactIdjakarta-oro/artifactId version/ /dependency dependency groupIdoro/groupId artifactIdoro/artifactId version2.0.8/version /dependency !-- this one is tricky, it is said to use jsp-2.0.jar from tomcat but I can't find it -- !-- we can use provided as scope here but wouldn't be compatible for those without a J2EE 1.4 container -- dependency groupIdtomcat/groupId artifactIdjsp-api/artifactId version5.0.18/version /dependency dependency groupIdjstl/groupId artifactIdjstl/artifactId version1.1.2/version /dependency dependency groupIdjstl/groupId artifactIdportlet-api/artifactId version1.1.2/version /dependency dependency groupIdservlet-api/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency !-- only for tiles support -- dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.7/version /dependency dependency groupIdtaglibrarydoc/groupId artifactIdtlddoc/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2.3/version /dependency dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymock/artifactId version1.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymockclassextension/artifactId version1.1/version scopetest/scope /dependency dependency groupIdcargo/groupId artifactIdcargo/artifactId version0.6/version scopetest/scope /dependency /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
[jira] Commented: (MEV-171) MyFaces is complete mess
In-Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [ http://jira.codehaus.org/browse/MEV-171?page=comments#action_49944 ] Alexandre Poitras commented on MEV-171: --- Would be nice to eliminate the transitive dependencies here but almost impossible until myfaces team or someone else convert their project to maven 2. In the mean times, they are all included in myfaces-all.pom MyFaces is complete mess -- Key: MEV-171 URL: http://jira.codehaus.org/browse/MEV-171 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The dependencies should be like that. I don't know how to clean the dependencies for the standalone myfaces composants (jsf-api,jsf-impl, tomahawk, ..). Note that I haven't tested that yet, (I will as soon as I deploy my app). The dependencies added there are based on the informations found on the page http://myfaces.apache.org/gettingstarted.html. dependencies dependency groupIdmyfaces/groupId artifactIdmyfaces/artifactId version1.0.9/version /dependency dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3.0/version /dependency dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.1/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.7/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency dependency groupIdcommons-fileupload/groupId artifactId commons-fileupload/artifactId version1.0/version /dependency dependency groupIdcommons-lang/groupId artifactId commons-lang/artifactId version2.1/version /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency dependency groupIdcommons-validator/groupId artifactIdcommons-validator/artifactId version1.1.4/version /dependency dependency groupIdjakarta-oro/groupId artifactIdjakarta-oro/artifactId version/ /dependency dependency groupIdoro/groupId artifactIdoro/artifactId version2.0.8/version /dependency !-- this one is tricky, it is said to use jsp-2.0.jar from tomcat but I can't find it -- !-- we can use provided as scope here but wouldn't be compatible for those without a J2EE 1.4 container -- dependency groupIdtomcat/groupId artifactIdjsp-api/artifactId version5.0.18/version /dependency dependency groupIdjstl/groupId artifactIdjstl/artifactId version1.1.2/version /dependency dependency groupIdjstl/groupId artifactIdportlet-api/artifactId version1.1.2/version /dependency dependency groupIdservlet-api/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency !-- only for tiles support -- dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.7/version /dependency dependency groupIdtaglibrarydoc/groupId artifactIdtlddoc/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2.3/version /dependency dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymock/artifactId version1.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymockclassextension/artifactId version1.1/version scopetest/scope /dependency dependency groupIdcargo/groupId artifactIdcargo/artifactId version0.6/version scopetest/scope /dependency /dependencies -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators:
[jira] Commented: (MEV-171) MyFaces is complete mess
In-Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [ http://jira.codehaus.org/browse/MEV-171?page=comments#action_49981 ] Alexandre Poitras commented on MEV-171: --- Delete this entry as well please : dependency groupIdjakarta-oro/groupId artifactIdjakarta-oro/artifactId version/ /dependency MyFaces is complete mess -- Key: MEV-171 URL: http://jira.codehaus.org/browse/MEV-171 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Alexandre Poitras The dependencies should be like that. I don't know how to clean the dependencies for the standalone myfaces composants (jsf-api,jsf-impl, tomahawk, ..). Note that I haven't tested that yet, (I will as soon as I deploy my app). The dependencies added there are based on the informations found on the page http://myfaces.apache.org/gettingstarted.html. dependencies dependency groupIdmyfaces/groupId artifactIdmyfaces/artifactId version1.0.9/version /dependency dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.7.0/version /dependency dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3.0/version /dependency dependency groupIdcommons-collections/groupId artifactIdcommons-collections/artifactId version3.1/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.7/version /dependency dependency groupIdcommons-el/groupId artifactIdcommons-el/artifactId version1.0/version /dependency dependency groupIdcommons-fileupload/groupId artifactId commons-fileupload/artifactId version1.0/version /dependency dependency groupIdcommons-lang/groupId artifactId commons-lang/artifactId version2.1/version /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency dependency groupIdcommons-validator/groupId artifactIdcommons-validator/artifactId version1.1.4/version /dependency dependency groupIdjakarta-oro/groupId artifactIdjakarta-oro/artifactId version/ /dependency dependency groupIdoro/groupId artifactIdoro/artifactId version2.0.8/version /dependency !-- this one is tricky, it is said to use jsp-2.0.jar from tomcat but I can't find it -- !-- we can use provided as scope here but wouldn't be compatible for those without a J2EE 1.4 container -- dependency groupIdtomcat/groupId artifactIdjsp-api/artifactId version5.0.18/version /dependency dependency groupIdjstl/groupId artifactIdjstl/artifactId version1.1.2/version /dependency dependency groupIdjstl/groupId artifactIdportlet-api/artifactId version1.1.2/version /dependency dependency groupIdservlet-api/groupId artifactIdservlet-api/artifactId version2.3/version scopeprovided/scope /dependency !-- only for tiles support -- dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.7/version /dependency dependency groupIdtaglibrarydoc/groupId artifactIdtlddoc/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2.3/version /dependency dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymock/artifactId version1.1/version scopetest/scope /dependency dependency groupIdeasymock/groupId artifactIdeasymockclassextension/artifactId version1.1/version scopetest/scope /dependency dependency groupIdcargo/groupId artifactIdcargo/artifactId version0.6/version scopetest/scope /dependency /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,
[jira] Commented: (MNG-1415) quoted arguments are not being protected
[ http://jira.codehaus.org/browse/MNG-1415?page=comments#action_49988 ] Alexandre Poitras commented on MNG-1415: Seems related to http://jira.codehaus.org/browse/MNG-1389 quoted arguments are not being protected Key: MNG-1415 URL: http://jira.codehaus.org/browse/MNG-1415 Project: Maven 2 Type: Bug Environment: Linux Reporter: Matthew Pocock Priority: Critical Arguments with whitespace protected by quotes are broken up into individual arguments by maven. It's not happening inside the mvn script - I've echoed the generated command-line to check that. This same exception is raised regardless of using... -x=y z -x=\y z\ -x='y z' -x=y z and several other combinations I can't remember. Here's an example failure: [EMAIL PROTECTED]:~/devel/fluxion/trunk/stack/sql-schema$ ~/m2_home/bin/mvn org.codehaus.mojo:maven-execute-plugin:0.1-SNAPSHOT:resources -Dexecute.class=org.comparagrid.fluxion.sql.schema.OWLFromSchema -Dexecute.args=-baseURI=fish -Xdebug + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/nmrp3/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/home/nmrp3/m2_home/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: org.comparagrid.fluxion:sql-schema:jar:0.1-SNAPSHOT [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] maven-execute-plugin: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: null:maven-execute-plugin:maven-plugin:0.1-SNAPSHOT [DEBUG] maven-execute-plugin: using locally installed snapshot [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'debug': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Invalid task 'debug': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1351) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:376) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu Nov 03 23:35:37 GMT 2005 [INFO] Final Memory: 1M/3M [INFO] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1448) Easy way to tell if the plugin is for m2 or m1
Easy way to tell if the plugin is for m2 or m1 -- Key: MNG-1448 URL: http://jira.codehaus.org/browse/MNG-1448 Project: Maven 2 Type: Bug Components: maven-plugins Reporter: Alexandre Poitras -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1448) Easy way to tell if the plugin is for m2 or m1
[ http://jira.codehaus.org/browse/MNG-1448?page=comments#action_50200 ] Alexandre Poitras commented on MNG-1448: Especially on the web site generated by maven. Something like an icon Maven 2.0 would be nice. Easy way to tell if the plugin is for m2 or m1 -- Key: MNG-1448 URL: http://jira.codehaus.org/browse/MNG-1448 Project: Maven 2 Type: Bug Components: maven-plugins Reporter: Alexandre Poitras -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
