You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Guest (JIRA)" <ji...@codehaus.org> on 2005/09/09 01:25:02 UTC
[jira] Created: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
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
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=comments#action_46234 ]
John Casey commented on MNG-851:
--------------------------------
This impacts maven-deploy-plugin, too...will fix in both.
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
John Casey updated MNG-851:
---------------------------
Remaining Estimate: 2 hours
Original Estimate: 7200
adding estimate for hours...will try to use ${project.file} instead of building up new File( ${basedir}, "pom.xml")
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
John Casey reopened MNG-851:
----------------------------
reopening to adjust remaining time.
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 1 hour
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
Brett Porter closed MNG-851:
----------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-2)
2.0-beta-1
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 0 minutes
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
John Casey updated MNG-851:
---------------------------
Remaining Estimate: 0 minutes (was: 1 hour)
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 0 minutes
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
Brett Porter reopened MNG-851:
------------------------------
fixing fix for
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 0 minutes
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
John Casey closed MNG-851:
--------------------------
Resolution: Fixed
fixed remaining time estimate.
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 0 minutes
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-851?page=all ]
John Casey closed MNG-851:
--------------------------
Resolution: Fixed
see it0066
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-2
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining: 1 hour
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-851) Hardcoded pom.xml name in InstallMojo.java
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org