You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/04/11 02:28:48 UTC
[jira] Created: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
javadoc:javadoc needs access to generated sources
-------------------------------------------------
Key: MJAVADOC-62
URL: http://jira.codehaus.org/browse/MJAVADOC-62
Project: Maven 2.x Javadoc Plugin
Type: Bug
Versions: 2.0
Reporter: John Casey
Priority: Blocker
Fix For: 2.0
currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
However, when I changed the report to have:
@execute phase="generate-sources"
It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=comments#action_63270 ]
John Casey commented on MJAVADOC-62:
------------------------------------
steps to reproduce:
1. go into maven-model
2. `mvn clean site`
3. open ${basedir}target/site/apidocs/index.html in your browser.
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.0
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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] Updated: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Brett Porter updated MJAVADOC-62:
---------------------------------
Attachment: MJAVADOC-62.diff
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.0
> Attachments: MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Vincent Siveton closed MJAVADOC-62.
-----------------------------------
Assignee: Vincent Siveton (was: Brett Porter)
Resolution: Fixed
Fix Version/s: 2.1
Already fixed (with MJAVADOC-61)
Tested with maven-model and rev 441291 for the plugin
#mvn clean javadoc:javadoc
#mvn clean site
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: John Casey
> Assigned To: Vincent Siveton
> Priority: Blocker
> Fix For: 2.1
>
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Brett Porter closed MJAVADOC-62:
--------------------------------
Assign To: Brett Porter
Resolution: Fixed
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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] Updated: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Brett Porter updated MJAVADOC-62:
---------------------------------
Fix Version: (was: 2.0)
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Assignee: Brett Porter
> Priority: Blocker
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=comments#action_64367 ]
Jesse McConnell commented on MJAVADOC-62:
-----------------------------------------
mvn generate-sources javadoc:javadoc works :)
working on the rest of it
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.0
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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] Updated: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Brett Porter updated MJAVADOC-62:
---------------------------------
Attachment: MJAVADOC-62.diff
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.0
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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] Reopened: (MJAVADOC-62) javadoc:javadoc needs access to
generated sources
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-62?page=all ]
Brett Porter reopened MJAVADOC-62:
----------------------------------
seeing now it doesn't work in the site plugin, even though the phase is executed
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: http://jira.codehaus.org/browse/MJAVADOC-62
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Versions: 2.0
> Reporter: John Casey
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling javadoc:javadoc. This is because maven-model's sources are generated, and the javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new lifecycle and cloning the project to call generate-sources, which means the report doesn't use the right project instance to create the report. However, I've been unable to inject ${executedProject} as a parameter; it fails the build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently have time to debug it properly, and I obviously haven't solved the problem.
--
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