You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "nicolas de loof (JIRA)" <ji...@codehaus.org> on 2006/08/18 14:51:48 UTC
[jira] Created: (MPECLIPSE-123) javadoc jar is not attached to
Eclipse
javadoc jar is not attached to Eclipse
--------------------------------------
Key: MPECLIPSE-123
URL: http://jira.codehaus.org/browse/MPECLIPSE-123
Project: maven-eclipse-plugin
Issue Type: Bug
Affects Versions: 1.11
Reporter: nicolas de loof
Priority: Minor
Fix For: 1.11.1
latest Plugin doesn't attach javadoc jar in the Eclipse Classpath. This is caused by a copy/paste of the chek-file-exists block that doesn't use the "jdocs" variable.
It would be great also to try downloading the javadocs when no sources jar is available : for example, the Oracle JDBC driver is closed-source but has javadoc that can be deployed in a corporate repository and be available to all corporate developpers.
--
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: (MPECLIPSE-123) javadoc jar is not attached to
Eclipse
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-123?page=all ]
nicolas de loof updated MPECLIPSE-123:
--------------------------------------
Attachment: MPECLIPSE-123.patch
This patch enables javadocs downloading when sources are not available. javadoc jar is added to .classpath using an absolute path due to lack of support for MAVEN_REPO classpath variable in Eclipse. As this classpath file can easily be re-created, I don't think this is a good reason for blocking this functionnality.
Patch contains code + doc improvement
> javadoc jar is not attached to Eclipse
> --------------------------------------
>
> Key: MPECLIPSE-123
> URL: http://jira.codehaus.org/browse/MPECLIPSE-123
> Project: maven-eclipse-plugin
> Issue Type: Bug
> Affects Versions: 1.11
> Reporter: nicolas de loof
> Priority: Minor
> Fix For: 1.11.1
>
> Attachments: MPECLIPSE-123.patch
>
>
> latest Plugin doesn't attach javadoc jar in the Eclipse Classpath. This is caused by a copy/paste of the chek-file-exists block that doesn't use the "jdocs" variable.
> It would be great also to try downloading the javadocs when no sources jar is available : for example, the Oracle JDBC driver is closed-source but has javadoc that can be deployed in a corporate repository and be available to all corporate developpers.
--
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: (MPECLIPSE-123) javadoc jar is not attached to
Eclipse
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-123?page=all ]
Stephane Nicoll closed MPECLIPSE-123.
-------------------------------------
Resolution: Fixed
This is fixed, thanks but:
- The patch was not on the latest version of SVN so it was a bit difficult to apply ; please rebuild from SVN and test your projects
- The copy paste of code was not really nice so I introduced an abstract class with common codes.
> javadoc jar is not attached to Eclipse
> --------------------------------------
>
> Key: MPECLIPSE-123
> URL: http://jira.codehaus.org/browse/MPECLIPSE-123
> Project: maven-eclipse-plugin
> Issue Type: Bug
> Affects Versions: 1.11
> Reporter: nicolas de loof
> Assigned To: Stephane Nicoll
> Priority: Minor
> Fix For: 1.11.1
>
> Attachments: MPECLIPSE-123.patch
>
>
> latest Plugin doesn't attach javadoc jar in the Eclipse Classpath. This is caused by a copy/paste of the chek-file-exists block that doesn't use the "jdocs" variable.
> It would be great also to try downloading the javadocs when no sources jar is available : for example, the Oracle JDBC driver is closed-source but has javadoc that can be deployed in a corporate repository and be available to all corporate developpers.
--
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: (MPECLIPSE-123) javadoc jar is not attached to
Eclipse
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-123?page=comments#action_72674 ]
nicolas de loof commented on MPECLIPSE-123:
-------------------------------------------
Sory for bad diagnostic, I was reading a modified plugin.jelly, not the SVN one.
According to plugin code, this is an expected behaviour as Eclipse before 3.2 doesn't support MAVEN_REPO classpath variable for javadoc attachement.
Maybe a property could make use of javadocs jars optional ? Maybe an eclipse version property could be usefull for other goals in this plugin, and could enable javadocs attachement / download ?
> javadoc jar is not attached to Eclipse
> --------------------------------------
>
> Key: MPECLIPSE-123
> URL: http://jira.codehaus.org/browse/MPECLIPSE-123
> Project: maven-eclipse-plugin
> Issue Type: Bug
> Affects Versions: 1.11
> Reporter: nicolas de loof
> Priority: Minor
> Fix For: 1.11.1
>
>
> latest Plugin doesn't attach javadoc jar in the Eclipse Classpath. This is caused by a copy/paste of the chek-file-exists block that doesn't use the "jdocs" variable.
> It would be great also to try downloading the javadocs when no sources jar is available : for example, the Oracle JDBC driver is closed-source but has javadoc that can be deployed in a corporate repository and be available to all corporate developpers.
--
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: (MPECLIPSE-123) javadoc jar is not attached to
Eclipse
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPECLIPSE-123?page=comments#action_72676 ]
nicolas de loof commented on MPECLIPSE-123:
-------------------------------------------
It seems there not a better support for classpath variables for javadoc in Eclipse 3.2
> javadoc jar is not attached to Eclipse
> --------------------------------------
>
> Key: MPECLIPSE-123
> URL: http://jira.codehaus.org/browse/MPECLIPSE-123
> Project: maven-eclipse-plugin
> Issue Type: Bug
> Affects Versions: 1.11
> Reporter: nicolas de loof
> Priority: Minor
> Fix For: 1.11.1
>
>
> latest Plugin doesn't attach javadoc jar in the Eclipse Classpath. This is caused by a copy/paste of the chek-file-exists block that doesn't use the "jdocs" variable.
> It would be great also to try downloading the javadocs when no sources jar is available : for example, the Oracle JDBC driver is closed-source but has javadoc that can be deployed in a corporate repository and be available to all corporate developpers.
--
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