Hi Tim!
That was a very well detailed help! With this I could get a build success!
On 3/12/07, Tim Moloney <[EMAIL PROTECTED]> wrote:
I posted the following on the Maven mailing list.
I was able to get Felix to build by doing the following.
Start clean.
cd ${HOME}
rm -r .m2
rm -rf felix-trunk
svn checkout http://svn.apache.org/repos/asf/incubator/felix/trunk
felix-trunk
Build maven-bundle-plugin first since Maven 2.0.5 complains that it
can't find it even though it hasn't built it yet.
cd ${HOME}/felix-trunk/tools/maven2/maven-bundle-plugin
edit pom.xml to add <relativePath>../../../pom.xml</relativePath> to
<parent>
mvn install
Attempt to build all of Felix, however Maven 2.0.5 will fail stating it
can't find maven-osgi-plugin even though it hasn't built it yet.
Unfortunately, we cant just build maven-osgi-plugin next since Maven
2.0.5 will complain that it can't find maven-plugin-plugin.
cd ${HOME}/felix-trunk
ant
Now build maven-osgi-plugin since the previous build attempt was able to
download maven-plugin-plugin into the local repository.
cd ${HOME}/felix-trunk/tools/maven2/maven-osgi-plugin
mvn install
Now that everything needed is in the local repository, build all of
Felix successfully.
cd ${HOME}/felix-trunk
ant
Tim
Ivo K. Koga wrote:
> Hi Carsten,
>
> I´m using the maven 2.0.5 too. Could you please tell me in what
> folders do I
> have to type the "mvn clean install" to install the plugins one by one?
> I´m afraid I have to do it in the 58 folders I found here.
>
> Regards,
>
> Ivo
>
> On 3/12/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>>
>> 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 <[EMAIL PROTECTED]> 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/
>>
>
>
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
