Re: [m2] included features with PDE-maven-plugin

2007-03-12 Thread Magali Helene

Actually, the features are not independants : a plugin of the second feature
needs a plugin of the first one to compile.

Magali

P.S. : here is a test.zip which is an example of my problem. Each of the
feature repositories contains a pom.xml. The Core project is the first one.
I can compile the feature without problem. The Project 1 is the second
project which depends on Core.  
As I compile it, the PDE-maven-plugin detects correctly the dependency with
the included core feature and places the needed first plugins in the
temprorary repository of the second feature. So it seems ok. Then it builds
the second plugin itself, and this build failed because it can't find the
first plugins. http://www.nabble.com/file/7113/test.zip test.zip 



dan tran wrote:
> 
> strange it should work since each feature is independently built. do you
> know some opensource that
> has similar set up that I can repoduce this issue?
> 
> -D
> 
> 
> On 3/8/07, Magali Helene <[EMAIL PROTECTED]> wrote:
>>
>>
>> Yes, it has his own feature.xml, which includes the first one with the
>>  tag.
>> Here is this feature.xml :
>>
>> 
>> >  id="com.arcadsoftware.skipper.features"
>>  label="ARCAD Plugin For Changer"
>>  version="2.0.0.2"
>>  provider-name="ARCAD Software"
>>  plugin="com.arcadsoftware.core"
>>  image="images/Arcad.gif"
>>  primary="true">
>>
>>   
>> ...
>>   
>>
>>   
>>  ...
>>   
>>
>>   
>>   ...
>>   
>>
>>   
>> ...
>>   
>>
>>   > id="com.arcadsoftware.core.features"
>> version="2.0.0.2"
>> name="ARCAD Plug-in Core"/>
>>
>>   
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  > match="equivalent"/>
>>  > match="equivalent"/>
>>  
>>  
>>   
>>
>>   > id="com.arcadsoftware.skipper"
>> download-size="0"
>> install-size="0"
>> version="2.0.0.2"/>
>>
>>   > id="com.arcadsoftware.skipper.nl"
>> download-size="0"
>> install-size="0"
>> version="2.0.0.2"
>> fragment="true"/>
>>
>> 
>>
>> Magali
>>
>>
>>
>>
>>
>> dan tran wrote:
>> >
>> > Does the second plugin has its own feature.xml?
>> >
>> > On 3/6/07, Magali Helene <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> Hello
>> >>
>> >> I am using the PDE-maven plugin to build plugins.
>> >> I have a first core plugin. I placed a pom.xml in the features
>> repository
>> >> and the build is ok. It takes into account the features and all the
>> >> plugins
>> >> listed in it.
>> >> Then I have a second plugin, which features includes my first core
>> >> plugin's
>> >> features. The PDE-maven plugin detects correctly this dependency and
>> >> places
>> >> the needed first plugins in the temprorary repository of the second
>> >> features
>> >> plugin. So it seems ok. Then it builds the second plugin itself, and
>> this
>> >> build failed because it can't find the first plugins ! Actually, when
>> I
>> >> am
>> >> looking in the build.xml file, I see that the javac classpath pointed
>> to
>> >> the
>> >> /plugins repositories instead of the temp repository of the features,
>> >> where,
>> >> juste before, the right plugins have been placed !
>> >> I don't know if I am clear enough, but it is really a problem for me
>> >> because
>> >> I can't build plugins that depends on others plugins.
>> >>
>> >> If someone has any ideas...
>> >>
>> >> Magali Helene
>> >> --
>> >> in my build.xml of the plugin:
>> >>
>> >> > >> failonerror="${javacFailOnError}" verbose="${javacVerbose}"
>> >> debug="${javacDebugInfo}" includeAntRuntime="no"
>>

Re: [m2] included features with PDE-maven-plugin

2007-03-08 Thread Magali Helene

Yes, it has his own feature.xml, which includes the first one with the
 tag.
Here is this feature.xml :




   
...
   

   
  ...
   

   
   ...
   

   
...
   

   

   
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
   

   

   



Magali





dan tran wrote:
> 
> Does the second plugin has its own feature.xml?
> 
> On 3/6/07, Magali Helene <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello
>>
>> I am using the PDE-maven plugin to build plugins.
>> I have a first core plugin. I placed a pom.xml in the features repository
>> and the build is ok. It takes into account the features and all the
>> plugins
>> listed in it.
>> Then I have a second plugin, which features includes my first core
>> plugin's
>> features. The PDE-maven plugin detects correctly this dependency and
>> places
>> the needed first plugins in the temprorary repository of the second
>> features
>> plugin. So it seems ok. Then it builds the second plugin itself, and this
>> build failed because it can't find the first plugins ! Actually, when I
>> am
>> looking in the build.xml file, I see that the javac classpath pointed to
>> the
>> /plugins repositories instead of the temp repository of the features,
>> where,
>> juste before, the right plugins have been placed !
>> I don't know if I am clear enough, but it is really a problem for me
>> because
>> I can't build plugins that depends on others plugins.
>>
>> If someone has any ideas...
>>
>> Magali Helene
>> --
>> in my build.xml of the plugin:
>>
>> > failonerror="${javacFailOnError}" verbose="${javacVerbose}"
>> debug="${javacDebugInfo}" includeAntRuntime="no"
>> bootclasspath="${bootclasspath}" source="${javacSource}"
>> target="${javacTarget}">
>>   
>>   
>>   
>>   
>> .
>> .
>> .
>> 
>> 
>>   
>>   
>> 
>>
>> instead of ?
>>   
>>   
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9335496
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9370916
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



included features with PDE-maven-plugin

2007-03-06 Thread Magali Helene

Hello

I am using the PDE-maven plugin to build plugins.
I have a first core plugin. I placed a pom.xml in the features repository
and the build is ok. It takes into account the features and all the plugins
listed in it.
Then I have a second plugin, which features includes my first core plugin's
features. The PDE-maven plugin detects correctly this dependency and places
the needed first plugins in the temprorary repository of the second features
plugin. So it seems ok. Then it builds the second plugin itself, and this
build failed because it can't find the first plugins ! Actually, when I am
looking in the build.xml file, I see that the javac classpath pointed to the
/plugins repositories instead of the temp repository of the features, where,
juste before, the right plugins have been placed !
I don't know if I am clear enough, but it is really a problem for me because
I can't build plugins that depends on others plugins.

If someone has any ideas...

Magali Helene
--
in my build.xml of the plugin:


   
   
   
   
 .
 .
 .
 
 
   
   


instead of ?
   
   


-- 
View this message in context: 
http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9335496
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]