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 K. Koga" <iv...@gmail.com> on 2007/03/07 19:53:34 UTC
How to build felix?
Hi guys,
I'm trying to build felix without success.
When I type ant, as the information in the wiki, it shows this message:
C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
Cannot ru
n program "mvn": CreateProcess error=2,
but when I type "mvn clean install", it seems to be ok, but do not create
the binaries of Felix. Can anyone help me on this?
Thanks in advance,
Ivo Koga
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Clement,
Thanks for your answer, but I still can´t build Felix with this maven error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.felix:maven-bundle-plugin' does not exist or
no va
lid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Mar 07 17:41:29 GMT-03:00 2007
[INFO] Final Memory: 2M/4M
Regards
Ivo Koga
On 3/7/07, Clement Escoffier <cl...@gmail.com> wrote:
>
> Ivo K. Koga a écrit :
> > Hi guys,
> >
> > I'm trying to build felix without success.
> >
> > When I type ant, as the information in the wiki, it shows this message:
> > C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
> > Cannot ru
> > n program "mvn": CreateProcess error=2,
> >
> > but when I type "mvn clean install", it seems to be ok, but do not
> create
> > the binaries of Felix. Can anyone help me on this?
> >
> > Thanks in advance,
> >
> > Ivo Koga
> For a strange reason (that I didn't discover), it does not work for me
> too.
> So, to compile launch the following commands (in this order) :
> mvn -Dpackaging=bundle clean install
> mvn -Dpackaging=osgi-bundle clean install
> mvn -Dpackaging=ipojo-bundle clean install
> mvn -Dpackaging=osgi-bundle-mosgi clean install
>
> All these commands should succeed (retry if you a a Maven-related error
> (download error, repository unaccessible ...)).
>
> Clement
>
>
> --
> Clement Escoffier
> Grenoble University
> LSR - Bat. C
> 220, Rue de la Chimie
> BP 53
> 38041 GRENOBLE CEDEX 9
> 04.76.51.40.24
> http://clement.plop-plop.net
>
>
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by Clement Escoffier <cl...@gmail.com>.
Ivo K. Koga a écrit :
> Hi guys,
>
> I'm trying to build felix without success.
>
> When I type ant, as the information in the wiki, it shows this message:
> C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
> Cannot ru
> n program "mvn": CreateProcess error=2,
>
> but when I type "mvn clean install", it seems to be ok, but do not create
> the binaries of Felix. Can anyone help me on this?
>
> Thanks in advance,
>
> Ivo Koga
For a strange reason (that I didn't discover), it does not work for me too.
So, to compile launch the following commands (in this order) :
mvn -Dpackaging=bundle clean install
mvn -Dpackaging=osgi-bundle clean install
mvn -Dpackaging=ipojo-bundle clean install
mvn -Dpackaging=osgi-bundle-mosgi clean install
All these commands should succeed (retry if you a a Maven-related error
(download error, repository unaccessible ...)).
Clement
--
Clement Escoffier
Grenoble University
LSR - Bat. C
220, Rue de la Chimie
BP 53
38041 GRENOBLE CEDEX 9
04.76.51.40.24
http://clement.plop-plop.net
Re: How to build felix?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Strange, it is working for me. As long as "mvn" is in your path, it
seems like it should work. I wonder if this is a Linux vs Windows issue...
If you specifically want to build the framework, then you can just type:
mvn -Dpackaging=bundle clean install
Look in the build.xml file to see the variations of this command for
building the other bundles too.
-> richard
Ivo K. Koga wrote:
> Hi guys,
>
> I'm trying to build felix without success.
>
> When I type ant, as the information in the wiki, it shows this message:
> C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
> Cannot ru
> n program "mvn": CreateProcess error=2,
>
> but when I type "mvn clean install", it seems to be ok, but do not create
> the binaries of Felix. Can anyone help me on this?
>
> Thanks in advance,
>
> Ivo Koga
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Richard,
Ok, thanks.
I´ll continue trying.
Regards,
Ivo
On 3/8/07, Richard S. Hall <he...@ungoverned.org> wrote:
>
> Ivo K. Koga wrote:
> > Hi Richard,
> >
> > I don´t have at my checkouted project the: tools/maven/maven-osgi/plugin
> > So I supposed to build the: tools\maven2\maven-osgi-plugin
>
> Sorry, type-o on my part.
>
> >
> > and I typed there the: mvn clean install. I got this error:
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Error building POM (may not be this project's POM).
>
> Well, I am pretty much at a loss for now...perhaps someone else can take
> a few guesses.
>
> -> richard
>
> >
> >
> > Project ID: org.apache.maven.plugins:maven-clean-plugin
> >
> > Reason: Error getting POM for
> > 'org.apache.maven.plugins:maven-clean-plugin'
> > from
> > the repository: Failed to resolve artifact, possibly due to a repository
> > list t
> > hat is not appropriately equipped for this artifact's metadata.
> > org.apache.maven.plugins:maven-clean-plugin:pom:2.2-SNAPSHOT
> >
> > from the specified remote repositories:
> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository
> ),
> > central (http://repo1.maven.org/maven2)
> >
> >
> >
> > Regards,
> >
> > Ivo Koga
> >
> >
> > On 3/8/07, Richard S. Hall <he...@ungoverned.org> 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 <he...@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
> >> >>
> >> >> Ivo K. Koga wrote:
> >> >> > Hi Felix!
> >> >> >
> >> >> > That was exactly the ant error. Thanks!
> >> >> >
> >> >> > But now I´m facing some problem inside maven (I think). This is
> the
> >> >> > output:
> >> >> >
> >> >> > [exec] [ERROR] BUILD ERROR
> >> >> > [exec] [INFO]
> >> >> > -------------------------------------------------------------
> >> >> > -----------
> >> >> > [exec] [INFO] The plugin '
> >> >> > org.apache.felix:org.apache.felix.ipojo.plugin' d
> >> >> > oes not exist or no valid version could be found
> >> >> >
> >> >> > Does anyone know how to fix that?
> >> >> >
> >> >> > Regards
> >> >> >
> >> >> > Ivo Koga
> >> >> >
> >> >> >
> >> >> > On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
> >> >> >>
> >> >> >> Hi,
> >> >> >>
> >> >> >> This seems in fact to be a Windows issue :-)
> >> >> >>
> >> >> >> The problems seems to be that the maven bin folder contains a
> >> mvn.bat
> >> >> >> and
> >> >> >> a
> >> >> >> mvn file. The mvn.bat file is a dos batch file while mvn is the
> >> unix
> >> >> >> shell
> >> >> >> script. It now seems that when ant is trying to call the mvn
> >> >> executable,
> >> >> >> the
> >> >> >> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat
> ".
> >> >> If I
> >> >> >> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to
> >> work.
> >> >> >>
> >> >> >> By testing for the OS and using a variable to take the mvn
> >> executale
> >> >> >> name,
> >> >> >> I
> >> >> >> could get to run on my windows and linux boxes:
> >> >> >>
> >> >> >> Regards
> >> >> >> Felix
> >> >> >>
> >> >> >> The hacked up build.xml :
> >> >> >> <!--
> >> >> >> Licensed to the Apache Software Foundation (ASF) under one
> >> >> >> or more contributor license agreements. See the NOTICE file
> >> >> >> distributed with this work for additional information
> >> >> >> regarding copyright ownership. The ASF licenses this file
> >> >> >> to you under the Apache License, Version 2.0 (the
> >> >> >> "License"); you may not use this file except in compliance
> >> >> >> with the License. You may obtain a copy of the License at
> >> >> >>
> >> >> >> http://www.apache.org/licenses/LICENSE-2.0
> >> >> >>
> >> >> >> Unless required by applicable law or agreed to in writing,
> >> >> >> software distributed under the License is distributed on an
> >> >> >> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> >> >> >> KIND, either express or implied. See the License for the
> >> >> >> specific language governing permissions and limitations
> >> >> >> under the License.
> >> >> >> -->
> >> >> >> <project default="all">
> >> >> >> <target name="init">
> >> >> >> <condition property="mvn" value="mvn.bat">
> >> >> >> <os family="dos" />
> >> >> >> </condition>
> >> >> >> <condition property="mvn" value="mvn">
> >> >> >> <not>
> >> >> >> <isset property="mvn" />
> >> >> >> </not>
> >> >> >> </condition>
> >> >> >> </target>
> >> >> >> <target name="clean" depends="init">
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=bundle clean" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle clean" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=ipojo-bundle clean" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
> >> >> >> </exec>
> >> >> >> </target>
> >> >> >> <target name="install" depends="init">
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=bundle install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=ipojo-bundle install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
> >> >> >> </exec>
> >> >> >> </target>
> >> >> >> <target name="all" depends="init">
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=bundle clean install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle clean install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=ipojo-bundle clean install" />
> >> >> >> </exec>
> >> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean
> >> >> install" />
> >> >> >> </exec>
> >> >> >> </target>
> >> >> >> </project>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Ivo K. Koga wrote:
> Hi Richard,
>
> I don´t have at my checkouted project the: tools/maven/maven-osgi/plugin
> So I supposed to build the: tools\maven2\maven-osgi-plugin
Sorry, type-o on my part.
>
> and I typed there the: mvn clean install. I got this error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
Well, I am pretty much at a loss for now...perhaps someone else can take
a few guesses.
-> richard
>
>
> Project ID: org.apache.maven.plugins:maven-clean-plugin
>
> Reason: Error getting POM for
> 'org.apache.maven.plugins:maven-clean-plugin'
> from
> the repository: Failed to resolve artifact, possibly due to a repository
> list t
> hat is not appropriately equipped for this artifact's metadata.
> org.apache.maven.plugins:maven-clean-plugin:pom:2.2-SNAPSHOT
>
> from the specified remote repositories:
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> central (http://repo1.maven.org/maven2)
>
>
>
> Regards,
>
> Ivo Koga
>
>
> On 3/8/07, Richard S. Hall <he...@ungoverned.org> 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 <he...@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
>> >>
>> >> Ivo K. Koga wrote:
>> >> > Hi Felix!
>> >> >
>> >> > That was exactly the ant error. Thanks!
>> >> >
>> >> > But now I´m facing some problem inside maven (I think). This is the
>> >> > output:
>> >> >
>> >> > [exec] [ERROR] BUILD ERROR
>> >> > [exec] [INFO]
>> >> > -------------------------------------------------------------
>> >> > -----------
>> >> > [exec] [INFO] The plugin '
>> >> > org.apache.felix:org.apache.felix.ipojo.plugin' d
>> >> > oes not exist or no valid version could be found
>> >> >
>> >> > Does anyone know how to fix that?
>> >> >
>> >> > Regards
>> >> >
>> >> > Ivo Koga
>> >> >
>> >> >
>> >> > On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> This seems in fact to be a Windows issue :-)
>> >> >>
>> >> >> The problems seems to be that the maven bin folder contains a
>> mvn.bat
>> >> >> and
>> >> >> a
>> >> >> mvn file. The mvn.bat file is a dos batch file while mvn is the
>> unix
>> >> >> shell
>> >> >> script. It now seems that when ant is trying to call the mvn
>> >> executable,
>> >> >> the
>> >> >> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat".
>> >> If I
>> >> >> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to
>> work.
>> >> >>
>> >> >> By testing for the OS and using a variable to take the mvn
>> executale
>> >> >> name,
>> >> >> I
>> >> >> could get to run on my windows and linux boxes:
>> >> >>
>> >> >> Regards
>> >> >> Felix
>> >> >>
>> >> >> The hacked up build.xml :
>> >> >> <!--
>> >> >> Licensed to the Apache Software Foundation (ASF) under one
>> >> >> or more contributor license agreements. See the NOTICE file
>> >> >> distributed with this work for additional information
>> >> >> regarding copyright ownership. The ASF licenses this file
>> >> >> to you under the Apache License, Version 2.0 (the
>> >> >> "License"); you may not use this file except in compliance
>> >> >> with the License. You may obtain a copy of the License at
>> >> >>
>> >> >> http://www.apache.org/licenses/LICENSE-2.0
>> >> >>
>> >> >> Unless required by applicable law or agreed to in writing,
>> >> >> software distributed under the License is distributed on an
>> >> >> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>> >> >> KIND, either express or implied. See the License for the
>> >> >> specific language governing permissions and limitations
>> >> >> under the License.
>> >> >> -->
>> >> >> <project default="all">
>> >> >> <target name="init">
>> >> >> <condition property="mvn" value="mvn.bat">
>> >> >> <os family="dos" />
>> >> >> </condition>
>> >> >> <condition property="mvn" value="mvn">
>> >> >> <not>
>> >> >> <isset property="mvn" />
>> >> >> </not>
>> >> >> </condition>
>> >> >> </target>
>> >> >> <target name="clean" depends="init">
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=bundle clean" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle clean" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=ipojo-bundle clean" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
>> >> >> </exec>
>> >> >> </target>
>> >> >> <target name="install" depends="init">
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=bundle install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=ipojo-bundle install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
>> >> >> </exec>
>> >> >> </target>
>> >> >> <target name="all" depends="init">
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=bundle clean install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle clean install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=ipojo-bundle clean install" />
>> >> >> </exec>
>> >> >> <exec executable="${mvn}" failonerror="true">
>> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean
>> >> install" />
>> >> >> </exec>
>> >> >> </target>
>> >> >> </project>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>
>
>
>
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Richard,
I don´t have at my checkouted project the: tools/maven/maven-osgi/plugin
So I supposed to build the: tools\maven2\maven-osgi-plugin
and I typed there the: mvn clean install. I got this error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.maven.plugins:maven-clean-plugin
Reason: Error getting POM for 'org.apache.maven.plugins:maven-clean-plugin'
from
the repository: Failed to resolve artifact, possibly due to a repository
list t
hat is not appropriately equipped for this artifact's metadata.
org.apache.maven.plugins:maven-clean-plugin:pom:2.2-SNAPSHOT
from the specified remote repositories:
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
central (http://repo1.maven.org/maven2)
Regards,
Ivo Koga
On 3/8/07, Richard S. Hall <he...@ungoverned.org> 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 <he...@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
> >>
> >> Ivo K. Koga wrote:
> >> > Hi Felix!
> >> >
> >> > That was exactly the ant error. Thanks!
> >> >
> >> > But now I´m facing some problem inside maven (I think). This is the
> >> > output:
> >> >
> >> > [exec] [ERROR] BUILD ERROR
> >> > [exec] [INFO]
> >> > -------------------------------------------------------------
> >> > -----------
> >> > [exec] [INFO] The plugin '
> >> > org.apache.felix:org.apache.felix.ipojo.plugin' d
> >> > oes not exist or no valid version could be found
> >> >
> >> > Does anyone know how to fix that?
> >> >
> >> > Regards
> >> >
> >> > Ivo Koga
> >> >
> >> >
> >> > On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> This seems in fact to be a Windows issue :-)
> >> >>
> >> >> The problems seems to be that the maven bin folder contains a
> mvn.bat
> >> >> and
> >> >> a
> >> >> mvn file. The mvn.bat file is a dos batch file while mvn is the unix
> >> >> shell
> >> >> script. It now seems that when ant is trying to call the mvn
> >> executable,
> >> >> the
> >> >> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat".
> >> If I
> >> >> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to
> work.
> >> >>
> >> >> By testing for the OS and using a variable to take the mvn executale
> >> >> name,
> >> >> I
> >> >> could get to run on my windows and linux boxes:
> >> >>
> >> >> Regards
> >> >> Felix
> >> >>
> >> >> The hacked up build.xml :
> >> >> <!--
> >> >> Licensed to the Apache Software Foundation (ASF) under one
> >> >> or more contributor license agreements. See the NOTICE file
> >> >> distributed with this work for additional information
> >> >> regarding copyright ownership. The ASF licenses this file
> >> >> to you under the Apache License, Version 2.0 (the
> >> >> "License"); you may not use this file except in compliance
> >> >> with the License. You may obtain a copy of the License at
> >> >>
> >> >> http://www.apache.org/licenses/LICENSE-2.0
> >> >>
> >> >> Unless required by applicable law or agreed to in writing,
> >> >> software distributed under the License is distributed on an
> >> >> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> >> >> KIND, either express or implied. See the License for the
> >> >> specific language governing permissions and limitations
> >> >> under the License.
> >> >> -->
> >> >> <project default="all">
> >> >> <target name="init">
> >> >> <condition property="mvn" value="mvn.bat">
> >> >> <os family="dos" />
> >> >> </condition>
> >> >> <condition property="mvn" value="mvn">
> >> >> <not>
> >> >> <isset property="mvn" />
> >> >> </not>
> >> >> </condition>
> >> >> </target>
> >> >> <target name="clean" depends="init">
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=bundle clean" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle clean" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=ipojo-bundle clean" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
> >> >> </exec>
> >> >> </target>
> >> >> <target name="install" depends="init">
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=bundle install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=ipojo-bundle install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
> >> >> </exec>
> >> >> </target>
> >> >> <target name="all" depends="init">
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=bundle clean install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle clean install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=ipojo-bundle clean install" />
> >> >> </exec>
> >> >> <exec executable="${mvn}" failonerror="true">
> >> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean
> >> install" />
> >> >> </exec>
> >> >> </target>
> >> >> </project>
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Carsten and others who answered this thread,
Thank you very much all for your help.
Regards,
Ivo Koga
On 3/12/07, Carsten Ziegeler <cz...@apache.org> wrote:
>
> 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.
> >
> No, go to the top level directory (where the build.xml is) and do a
> > mvn install
>
> Then go to the tools/maven2 directory and do a "mvn install" in all
> directories which name ends with "plugin".
> Go back to the top level directory and then cd into the "ipojo.plugin"
> directory and do "mvn install" there as well.
>
> That's it, you should now be able to use the provided ant script as
> document.
>
> HTH
> Carsten
> --
> Carsten Ziegeler
> http://www.osoco.org/weblogs/rael/
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by Carsten Ziegeler <cz...@apache.org>.
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.
>
No, go to the top level directory (where the build.xml is) and do a
> mvn install
Then go to the tools/maven2 directory and do a "mvn install" in all
directories which name ends with "plugin".
Go back to the top level directory and then cd into the "ipojo.plugin"
directory and do "mvn install" there as well.
That's it, you should now be able to use the provided ant script as
document.
HTH
Carsten
--
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Tim!
That was a very well detailed help! With this I could get a build success!
On 3/12/07, Tim Moloney <t....@verizon.net> 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 <cz...@apache.org> 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 <he...@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/
> >>
> >
> >
> >
>
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by Tim Moloney <t....@verizon.net>.
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 <cz...@apache.org> 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 <he...@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/
>>
>
>
>
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
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 <cz...@apache.org> 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 <he...@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/
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by Carsten Ziegeler <cz...@apache.org>.
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 <he...@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/
Re: How to build felix?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
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 <he...@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
>>
>> Ivo K. Koga wrote:
>> > Hi Felix!
>> >
>> > That was exactly the ant error. Thanks!
>> >
>> > But now I´m facing some problem inside maven (I think). This is the
>> > output:
>> >
>> > [exec] [ERROR] BUILD ERROR
>> > [exec] [INFO]
>> > -------------------------------------------------------------
>> > -----------
>> > [exec] [INFO] The plugin '
>> > org.apache.felix:org.apache.felix.ipojo.plugin' d
>> > oes not exist or no valid version could be found
>> >
>> > Does anyone know how to fix that?
>> >
>> > Regards
>> >
>> > Ivo Koga
>> >
>> >
>> > On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> This seems in fact to be a Windows issue :-)
>> >>
>> >> The problems seems to be that the maven bin folder contains a mvn.bat
>> >> and
>> >> a
>> >> mvn file. The mvn.bat file is a dos batch file while mvn is the unix
>> >> shell
>> >> script. It now seems that when ant is trying to call the mvn
>> executable,
>> >> the
>> >> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat".
>> If I
>> >> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
>> >>
>> >> By testing for the OS and using a variable to take the mvn executale
>> >> name,
>> >> I
>> >> could get to run on my windows and linux boxes:
>> >>
>> >> Regards
>> >> Felix
>> >>
>> >> The hacked up build.xml :
>> >> <!--
>> >> Licensed to the Apache Software Foundation (ASF) under one
>> >> or more contributor license agreements. See the NOTICE file
>> >> distributed with this work for additional information
>> >> regarding copyright ownership. The ASF licenses this file
>> >> to you under the Apache License, Version 2.0 (the
>> >> "License"); you may not use this file except in compliance
>> >> with the License. You may obtain a copy of the License at
>> >>
>> >> http://www.apache.org/licenses/LICENSE-2.0
>> >>
>> >> Unless required by applicable law or agreed to in writing,
>> >> software distributed under the License is distributed on an
>> >> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>> >> KIND, either express or implied. See the License for the
>> >> specific language governing permissions and limitations
>> >> under the License.
>> >> -->
>> >> <project default="all">
>> >> <target name="init">
>> >> <condition property="mvn" value="mvn.bat">
>> >> <os family="dos" />
>> >> </condition>
>> >> <condition property="mvn" value="mvn">
>> >> <not>
>> >> <isset property="mvn" />
>> >> </not>
>> >> </condition>
>> >> </target>
>> >> <target name="clean" depends="init">
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=bundle clean" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle clean" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=ipojo-bundle clean" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
>> >> </exec>
>> >> </target>
>> >> <target name="install" depends="init">
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=bundle install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=ipojo-bundle install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
>> >> </exec>
>> >> </target>
>> >> <target name="all" depends="init">
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=bundle clean install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle clean install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=ipojo-bundle clean install" />
>> >> </exec>
>> >> <exec executable="${mvn}" failonerror="true">
>> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean
>> install" />
>> >> </exec>
>> >> </target>
>> >> </project>
>> >>
>> >
>> >
>> >
>>
>
>
>
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
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
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?
Regards,
Ivo Koga
On 3/8/07, Richard S. Hall <he...@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
>
> Ivo K. Koga wrote:
> > Hi Felix!
> >
> > That was exactly the ant error. Thanks!
> >
> > But now I´m facing some problem inside maven (I think). This is the
> > output:
> >
> > [exec] [ERROR] BUILD ERROR
> > [exec] [INFO]
> > -------------------------------------------------------------
> > -----------
> > [exec] [INFO] The plugin '
> > org.apache.felix:org.apache.felix.ipojo.plugin' d
> > oes not exist or no valid version could be found
> >
> > Does anyone know how to fix that?
> >
> > Regards
> >
> > Ivo Koga
> >
> >
> > On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
> >>
> >> Hi,
> >>
> >> This seems in fact to be a Windows issue :-)
> >>
> >> The problems seems to be that the maven bin folder contains a mvn.bat
> >> and
> >> a
> >> mvn file. The mvn.bat file is a dos batch file while mvn is the unix
> >> shell
> >> script. It now seems that when ant is trying to call the mvn
> executable,
> >> the
> >> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat". If I
> >> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
> >>
> >> By testing for the OS and using a variable to take the mvn executale
> >> name,
> >> I
> >> could get to run on my windows and linux boxes:
> >>
> >> Regards
> >> Felix
> >>
> >> The hacked up build.xml :
> >> <!--
> >> Licensed to the Apache Software Foundation (ASF) under one
> >> or more contributor license agreements. See the NOTICE file
> >> distributed with this work for additional information
> >> regarding copyright ownership. The ASF licenses this file
> >> to you under the Apache License, Version 2.0 (the
> >> "License"); you may not use this file except in compliance
> >> with the License. You may obtain a copy of the License at
> >>
> >> http://www.apache.org/licenses/LICENSE-2.0
> >>
> >> Unless required by applicable law or agreed to in writing,
> >> software distributed under the License is distributed on an
> >> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> >> KIND, either express or implied. See the License for the
> >> specific language governing permissions and limitations
> >> under the License.
> >> -->
> >> <project default="all">
> >> <target name="init">
> >> <condition property="mvn" value="mvn.bat">
> >> <os family="dos" />
> >> </condition>
> >> <condition property="mvn" value="mvn">
> >> <not>
> >> <isset property="mvn" />
> >> </not>
> >> </condition>
> >> </target>
> >> <target name="clean" depends="init">
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=bundle clean" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle clean" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=ipojo-bundle clean" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
> >> </exec>
> >> </target>
> >> <target name="install" depends="init">
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=bundle install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=ipojo-bundle install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
> >> </exec>
> >> </target>
> >> <target name="all" depends="init">
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=bundle clean install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle clean install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=ipojo-bundle clean install" />
> >> </exec>
> >> <exec executable="${mvn}" failonerror="true">
> >> <arg line="-Dpackaging=osgi-bundle-mosgi clean install" />
> >> </exec>
> >> </target>
> >> </project>
> >>
> >
> >
> >
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
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
Ivo K. Koga wrote:
> Hi Felix!
>
> That was exactly the ant error. Thanks!
>
> But now I´m facing some problem inside maven (I think). This is the
> output:
>
> [exec] [ERROR] BUILD ERROR
> [exec] [INFO]
> -------------------------------------------------------------
> -----------
> [exec] [INFO] The plugin '
> org.apache.felix:org.apache.felix.ipojo.plugin' d
> oes not exist or no valid version could be found
>
> Does anyone know how to fix that?
>
> Regards
>
> Ivo Koga
>
>
> On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
>>
>> Hi,
>>
>> This seems in fact to be a Windows issue :-)
>>
>> The problems seems to be that the maven bin folder contains a mvn.bat
>> and
>> a
>> mvn file. The mvn.bat file is a dos batch file while mvn is the unix
>> shell
>> script. It now seems that when ant is trying to call the mvn executable,
>> the
>> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat". If I
>> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
>>
>> By testing for the OS and using a variable to take the mvn executale
>> name,
>> I
>> could get to run on my windows and linux boxes:
>>
>> Regards
>> Felix
>>
>> The hacked up build.xml :
>> <!--
>> Licensed to the Apache Software Foundation (ASF) under one
>> or more contributor license agreements. See the NOTICE file
>> distributed with this work for additional information
>> regarding copyright ownership. The ASF licenses this file
>> to you under the Apache License, Version 2.0 (the
>> "License"); you may not use this file except in compliance
>> with the License. You may obtain a copy of the License at
>>
>> http://www.apache.org/licenses/LICENSE-2.0
>>
>> Unless required by applicable law or agreed to in writing,
>> software distributed under the License is distributed on an
>> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>> KIND, either express or implied. See the License for the
>> specific language governing permissions and limitations
>> under the License.
>> -->
>> <project default="all">
>> <target name="init">
>> <condition property="mvn" value="mvn.bat">
>> <os family="dos" />
>> </condition>
>> <condition property="mvn" value="mvn">
>> <not>
>> <isset property="mvn" />
>> </not>
>> </condition>
>> </target>
>> <target name="clean" depends="init">
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=bundle clean" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle clean" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=ipojo-bundle clean" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
>> </exec>
>> </target>
>> <target name="install" depends="init">
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=bundle install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=ipojo-bundle install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
>> </exec>
>> </target>
>> <target name="all" depends="init">
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=bundle clean install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle clean install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=ipojo-bundle clean install" />
>> </exec>
>> <exec executable="${mvn}" failonerror="true">
>> <arg line="-Dpackaging=osgi-bundle-mosgi clean install" />
>> </exec>
>> </target>
>> </project>
>>
>
>
>
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Felix!
That was exactly the ant error. Thanks!
But now I´m facing some problem inside maven (I think). This is the output:
[exec] [ERROR] BUILD ERROR
[exec] [INFO]
-------------------------------------------------------------
-----------
[exec] [INFO] The plugin '
org.apache.felix:org.apache.felix.ipojo.plugin' d
oes not exist or no valid version could be found
Does anyone know how to fix that?
Regards
Ivo Koga
On 3/8/07, Felix Meschberger <Fe...@day.com> wrote:
>
> Hi,
>
> This seems in fact to be a Windows issue :-)
>
> The problems seems to be that the maven bin folder contains a mvn.bat and
> a
> mvn file. The mvn.bat file is a dos batch file while mvn is the unix shell
> script. It now seems that when ant is trying to call the mvn executable,
> the
> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat". If I
> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
>
> By testing for the OS and using a variable to take the mvn executale name,
> I
> could get to run on my windows and linux boxes:
>
> Regards
> Felix
>
> The hacked up build.xml :
> <!--
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements. See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership. The ASF licenses this file
> to you under the Apache License, Version 2.0 (the
> "License"); you may not use this file except in compliance
> with the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing,
> software distributed under the License is distributed on an
> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> KIND, either express or implied. See the License for the
> specific language governing permissions and limitations
> under the License.
> -->
> <project default="all">
> <target name="init">
> <condition property="mvn" value="mvn.bat">
> <os family="dos" />
> </condition>
> <condition property="mvn" value="mvn">
> <not>
> <isset property="mvn" />
> </not>
> </condition>
> </target>
> <target name="clean" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
> </exec>
> </target>
> <target name="install" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
> </exec>
> </target>
> <target name="all" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi clean install" />
> </exec>
> </target>
> </project>
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Cool, I just committed the fix...thanks a lot.
-> richard
Felix Meschberger wrote:
> Hi,
>
> This seems in fact to be a Windows issue :-)
>
> The problems seems to be that the maven bin folder contains a mvn.bat
> and a
> mvn file. The mvn.bat file is a dos batch file while mvn is the unix
> shell
> script. It now seems that when ant is trying to call the mvn
> executable, the
> Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat". If I
> change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
>
> By testing for the OS and using a variable to take the mvn executale
> name, I
> could get to run on my windows and linux boxes:
>
> Regards
> Felix
>
> The hacked up build.xml :
> <!--
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements. See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership. The ASF licenses this file
> to you under the Apache License, Version 2.0 (the
> "License"); you may not use this file except in compliance
> with the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing,
> software distributed under the License is distributed on an
> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> KIND, either express or implied. See the License for the
> specific language governing permissions and limitations
> under the License.
> -->
> <project default="all">
> <target name="init">
> <condition property="mvn" value="mvn.bat">
> <os family="dos" />
> </condition>
> <condition property="mvn" value="mvn">
> <not>
> <isset property="mvn" />
> </not>
> </condition>
> </target>
> <target name="clean" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle clean" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi clean" />
> </exec>
> </target>
> <target name="install" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi install" />
> </exec>
> </target>
> <target name="all" depends="init">
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=ipojo-bundle clean install" />
> </exec>
> <exec executable="${mvn}" failonerror="true">
> <arg line="-Dpackaging=osgi-bundle-mosgi clean install" />
> </exec>
> </target>
> </project>
>
Re: How to build felix?
Posted by Felix Meschberger <Fe...@day.com>.
Hi,
This seems in fact to be a Windows issue :-)
The problems seems to be that the maven bin folder contains a mvn.bat and a
mvn file. The mvn.bat file is a dos batch file while mvn is the unix shell
script. It now seems that when ant is trying to call the mvn executable, the
Java VM or Windows or whoever does not resovle "mvn" to "mvn.bat". If I
change 'executable="mvn"' to 'executable="mvn.bat"' it seems to work.
By testing for the OS and using a variable to take the mvn executale name, I
could get to run on my windows and linux boxes:
Regards
Felix
The hacked up build.xml :
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<project default="all">
<target name="init">
<condition property="mvn" value="mvn.bat">
<os family="dos" />
</condition>
<condition property="mvn" value="mvn">
<not>
<isset property="mvn" />
</not>
</condition>
</target>
<target name="clean" depends="init">
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=bundle clean" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle clean" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=ipojo-bundle clean" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle-mosgi clean" />
</exec>
</target>
<target name="install" depends="init">
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=bundle install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=ipojo-bundle install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle-mosgi install" />
</exec>
</target>
<target name="all" depends="init">
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=bundle clean install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle clean install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=ipojo-bundle clean install" />
</exec>
<exec executable="${mvn}" failonerror="true">
<arg line="-Dpackaging=osgi-bundle-mosgi clean install" />
</exec>
</target>
</project>
Re: How to build felix?
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Felix,
I think this is the error when I type "ant" in the checkouted dir of felix
and it doesn´t work. But It´s weird since when I type mvn this works. I´m
using Windows XP and the ant and mvn is in the PATH enviroment variable.
Regards,
Ivo
On 3/7/07, Felix Meschberger <Fe...@day.com> wrote:
>
> Hi,
>
> Just wild guessing ...
>
> Could it be that - somehow - your ant installation cannot find the mvn
> binary/batch file? In this case, this sounds very much like a path issue.
>
> Regards
> Felix
>
> On 3/7/07, Ivo K. Koga <iv...@gmail.com> wrote:
> >
> > Hi guys,
> >
> > I'm trying to build felix without success.
> >
> > When I type ant, as the information in the wiki, it shows this message:
> > C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
> > Cannot ru
> > n program "mvn": CreateProcess error=2,
> >
> > but when I type "mvn clean install", it seems to be ok, but do not
> create
> > the binaries of Felix. Can anyone help me on this?
> >
> > Thanks in advance,
> >
> > Ivo Koga
> > --
> > Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
> > Measurement WG - RNP/Brazil
> >
>
--
Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
Measurement WG - RNP/Brazil
Re: How to build felix?
Posted by Felix Meschberger <Fe...@day.com>.
Hi,
Just wild guessing ...
Could it be that - somehow - your ant installation cannot find the mvn
binary/batch file? In this case, this sounds very much like a path issue.
Regards
Felix
On 3/7/07, Ivo K. Koga <iv...@gmail.com> wrote:
>
> Hi guys,
>
> I'm trying to build felix without success.
>
> When I type ant, as the information in the wiki, it shows this message:
> C:\Felix\2007-03-07\build.xml:49: Execute failed: java.io.IOException:
> Cannot ru
> n program "mvn": CreateProcess error=2,
>
> but when I type "mvn clean install", it seems to be ok, but do not create
> the binaries of Felix. Can anyone help me on this?
>
> Thanks in advance,
>
> Ivo Koga
> --
> Msc. Candidate in Computer Networks at Universidade Salvador/BA/Brazil
> Measurement WG - RNP/Brazil
>