You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mike Taylor (JIRA)" <ji...@codehaus.org> on 2005/10/21 20:11:11 UTC
[jira] Created: (MNG-1271) Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
--------------------------------------------------------------------------------------------------------
Key: MNG-1271
URL: http://jira.codehaus.org/browse/MNG-1271
Project: Maven 2
Type: Improvement
Components: design
Versions: 2.0
Reporter: Mike Taylor
I was installing Maven 2 per the Installation Instructions and after running mvn --version and seeing 2.0 I decided to "try it out" - now realize I am a build/release guy, *not* a java coder so I'm coming from this as a complete newbie.
So, happy that Maven 2 was installed I went over to the working directory for our Maven 1 project and typed "mvn compile" and after a couple minutes of some downloading I get the following:
[ERROR] BUILD ERROR
...
[INFO] Cannot execute mojo: resources. It requires a project, but the build is not using one.
...
[INFO] For more information, run Maven with the -e switch
ok, hmm, I'm thinking "well, I *see* project.xml - what the heck does it want" but I run mvn -e compile to be safe. That spews a nice stack trace (and if I was a java guy it would probably make sense) but still nothing says "hey fool - this is Maven *2* - you need a pom.xml file not that so-last-decade project.xml file!"
anywho - sorry for the long winded report - can you change the INFO message to mention pom.xml?
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1271) Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1271?page=all ]
Brett Porter updated MNG-1271:
------------------------------
Fix Version: 2.0.1
> Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-1271
> URL: http://jira.codehaus.org/browse/MNG-1271
> Project: Maven 2
> Type: Improvement
> Components: design
> Versions: 2.0
> Reporter: Mike Taylor
> Fix For: 2.0.1
>
>
> I was installing Maven 2 per the Installation Instructions and after running mvn --version and seeing 2.0 I decided to "try it out" - now realize I am a build/release guy, *not* a java coder so I'm coming from this as a complete newbie.
> So, happy that Maven 2 was installed I went over to the working directory for our Maven 1 project and typed "mvn compile" and after a couple minutes of some downloading I get the following:
> [ERROR] BUILD ERROR
> ...
> [INFO] Cannot execute mojo: resources. It requires a project, but the build is not using one.
> ...
> [INFO] For more information, run Maven with the -e switch
> ok, hmm, I'm thinking "well, I *see* project.xml - what the heck does it want" but I run mvn -e compile to be safe. That spews a nice stack trace (and if I was a java guy it would probably make sense) but still nothing says "hey fool - this is Maven *2* - you need a pom.xml file not that so-last-decade project.xml file!"
> anywho - sorry for the long winded report - can you change the INFO message to mention pom.xml?
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1271) Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1271?page=all ]
Brett Porter closed MNG-1271:
-----------------------------
Resolution: Fixed
> Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-1271
> URL: http://jira.codehaus.org/browse/MNG-1271
> Project: Maven 2
> Type: Improvement
> Components: design
> Versions: 2.0
> Reporter: Mike Taylor
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1271-maven-core.patch
>
>
> I was installing Maven 2 per the Installation Instructions and after running mvn --version and seeing 2.0 I decided to "try it out" - now realize I am a build/release guy, *not* a java coder so I'm coming from this as a complete newbie.
> So, happy that Maven 2 was installed I went over to the working directory for our Maven 1 project and typed "mvn compile" and after a couple minutes of some downloading I get the following:
> [ERROR] BUILD ERROR
> ...
> [INFO] Cannot execute mojo: resources. It requires a project, but the build is not using one.
> ...
> [INFO] For more information, run Maven with the -e switch
> ok, hmm, I'm thinking "well, I *see* project.xml - what the heck does it want" but I run mvn -e compile to be safe. That spews a nice stack trace (and if I was a java guy it would probably make sense) but still nothing says "hey fool - this is Maven *2* - you need a pom.xml file not that so-last-decade project.xml file!"
> anywho - sorry for the long winded report - can you change the INFO message to mention pom.xml?
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1271) Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1271?page=all ]
Edwin Punzalan updated MNG-1271:
--------------------------------
Attachment: MNG-1271-maven-core.patch
Attached patch should output:
Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.
> Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-1271
> URL: http://jira.codehaus.org/browse/MNG-1271
> Project: Maven 2
> Type: Improvement
> Components: design
> Versions: 2.0
> Reporter: Mike Taylor
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1271-maven-core.patch
>
>
> I was installing Maven 2 per the Installation Instructions and after running mvn --version and seeing 2.0 I decided to "try it out" - now realize I am a build/release guy, *not* a java coder so I'm coming from this as a complete newbie.
> So, happy that Maven 2 was installed I went over to the working directory for our Maven 1 project and typed "mvn compile" and after a couple minutes of some downloading I get the following:
> [ERROR] BUILD ERROR
> ...
> [INFO] Cannot execute mojo: resources. It requires a project, but the build is not using one.
> ...
> [INFO] For more information, run Maven with the -e switch
> ok, hmm, I'm thinking "well, I *see* project.xml - what the heck does it want" but I run mvn -e compile to be safe. That spews a nice stack trace (and if I was a java guy it would probably make sense) but still nothing says "hey fool - this is Maven *2* - you need a pom.xml file not that so-last-decade project.xml file!"
> anywho - sorry for the long winded report - can you change the INFO message to mention pom.xml?
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org