felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: How to build felix?
Date Mon, 12 Mar 2007 09:43:13 GMT
I had similar problems with a recent checkout from svn and a clean maven
2 repo using maven 2.0.5. For some strange reason, the snapshot
repository is never asked for artifacts.

So I first had to build the maven plugins, but as these require the root
felix pom (which is at that time not in my repository) i first have to
do a "mvn install" in the felix root directory to install the root pom,
then I can build the plugins (one by one) and then the provided ant
script to build felix works.

Perhaps this helps others as well.

Carsten

Richard S. Hall wrote:
> Ivo K. Koga wrote:
>> Hi Richard,
>>
>> When I type ant I got the same error:
>>
>> -----------
>>     [exec] [ERROR] BUILD ERROR
>>     [exec] [INFO]
>> -------------------------------------------------------------
>> -----------
>>     [exec] [INFO] The plugin 'org.apache.felix.plugins:maven-osgi-plugin'
>> does
>> not exist or no valid version could be found
> 
> You could try to build tools/maven/maven-osgi/plugin manually too. This 
> is another plugin. Maven is strange with plugins, it wants to find them 
> in a repository first, even if they are part of the project you are 
> building. Thus you can sometimes fix your dependency issues by building 
> the plugins first so they get installed into your local repository. If 
> you build this plugin, then perhaps you can try ant at the top level again.
> 
> I don't know why you are having this difficulty. It is almost like you 
> cannot access the snapshot repository.
> 
>> But when I type: mvn clean install, I got a:
>> [INFO] BUILD SUCCESSFUL
>>
>> Is there any problem using mvn clean install instead of Ant build.xml?
> 
> "mvn clean install" won't do anything in the trunk because it won't find 
> any modules to build. Due to another Maven bug that we are working 
> around, we had to define different "packaging profiles" for our 
> different subprojects that use different maven packaging plugins.
> 
> Thus, you HAVE to specify a packaging profile to compile the subprojects 
> associated with the given packaging profile; look into the build.xml to 
> see what it does to get an idea.
> 
> For example, if you want to build the framework, core bundles, and 
> other, you MUST type:
> 
>     mvn -Dpackaging=bundle clean install
> 
> This builds all subprojects that use the "maven-bundle-plugin". You can 
> search the pom.xml file for <profile> to see the various profiles that 
> are available.
> 
> We are hopeful that the Maven team will fix this packaging bug so that 
> in the future we can put all subprojects in the same profile and then we 
> won't need the ant file at all.
> 
> -> richard
> 
>> Regards,
>>
>> Ivo Koga
>>
>>
>> On 3/8/07, Richard S. Hall <heavy@ungoverned.org> wrote:
>>> Strange. I just deleted my local maven repo and rebuilt from scratch and
>>> it worked for me. Make sure you try again, since sometimes these things
>>> are spurious.
>>>
>>> iPOJO definitely exists in the SNAPSHOT repo.
>>>
>>> Perhaps you could try to 'cd' into the iPOJO subprojects manually and do
>>> "mvn clean install" to see if you can get them to build. If so, then try
>>> again with the build.xml file.
>>>
>>> -> richard
>>>



-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Mime
View raw message