Re: [result] [vote] Shinobu Kawai as Maven Plugins committer

Thanks, everybody! I'll see what I can do to improve the plugins and the community. :) On 8/3/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: 5x +1 Welcome Shinobu! -Lukas Best regards, -- Shinobu -- Shinobu Kawai <[E

[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 >

[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 plu

[jira] Created: (MNG-1956) profile build without pluginManagement fails if pom build has pluginManagement

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

[jira] Created: (MAVENUPLOAD-672) cactus:cactus:13-1.7 relocation to cactus:cactus-13:1.7 incomplete

: 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

[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 namin

[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 >

[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 >

[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

[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:

[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 ArtifactTypeHand

[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

[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

[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 ArtifactTypeHand

[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 ArtifactTypeHand

[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

[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. >

[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

[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

[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

[jira] Created: (CONTINUUM-495) Use quiet notation for Developers

: 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 na

[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 cause

[jira] Created: (SCM-90) cvsroot doesn't work for cvs 1.10 when using pserver

eta-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

[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 an

[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 doe

[jira] Created: (CONTINUUM-454) CLONE -build reported as successful on win xp even when maven build fails if continuum is run as a service

/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

[jira] Created: (MNG-1513) specifying visibility levels other than package requires setting showPackage to false

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, -pr

[jira] Created: (MNG-1510) site-embedded report mode check always returns true

: 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

Re: Who's maintaining the Velocity repository?

Hi Brett, > I'll leave the Velocity team to answer, please don't cross post. > > SNAPSHOTs are not generally published to Ibiblio by ASF projects - they > are published to http://cvs.apache.org/repository OK, thanks. Sorry for the cross post. Best regards, -- Shinobu --

Who's maintaining the Velocity repository?

NAPSHOT I don't know how recent the SNAPSHOT's are, but it would be great if we could get the latest for all artifacts up there. :) Best regards, -- Shinobu -- Shinobu Kawai <[EMAIL PROTECTED]> - To unsubscribe

Re: Wrong links to jira at maven site

aus.org/browse/MAVEN-1471 > > > > Maybe this itself needs to go to jira. ;) And here it is: http://jira.codehaus.org/browse/MPCHANGES-21 Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED]> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wrong links to jira at maven site

maven.changes.issue.template=%URL%/browse/%ISSUE% changes:report Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED]> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wrong links to jira at maven site

ably changing maven-plugins/changes/plugin.properties maven.changes.issue.template = %URL%/%ISSUE% to maven.changes.issue.template = %URL%/browse/%ISSUE% should do the trick. (Just guessing.) Best regards, -- Shinobu Kawai -- Shin

[ANN] maven-doccheck-plugin 1.4-0.1

0.1 For a manual installation, you can download the plugin here: http://maven-doccheck.sourceforge.net/maven/doccheck/plugins/maven-doccheck-plugin-1.4-0.1.jar Have fun! -The Maven-DocCheck team -- Shinobu Kawai <[EMAIL PROTECTED]>

Re: Debugging Maven

nd whatever options that are needed. Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED], [EMAIL PROTECTED]> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

proprietary jars in ibiblio : Javadoc API

hread, but here I would like to ask another question. (Not that I talked to their lawyers...) Shouldn't license issues be checked before things are uploaded to ibiblio? (I mean, the last thing we'd want to do is put an archive licensed to SCO up there without permission. :) Best regards, -