Stuart McCulloch wrote:
On 17/04/2008, Richard S. Hall <[EMAIL PROTECTED]> wrote:
I am not sure why maven-felix-plugin has been added to the build anyway,
it used to be excluded.
FYI, it was added because it is needed by the following examples
sub-project:
felix/examples/dictionaryservice.itest/pom.xml
if you try to build Felix using an empty local m2 repository then it will
fail here
unless you have already built the maven-felix-plugin (using the plugins
build)
As far as I understand, there is no progress on this, it was just a proof of
concept, so it probably shouldn't be in the build.
if so then it also needs to be removed from the above examples sub-project
Yes, it does. The itest example was just a demonstration of how to use
the maven-felix-plugin itself. It is not a useful example, just part of
the proof of concept.
-> richard
-> richard
Clement Escoffier wrote:
Hi,
I have an error when trying to build the Felix trunk from scratch (empty
maven repository). It seems that the maven-felix-plugin does not target
a
consistent version of the parent artifact:
<parent>
<artifactId>felix</artifactId>
<groupId>org.apache.felix</groupId>
<version>1.1.0-SNAPSHOT</version>
<relativePath>../../../pom/pom.xml</relativePath>
</parent>
I change it to be
<parent>
<groupId>org.apache.felix</groupId>
<artifactId>felix</artifactId>
<version>1.0.2</version>
<relativePath>../../../pom/pom.xml</relativePath>
</parent>
However, after setting this, when compiling the Apache Felix Example
Dictionary Service Integration Test project, I have an NPE:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:394)
at
org.apache.felix.tools.maven.felix.plugin.FelixRunMojo.execute(FelixRunMojo.
java:618)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:539)
.. Blablabla
Any idea to solve this issue ?
Clement
