[jira] Created: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
Container dependency jar file get copied during the deployment or during hte installation1 -- Key: MDEP-112 URL: http://jira.codehaus.org/browse/MDEP-112 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: copy-dependencies Affects Versions: 2.0 Environment: WindowXP(CYGWIN) JDK 1.5.0_07 Reporter: Alan Mehio Assignee: Brian Fox Priority: Trivial The dependency get copied even it is provided by the container This happens in the following scenario : module A has dependecies as below axis axis-schema 1.3 axis axis-wsdl4j 1.3 xml-apis xml-apis 1.0.b2 javax.xml jaxrpc-api 1.1 commons-discovery commons-discovery 0.2 axis axis-saaj 1.2 you have module B which has the below dependencies mygroup common 1.0.0 mygroup service 1.0.0 mygroup model 1.0.0 tomcat servlet-api 5.0.18 provided The one which get copied is servlet-api-2.3.jar On the otherhand, the other project is using the same dependency ( servlet-api ) but the only difference is the axis artifact and its dependencies are not included Regards, Alan Mehio London, UK -- 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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[
http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107783
]
Alan Mehio commented on MDEP-112:
-
Brian,
Many thanks for your reply. Sorry for my brief description. the servlet-api get
copied into the ${TOMCAT_HOME}/webapps/myweb/WEB-INF/lib
even it is stated that the dependency is provided by the container (Tomcat web
container).
I am wondering why should the servlet-api get copied into the above mentioned
directory even it is supplied by the container. I have checked my other pom and
there is no mention for servlet-api dependency except in the above mentioned
module.
As I understand from the provided, it will not be copied since
the artifact will be provided by the container.
Many thanks
Regards,
Alan Mehio
London, UK
> Container dependency jar file get copied during the deployment or during hte
> installation1
> --
>
> Key: MDEP-112
> URL: http://jira.codehaus.org/browse/MDEP-112
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 2.0
> Environment: WindowXP(CYGWIN) JDK 1.5.0_07
>Reporter: Alan Mehio
>Assignee: Brian Fox
>Priority: Trivial
>
> The dependency get copied even it is provided by the container
> This happens in the following scenario :
> module A has dependecies as below
>
>
> axis
> axis-schema
> 1.3
>
>
> axis
> axis-wsdl4j
> 1.3
>
>
> xml-apis
> xml-apis
> 1.0.b2
>
>
> javax.xml
> jaxrpc-api
> 1.1
>
>
> commons-discovery
> commons-discovery
> 0.2
>
>
> axis
> axis-saaj
> 1.2
>
>
> you have module B which has the below dependencies
>
>
> mygroup
> common
> 1.0.0
>
>
> mygroup
> service
> 1.0.0
>
>
> mygroup
> model
> 1.0.0
>
>
> tomcat
> servlet-api
> 5.0.18
> provided
>
>
> The one which get copied is servlet-api-2.3.jar
> On the otherhand, the other project is using the same dependency (
> servlet-api ) but the only difference is the axis artifact and its
> dependencies are not included
> Regards,
> Alan Mehio
> London, UK
--
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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[ http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107826 ] Alan Mehio commented on MDEP-112: - Brian, Idealy maven dependency should not copy the servlet-api since the container provide it maven is copying the one which struts depends on please see the pom below The one which get copied into my web application lib directory is a subset of the one which is supplied by the container Manen dependency plugin should look at the jar content and prevent duplication of the same classes http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 mygroupId mygroupId-parent 1 mygroupId groupmarketrisk 1.0.0 mygroup http://maven.apache.org pom common model dao service web commons-logging commons-logging 1.0.4 commons-lang commons-lang 2.0 commons-beanutils commons-beanutils 1.6 org.hibernate hibernate 3.0.3 org.springframework spring 1.2 tomcat servlet-api 5.0.18 provided struts struts 1.2.4 dbunit dbunit 2.1 test maven-compiler-plugin 1.5 1.5 Regards, Alan Mehio London, UK > Container dependency jar file get copied during the deployment or during hte > installation1 > -- > > Key: MDEP-112 > URL: http://jira.codehaus.org/browse/MDEP-112 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 > Environment: WindowXP(CYGWIN) JDK 1.5.0_07 >Reporter: Alan Mehio >Assignee: Brian Fox >Priority: Trivial > > The dependency get copied even it is provided by the container > This happens in the following scenario : > module A has dependecies as below > > > axis > axis-schema > 1.3 > > > axis > axis-wsdl4j > 1.3 > > > xml-apis > xml-apis > 1.0.b2 > > > javax.xml > jaxrpc-api > 1.1 > > > commons-discovery > commons-discovery > 0.2 > > > axis > axis-saaj > 1.2 > > > you have module B which has the below dependencies > > > mygroup > common > 1.0.0 > > > mygroup > service > 1.0.0 > > > mygroup > model > 1.0.0 > > > tomcat > servlet-api > 5.0.18 > provided > > > The one which get copied is servlet-api-2.3.jar > On the otherhand, the
[jira] Commented: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[ http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107896 ] Alan Mehio commented on MDEP-112: - Brian, thanks again. Yes I am not running mvn dependency:copy-dependencies from the command line. I am using the war plugin functionality. I totally agree with you concerning the below statement The dependency plugin only does what you ask of it and analyzing the contents of the jars is outside the scope. I will close this issue Regards, Alan Mehio London UK > Container dependency jar file get copied during the deployment or during hte > installation1 > -- > > Key: MDEP-112 > URL: http://jira.codehaus.org/browse/MDEP-112 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 > Environment: WindowXP(CYGWIN) JDK 1.5.0_07 >Reporter: Alan Mehio >Assignee: Brian Fox >Priority: Trivial > > The dependency get copied even it is provided by the container > This happens in the following scenario : > module A has dependecies as below > > > axis > axis-schema > 1.3 > > > axis > axis-wsdl4j > 1.3 > > > xml-apis > xml-apis > 1.0.b2 > > > javax.xml > jaxrpc-api > 1.1 > > > commons-discovery > commons-discovery > 0.2 > > > axis > axis-saaj > 1.2 > > > you have module B which has the below dependencies > > > mygroup > common > 1.0.0 > > > mygroup > service > 1.0.0 > > > mygroup > model > 1.0.0 > > > tomcat > servlet-api > 5.0.18 > provided > > > The one which get copied is servlet-api-2.3.jar > On the otherhand, the other project is using the same dependency ( > servlet-api ) but the only difference is the axis artifact and its > dependencies are not included > Regards, > Alan Mehio > London, UK -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[ http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Mehio closed MDEP-112. --- Resolution: Fixed Fix Version/s: 2.0 The dependency plugin does not make jar analysis. > Container dependency jar file get copied during the deployment or during hte > installation1 > -- > > Key: MDEP-112 > URL: http://jira.codehaus.org/browse/MDEP-112 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 > Environment: WindowXP(CYGWIN) JDK 1.5.0_07 >Reporter: Alan Mehio >Assignee: Brian Fox >Priority: Trivial > Fix For: 2.0 > > > The dependency get copied even it is provided by the container > This happens in the following scenario : > module A has dependecies as below > > > axis > axis-schema > 1.3 > > > axis > axis-wsdl4j > 1.3 > > > xml-apis > xml-apis > 1.0.b2 > > > javax.xml > jaxrpc-api > 1.1 > > > commons-discovery > commons-discovery > 0.2 > > > axis > axis-saaj > 1.2 > > > you have module B which has the below dependencies > > > mygroup > common > 1.0.0 > > > mygroup > service > 1.0.0 > > > mygroup > model > 1.0.0 > > > tomcat > servlet-api > 5.0.18 > provided > > > The one which get copied is servlet-api-2.3.jar > On the otherhand, the other project is using the same dependency ( > servlet-api ) but the only difference is the axis artifact and its > dependencies are not included > Regards, > Alan Mehio > London, UK -- 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: (MANTRUN-58) Update depencies to include all ant artifacts so all ant tasks can be used
[ http://jira.codehaus.org/browse/MANTRUN-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107927 ] Alan Mehio commented on MANTRUN-58: --- I had some issue with the dependecy of the following tasks which get executed from mavenantrun plugin the tasks are telnet ftp the dependency are : ant-commons-net commons-net I have checked the plugin class path ( printed out) and found the above dependency are not included. the plug in should bring its dependencies and know about its dependencies. I would say; manvenantrun plugin should include all the depdencies needed to run ant task or at least it should be documented in the examples at http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html The solution is to explicitly mention the dependency as below which needs to be documented. I found it after opening the source code and analysing the whole code of the manvenantrun plugin which took me some time. org.apache.maven.plugins maven-antrun-plugin commons-net commons-net 1.4.1 ant ant-commons-net 1.6.5 pricingDeployment pricingDeployment run Regards, Alan Mehio London, UK > Update depencies to include all ant artifacts so all ant tasks can be used > -- > > Key: MANTRUN-58 > URL: http://jira.codehaus.org/browse/MANTRUN-58 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Reporter: Jason Chaffee >Priority: Blocker > > Should add ALL ant distribution artifacts as dependencies as some tasks > cannot be run without them. For example, ant-trax is needed to use > with the trax processor. -- 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: (MANTRUN-75) tasks if or unless does not work properly
tasks if or unless does not work properly -- Key: MANTRUN-75 URL: http://jira.codehaus.org/browse/MANTRUN-75 Project: Maven 2.x Antrun Plugin Issue Type: Bug Environment: Win XP ( CYGWIN) JDK 1.5 update 7 Reporter: Alan Mehio the below does not work from the example at http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html The complete POM file ; please see below http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://vmaven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 mygr myartifact pom 1.1.0 myartifact http://maven.apache.org junit junit 3.8.1 test org.apache.maven.plugins maven-compiler-plugin 1.5 1.5 org.apache.maven.plugins maven-jar-plugin true ./ org.apache.maven.plugins maven-antrun-plugin commons-net commons-net 1.4.1 ant ant-commons-net 1.6.5 install install run the command I run is mvn clean install -Dmaven.test.skip=true it did not skip the "tasks" and it always go through the tasks I use the "if" attribute and it does not do any check for the property; it passes the validation eventhougth the property is not set it passes the check (if condition) event the property "maven.project.alan.mehio.does.not.exit" does not exist Regards, Alan Mehio London, UK -- 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: (WAGONFTP-17) Null pointer at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:130)
[ http://jira.codehaus.org/browse/WAGONFTP-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98622 ] Alan Mehio commented on WAGONFTP-17: I totally agree with Carlos Sanchez, if the server id does not match or if there is a username or password error, the method shoud through AuthenticationException. Regards, Alan Mehio London, UK > Null pointer at > org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:130) > --- > > Key: WAGONFTP-17 > URL: http://jira.codehaus.org/browse/WAGONFTP-17 > Project: wagon-ftp > Issue Type: Bug >Affects Versions: 1.0-alpha-6 > Environment: Windows XP, java 1.5 , maven 2.0.6 >Reporter: Rahul Khot >Assignee: Carlos Sanchez > Fix For: 1.0 > > > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' --> > [DEBUG] (f) artifact = abc-plugins:abc-plugin:maven-plugin:1.0.0.0 > [DEBUG] (f) attachedArtifacts = [] > [DEBUG] (f) deploymentRepository = [helixasptest] -> > ftp://abc.com/public_html > [DEBUG] (s) localRepository = [local] -> file://C:\Documents and > Settings\user\.m2\repository > [DEBUG] (f) packaging = maven-plugin > [DEBUG] (f) pomFile = C:\Documents and > Settings\user\workspace\abc\abc-plugins\abc-plugin\pom.xml > [DEBUG] (f) updateReleaseInfo = false > [DEBUG] -- end configuration -- > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [DEBUG] Trace > java.lang.NullPointerException -- 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] (MNG-5501) Prerequisites don't work against Maven-3.1.0
[
https://jira.codehaus.org/browse/MNG-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349190#comment-349190
]
Alan Mehio edited comment on MNG-5501 at 7/5/14 4:21 AM:
-
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
Regards,
Alan Mehio
London,UK
was (Author: alanmehio):
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
> Prerequisites don't work against Maven-3.1.0
>
>
> Key: MNG-5501
> URL: https://jira.codehaus.org/browse/MNG-5501
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4, 3.0.5, 3.1.0
>Reporter: Michael Semb Wever
>
> adding
> {code}3.1.0{code}
> does not stop the project from being built with mvn-3.0.4 or mvn-3.0.5
> Is Prerequisites suppose to work or not?
> Because there is no sign of it being deprecated throughout the documentation.
> (I don't want to use the enforcer plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5501) Prerequisites don't work against Maven-3.1.0
[
https://jira.codehaus.org/browse/MNG-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349190#comment-349190
]
Alan Mehio commented on MNG-5501:
-
As per maven pom specification from
http://maven.apache.org/pom.html#Prerequisites
it states the following:
"The POM may have certain prerequisites in order to execute correctly. For
example, perhaps there was a fix in Maven 2.0.3 that you need in order to
deploy using sftp. Here is where you give the prerequisites to building. If
these are not met, Maven will fail the build before even starting. The only
element that exists as a prerequisite in POM 4.0 is the maven element, which
takes a minimum version number."
It is still not working on maven 3.2.2 for invoking appengine-maven-plugin
which states the below in its pom
3.1.0
> Prerequisites don't work against Maven-3.1.0
>
>
> Key: MNG-5501
> URL: https://jira.codehaus.org/browse/MNG-5501
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0.4, 3.0.5, 3.1.0
>Reporter: Michael Semb Wever
>
> adding
> {code}3.1.0{code}
> does not stop the project from being built with mvn-3.0.4 or mvn-3.0.5
> Is Prerequisites suppose to work or not?
> Because there is no sign of it being deprecated throughout the documentation.
> (I don't want to use the enforcer plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
Alan Mehio created MNG-5660: --- Summary: prerequisites element in pom does not work on maven 3.2.2 Key: MNG-5660 URL: https://jira.codehaus.org/browse/MNG-5660 Project: Maven Issue Type: Bug Components: Command Line, Errors Affects Versions: 3.2.2 Environment: java 1.7 Reporter: Alan Mehio Priority: Minor Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on project guestbook: The plugin com.google .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> It should work on a min version of 3.1.0 and not exact same version as explained in maven pom specification below: http://maven.apache.org/pom.html#Prerequisites "The POM may have certain prerequisites in order to execute correctly. For example, perhaps there was a fix in Maven 2.0.3 that you need in order to deploy using sftp. Here is where you give the prerequisites to building. If these are not met, Maven will fail the build before even starting. The only element that exists as a prerequisite in POM 4.0 is the maven element, which takes a minimum version number." look at the project https://code.google.com/p/appengine-maven-plugin/ and its usage https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code and the command line which cause the issue "mvn appengine:devserver" error message : Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on project guestbook: The plugin com.google .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help 1] the pom file from the google app engine maven plugin 3.1.0 . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
[ https://jira.codehaus.org/browse/MNG-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349206#comment-349206 ] Alan Mehio commented on MNG-5660: - Jason, Please close the issue. I have tested it using maven 3.2.2 and it works fine now The maven specification and the implementation matches. Please close this issue and mark it as invalid > prerequisites element in pom does not work on maven 3.2.2 > - > > Key: MNG-5660 > URL: https://jira.codehaus.org/browse/MNG-5660 > Project: Maven > Issue Type: Bug > Components: Command Line, Errors >Affects Versions: 3.2.2 > Environment: java 1.7 >Reporter: Alan Mehio >Priority: Minor > Fix For: 3.2.x > > > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> > It should work on a min version of 3.1.0 and not exact same version as > explained in maven pom specification below: > http://maven.apache.org/pom.html#Prerequisites > "The POM may have certain prerequisites in order to execute correctly. For > example, perhaps there was a fix in Maven 2.0.3 that you need in order to > deploy using sftp. Here is where you give the prerequisites to building. If > these are not met, Maven will fail the build before even starting. The only > element that exists as a prerequisite in POM 4.0 is the maven element, which > takes a minimum version number." > look at the project > https://code.google.com/p/appengine-maven-plugin/ > and its usage > https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code > and the command line which cause the issue > "mvn appengine:devserver" > error message : > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help > 1] > the pom file from the google app engine maven plugin > > > 3.1.0 > > . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
[ https://jira.codehaus.org/browse/MNG-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349206#comment-349206 ] Alan Mehio edited comment on MNG-5660 at 7/6/14 10:52 AM: -- Jason, I have tested it using maven 3.2.2 and it works fine now The maven specification and the implementation matches. I will close this issue now. Cheers Alan Mehio was (Author: alanmehio): Jason, Please close the issue. I have tested it using maven 3.2.2 and it works fine now The maven specification and the implementation matches. Please close this issue and mark it as invalid > prerequisites element in pom does not work on maven 3.2.2 > - > > Key: MNG-5660 > URL: https://jira.codehaus.org/browse/MNG-5660 > Project: Maven > Issue Type: Bug > Components: Command Line, Errors >Affects Versions: 3.2.2 > Environment: java 1.7 >Reporter: Alan Mehio >Priority: Minor > Fix For: 3.2.x > > > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> > It should work on a min version of 3.1.0 and not exact same version as > explained in maven pom specification below: > http://maven.apache.org/pom.html#Prerequisites > "The POM may have certain prerequisites in order to execute correctly. For > example, perhaps there was a fix in Maven 2.0.3 that you need in order to > deploy using sftp. Here is where you give the prerequisites to building. If > these are not met, Maven will fail the build before even starting. The only > element that exists as a prerequisite in POM 4.0 is the maven element, which > takes a minimum version number." > look at the project > https://code.google.com/p/appengine-maven-plugin/ > and its usage > https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code > and the command line which cause the issue > "mvn appengine:devserver" > error message : > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help > 1] > the pom file from the google app engine maven plugin > > > 3.1.0 > > . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5660) prerequisites element in pom does not work on maven 3.2.2
[ https://jira.codehaus.org/browse/MNG-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Mehio closed MNG-5660. --- Resolution: Not A Bug Fix Version/s: 3.2.x It works fine after testing the google app Engine maven plugin with maven 3.2.2 > prerequisites element in pom does not work on maven 3.2.2 > - > > Key: MNG-5660 > URL: https://jira.codehaus.org/browse/MNG-5660 > Project: Maven > Issue Type: Bug > Components: Command Line, Errors >Affects Versions: 3.2.2 > Environment: java 1.7 >Reporter: Alan Mehio >Priority: Minor > Fix For: 3.2.x > > > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> > It should work on a min version of 3.1.0 and not exact same version as > explained in maven pom specification below: > http://maven.apache.org/pom.html#Prerequisites > "The POM may have certain prerequisites in order to execute correctly. For > example, perhaps there was a fix in Maven 2.0.3 that you need in order to > deploy using sftp. Here is where you give the prerequisites to building. If > these are not met, Maven will fail the build before even starting. The only > element that exists as a prerequisite in POM 4.0 is the maven element, which > takes a minimum version number." > look at the project > https://code.google.com/p/appengine-maven-plugin/ > and its usage > https://developers.google.com/appengine/docs/java/gettingstarted/ui_and_code > and the command line which cause the issue > "mvn appengine:devserver" > error message : > Failed to execute goal > com.google.appengine:appengine-maven-plugin:1.9.6:devserver (default-cli) on > project guestbook: The plugin com.google > .appengine:appengine-maven-plugin:1.9.6 requires Maven version 3.1.0 -> [Help > 1] > the pom file from the google app engine maven plugin > > > 3.1.0 > > . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
