You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Magali Helene <mh...@arcadsoftware.com> on 2007/03/08 10:05:09 UTC
Re: [m2] included features with PDE-maven-plugin
Yes, it has his own feature.xml, which includes the first one with the
<includes/> tag.
Here is this feature.xml :
<?xml version="1.0" encoding="UTF-8"?>
<feature
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">
<description>
...
</description>
<copyright>
...
</copyright>
<license url="licence.txt">
...
</license>
<url>
...
</url>
<includes
id="com.arcadsoftware.core.features"
version="2.0.0.2"
name="ARCAD Plug-in Core"/>
<requires>
<import plugin="org.eclipse.ui.ide"/>
<import plugin="org.eclipse.ui.views"/>
<import plugin="org.eclipse.jface.text"/>
<import plugin="org.eclipse.ui.workbench.texteditor"/>
<import plugin="org.eclipse.ui.editors"/>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.ui"/>
<import plugin="com.ibm.etools.iseries.core"/>
<import plugin="com.ibm.etools.iseries.toolbox"/>
<import plugin="com.ibm.etools.systems.core"/>
<import plugin="com.ibm.etools.systems.dstore.core"/>
<import plugin="com.ibm.etools.systems.logging"/>
<import plugin="com.ibm.etools.systems.dstore.extra"/>
<import plugin="com.ibm.etools.systems.editor"/>
<import plugin="com.arcadsoftware.core.ui" version="2.0.0.2"
match="equivalent"/>
<import plugin="com.arcadsoftware.core" version="2.0.0.2"
match="equivalent"/>
<import plugin="com.ibm.lpex"/>
<import plugin="org.eclipse.core.runtime"/>
</requires>
<plugin
id="com.arcadsoftware.skipper"
download-size="0"
install-size="0"
version="2.0.0.2"/>
<plugin
id="com.arcadsoftware.skipper.nl"
download-size="0"
install-size="0"
version="2.0.0.2"
fragment="true"/>
</feature>
Magali
dan tran wrote:
>
> Does the second plugin has its own feature.xml?
>
> On 3/6/07, Magali Helene <mh...@arcadsoftware.com> 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:
>>
>> <javac destdir="${temp.folder}/arpchangerclient.jar.bin"
>> failonerror="${javacFailOnError}" verbose="${javacVerbose}"
>> debug="${javacDebugInfo}" includeAntRuntime="no"
>> bootclasspath="${bootclasspath}" source="${javacSource}"
>> target="${javacTarget}" >
>> <compilerarg line="${compilerArg}"/>
>> <classpath>
>> <pathelement path="../../../../../../../Program
>> Files/eclipse
>> 3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar"/>
>> <pathelement path="../../../../../../../Program
>> Files/eclipse 3.0.2/eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar"/>
>> .
>> .
>> .
>> <pathelement path="../FR - Plugin Core/arpcore.jar"/>
>> <pathelement path="../NL - Plugin
>> Core/arpcoreus.jar"/>
>> </classpath>
>> <src path="src/" />
>> </javac>
>>
>> instead of ?
>> <pathelement path="${pluginTemp}/FR - Plugin
>> Core/arpcore.jar"/>
>> <pathelement path="${pluginTemp}/NL - Plugin
>> Core/arpcoreus.jar"/>
>>
>>
>> --
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] included features with PDE-maven-plugin
Posted by Dan Tran <da...@gmail.com>.
Thanks for the test files, I will take a look at the build tonight.
-D
On 3/12/07, Magali Helene <mh...@arcadsoftware.com> wrote:
>
>
> 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 <mh...@arcadsoftware.com> wrote:
> >>
> >>
> >> Yes, it has his own feature.xml, which includes the first one with the
> >> <includes/> tag.
> >> Here is this feature.xml :
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <feature
> >> 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">
> >>
> >> <description>
> >> ...
> >> </description>
> >>
> >> <copyright>
> >> ...
> >> </copyright>
> >>
> >> <license url="licence.txt">
> >> ...
> >> </license>
> >>
> >> <url>
> >> ...
> >> </url>
> >>
> >> <includes
> >> id="com.arcadsoftware.core.features"
> >> version="2.0.0.2"
> >> name="ARCAD Plug-in Core"/>
> >>
> >> <requires>
> >> <import plugin="org.eclipse.ui.ide"/>
> >> <import plugin="org.eclipse.ui.views"/>
> >> <import plugin="org.eclipse.jface.text"/>
> >> <import plugin="org.eclipse.ui.workbench.texteditor"/>
> >> <import plugin="org.eclipse.ui.editors"/>
> >> <import plugin="org.eclipse.core.resources"/>
> >> <import plugin="org.eclipse.ui"/>
> >> <import plugin="com.ibm.etools.iseries.core"/>
> >> <import plugin="com.ibm.etools.iseries.toolbox"/>
> >> <import plugin="com.ibm.etools.systems.core"/>
> >> <import plugin="com.ibm.etools.systems.dstore.core"/>
> >> <import plugin="com.ibm.etools.systems.logging"/>
> >> <import plugin="com.ibm.etools.systems.dstore.extra"/>
> >> <import plugin="com.ibm.etools.systems.editor"/>
> >> <import plugin="com.arcadsoftware.core.ui" version="2.0.0.2"
> >> match="equivalent"/>
> >> <import plugin="com.arcadsoftware.core" version="2.0.0.2"
> >> match="equivalent"/>
> >> <import plugin="com.ibm.lpex"/>
> >> <import plugin="org.eclipse.core.runtime"/>
> >> </requires>
> >>
> >> <plugin
> >> id="com.arcadsoftware.skipper"
> >> download-size="0"
> >> install-size="0"
> >> version="2.0.0.2"/>
> >>
> >> <plugin
> >> id="com.arcadsoftware.skipper.nl"
> >> download-size="0"
> >> install-size="0"
> >> version="2.0.0.2"
> >> fragment="true"/>
> >>
> >> </feature>
> >>
> >> Magali
> >>
> >>
> >>
> >>
> >>
> >> dan tran wrote:
> >> >
> >> > Does the second plugin has its own feature.xml?
> >> >
> >> > On 3/6/07, Magali Helene <mh...@arcadsoftware.com> 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:
> >> >>
> >> >> <javac destdir="${temp.folder}/arpchangerclient.jar.bin"
> >> >> failonerror="${javacFailOnError}" verbose="${javacVerbose}"
> >> >> debug="${javacDebugInfo}" includeAntRuntime="no"
> >> >> bootclasspath="${bootclasspath}" source="${javacSource}"
> >> >> target="${javacTarget}" >
> >> >> <compilerarg line="${compilerArg}"/>
> >> >> <classpath>
> >> >> <pathelement path="../../../../../../../Program
> >> >> Files/eclipse
> >> >> 3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar"/>
> >> >> <pathelement path="../../../../../../../Program
> >> >> Files/eclipse 3.0.2
> /eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar"/>
> >> >> .
> >> >> .
> >> >> .
> >> >> <pathelement path="../FR - Plugin
> >> Core/arpcore.jar"/>
> >> >> <pathelement path="../NL - Plugin
> >> >> Core/arpcoreus.jar"/>
> >> >> </classpath>
> >> >> <src path="src/" />
> >> >> </javac>
> >> >>
> >> >> instead of ?
> >> >> <pathelement path="${pluginTemp}/FR - Plugin
> >> >> Core/arpcore.jar"/>
> >> >> <pathelement path="${pluginTemp}/NL - Plugin
> >> >> Core/arpcoreus.jar"/>
> >> >>
> >> >>
> >> >> --
> >> >> 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: users-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: users-help@maven.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> --
> >> 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: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9438658
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] included features with PDE-maven-plugin
Posted by Magali Helene <mh...@arcadsoftware.com>.
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 <mh...@arcadsoftware.com> wrote:
>>
>>
>> Yes, it has his own feature.xml, which includes the first one with the
>> <includes/> tag.
>> Here is this feature.xml :
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <feature
>> 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">
>>
>> <description>
>> ...
>> </description>
>>
>> <copyright>
>> ...
>> </copyright>
>>
>> <license url="licence.txt">
>> ...
>> </license>
>>
>> <url>
>> ...
>> </url>
>>
>> <includes
>> id="com.arcadsoftware.core.features"
>> version="2.0.0.2"
>> name="ARCAD Plug-in Core"/>
>>
>> <requires>
>> <import plugin="org.eclipse.ui.ide"/>
>> <import plugin="org.eclipse.ui.views"/>
>> <import plugin="org.eclipse.jface.text"/>
>> <import plugin="org.eclipse.ui.workbench.texteditor"/>
>> <import plugin="org.eclipse.ui.editors"/>
>> <import plugin="org.eclipse.core.resources"/>
>> <import plugin="org.eclipse.ui"/>
>> <import plugin="com.ibm.etools.iseries.core"/>
>> <import plugin="com.ibm.etools.iseries.toolbox"/>
>> <import plugin="com.ibm.etools.systems.core"/>
>> <import plugin="com.ibm.etools.systems.dstore.core"/>
>> <import plugin="com.ibm.etools.systems.logging"/>
>> <import plugin="com.ibm.etools.systems.dstore.extra"/>
>> <import plugin="com.ibm.etools.systems.editor"/>
>> <import plugin="com.arcadsoftware.core.ui" version="2.0.0.2"
>> match="equivalent"/>
>> <import plugin="com.arcadsoftware.core" version="2.0.0.2"
>> match="equivalent"/>
>> <import plugin="com.ibm.lpex"/>
>> <import plugin="org.eclipse.core.runtime"/>
>> </requires>
>>
>> <plugin
>> id="com.arcadsoftware.skipper"
>> download-size="0"
>> install-size="0"
>> version="2.0.0.2"/>
>>
>> <plugin
>> id="com.arcadsoftware.skipper.nl"
>> download-size="0"
>> install-size="0"
>> version="2.0.0.2"
>> fragment="true"/>
>>
>> </feature>
>>
>> Magali
>>
>>
>>
>>
>>
>> dan tran wrote:
>> >
>> > Does the second plugin has its own feature.xml?
>> >
>> > On 3/6/07, Magali Helene <mh...@arcadsoftware.com> 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:
>> >>
>> >> <javac destdir="${temp.folder}/arpchangerclient.jar.bin"
>> >> failonerror="${javacFailOnError}" verbose="${javacVerbose}"
>> >> debug="${javacDebugInfo}" includeAntRuntime="no"
>> >> bootclasspath="${bootclasspath}" source="${javacSource}"
>> >> target="${javacTarget}" >
>> >> <compilerarg line="${compilerArg}"/>
>> >> <classpath>
>> >> <pathelement path="../../../../../../../Program
>> >> Files/eclipse
>> >> 3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar"/>
>> >> <pathelement path="../../../../../../../Program
>> >> Files/eclipse 3.0.2/eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar"/>
>> >> .
>> >> .
>> >> .
>> >> <pathelement path="../FR - Plugin
>> Core/arpcore.jar"/>
>> >> <pathelement path="../NL - Plugin
>> >> Core/arpcoreus.jar"/>
>> >> </classpath>
>> >> <src path="src/" />
>> >> </javac>
>> >>
>> >> instead of ?
>> >> <pathelement path="${pluginTemp}/FR - Plugin
>> >> Core/arpcore.jar"/>
>> >> <pathelement path="${pluginTemp}/NL - Plugin
>> >> Core/arpcoreus.jar"/>
>> >>
>> >>
>> >> --
>> >> 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: users-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9438658
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] included features with PDE-maven-plugin
Posted by Dan Tran <da...@gmail.com>.
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 <mh...@arcadsoftware.com> wrote:
>
>
> Yes, it has his own feature.xml, which includes the first one with the
> <includes/> tag.
> Here is this feature.xml :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <feature
> 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">
>
> <description>
> ...
> </description>
>
> <copyright>
> ...
> </copyright>
>
> <license url="licence.txt">
> ...
> </license>
>
> <url>
> ...
> </url>
>
> <includes
> id="com.arcadsoftware.core.features"
> version="2.0.0.2"
> name="ARCAD Plug-in Core"/>
>
> <requires>
> <import plugin="org.eclipse.ui.ide"/>
> <import plugin="org.eclipse.ui.views"/>
> <import plugin="org.eclipse.jface.text"/>
> <import plugin="org.eclipse.ui.workbench.texteditor"/>
> <import plugin="org.eclipse.ui.editors"/>
> <import plugin="org.eclipse.core.resources"/>
> <import plugin="org.eclipse.ui"/>
> <import plugin="com.ibm.etools.iseries.core"/>
> <import plugin="com.ibm.etools.iseries.toolbox"/>
> <import plugin="com.ibm.etools.systems.core"/>
> <import plugin="com.ibm.etools.systems.dstore.core"/>
> <import plugin="com.ibm.etools.systems.logging"/>
> <import plugin="com.ibm.etools.systems.dstore.extra"/>
> <import plugin="com.ibm.etools.systems.editor"/>
> <import plugin="com.arcadsoftware.core.ui" version="2.0.0.2"
> match="equivalent"/>
> <import plugin="com.arcadsoftware.core" version="2.0.0.2"
> match="equivalent"/>
> <import plugin="com.ibm.lpex"/>
> <import plugin="org.eclipse.core.runtime"/>
> </requires>
>
> <plugin
> id="com.arcadsoftware.skipper"
> download-size="0"
> install-size="0"
> version="2.0.0.2"/>
>
> <plugin
> id="com.arcadsoftware.skipper.nl"
> download-size="0"
> install-size="0"
> version="2.0.0.2"
> fragment="true"/>
>
> </feature>
>
> Magali
>
>
>
>
>
> dan tran wrote:
> >
> > Does the second plugin has its own feature.xml?
> >
> > On 3/6/07, Magali Helene <mh...@arcadsoftware.com> 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:
> >>
> >> <javac destdir="${temp.folder}/arpchangerclient.jar.bin"
> >> failonerror="${javacFailOnError}" verbose="${javacVerbose}"
> >> debug="${javacDebugInfo}" includeAntRuntime="no"
> >> bootclasspath="${bootclasspath}" source="${javacSource}"
> >> target="${javacTarget}" >
> >> <compilerarg line="${compilerArg}"/>
> >> <classpath>
> >> <pathelement path="../../../../../../../Program
> >> Files/eclipse
> >> 3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar"/>
> >> <pathelement path="../../../../../../../Program
> >> Files/eclipse 3.0.2/eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar"/>
> >> .
> >> .
> >> .
> >> <pathelement path="../FR - Plugin
> Core/arpcore.jar"/>
> >> <pathelement path="../NL - Plugin
> >> Core/arpcoreus.jar"/>
> >> </classpath>
> >> <src path="src/" />
> >> </javac>
> >>
> >> instead of ?
> >> <pathelement path="${pluginTemp}/FR - Plugin
> >> Core/arpcore.jar"/>
> >> <pathelement path="${pluginTemp}/NL - Plugin
> >> Core/arpcoreus.jar"/>
> >>
> >>
> >> --
> >> 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: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>