[ http://jira.codehaus.org/browse/MNG-851?page=all ]

Brett Porter updated MNG-851:
-----------------------------

    Fix Version: 2.0-beta-2

> Hardcoded pom.xml name in InstallMojo.java
> ------------------------------------------
>
>          Key: MNG-851
>          URL: http://jira.codehaus.org/browse/MNG-851
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugins
>     Versions: 2.0-beta-1
>     Reporter: Guest
>     Priority: Blocker
>      Fix For: 2.0-beta-2

>
>
> Just ran the install lifecycle against a pom with a made-up name but the code 
> eventually looks for a file called pom.xml. Here's the command I ran
> m2 -f testpom.xml install
> and got an exception:
> Caused by: java.io.FileNotFoundException: 
> /Users/developer/projects/java-source-repository/home/pom.xml (No such file 
> or directory)
>         at java.io.FileInputStream.open(Native Method)
>         at java.io.FileInputStream.<init>(FileInputStream.java:106)
>         at java.io.FileReader.<init>(FileReader.java:55)
>         at 
> org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository(ProjectArtifactMetadata.java:82)
> a quick check of the source code reveals a hardcoded reference to pom.xml in 
> InstallMojo.execute line 92 in my version:
>     public void execute()
>         throws MojoExecutionException
>     {
>         // TODO: push into transformation
>         boolean isPomArtifact = "pom".equals( packaging );
>         File pom = new File( basedir, "pom.xml" );
>         if ( !isPomArtifact )
> ...
> Just renamed the file back to pom.xml again and this time the install worked.

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

Reply via email to