You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Ivo Koga <iv...@gmail.com> on 2006/07/13 05:31:49 UTC
Problem trying installing Felix
Hi All,
I´m new to Felix and to Maven and when I tried to install Felix from maven I
got the following error:
================================
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] org.apache.maven.plugin.descriptor.Parameter.setImplementation
(Ljava/lang
/String;)V
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.plugin.descriptor.Parameter.setImp
lementation(Ljava/lang/String;)V
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.extractParameters(JavaMojoDescriptorExtractor.java:431)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:303)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtrac
tor.execute(JavaMojoDescriptorExtractor.java:500)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePlug
inDescriptor(DefaultMojoScanner.java:69)
at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute
(Abstract
GeneratorMojo.java:99)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
================================
What I did was to checkout the trunk directory from svn Felix repository and
just typed: mvn clean install.
Is there anything else I didn´t do? Can anyone help me installing Felix?
I used the doc from: http://docs.safehaus.org/display/OSGI/Building+Felix to
make this.
Best Regards,
Ivo K. Koga
Re: Problem trying installing Felix
Posted by Ivo Koga <iv...@gmail.com>.
Hi Marcel,
I just remove completely the ~/.m2/ directory and executed: mvn clean
install and it worked!
Thanks a lot
Ivo K. Koga
On 7/13/06, Marcel Offermans <ma...@luminis.nl> wrote:
>
>
> On Jul 13, 2006, at 17:32 , Ivo Koga wrote:
>
> > I´ve just tried to build it again and it didn´t work.
> >
> > I made a new checkout from svn and typed: mvn clean install and got
> > the same
> > error. :-(
>
> Weird. Let's see, you are using Maven 2.0.4? Have you tried "mvn -U
> clean install" (I did that once today but I don't think it mattered)?
> Are you still getting exactly the same error as before? One other
> thing that I've tried in the past is to completely remove my ~/.m2/
> directory, forcing Maven to download fresh copies of all dependencies.
>
> I tried the same thing here again, and it works for me.
>
> Anybody else still experiencing problems?
>
> Greetings, Marcel
>
>
>
>
Re: Problem trying installing Felix
Posted by Marcel Offermans <ma...@luminis.nl>.
On Jul 13, 2006, at 17:32 , Ivo Koga wrote:
> I´ve just tried to build it again and it didn´t work.
>
> I made a new checkout from svn and typed: mvn clean install and got
> the same
> error. :-(
Weird. Let's see, you are using Maven 2.0.4? Have you tried "mvn -U
clean install" (I did that once today but I don't think it mattered)?
Are you still getting exactly the same error as before? One other
thing that I've tried in the past is to completely remove my ~/.m2/
directory, forcing Maven to download fresh copies of all dependencies.
I tried the same thing here again, and it works for me.
Anybody else still experiencing problems?
Greetings, Marcel
Re: Problem trying installing Felix
Posted by Ivo Koga <iv...@gmail.com>.
Hi Marcel,
I´ve just tried to build it again and it didn´t work.
I made a new checkout from svn and typed: mvn clean install and got the same
error. :-(
Regards,
Ivo K. Koga
On 7/13/06, Richard S. Hall <he...@ungoverned.org> wrote:
>
> Definitely, I agree. We need to pin down our build process to make it
> more stable, since we have been bitten by this type of thing more than
> once.
>
> This also highlights the need for us to get an actual Felix release of
> some sort out the door with a simplified build process that bypasses
> this stuff.
>
> Regarding the snapshot repository, I think that is for our OSGi Maven
> plugin...from my experience, the plugin needs to be in a repo otherwise
> you cannot initially build bundles that require it. There might be a way
> around this, such as requiring a manual install of the plugin into the
> local repository, but I am not sure.
>
> It seems better if we could somehow order the repos so that Maven would
> search them in order, thus we could put the snapshot repository
> last...or something.
>
> -> richard
>
> Marcel Offermans wrote:
> > Hello Ivo,
> >
> > I just talked to the maven developers (on the codehaus irc #maven
> > channel) and they quicky fixed the problem. There was an issue with a
> > specific plugin that they fixed. Please try building again. Try
> > building again!
> >
> > To all: we really need to review the way we build with maven.
> > Appearantly, because we include a snapshot repository in our build, we
> > automatically get a snapshot version of everything else too, which
> > basically means we're running on a very unstable version. This has
> > bitten us a couple of times now.
> >
> > Now, I'm not sure why we include this snapshot repository, but the
> > advice on the #maven channel was to see if we could remove that from
> > our pom.xml (the <pluginRepository> that points to a snapshot
> > repository). Did anybody add that one for a specific reason?
> >
> > Our other option would be to manually "pin down" each individual
> > plugin we use in the build. I got a hint on that, we should somehow
> > specify "build > plugins > plugin > version" for each plugin. This
> > seems a lot of work though, so I'd rather go for the default of not
> > going for snapshots at all.
> >
> > Greetings, Marcel
> >
> >
>
Re: Problem trying installing Felix
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Definitely, I agree. We need to pin down our build process to make it
more stable, since we have been bitten by this type of thing more than once.
This also highlights the need for us to get an actual Felix release of
some sort out the door with a simplified build process that bypasses
this stuff.
Regarding the snapshot repository, I think that is for our OSGi Maven
plugin...from my experience, the plugin needs to be in a repo otherwise
you cannot initially build bundles that require it. There might be a way
around this, such as requiring a manual install of the plugin into the
local repository, but I am not sure.
It seems better if we could somehow order the repos so that Maven would
search them in order, thus we could put the snapshot repository
last...or something.
-> richard
Marcel Offermans wrote:
> Hello Ivo,
>
> I just talked to the maven developers (on the codehaus irc #maven
> channel) and they quicky fixed the problem. There was an issue with a
> specific plugin that they fixed. Please try building again. Try
> building again!
>
> To all: we really need to review the way we build with maven.
> Appearantly, because we include a snapshot repository in our build, we
> automatically get a snapshot version of everything else too, which
> basically means we're running on a very unstable version. This has
> bitten us a couple of times now.
>
> Now, I'm not sure why we include this snapshot repository, but the
> advice on the #maven channel was to see if we could remove that from
> our pom.xml (the <pluginRepository> that points to a snapshot
> repository). Did anybody add that one for a specific reason?
>
> Our other option would be to manually "pin down" each individual
> plugin we use in the build. I got a hint on that, we should somehow
> specify "build > plugins > plugin > version" for each plugin. This
> seems a lot of work though, so I'd rather go for the default of not
> going for snapshots at all.
>
> Greetings, Marcel
>
>
Re: Problem trying installing Felix
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Ivo,
I just talked to the maven developers (on the codehaus irc #maven
channel) and they quicky fixed the problem. There was an issue with a
specific plugin that they fixed. Please try building again. Try
building again!
To all: we really need to review the way we build with maven.
Appearantly, because we include a snapshot repository in our build,
we automatically get a snapshot version of everything else too, which
basically means we're running on a very unstable version. This has
bitten us a couple of times now.
Now, I'm not sure why we include this snapshot repository, but the
advice on the #maven channel was to see if we could remove that from
our pom.xml (the <pluginRepository> that points to a snapshot
repository). Did anybody add that one for a specific reason?
Our other option would be to manually "pin down" each individual
plugin we use in the build. I got a hint on that, we should somehow
specify "build > plugins > plugin > version" for each plugin. This
seems a lot of work though, so I'd rather go for the default of not
going for snapshots at all.
Greetings, Marcel
Re: Problem trying installing Felix
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Ivo,
On Jul 13, 2006, at 5:31 , Ivo Koga wrote:
> I´m new to Felix and to Maven and when I tried to install Felix
> from maven I
> got the following error:
[error log...]
>
> What I did was to checkout the trunk directory from svn Felix
> repository and
> just typed: mvn clean install.
> Is there anything else I didn´t do? Can anyone help me installing
> Felix?
I am getting the same error now, when I did the same thing. You're
not doing anything wrong but it seems somehow the build is broken. No
idea yet why, but it seems related to Maven (updates).
Greetings, Marcel