| Controlling primary fetures within CVS [message #120063] |
Mon, 01 September 2003 15:44  |
Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
Hi, I have read that a primary feature requieres a plugin with exactly
the same name.
I am looking for comments about how to maintain the feature and the
plugin on the same CVS. What are you doing?
Thanks in advance,
Chemi.
|
|
|
| Re: Controlling primary fetures within CVS [message #120606 is a reply to message #120063] |
Tue, 02 September 2003 18:54  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NOSPAM.us.ibm.com
Typically the project in Eclipse and CVS for the feature has "-feature"
attached to the name. (I.e. the project that has the feature.xml in it).
For example if your feature was x.y.z the project for the feature would
be x.y.z-feature
Rich
|
|
|
| Re: Controlling primary fetures within CVS [message #121834 is a reply to message #120606] |
Wed, 03 September 2003 11:27 |
| Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
Thanks, I was doing this and then the build.xml script changes the name
when exporting.....
Thanks,
Chemi.
Richard L. Kulp wrote:
> Typically the project in Eclipse and CVS for the feature has
> "-feature" attached to the name. (I.e. the project that has the
> feature.xml in it). For example if your feature was x.y.z the project
> for the feature would be x.y.z-feature
>
> Rich
|
|
|
| Re: Controlling primary fetures within CVS [message #122016 is a reply to message #121834] |
Wed, 03 September 2003 14:02 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NOSPAM.us.ibm.com
Chemi wrote:
> Thanks, I was doing this and then the build.xml script changes the name
> when exporting.....
>
> Thanks,
>
> Chemi.
>
Are you saying it isn't working correctly, or that it is working correctly?
The build.xml isn't renaming the project itself is it? Or is the
build.xml renaming the feature instead to have -feature on the end?
--
Thanks, Rich Kulp
|
|
|
| Re: Controlling primary fetures within CVS [message #122241 is a reply to message #122016] |
Wed, 03 September 2003 15:57 |
| Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
Sorry, I didn't explain corectly myself.
What I mean is that I followed your suggestion. My feture project has a
es.org.chemi.games.feature name within CVS. But at deployment time, it
should be called es.org.chemi.games (I mean under /fetaures directory).
So I wrote an ANT script which export the feature content into a
es.org.chemi.games directory name.
That's all.
Thanks,
Chemi.
Richard L. Kulp wrote:
> Chemi wrote:
>
>> Thanks, I was doing this and then the build.xml script changes the
>> name when exporting.....
>>
>> Thanks,
>>
>> Chemi.
>>
> Are you saying it isn't working correctly, or that it is working
> correctly?
>
> The build.xml isn't renaming the project itself is it? Or is the
> build.xml renaming the feature instead to have -feature on the end?
|
|
|
| Re: Controlling primary fetures within CVS [message #122342 is a reply to message #122241] |
Wed, 03 September 2003 20:21 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NOSPAM.us.ibm.com
That shouldn't be necessary. Use PDE's export Feature and it will do all
of that for you. No special ANT script is needed. Look up feature
developement in the help guide for PDE Features.
Rich
|
|
|
| Re: Controlling primary fetures within CVS [message #122513 is a reply to message #122342] |
Thu, 04 September 2003 07:33 |
| Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
Thanks Rich, I was not aware of that feature. Is it new to R2.1?
Well, the porblem is that it seems it is not aware of some important
files like: .options, plugin.properties, /icons, welcome.xml, etc.....
which are not exported. Id there any way to customize the export process?
Thanks again,
Chemi.
Richard L. Kulp wrote:
> That shouldn't be necessary. Use PDE's export Feature and it will do
> all of that for you. No special ANT script is needed. Look up feature
> developement in the help guide for PDE Features.
>
> Rich
|
|
|
| Re: Controlling primary fetures within CVS [message #122599 is a reply to message #122513] |
Thu, 04 September 2003 10:52 |
| Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
And it doesn't extract Help plugins.
My feature refers to five plugins: three of them with code (so with /src
and /bin directories) and two of them just with help content (so no /src
directory). The export feature just include the first three plugins. ¿?
Thanks in advance,
Chemi.
Chemi wrote:
> Thanks Rich, I was not aware of that feature. Is it new to R2.1?
>
> Well, the porblem is that it seems it is not aware of some important
> files like: .options, plugin.properties, /icons, welcome.xml, etc.....
> which are not exported. Id there any way to customize the export process?
>
> Thanks again,
>
> Chemi.
|
|
|
| Re: Controlling primary fetures within CVS [message #122680 is a reply to message #122599] |
Thu, 04 September 2003 14:26 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NOSPAM.us.ibm.com
I don't know about the help. Never tried it. But to get the other files,
you update the build.properties file. In bin.includes= line you list,
separated by commas, all of the other files you want in the binary build
that are not being copied now.
To see what all goes in the build.properties files, go to the PDE help
and look under deploying fragments->Build Configuration. (Not exactly
sure of all of the intermediate nodes in the help tree, but the last
node is Build Configuration). It may be that for the non-code help
plugins you need some build.properties entries set.
Rich
|
|
|
| Re: Controlling primary fetures within CVS [message #122754 is a reply to message #122680] |
Thu, 04 September 2003 18:38 |
| Eclipse User |
|
|
|
Originally posted by: jmordax.terra.es
Here it is:
http://dev.eclipse.org/help21/index.jsp?topic=/org.eclipse.p de.doc.user/guide/pde_feature_generating_build.htm
Thank you very much Rich. As I started to develop plugins with Eclipse
R1.0 and AFAIK this export features didn't exist, I created my own ANT
scripts and I have continued developing with them. Now it seems
everything is easier. So the trick is to update the buil.properties file
instead my build.xml file. Cool.
Thanks again,
Chemi.
Richard L. Kulp wrote:
> I don't know about the help. Never tried it. But to get the other
> files, you update the build.properties file. In bin.includes= line you
> list, separated by commas, all of the other files you want in the
> binary build that are not being copied now.
>
> To see what all goes in the build.properties files, go to the PDE help
> and look under deploying fragments->Build Configuration. (Not exactly
> sure of all of the intermediate nodes in the help tree, but the last
> node is Build Configuration). It may be that for the non-code help
> plugins you need some build.properties entries set.
>
> Rich
|
|
|
Powered by
FUDForum. Page generated in 0.03946 seconds
] 
Search
Help
Register
Login
Home
