RE: [m201] Plugin Dependency Configuration
Dear, the version of plugin should be written out. thanks. Tel: (020)36315358-328 Fax: (020)36315170 Allison, Bob [EMAIL PROTECTED]To: Maven Users List users@maven.apache.org west.comcc: Subject: RE: [m201] Plugin Dependency Configuration 09/01/2006 17:39 Please respond to Maven Users List Anybody have any idea what I am doing wrong? -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 06:52 To: Maven Users List Subject: [m201] Plugin Dependency Configuration I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ Hactl..Moving forward with you. Best Air Cargo Terminal - Asia 2005 Air Cargo Terminal of the Year 2002, 2003 2004 Web: http://www.hactl.com DISCLAIMER :- The information contained in this message, including any attachment, is confidential and may also be privileged. The information is intended only for the person or entity to which it is addressed. Any review, re-transmission, copying, storage, distribution or other use or disclosure of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please contact the sender immediately by return email and delete this message from your system. Thank you. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m201] Plugin Dependency Configuration
Yes. That does work. For anyone following this thread, using Brett's suggestion involves duplicating the plugin stanza from the reporting stanza so it is under buildplugins; after copying the XML, remove the configuration section from the copy in buildplugins and the dependencies section from the copy in reporting. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 16:37 To: Maven Users List Subject: Re: [m201] Plugin Dependency Configuration We should also allow them in the reporting section I imagine, for consistency. I will file it in JIRA. However, it should still take effect if you put a plugin definition in your build section with the dependencies and the rest remains in the reporting section. - Brett On 1/9/06, Kees de Kooter [EMAIL PROTECTED] wrote: According to the maven xsd dependencies are not allowed inside reporting/plugins/plugin tags. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m201] Plugin Dependency Configuration
Anybody have any idea what I am doing wrong? -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 06:52 To: Maven Users List Subject: [m201] Plugin Dependency Configuration I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m201] Plugin Dependency Configuration
On 1/9/06, Allison, Bob [EMAIL PROTECTED] wrote: Anybody have any idea what I am doing wrong? Could you please post your pom? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m201] Plugin Dependency Configuration
?xml version=1.0 encoding=ISO-8859-1? project modelVersion4.0.0/modelVersion groupIdqaccess/groupId artifactIdtoplevel/artifactId packagingpom/packaging nameBob's Maven 2.0 Experiment/name version3.0-SNAPSHOT/version urlhttp://qadev-home.dev.qintra.com//url issueManagement systemMantis/system urlhttp://qadev-home.dev.qintra.com/mantis/url /issueManagement ciManagement systemcontinuum/system notifiers notifier typemail/type address[EMAIL PROTECTED]/address /notifier /notifiers /ciManagement inceptionYear2004/inceptionYear developers developer idallisord/id nameBob Allison/name email[EMAIL PROTECTED]/email organizationQwest/organization roles roleDeveloper/role /roles timezone-5/timezone /developer /developers contributors /contributors licenses license nameQwest Proprietary/name urlhttp://qadev-home.dev.qintra.com/m2/LICENSE.txt/url distributionmanual/distribution /license /licenses scm connectionscm:svn:file:///svn/qaccess/trunk/connection developerConnectionscm:svn:file:///svn/qaccess/trunk/developerConnect ion /scm organization nameQwest/name urlhttp://www.qwest.com//url /organization build defaultGoaltest/defaultGoal pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.4/source target1.4/target /configuration /plugin /plugins /pluginManagement /build dependencies /dependencies reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdqaccess/groupId artifactIdbuild-tools/artifactId version3.0-SNAPSHOT/version /dependency /dependencies configuration configLocationstyle/Q.Access.xml/configLocation headerLocationLICENSE.txt/headerLocation /configuration /plugin /plugins /reporting /project -Original Message- From: Kees de Kooter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 05:24 To: Maven Users List Subject: Re: [m201] Plugin Dependency Configuration On 1/9/06, Allison, Bob [EMAIL PROTECTED] wrote: Anybody have any idea what I am doing wrong? Could you please post your pom? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m201] Plugin Dependency Configuration
Bob, What I can see from your pom.xml, is that you included the dependency in the report section, of which the outline is added below, and there are no dependencies given... Mylene reporting excludeDefaults/ outputDirectory/ plugins plugin groupId/ artifactId/ version/ inherited/ configuration/ reportSets reportSet id/ configuration/ inherited/ reports/ /reportSet /reportSets /plugin /plugins /reporting On 1/9/06, Allison, Bob [EMAIL PROTECTED] wrote: ?xml version=1.0 encoding=ISO-8859-1? project (...) reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdqaccess/groupId artifactIdbuild-tools/artifactId version3.0-SNAPSHOT/version /dependency /dependencies configuration configLocationstyle/Q.Access.xml/configLocation headerLocationLICENSE.txt/headerLocation /configuration /plugin /plugins /reporting /project -Original Message- From: Kees de Kooter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 05:24 To: Maven Users List Subject: Re: [m201] Plugin Dependency Configuration On 1/9/06, Allison, Bob [EMAIL PROTECTED] wrote: Anybody have any idea what I am doing wrong? Could you please post your pom? -- Mylene Books just wanna be FREE! See what I mean at: http://bookcrossing.com/friend/mylene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m201] Plugin Dependency Configuration
According to the maven xsd dependencies are not allowed inside reporting/plugins/plugin tags. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m201] Plugin Dependency Configuration
We should also allow them in the reporting section I imagine, for consistency. I will file it in JIRA. However, it should still take effect if you put a plugin definition in your build section with the dependencies and the rest remains in the reporting section. - Brett On 1/9/06, Kees de Kooter [EMAIL PROTECTED] wrote: According to the maven xsd dependencies are not allowed inside reporting/plugins/plugin tags. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m201] Plugin Dependency Configuration
I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
