[jira] Updated: (MPASPECTJ-23) Report for the plugin
[ http://jira.codehaus.org/browse/MPASPECTJ-23?page=all ] Shinobu Kawai Yoshida updated MPASPECTJ-23: --- Attachment: MPASPECTJ-23.xdocs.patch > Report for the plugin > - > > Key: MPASPECTJ-23 > URL: http://jira.codehaus.org/browse/MPASPECTJ-23 > Project: maven-aspectj-plugin > Type: Wish > Reporter: Shinobu Kawai Yoshida > Priority: Trivial > Attachments: MPASPECTJ-23.patch, MPASPECTJ-23.xdocs.patch > > > It would be great if there was a report feature to the 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-1956) profile build without pluginManagement fails if pom build has pluginManagement
[ http://jira.codehaus.org/browse/MNG-1956?page=comments#action_55578 ] Shinobu Kawai Yoshida commented on MNG-1956: You can see the exception with "mvn -Denv=dev" > profile build without pluginManagement fails if pom build has pluginManagement > -- > > Key: MNG-1956 > URL: http://jira.codehaus.org/browse/MNG-1956 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0.1 > Reporter: Shinobu Kawai Yoshida > Attachments: pom.xml > > > If the build sections has a pluginManagement, profiles without > pluginManagement fails with the following: > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.project.injection.DefaultProfileInjector.injectPlugins(DefaultProfileInjector.java:147) > at > org.apache.maven.project.injection.DefaultProfileInjector.injectBuild(DefaultProfileInjector.java:134) > at > org.apache.maven.project.injection.DefaultProfileInjector.inject(DefaultProfileInjector.java:80) > at > org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfiles(DefaultMavenProjectBuilder.java:1037) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:838) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:594) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > 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: Wed Jan 11 16:29:00 PST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > > Attached is a sample pom.xml to reproduce. > Workaround is to put an empty in the profile build. -- 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-1956) profile build without pluginManagement fails if pom build has pluginManagement
profile build without pluginManagement fails if pom build has pluginManagement -- Key: MNG-1956 URL: http://jira.codehaus.org/browse/MNG-1956 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.1 Reporter: Shinobu Kawai Yoshida Attachments: pom.xml If the build sections has a pluginManagement, profiles without pluginManagement fails with the following: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.injection.DefaultProfileInjector.injectPlugins(DefaultProfileInjector.java:147) at org.apache.maven.project.injection.DefaultProfileInjector.injectBuild(DefaultProfileInjector.java:134) at org.apache.maven.project.injection.DefaultProfileInjector.inject(DefaultProfileInjector.java:80) at org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfiles(DefaultMavenProjectBuilder.java:1037) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:838) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:594) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) 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: Wed Jan 11 16:29:00 PST 2006 [INFO] Final Memory: 1M/2M [INFO] Attached is a sample pom.xml to reproduce. Workaround is to put an empty in the profile build. -- 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-672) cactus:cactus:13-1.7 relocation to cactus:cactus-13:1.7 incomplete
cactus:cactus:13-1.7 relocation to cactus:cactus-13:1.7 incomplete -- Key: MAVENUPLOAD-672 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-672 Project: maven-upload-requests Type: Bug Reporter: Shinobu Kawai Yoshida Adding cactus:cactus:13-1.7 to dependencies causes the following BUILD ERROR: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] While downloading cactus:cactus:13-1.7 This artifact has been relocated to cactus:cactus-13:1.7. Downloading: http://repo1.maven.org/maven2/cactus/cactus-13/1.7/cactus-13-1.7.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/cactus/cactus-13/1.7/cactus-13-1.7.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file cactus:cactus-13:jar:1.7 from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) com.mycompany.app:my-app:jar:1.0-SNAPSHOT 2) cactus:cactus-13:jar:1.7 -- 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: (MWAR-7) Referenced projects' artifacts naming scheme behaves differently when ran from reactor
[ http://jira.codehaus.org/browse/MWAR-7?page=comments#action_54061 ]
Shinobu Kawai Yoshida commented on MWAR-7:
--
It would be great if the war plugin had a bundleFileName property like the ear
plugin.
> Referenced projects' artifacts naming scheme behaves differently when ran
> from reactor
> --
>
> Key: MWAR-7
> URL: http://jira.codehaus.org/browse/MWAR-7
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: maven-war-plugin versions 2.0-beta-1 and 2.0-beta-2
> Reporter: Cédric Vidal
>
>
> When running mvn install from a war packaged project, the referenced
> projects' artifacts are bundled into the WEB-INF/lib directory with the
> following naming scheme ${groupId}-${artifactId}-${version}.jar, but when
> running mvn install as part of the reactor, the referenced projects'
> artifacts are bundled into the WEB-INF/lib directory with the following
> naming scheme ${pom.build.finalName}.jar
> The naming scheme should be the same in the two situations for the sake of
> consistency, but also to avoid the disturbing (for the end user) situation
> where you end up having the same dependencies present twice with different
> names.
--
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: (MPASPECTJ-23) Report for the plugin
[ http://jira.codehaus.org/browse/MPASPECTJ-23?page=all ] Shinobu Kawai Yoshida updated MPASPECTJ-23: --- Attachment: MPASPECTJ-23.patch > Report for the plugin > - > > Key: MPASPECTJ-23 > URL: http://jira.codehaus.org/browse/MPASPECTJ-23 > Project: maven-aspectj-plugin > Type: Wish > Reporter: Shinobu Kawai Yoshida > Priority: Trivial > Attachments: MPASPECTJ-23.patch > > > It would be great if there was a report feature to the 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] Updated: (MPASPECTJ-24) failonerror support
[ http://jira.codehaus.org/browse/MPASPECTJ-24?page=all ] Shinobu Kawai Yoshida updated MPASPECTJ-24: --- Attachment: MPASPECTJ-24-xdocs.patch > failonerror support > --- > > Key: MPASPECTJ-24 > URL: http://jira.codehaus.org/browse/MPASPECTJ-24 > Project: maven-aspectj-plugin > Type: Wish > Versions: 3.2 > Reporter: Shinobu Kawai Yoshida > Priority: Minor > Fix For: 3.3 > Attachments: MPASPECTJ-24-xdocs.patch, MPASPECTJ-24.patch > > > It would be great if the plugin supported the "failonerror" attribute. > cf. > http://www.eclipse.org/aspectj/doc/released/devguide/antTasks-iajc.html#d0e1506 -- 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: (MPASPECTJ-24) failonerror support
failonerror support --- Key: MPASPECTJ-24 URL: http://jira.codehaus.org/browse/MPASPECTJ-24 Project: maven-aspectj-plugin Type: Wish Versions: 3.2 Reporter: Shinobu Kawai Yoshida Priority: Minor Attachments: MPASPECTJ-24.patch It would be great if the plugin supported the "failonerror" attribute. cf. http://www.eclipse.org/aspectj/doc/released/devguide/antTasks-iajc.html#d0e1506 -- 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: (MPASPECTJ-24) failonerror support
[ http://jira.codehaus.org/browse/MPASPECTJ-24?page=all ] Shinobu Kawai Yoshida updated MPASPECTJ-24: --- Attachment: MPASPECTJ-24.patch patch for failonerror support > failonerror support > --- > > Key: MPASPECTJ-24 > URL: http://jira.codehaus.org/browse/MPASPECTJ-24 > Project: maven-aspectj-plugin > Type: Wish > Versions: 3.2 > Reporter: Shinobu Kawai Yoshida > Priority: Minor > Attachments: MPASPECTJ-24.patch > > > It would be great if the plugin supported the "failonerror" attribute. > cf. > http://www.eclipse.org/aspectj/doc/released/devguide/antTasks-iajc.html#d0e1506 -- 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] Resolved: (MPARTIFACT-63) Cannot deploy artifacts with own ArtifactTypeHandler.
[ http://jira.codehaus.org/browse/MPARTIFACT-63?page=all ] Shinobu Kawai Yoshida resolved MPARTIFACT-63: - Resolution: Fixed Hey, it works! Thanks, Lukas! > Cannot deploy artifacts with own ArtifactTypeHandler. > - > > Key: MPARTIFACT-63 > URL: http://jira.codehaus.org/browse/MPARTIFACT-63 > Project: maven-artifact-plugin > Type: Bug > Versions: 1.7 > Reporter: Shinobu Kawai Yoshida > Priority: Critical > Fix For: 1.7 > Attachments: MPARTIFACT-63.patch > > > As of MPARTIFACT-35, DeployBean#typeHandler became a NamedArtifactTypeHandler > (was ArtifactTypeHandler in 1.6). As a result, any artifact which uses it's > own ArtifactTypeHandler and does not extend NamedArtifactTypeHandler fails. > eg. maven ejb:deploy results in: > BUILD FAILED > File.. C:\Documents and > Settings\shinobu\.maven\cache\maven-artifact-plugin-1.7-SNAPSHOT\plugin.jelly > Element... artifact:artifact-deploy > Line.. 103 > Column 9 > Property 'typeHandler' has no write method > Total time : 2 minutes 7 seconds > Finished at : Monday, December 5, 2005 12:26:38 PM PST -- 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: (MPASPECTJ-22) bootclasspath support
bootclasspath support - Key: MPASPECTJ-22 URL: http://jira.codehaus.org/browse/MPASPECTJ-22 Project: maven-aspectj-plugin Type: Wish Versions: 3.2 Reporter: Shinobu Kawai Yoshida Priority: Minor It would be great if the plugin supported the bootclasspath attribute. cf. http://www.eclipse.org/aspectj/doc/released/devguide/antTasks-iajc.html -- 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: (MPASPECTJ-23) Report for the plugin
Report for the plugin - Key: MPASPECTJ-23 URL: http://jira.codehaus.org/browse/MPASPECTJ-23 Project: maven-aspectj-plugin Type: Wish Reporter: Shinobu Kawai Yoshida Priority: Trivial It would be great if there was a report feature to the 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] Updated: (MPARTIFACT-63) Cannot deploy artifacts with own ArtifactTypeHandler.
[ http://jira.codehaus.org/browse/MPARTIFACT-63?page=all ] Shinobu Kawai Yoshida updated MPARTIFACT-63: Attachment: MPARTIFACT-63.patch A quick fix. > Cannot deploy artifacts with own ArtifactTypeHandler. > - > > Key: MPARTIFACT-63 > URL: http://jira.codehaus.org/browse/MPARTIFACT-63 > Project: maven-artifact-plugin > Type: Bug > Versions: 1.7 > Reporter: Shinobu Kawai Yoshida > Priority: Critical > Fix For: 1.7 > Attachments: MPARTIFACT-63.patch > > > As of MPARTIFACT-35, DeployBean#typeHandler became a NamedArtifactTypeHandler > (was ArtifactTypeHandler in 1.6). As a result, any artifact which uses it's > own ArtifactTypeHandler and does not extend NamedArtifactTypeHandler fails. > eg. maven ejb:deploy results in: > BUILD FAILED > File.. C:\Documents and > Settings\shinobu\.maven\cache\maven-artifact-plugin-1.7-SNAPSHOT\plugin.jelly > Element... artifact:artifact-deploy > Line.. 103 > Column 9 > Property 'typeHandler' has no write method > Total time : 2 minutes 7 seconds > Finished at : Monday, December 5, 2005 12:26:38 PM PST -- 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: (MPARTIFACT-63) Cannot deploy artifacts with own ArtifactTypeHandler.
[ http://jira.codehaus.org/browse/MPARTIFACT-63?page=comments#action_52809 ] Shinobu Kawai Yoshida commented on MPARTIFACT-63: - The actual fix was in MPARTIFACT-57. > Cannot deploy artifacts with own ArtifactTypeHandler. > - > > Key: MPARTIFACT-63 > URL: http://jira.codehaus.org/browse/MPARTIFACT-63 > Project: maven-artifact-plugin > Type: Bug > Versions: 1.7 > Reporter: Shinobu Kawai Yoshida > Priority: Critical > > > As of MPARTIFACT-35, DeployBean#typeHandler became a NamedArtifactTypeHandler > (was ArtifactTypeHandler in 1.6). As a result, any artifact which uses it's > own ArtifactTypeHandler and does not extend NamedArtifactTypeHandler fails. > eg. maven ejb:deploy results in: > BUILD FAILED > File.. C:\Documents and > Settings\shinobu\.maven\cache\maven-artifact-plugin-1.7-SNAPSHOT\plugin.jelly > Element... artifact:artifact-deploy > Line.. 103 > Column 9 > Property 'typeHandler' has no write method > Total time : 2 minutes 7 seconds > Finished at : Monday, December 5, 2005 12:26:38 PM PST -- 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: (MPARTIFACT-63) Cannot deploy artifacts with own ArtifactTypeHandler.
Cannot deploy artifacts with own ArtifactTypeHandler. - Key: MPARTIFACT-63 URL: http://jira.codehaus.org/browse/MPARTIFACT-63 Project: maven-artifact-plugin Type: Bug Versions: 1.7 Reporter: Shinobu Kawai Yoshida Priority: Critical As of MPARTIFACT-35, DeployBean#typeHandler became a NamedArtifactTypeHandler (was ArtifactTypeHandler in 1.6). As a result, any artifact which uses it's own ArtifactTypeHandler and does not extend NamedArtifactTypeHandler fails. eg. maven ejb:deploy results in: BUILD FAILED File.. C:\Documents and Settings\shinobu\.maven\cache\maven-artifact-plugin-1.7-SNAPSHOT\plugin.jelly Element... artifact:artifact-deploy Line.. 103 Column 9 Property 'typeHandler' has no write method Total time : 2 minutes 7 seconds Finished at : Monday, December 5, 2005 12:26:38 PM PST -- 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: (MPARTIFACT-59) allow configuring deploying a timedstamped artifact when using SNAPSHOT in the version
[ http://jira.codehaus.org/browse/MPARTIFACT-59?page=comments#action_52804 ] Shinobu Kawai Yoshida commented on MPARTIFACT-59: - For those of you wondering, it's the "maven.artifact.deploy.timestamps" boolean property. > allow configuring deploying a timedstamped artifact when using SNAPSHOT in > the version > -- > > Key: MPARTIFACT-59 > URL: http://jira.codehaus.org/browse/MPARTIFACT-59 > Project: maven-artifact-plugin > Type: New Feature > Versions: 1.6 > Environment: Maven 1.1b1 > Reporter: Wim Deblauwe > Fix For: 1.7 > > > I just upgraded to 1.1b1 and version 1.6 of the artifact plugin. I see now > that when I do jar:deploy, I get everything double in my repository. > I get for example: > myjar-1.0-SNAPSHOT.jar > myjar-1.0-20050825.075855.jar > I only want the first one. The version defined in my project.xml is > 1.0-SNAPSHOT. > Please make this configurable! > regards, > Wim -- 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: (MPARTIFACT-62) uniqueVersion support for snapshots like m2
uniqueVersion support for snapshots like m2 --- Key: MPARTIFACT-62 URL: http://jira.codehaus.org/browse/MPARTIFACT-62 Project: maven-artifact-plugin Type: Wish Versions: 1.6 Reporter: Shinobu Kawai Yoshida Priority: Trivial It would be great if the M1 plugin also supported a uniqueVersion-like feature. cf. http://maven.apache.org/maven-model/maven.html#class_snapshotRepository -- 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: (CONTINUUM-497) Ability to download from the Working Copy page.
Ability to download from the Working Copy page. --- Key: CONTINUUM-497 URL: http://jira.codehaus.org/browse/CONTINUUM-497 Project: Continuum Type: Wish Components: Web interface Reporter: Shinobu Kawai Yoshida Priority: Trivial It would be great if there was an interface to download a file from the Working Copy page. -- 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: (CONTINUUM-494) Unable to create schedule with year
Unable to create schedule with year --- Key: CONTINUUM-494 URL: http://jira.codehaus.org/browse/CONTINUUM-494 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.1 Reporter: Shinobu Kawai Yoshida The schedule does not allow cron expressions with year. eg. 0 15 10 * * ? 2005 cf. http://www.opensymphony.com/quartz/api/org/quartz/CronTrigger.html -- 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: (CONTINUUM-495) Use quiet notation for Developers
Use quiet notation for Developers - Key: CONTINUUM-495 URL: http://jira.codehaus.org/browse/CONTINUUM-495 Project: Continuum Type: Improvement Components: Web interface Versions: 1.0.1 Environment: maven 2.0 Reporter: Shinobu Kawai Yoshida Priority: Trivial In the Developers list, if the name or email is not set in the pom.xml, it shows "$developer.name" and "$developer.email" instead. It would look better if it showed blank for unset values. ## Maybe we should show the id if the name is not set... cf. http://jakarta.apache.org/velocity/docs/user-guide.html#Quiet%20Reference%20Notation -- 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: (SCM-90) cvsroot doesn't work for cvs 1.10 when using pserver
[ http://jira.codehaus.org/browse/SCM-90?page=comments#action_52370 ] Shinobu Kawai Yoshida commented on SCM-90: -- As a workaround, you can set connection to "scm:cvs:pserver:[EMAIL PROTECTED]:-1:/bar:module", but this causes MOJO-152. :( > cvsroot doesn't work for cvs 1.10 when using pserver > > > Key: SCM-90 > URL: http://jira.codehaus.org/browse/SCM-90 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-beta-1 > Environment: cvs 1.10 > Reporter: Shinobu Kawai Yoshida > Priority: Minor > > > In CvsScmProvider#parseScmUrl when using pserver, the default port 2401 is > forced with the comment "set default port, it's necessary for checking > entries in .cvspass". However, in cvs 1.10, CVSROOT does not support the > port, so it figures that the port number is part of the repository path. > This causes the cvs operation to fail. > For example, if the urlConnection was "scm:cvs:pserver:[EMAIL > PROTECTED]:/bar:module", it will set cvsroot to ":pserver:[EMAIL > PROTECTED]:2401/bar". This works with cvs 1.11, but 1.10 looks for the path > "2401/bar". -- 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: (SCM-90) cvsroot doesn't work for cvs 1.10 when using pserver
cvsroot doesn't work for cvs 1.10 when using pserver Key: SCM-90 URL: http://jira.codehaus.org/browse/SCM-90 Project: Maven SCM Type: Bug Components: maven-scm-provider-cvs Versions: 1.0-beta-1 Environment: cvs 1.10 Reporter: Shinobu Kawai Yoshida Priority: Minor In CvsScmProvider#parseScmUrl when using pserver, the default port 2401 is forced with the comment "set default port, it's necessary for checking entries in .cvspass". However, in cvs 1.10, CVSROOT does not support the port, so it figures that the port number is part of the repository path. This causes the cvs operation to fail. For example, if the urlConnection was "scm:cvs:pserver:[EMAIL PROTECTED]:/bar:module", it will set cvsroot to ":pserver:[EMAIL PROTECTED]:2401/bar". This works with cvs 1.11, but 1.10 looks for the path "2401/bar". -- 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: (CONTINUUM-454) CLONE -build reported as successful on win xp even when maven build fails if continuum is run as a service
[ http://jira.codehaus.org/browse/CONTINUUM-454?page=comments#action_51155 ] Shinobu Kawai Yoshida commented on CONTINUUM-454: - Adding set.MAVEN_TERMINATE_CMD=on to wrapper.conf does the trick. Now, you don't need the run.bat fix anymore. :) > CLONE -build reported as successful on win xp even when maven build fails if > continuum is run as a service > -- > > Key: CONTINUUM-454 > URL: http://jira.codehaus.org/browse/CONTINUUM-454 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: Maven 1.0.2 > Java 1.5 > Win XP SP2 > Continuum 1.0 > Reporter: Shinobu Kawai Yoshida > Assignee: Emmanuel Venisse > Fix For: 1.0.1 > > > Continuum always reports a successful build even when Maven reports a build > failure. -- 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: (CONTINUUM-454) CLONE -build reported as successful on win xp even when maven build fails if continuum is run as a service
[ http://jira.codehaus.org/browse/CONTINUUM-454?page=comments#action_51153 ] Shinobu Kawai Yoshida commented on CONTINUUM-454: - Sorry, I didn't know how to reopen an issue. This is an addition to CONTINUUM-413. The workaround does not work if Continuum is run as a service, because run.bat is not used. > CLONE -build reported as successful on win xp even when maven build fails if > continuum is run as a service > -- > > Key: CONTINUUM-454 > URL: http://jira.codehaus.org/browse/CONTINUUM-454 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: Maven 1.0.2 > Java 1.5 > Win XP SP2 > Continuum 1.0 > Reporter: Shinobu Kawai Yoshida > Assignee: Emmanuel Venisse > Fix For: 1.0.1 > > > Continuum always reports a successful build even when Maven reports a build > failure. -- 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: (CONTINUUM-454) CLONE -build reported as successful on win xp even when maven build fails if continuum is run as a service
CLONE -build reported as successful on win xp even when maven build fails if continuum is run as a service -- Key: CONTINUUM-454 URL: http://jira.codehaus.org/browse/CONTINUUM-454 Project: Continuum Type: Bug Versions: 1.0 Environment: Maven 1.0.2 Java 1.5 Win XP SP2 Continuum 1.0 Reporter: Shinobu Kawai Yoshida Assigned to: Emmanuel Venisse Fix For: 1.0.1 Continuum always reports a successful build even when Maven reports a build failure. -- 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-1513) specifying visibility levels other than package requires setting showPackage to false
specifying visibility levels other than package requires setting showPackage to false - Key: MNG-1513 URL: http://jira.codehaus.org/browse/MNG-1513 Project: Maven 2 Type: Wish Components: maven-javadoc-plugin Versions: 2.0 Reporter: Shinobu Kawai Yoshida Priority: Minor In order to specify a visibility level other than package, you need to explicitly set showPackage to false. Otherwise, javadoc complains that "error - More than one of -public, -private, -package, or -protected specified.". It would be nice if the default was handled in the code instead of the @parameter annotation. -- 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-1510) site-embedded report mode check always returns true
site-embedded report mode check always returns true --- Key: MNG-1510 URL: http://jira.codehaus.org/browse/MNG-1510 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2.0 Reporter: Shinobu Kawai Yoshida o.a.m.p.javadoc.JavadocReport#executeReport Line 685: if ( !javadocDirectory.equals( getOutputDirectory() ) ) javadocDirectory is a File and getOutputDirectory() is a String. This will never return false. -- 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]
