Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless build of features with a different folder name
Headless build of features with a different folder name [message #25891] Wed, 08 October 2008 16:17 Go to next message
romu is currently offline romuFriend
Messages: 34
Registered: July 2009
Member
Hi all,
I would like to know how I can headless build features
(com.company.feature1,...) which are located in folders like
com.company.feature1.feature (...)?

The allElements.xml template tells to set the pluginPath property but how?
where?
Can I set this property several times, for each of my features?

I'm very far from being an Eclipse expert, but I have the bad feeling that
people in charge of Eclipse and people in charge of the PDE don't talk to
together.

Thanks for your help.
Re: Headless build of features with a different folder name [message #25932 is a reply to message #25891] Thu, 09 October 2008 17:30 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
There is no general requirement for the project name to match the
feature name. The single exception to this is the level feature that
you are specifying in the allElements.xml. In this case, if the project
name and feature name do not match, then you will need to set
"elementPath" which can be done in the allElements delegator task:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="com.foo" />
<property name="elementPath"
value="${buildDirectory}/features/com.foo-feature" />
</ant>
</target>

Or you can also set it in the build configuration's build.properties file.
This is also where you would set the pluginPath. Note that setting
pluginPath wouldn't actually help you in this case.

-Andrew

romu wrote:
> Hi all,
> I would like to know how I can headless build features
> (com.company.feature1,...) which are located in folders like
> com.company.feature1.feature (...)?
>
> The allElements.xml template tells to set the pluginPath property but
> how? where?
> Can I set this property several times, for each of my features?
>
> I'm very far from being an Eclipse expert, but I have the bad feeling
> that people in charge of Eclipse and people in charge of the PDE don't
> talk to together.
>
> Thanks for your help.
>
Re: Headless build of features with a different folder name [message #37206 is a reply to message #25932] Fri, 12 December 2008 05:23 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: prashanto.chatterjee.gmail.com

Hi Andrew,
I have just finished the exercise on the pde headless build and try as much
as I can I couldn't get the 'pluginPath' property to work. I tried a lot
many combinations but did not get the expected results. I got around it by
copying my features and plugins into the 'buildDirectory' first.
Does the pluginPath property actually work and if yes what should be the
target value for it?

Regards,
Prashanto


"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:gclf4e$pu9$1@build.eclipse.org...
> There is no general requirement for the project name to match the feature
> name. The single exception to this is the level feature that you are
> specifying in the allElements.xml. In this case, if the project name and
> feature name do not match, then you will need to set
> "elementPath" which can be done in the allElements delegator task:
>
> <target name="allElementsDelegator">
> <ant antfile="${genericTargets}" target="${target}">
> <property name="type" value="feature" />
> <property name="id" value="com.foo" />
> <property name="elementPath"
> value="${buildDirectory}/features/com.foo-feature" />
> </ant>
> </target>
>
> Or you can also set it in the build configuration's build.properties file.
> This is also where you would set the pluginPath. Note that setting
> pluginPath wouldn't actually help you in this case.
>
> -Andrew
>
> romu wrote:
>> Hi all,
>> I would like to know how I can headless build features
>> (com.company.feature1,...) which are located in folders like
>> com.company.feature1.feature (...)?
>>
>> The allElements.xml template tells to set the pluginPath property but
>> how? where?
>> Can I set this property several times, for each of my features?
>>
>> I'm very far from being an Eclipse expert, but I have the bad feeling
>> that people in charge of Eclipse and people in charge of the PDE don't
>> talk to together.
>>
>> Thanks for your help.
>>
Re: Headless build of features with a different folder name [message #37410 is a reply to message #37206] Fri, 12 December 2008 15:48 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Yes pluginPath works. Its value is a File.pathSeparator separated list
of directories. These directories can be:
- an eclipse directory containing "plugins" and "features" subdirectories
- the project directory for a plugin or feature
- a workspace-like directory which contains projects for plugins and
features.

Note that stated earlier in this thread, pluginPath won't help in the
case where the top level feature that you are building has a feature-id
that does not match the project name.

Prashanto Chatterjee wrote:
> Hi Andrew,
> I have just finished the exercise on the pde headless build and try as much
> as I can I couldn't get the 'pluginPath' property to work. I tried a lot
> many combinations but did not get the expected results. I got around it by
> copying my features and plugins into the 'buildDirectory' first.
> Does the pluginPath property actually work and if yes what should be the
> target value for it?
>
> Regards,
> Prashanto
>
>
> "Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
> news:gclf4e$pu9$1@build.eclipse.org...
>> There is no general requirement for the project name to match the feature
>> name. The single exception to this is the level feature that you are
>> specifying in the allElements.xml. In this case, if the project name and
>> feature name do not match, then you will need to set
>> "elementPath" which can be done in the allElements delegator task:
>>
>> <target name="allElementsDelegator">
>> <ant antfile="${genericTargets}" target="${target}">
>> <property name="type" value="feature" />
>> <property name="id" value="com.foo" />
>> <property name="elementPath"
>> value="${buildDirectory}/features/com.foo-feature" />
>> </ant>
>> </target>
>>
>> Or you can also set it in the build configuration's build.properties file.
>> This is also where you would set the pluginPath. Note that setting
>> pluginPath wouldn't actually help you in this case.
>>
>> -Andrew
>>
>> romu wrote:
>>> Hi all,
>>> I would like to know how I can headless build features
>>> (com.company.feature1,...) which are located in folders like
>>> com.company.feature1.feature (...)?
>>>
>>> The allElements.xml template tells to set the pluginPath property but
>>> how? where?
>>> Can I set this property several times, for each of my features?
>>>
>>> I'm very far from being an Eclipse expert, but I have the bad feeling
>>> that people in charge of Eclipse and people in charge of the PDE don't
>>> talk to together.
>>>
>>> Thanks for your help.
>>>
>
>
Re: Headless build of features with a different folder name [message #582516 is a reply to message #25891] Thu, 09 October 2008 17:30 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
There is no general requirement for the project name to match the
feature name. The single exception to this is the level feature that
you are specifying in the allElements.xml. In this case, if the project
name and feature name do not match, then you will need to set
"elementPath" which can be done in the allElements delegator task:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="com.foo" />
<property name="elementPath"
value="${buildDirectory}/features/com.foo-feature" />
</ant>
</target>

Or you can also set it in the build configuration's build.properties file.
This is also where you would set the pluginPath. Note that setting
pluginPath wouldn't actually help you in this case.

-Andrew

romu wrote:
> Hi all,
> I would like to know how I can headless build features
> (com.company.feature1,...) which are located in folders like
> com.company.feature1.feature (...)?
>
> The allElements.xml template tells to set the pluginPath property but
> how? where?
> Can I set this property several times, for each of my features?
>
> I'm very far from being an Eclipse expert, but I have the bad feeling
> that people in charge of Eclipse and people in charge of the PDE don't
> talk to together.
>
> Thanks for your help.
>
Re: Headless build of features with a different folder name [message #586998 is a reply to message #25932] Fri, 12 December 2008 05:23 Go to previous message
Eclipse UserFriend
Originally posted by: prashanto.chatterjee.gmail.com

Hi Andrew,
I have just finished the exercise on the pde headless build and try as much
as I can I couldn't get the 'pluginPath' property to work. I tried a lot
many combinations but did not get the expected results. I got around it by
copying my features and plugins into the 'buildDirectory' first.
Does the pluginPath property actually work and if yes what should be the
target value for it?

Regards,
Prashanto


"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:gclf4e$pu9$1@build.eclipse.org...
> There is no general requirement for the project name to match the feature
> name. The single exception to this is the level feature that you are
> specifying in the allElements.xml. In this case, if the project name and
> feature name do not match, then you will need to set
> "elementPath" which can be done in the allElements delegator task:
>
> <target name="allElementsDelegator">
> <ant antfile="${genericTargets}" target="${target}">
> <property name="type" value="feature" />
> <property name="id" value="com.foo" />
> <property name="elementPath"
> value="${buildDirectory}/features/com.foo-feature" />
> </ant>
> </target>
>
> Or you can also set it in the build configuration's build.properties file.
> This is also where you would set the pluginPath. Note that setting
> pluginPath wouldn't actually help you in this case.
>
> -Andrew
>
> romu wrote:
>> Hi all,
>> I would like to know how I can headless build features
>> (com.company.feature1,...) which are located in folders like
>> com.company.feature1.feature (...)?
>>
>> The allElements.xml template tells to set the pluginPath property but
>> how? where?
>> Can I set this property several times, for each of my features?
>>
>> I'm very far from being an Eclipse expert, but I have the bad feeling
>> that people in charge of Eclipse and people in charge of the PDE don't
>> talk to together.
>>
>> Thanks for your help.
>>
Re: Headless build of features with a different folder name [message #587077 is a reply to message #37206] Fri, 12 December 2008 15:48 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Yes pluginPath works. Its value is a File.pathSeparator separated list
of directories. These directories can be:
- an eclipse directory containing "plugins" and "features" subdirectories
- the project directory for a plugin or feature
- a workspace-like directory which contains projects for plugins and
features.

Note that stated earlier in this thread, pluginPath won't help in the
case where the top level feature that you are building has a feature-id
that does not match the project name.

Prashanto Chatterjee wrote:
> Hi Andrew,
> I have just finished the exercise on the pde headless build and try as much
> as I can I couldn't get the 'pluginPath' property to work. I tried a lot
> many combinations but did not get the expected results. I got around it by
> copying my features and plugins into the 'buildDirectory' first.
> Does the pluginPath property actually work and if yes what should be the
> target value for it?
>
> Regards,
> Prashanto
>
>
> "Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
> news:gclf4e$pu9$1@build.eclipse.org...
>> There is no general requirement for the project name to match the feature
>> name. The single exception to this is the level feature that you are
>> specifying in the allElements.xml. In this case, if the project name and
>> feature name do not match, then you will need to set
>> "elementPath" which can be done in the allElements delegator task:
>>
>> <target name="allElementsDelegator">
>> <ant antfile="${genericTargets}" target="${target}">
>> <property name="type" value="feature" />
>> <property name="id" value="com.foo" />
>> <property name="elementPath"
>> value="${buildDirectory}/features/com.foo-feature" />
>> </ant>
>> </target>
>>
>> Or you can also set it in the build configuration's build.properties file.
>> This is also where you would set the pluginPath. Note that setting
>> pluginPath wouldn't actually help you in this case.
>>
>> -Andrew
>>
>> romu wrote:
>>> Hi all,
>>> I would like to know how I can headless build features
>>> (com.company.feature1,...) which are located in folders like
>>> com.company.feature1.feature (...)?
>>>
>>> The allElements.xml template tells to set the pluginPath property but
>>> how? where?
>>> Can I set this property several times, for each of my features?
>>>
>>> I'm very far from being an Eclipse expert, but I have the bad feeling
>>> that people in charge of Eclipse and people in charge of the PDE don't
>>> talk to together.
>>>
>>> Thanks for your help.
>>>
>
>
Previous Topic:How to act on presentation out of non-Display Thread
Next Topic:PDE Build fails on Linux with Java returned: 13
Goto Forum:
  


Current Time: Sun Sep 26 09:23:09 GMT 2021

Powered by FUDForum. Page generated in 0.02096 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top