You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stefano Lenzi (JIRA)" <ji...@apache.org> on 2008/02/19 20:22:49 UTC
[jira] Created: (FELIX-498) Enable javadoc deployment on OBR
repository
Enable javadoc deployment on OBR repository
-------------------------------------------
Key: FELIX-498
URL: https://issues.apache.org/jira/browse/FELIX-498
Project: Felix
Issue Type: New Feature
Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
Reporter: Stefano Lenzi
Priority: Trivial
I think that it would be nice if the command:
mvn javadoc:jar <install|deploy>
will add to the OBR repository the javadoc artifact.
I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-498) Enable javadoc deployment on OBR
repository
Posted by "Stefano Lenzi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Lenzi closed FELIX-498.
-------------------------------
I haven't tested the new "obr javadoc" command, but the rest is working.
> Enable javadoc deployment on OBR repository
> -------------------------------------------
>
> Key: FELIX-498
> URL: https://issues.apache.org/jira/browse/FELIX-498
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Trivial
> Fix For: 1.4.0
>
>
> I think that it would be nice if the command:
> mvn javadoc:jar <install|deploy>
> will add to the OBR repository the javadoc artifact.
> I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
> if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-498) Enable javadoc deployment on OBR
repository
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570592#action_12570592 ]
Stuart McCulloch commented on FELIX-498:
----------------------------------------
actually, the RFC says we can add our own user-defined properties to a resource
> Enable javadoc deployment on OBR repository
> -------------------------------------------
>
> Key: FELIX-498
> URL: https://issues.apache.org/jira/browse/FELIX-498
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Trivial
>
> I think that it would be nice if the command:
> mvn javadoc:jar <install|deploy>
> will add to the OBR repository the javadoc artifact.
> I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
> if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-498) Enable javadoc deployment on OBR
repository
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570519#action_12570519 ]
Stuart McCulloch commented on FELIX-498:
----------------------------------------
Added support for using attached javadoc as the documentation when there's no Bundle-DocURL or Maven project URL. Deployed new snapshot (1.3.0-20080220.005657-4)
Not sure about adding the javadoc tag, will need to consult the RFC about new tags.
> Enable javadoc deployment on OBR repository
> -------------------------------------------
>
> Key: FELIX-498
> URL: https://issues.apache.org/jira/browse/FELIX-498
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Trivial
>
> I think that it would be nice if the command:
> mvn javadoc:jar <install|deploy>
> will add to the OBR repository the javadoc artifact.
> I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
> if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-498) Enable javadoc deployment on OBR
repository
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-498.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Committed all bundle and OBR changes, and deployed new bundleplugin snapshot (1.3.0-20080220.072136-6).
Added new 'obr javadoc' command to the bundlerepository in trunk, but have not deployed a new snapshot of this.
> Enable javadoc deployment on OBR repository
> -------------------------------------------
>
> Key: FELIX-498
> URL: https://issues.apache.org/jira/browse/FELIX-498
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Trivial
> Fix For: 1.4.0
>
>
> I think that it would be nice if the command:
> mvn javadoc:jar <install|deploy>
> will add to the OBR repository the javadoc artifact.
> I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
> if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-498) Enable javadoc deployment on OBR
repository
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-498:
--------------------------------------
Assignee: Stuart McCulloch
> Enable javadoc deployment on OBR repository
> -------------------------------------------
>
> Key: FELIX-498
> URL: https://issues.apache.org/jira/browse/FELIX-498
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR), Maven Bundle Plugin, Maven OBR Plugin
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Trivial
>
> I think that it would be nice if the command:
> mvn javadoc:jar <install|deploy>
> will add to the OBR repository the javadoc artifact.
> I think that we can use either a javadocURL tag pointing the URL containing the Javadoc or the documentation tag. IMHO the best policy would be:
> if documentation info is extracted from the bundle or POM that we set javadocURL tag otherwise we set either documentation and javadocURL to the javadocArtifact.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.