felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FELIX-4135) Bnd scrplugin contrib
Date Wed, 11 Sep 2013 13:22:51 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764253#comment-13764253
] 

Pierre De Rop edited comment on FELIX-4135 at 9/11/13 1:20 PM:
---------------------------------------------------------------

I would like to publish an (overdue) tutorial about the bnd plugin currently committed (we
need some documentations before doing any release).

Are you ok if I do this, or do you prefer me to just attach in this issue the proposed tutorial
?
If you are ok, then I have some questions regarding CMS site documentation:

Basically, I'd like to add a link to a new  "apache-felix-scr-bndtools-use.mdtext" file, in
the current apache-felix-maven-scr-plugin.mdtext page (in the "Where to go from here" part):

## Where to go from here

* [{{ refs.apache-felix-maven-scr-plugin-use.headers.excerpt }}]({{ refs.apache-felix-maven-scr-plugin-use.path
}})
* [{{ refs.apache-felix-scr-ant-task-use.headers.excerpt }}]({{ refs.apache-felix-scr-ant-task-use.path
}})
* [{{ refs.apache-felix-scr-bndtools-use.headers.excerpt }}]({{ refs.apache-felix-scr-bndtools-use.path
}})
* [{{ refs.scr-annotations.headers.excerpt }}]({{ refs.scr-annotations.path }})
* [{{ refs.scr-javadoc-tags.headers.excerpt }}]({{ refs.scr-javadoc-tags.path }})
* [{{ refs.extending-scr-annotations.headers.excerpt }}]({{ refs.extending-scr-annotations.path
}})

and I will then add my tutorial in the new apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.mdtext
file.

Now, my question is: may I do this from the CMS GUI (I have installed the ASF CMS bookmarklet)
? or should I first manually commit the initial version just using svn, and then finalize
the formatting using the CMS GUI ?
If I update "http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html"
using the CMS bookmarklet, and add the new link :

* [{{ refs.apache-felix-scr-bndtools-use.headers.excerpt }}]({{ refs.apache-felix-scr-bndtools-use.path
}})

then will CMS automatically create and commit the new "apache-felix-scr-bndtools-use.mdtext"
in svn ?

(I am under the impression that I should first bootstrap my tutorial manually, and then finish
the formatting using CMS GUI, right ?)

thanks.

                
      was (Author: pderop):
    I would like to publish an (overdue) tutorial about the bnd plugin currently committed
(we need some documentations before doing any release).

Are you ok if I do this, or do you prefer me to just attach in this issue the proposed tutorial
?
If you are ok, then I some questions regarding CMS site documentation:

Basically, I'd like to add a link to a new  "apache-felix-scr-bndtools-use.mdtext" file, in
the current apache-felix-maven-scr-plugin.mdtext page (in the "Where to go from here" part):

## Where to go from here

* [{{ refs.apache-felix-maven-scr-plugin-use.headers.excerpt }}]({{ refs.apache-felix-maven-scr-plugin-use.path
}})
* [{{ refs.apache-felix-scr-ant-task-use.headers.excerpt }}]({{ refs.apache-felix-scr-ant-task-use.path
}})
* [{{ refs.apache-felix-scr-bndtools-use.headers.excerpt }}]({{ refs.apache-felix-scr-bndtools-use.path
}})
* [{{ refs.scr-annotations.headers.excerpt }}]({{ refs.scr-annotations.path }})
* [{{ refs.scr-javadoc-tags.headers.excerpt }}]({{ refs.scr-javadoc-tags.path }})
* [{{ refs.extending-scr-annotations.headers.excerpt }}]({{ refs.extending-scr-annotations.path
}})

and I will then add my tutorial in the new apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.mdtext
file.

Now, my question is: may I do this from the CMS GUI (I have installed the ASF CMS bookmarklet)
? or should I first manually commit the initial version just using svn, and then finalize
the formatting using the CMS GUI ?
If I update "http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html"
using the CMS bookmarklet, and add the new link :

* [{{ refs.apache-felix-scr-bndtools-use.headers.excerpt }}]({{ refs.apache-felix-scr-bndtools-use.path
}})

then will CMS automatically create and commit the new "apache-felix-scr-bndtools-use.mdtext"
in svn ?

(I am under the impression that I should first bootstrap my tutorial manually, and then finish
the formatting using CMS GUI, right ?)

thanks.

                  
> Bnd scrplugin contrib
> ---------------------
>
>                 Key: FELIX-4135
>                 URL: https://issues.apache.org/jira/browse/FELIX-4135
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven SCR Plugin
>            Reporter: Pierre De Rop
>            Priority: Minor
>         Attachments: bnd-scr-plugin.2.tgz, bnd-scr-plugin.3.tgz, bnd-scr-plugin.tgz,
test.bndtools.scrplugin.2.tgz, test.bndtools.scrplugin.tgz
>
>
> This issue is related to the following post, which is about writing a bndtools plugin
for the Apache Felix Scrplugin annotations:
>  http://www.mail-archive.com/dev@felix.apache.org/msg29200.html
> If this may help, I have attached to this issue a simple BND plugin, which internally
invokes the SCRDescriptorGenerator in order to generate the descriptors for Apache Felix Scr
annotations, as well as DS 1.2 annotations (using the scrplugin generator).
> Basically, just adding the following parameter in a directives.bnd file allows to invoke
the plugin:
>     -plugin org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=target/classes
> I did some tests using a BND Ant task, and it seems to work, and will try to do a test
with bndtools this week (for now I don't know how to add a plugin in bndtools, but I guess
it's easy).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message