You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall" <he...@ungoverned.org> on 2007/05/04 18:59:09 UTC
UPnP bundles
The UPnP bundles were causing my build to fail (as pointed out to me by
Stephane), so I commented them out of the main pom file. Once the issue
is resolved, we need to uncomment them.
Two questions about the pom:
1. MOSGi has a dependency on Java 1.5 which causes the build to fail
under 1.4. Can we put MOSGi into a profile that only gets build on
> Java 1.5?
2. Is there a way to modify the pom file so that the build does not
stop if one of the modules fails? Would this be a better approach?
-> richard
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Committing works again! :-)
-> richard
Richard S. Hall wrote:
> I think I might have found the issue in the svn-authorization file,
> but I am asking for confirmation before making the edit, since I don't
> want to do something stupid. :-)
>
> -> richard
>
> Richard S. Hall wrote:
>> Karl Pauls wrote:
>>> Is it possible that we don't have commit rights yet?
>>
>> Could be. Perhaps that is why I thought I committed the commenting
>> out of the UPnP bundles, but the changes didn't actually appear. I
>> must not have noticed that it errored then.
>>
>> -> richard
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On 5/4/07, Richard S. Hall <he...@ungoverned.org> wrote:
>>>> Strange. I am trying to commit the patch, but I get this error
>>>> message:
>>>>
>>>> heavy:~/tmp/felix-trunk2$ svn commit
>>>> Sending examples/pom.xml
>>>> svn: Commit failed (details follow):
>>>> svn: CHECKOUT of
>>>> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>>>> Forbidden
>>>> (https://svn.apache.org)
>>>> svn: Your commit message was left in a temporary file:
>>>> svn: '/home/rickhall/tmp/felix-trunk2/svn-commit.tmp'
>>>> heavy:~/tmp/felix-trunk2$
>>>>
>>>> Anyone have any idea what this means?
>>>>
>>>> This was on a fresh checkout of the trunk.
>>>>
>>>> -> richard
>>>>
>>>>
>>>> Richard S. Hall wrote:
>>>> > Ok, sorry for blaming the UPnP bundles! :-)
>>>> >
>>>> > This bug was actually introduced by me, when I committed Didier's
>>>> pom
>>>> > file for the spellcheckscr example...I didn't even think about this
>>>> > issue.
>>>> >
>>>> > Whenever we change the packaging of any subproject, we have to
>>>> > remember to change the profile it is in. This is the second time we
>>>> > had issues due to changing the packaging of a bundle, but forgetting
>>>> > to changes it profile.
>>>> >
>>>> > It will be nice if we can get a Maven fix for this so we can quit
>>>> > running into these sorts of issues.
>>>> >
>>>> > I will commit your patch and uncomment the UPnP bundles...
>>>> >
>>>> > Thanks for looking into it.
>>>> >
>>>> > -> richard
>>>> >
>>>> > Stefano Lenzi wrote:
>>>> >> Richard S. Hall wrote:
>>>> >>> Francesco Furfari wrote:
>>>> >>>>
>>>> >>>> Richard S. Hall wrote:
>>>> >>>>> The UPnP bundles were causing my build to fail (as pointed
>>>> out to
>>>> >>>>> me by Stephane), so I commented them out of the main pom file.
>>>> >>>>> Once the issue is resolved, we need to uncomment them.
>>>> >>>>
>>>> >>>> Sorry to which bundles are you referring to?
>>>> >>>> In the trunk there aren't dependencies between UPnP and MOSGi
>>>> >>>> ... and actually they are not commented !!
>>>> >>>> Are you talking about my sandbox?
>>>> >>>
>>>> >>> I tried to do a clean build of the trunk and I got an error which
>>>> >>> says that it could not resolve a dependency for one of the UPnP
>>>> >>> bundles...I don't remember which. It looked like the dependency
>>>> was
>>>> >>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
>>>> >>> heard of such a version.
>>>> >>>
>>>> >>> Clear your .m2/repository and try to build from scratch using
>>>> "ant"
>>>> >>> in the trunk and see what happens...that is what I did.
>>>> >> Hi All,
>>>> >> we have just made some tests and we found that the problem
>>>> >> resides in the org.apache.felix.examples.spellcheckscr project that
>>>> >> uses the bundle packaging even if it's in the profile for that
>>>> uses
>>>> >> the osgi-bundle packaging. In fact if you look at your
>>>> repository you
>>>> >> may find also the wireadmin bundle installed as .osgi-bundle
>>>> artifact
>>>> >> instead of .jar due to the famous maven bug ^_^
>>>> >>
>>>> >> So we have solved the issue by defining the profiles for the
>>>> >> examples pom.xml as you have done for the trunk pom.xml
>>>> >> I have tried to send the patch but I get the following
>>>> error
>>>> >> message:
>>>> >> Sending examples/pom.xml
>>>> >> svn: Commit failed (details follow):
>>>> >> svn: CHECKOUT of
>>>> >> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>>>> >> Forbidden (https://svn.apache.org)
>>>> >>
>>>> >> So I'll attach the patch :S
>>>> >>
>>>> >> Ciao,
>>>> >> Stefano "Kismet" Lenzi
>>>> >>
>>>> >>
>>>>
>>>
>>>
>
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I think I might have found the issue in the svn-authorization file, but
I am asking for confirmation before making the edit, since I don't want
to do something stupid. :-)
-> richard
Richard S. Hall wrote:
> Karl Pauls wrote:
>> Is it possible that we don't have commit rights yet?
>
> Could be. Perhaps that is why I thought I committed the commenting out
> of the UPnP bundles, but the changes didn't actually appear. I must
> not have noticed that it errored then.
>
> -> richard
>>
>> regards,
>>
>> Karl
>>
>> On 5/4/07, Richard S. Hall <he...@ungoverned.org> wrote:
>>> Strange. I am trying to commit the patch, but I get this error message:
>>>
>>> heavy:~/tmp/felix-trunk2$ svn commit
>>> Sending examples/pom.xml
>>> svn: Commit failed (details follow):
>>> svn: CHECKOUT of
>>> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>>> Forbidden
>>> (https://svn.apache.org)
>>> svn: Your commit message was left in a temporary file:
>>> svn: '/home/rickhall/tmp/felix-trunk2/svn-commit.tmp'
>>> heavy:~/tmp/felix-trunk2$
>>>
>>> Anyone have any idea what this means?
>>>
>>> This was on a fresh checkout of the trunk.
>>>
>>> -> richard
>>>
>>>
>>> Richard S. Hall wrote:
>>> > Ok, sorry for blaming the UPnP bundles! :-)
>>> >
>>> > This bug was actually introduced by me, when I committed Didier's pom
>>> > file for the spellcheckscr example...I didn't even think about this
>>> > issue.
>>> >
>>> > Whenever we change the packaging of any subproject, we have to
>>> > remember to change the profile it is in. This is the second time we
>>> > had issues due to changing the packaging of a bundle, but forgetting
>>> > to changes it profile.
>>> >
>>> > It will be nice if we can get a Maven fix for this so we can quit
>>> > running into these sorts of issues.
>>> >
>>> > I will commit your patch and uncomment the UPnP bundles...
>>> >
>>> > Thanks for looking into it.
>>> >
>>> > -> richard
>>> >
>>> > Stefano Lenzi wrote:
>>> >> Richard S. Hall wrote:
>>> >>> Francesco Furfari wrote:
>>> >>>>
>>> >>>> Richard S. Hall wrote:
>>> >>>>> The UPnP bundles were causing my build to fail (as pointed out to
>>> >>>>> me by Stephane), so I commented them out of the main pom file.
>>> >>>>> Once the issue is resolved, we need to uncomment them.
>>> >>>>
>>> >>>> Sorry to which bundles are you referring to?
>>> >>>> In the trunk there aren't dependencies between UPnP and MOSGi
>>> >>>> ... and actually they are not commented !!
>>> >>>> Are you talking about my sandbox?
>>> >>>
>>> >>> I tried to do a clean build of the trunk and I got an error which
>>> >>> says that it could not resolve a dependency for one of the UPnP
>>> >>> bundles...I don't remember which. It looked like the dependency was
>>> >>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
>>> >>> heard of such a version.
>>> >>>
>>> >>> Clear your .m2/repository and try to build from scratch using "ant"
>>> >>> in the trunk and see what happens...that is what I did.
>>> >> Hi All,
>>> >> we have just made some tests and we found that the problem
>>> >> resides in the org.apache.felix.examples.spellcheckscr project that
>>> >> uses the bundle packaging even if it's in the profile for that uses
>>> >> the osgi-bundle packaging. In fact if you look at your repository
>>> you
>>> >> may find also the wireadmin bundle installed as .osgi-bundle
>>> artifact
>>> >> instead of .jar due to the famous maven bug ^_^
>>> >>
>>> >> So we have solved the issue by defining the profiles for the
>>> >> examples pom.xml as you have done for the trunk pom.xml
>>> >> I have tried to send the patch but I get the following error
>>> >> message:
>>> >> Sending examples/pom.xml
>>> >> svn: Commit failed (details follow):
>>> >> svn: CHECKOUT of
>>> >> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>>> >> Forbidden (https://svn.apache.org)
>>> >>
>>> >> So I'll attach the patch :S
>>> >>
>>> >> Ciao,
>>> >> Stefano "Kismet" Lenzi
>>> >>
>>> >>
>>>
>>
>>
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Karl Pauls wrote:
> Is it possible that we don't have commit rights yet?
Could be. Perhaps that is why I thought I committed the commenting out
of the UPnP bundles, but the changes didn't actually appear. I must not
have noticed that it errored then.
-> richard
>
> regards,
>
> Karl
>
> On 5/4/07, Richard S. Hall <he...@ungoverned.org> wrote:
>> Strange. I am trying to commit the patch, but I get this error message:
>>
>> heavy:~/tmp/felix-trunk2$ svn commit
>> Sending examples/pom.xml
>> svn: Commit failed (details follow):
>> svn: CHECKOUT of
>> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403 Forbidden
>> (https://svn.apache.org)
>> svn: Your commit message was left in a temporary file:
>> svn: '/home/rickhall/tmp/felix-trunk2/svn-commit.tmp'
>> heavy:~/tmp/felix-trunk2$
>>
>> Anyone have any idea what this means?
>>
>> This was on a fresh checkout of the trunk.
>>
>> -> richard
>>
>>
>> Richard S. Hall wrote:
>> > Ok, sorry for blaming the UPnP bundles! :-)
>> >
>> > This bug was actually introduced by me, when I committed Didier's pom
>> > file for the spellcheckscr example...I didn't even think about this
>> > issue.
>> >
>> > Whenever we change the packaging of any subproject, we have to
>> > remember to change the profile it is in. This is the second time we
>> > had issues due to changing the packaging of a bundle, but forgetting
>> > to changes it profile.
>> >
>> > It will be nice if we can get a Maven fix for this so we can quit
>> > running into these sorts of issues.
>> >
>> > I will commit your patch and uncomment the UPnP bundles...
>> >
>> > Thanks for looking into it.
>> >
>> > -> richard
>> >
>> > Stefano Lenzi wrote:
>> >> Richard S. Hall wrote:
>> >>> Francesco Furfari wrote:
>> >>>>
>> >>>> Richard S. Hall wrote:
>> >>>>> The UPnP bundles were causing my build to fail (as pointed out to
>> >>>>> me by Stephane), so I commented them out of the main pom file.
>> >>>>> Once the issue is resolved, we need to uncomment them.
>> >>>>
>> >>>> Sorry to which bundles are you referring to?
>> >>>> In the trunk there aren't dependencies between UPnP and MOSGi
>> >>>> ... and actually they are not commented !!
>> >>>> Are you talking about my sandbox?
>> >>>
>> >>> I tried to do a clean build of the trunk and I got an error which
>> >>> says that it could not resolve a dependency for one of the UPnP
>> >>> bundles...I don't remember which. It looked like the dependency was
>> >>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
>> >>> heard of such a version.
>> >>>
>> >>> Clear your .m2/repository and try to build from scratch using "ant"
>> >>> in the trunk and see what happens...that is what I did.
>> >> Hi All,
>> >> we have just made some tests and we found that the problem
>> >> resides in the org.apache.felix.examples.spellcheckscr project that
>> >> uses the bundle packaging even if it's in the profile for that uses
>> >> the osgi-bundle packaging. In fact if you look at your repository you
>> >> may find also the wireadmin bundle installed as .osgi-bundle artifact
>> >> instead of .jar due to the famous maven bug ^_^
>> >>
>> >> So we have solved the issue by defining the profiles for the
>> >> examples pom.xml as you have done for the trunk pom.xml
>> >> I have tried to send the patch but I get the following error
>> >> message:
>> >> Sending examples/pom.xml
>> >> svn: Commit failed (details follow):
>> >> svn: CHECKOUT of
>> >> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>> >> Forbidden (https://svn.apache.org)
>> >>
>> >> So I'll attach the patch :S
>> >>
>> >> Ciao,
>> >> Stefano "Kismet" Lenzi
>> >>
>> >>
>>
>
>
Re: UPnP bundles
Posted by Karl Pauls <ka...@gmail.com>.
Is it possible that we don't have commit rights yet?
regards,
Karl
On 5/4/07, Richard S. Hall <he...@ungoverned.org> wrote:
> Strange. I am trying to commit the patch, but I get this error message:
>
> heavy:~/tmp/felix-trunk2$ svn commit
> Sending examples/pom.xml
> svn: Commit failed (details follow):
> svn: CHECKOUT of
> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403 Forbidden
> (https://svn.apache.org)
> svn: Your commit message was left in a temporary file:
> svn: '/home/rickhall/tmp/felix-trunk2/svn-commit.tmp'
> heavy:~/tmp/felix-trunk2$
>
> Anyone have any idea what this means?
>
> This was on a fresh checkout of the trunk.
>
> -> richard
>
>
> Richard S. Hall wrote:
> > Ok, sorry for blaming the UPnP bundles! :-)
> >
> > This bug was actually introduced by me, when I committed Didier's pom
> > file for the spellcheckscr example...I didn't even think about this
> > issue.
> >
> > Whenever we change the packaging of any subproject, we have to
> > remember to change the profile it is in. This is the second time we
> > had issues due to changing the packaging of a bundle, but forgetting
> > to changes it profile.
> >
> > It will be nice if we can get a Maven fix for this so we can quit
> > running into these sorts of issues.
> >
> > I will commit your patch and uncomment the UPnP bundles...
> >
> > Thanks for looking into it.
> >
> > -> richard
> >
> > Stefano Lenzi wrote:
> >> Richard S. Hall wrote:
> >>> Francesco Furfari wrote:
> >>>>
> >>>> Richard S. Hall wrote:
> >>>>> The UPnP bundles were causing my build to fail (as pointed out to
> >>>>> me by Stephane), so I commented them out of the main pom file.
> >>>>> Once the issue is resolved, we need to uncomment them.
> >>>>
> >>>> Sorry to which bundles are you referring to?
> >>>> In the trunk there aren't dependencies between UPnP and MOSGi
> >>>> ... and actually they are not commented !!
> >>>> Are you talking about my sandbox?
> >>>
> >>> I tried to do a clean build of the trunk and I got an error which
> >>> says that it could not resolve a dependency for one of the UPnP
> >>> bundles...I don't remember which. It looked like the dependency was
> >>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
> >>> heard of such a version.
> >>>
> >>> Clear your .m2/repository and try to build from scratch using "ant"
> >>> in the trunk and see what happens...that is what I did.
> >> Hi All,
> >> we have just made some tests and we found that the problem
> >> resides in the org.apache.felix.examples.spellcheckscr project that
> >> uses the bundle packaging even if it's in the profile for that uses
> >> the osgi-bundle packaging. In fact if you look at your repository you
> >> may find also the wireadmin bundle installed as .osgi-bundle artifact
> >> instead of .jar due to the famous maven bug ^_^
> >>
> >> So we have solved the issue by defining the profiles for the
> >> examples pom.xml as you have done for the trunk pom.xml
> >> I have tried to send the patch but I get the following error
> >> message:
> >> Sending examples/pom.xml
> >> svn: Commit failed (details follow):
> >> svn: CHECKOUT of
> >> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
> >> Forbidden (https://svn.apache.org)
> >>
> >> So I'll attach the patch :S
> >>
> >> Ciao,
> >> Stefano "Kismet" Lenzi
> >>
> >>
>
--
Karl Pauls
karlpauls@gmail.com
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Strange. I am trying to commit the patch, but I get this error message:
heavy:~/tmp/felix-trunk2$ svn commit
Sending examples/pom.xml
svn: Commit failed (details follow):
svn: CHECKOUT of
'/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403 Forbidden
(https://svn.apache.org)
svn: Your commit message was left in a temporary file:
svn: '/home/rickhall/tmp/felix-trunk2/svn-commit.tmp'
heavy:~/tmp/felix-trunk2$
Anyone have any idea what this means?
This was on a fresh checkout of the trunk.
-> richard
Richard S. Hall wrote:
> Ok, sorry for blaming the UPnP bundles! :-)
>
> This bug was actually introduced by me, when I committed Didier's pom
> file for the spellcheckscr example...I didn't even think about this
> issue.
>
> Whenever we change the packaging of any subproject, we have to
> remember to change the profile it is in. This is the second time we
> had issues due to changing the packaging of a bundle, but forgetting
> to changes it profile.
>
> It will be nice if we can get a Maven fix for this so we can quit
> running into these sorts of issues.
>
> I will commit your patch and uncomment the UPnP bundles...
>
> Thanks for looking into it.
>
> -> richard
>
> Stefano Lenzi wrote:
>> Richard S. Hall wrote:
>>> Francesco Furfari wrote:
>>>>
>>>> Richard S. Hall wrote:
>>>>> The UPnP bundles were causing my build to fail (as pointed out to
>>>>> me by Stephane), so I commented them out of the main pom file.
>>>>> Once the issue is resolved, we need to uncomment them.
>>>>
>>>> Sorry to which bundles are you referring to?
>>>> In the trunk there aren't dependencies between UPnP and MOSGi
>>>> ... and actually they are not commented !!
>>>> Are you talking about my sandbox?
>>>
>>> I tried to do a clean build of the trunk and I got an error which
>>> says that it could not resolve a dependency for one of the UPnP
>>> bundles...I don't remember which. It looked like the dependency was
>>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
>>> heard of such a version.
>>>
>>> Clear your .m2/repository and try to build from scratch using "ant"
>>> in the trunk and see what happens...that is what I did.
>> Hi All,
>> we have just made some tests and we found that the problem
>> resides in the org.apache.felix.examples.spellcheckscr project that
>> uses the bundle packaging even if it's in the profile for that uses
>> the osgi-bundle packaging. In fact if you look at your repository you
>> may find also the wireadmin bundle installed as .osgi-bundle artifact
>> instead of .jar due to the famous maven bug ^_^
>>
>> So we have solved the issue by defining the profiles for the
>> examples pom.xml as you have done for the trunk pom.xml
>> I have tried to send the patch but I get the following error
>> message:
>> Sending examples/pom.xml
>> svn: Commit failed (details follow):
>> svn: CHECKOUT of
>> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
>> Forbidden (https://svn.apache.org)
>>
>> So I'll attach the patch :S
>>
>> Ciao,
>> Stefano "Kismet" Lenzi
>>
>>
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Ok, sorry for blaming the UPnP bundles! :-)
This bug was actually introduced by me, when I committed Didier's pom
file for the spellcheckscr example...I didn't even think about this issue.
Whenever we change the packaging of any subproject, we have to remember
to change the profile it is in. This is the second time we had issues
due to changing the packaging of a bundle, but forgetting to changes it
profile.
It will be nice if we can get a Maven fix for this so we can quit
running into these sorts of issues.
I will commit your patch and uncomment the UPnP bundles...
Thanks for looking into it.
-> richard
Stefano Lenzi wrote:
> Richard S. Hall wrote:
>> Francesco Furfari wrote:
>>>
>>> Richard S. Hall wrote:
>>>> The UPnP bundles were causing my build to fail (as pointed out to
>>>> me by Stephane), so I commented them out of the main pom file. Once
>>>> the issue is resolved, we need to uncomment them.
>>>
>>> Sorry to which bundles are you referring to?
>>> In the trunk there aren't dependencies between UPnP and MOSGi
>>> ... and actually they are not commented !!
>>> Are you talking about my sandbox?
>>
>> I tried to do a clean build of the trunk and I got an error which
>> says that it could not resolve a dependency for one of the UPnP
>> bundles...I don't remember which. It looked like the dependency was
>> on 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't
>> heard of such a version.
>>
>> Clear your .m2/repository and try to build from scratch using "ant"
>> in the trunk and see what happens...that is what I did.
> Hi All,
> we have just made some tests and we found that the problem resides
> in the org.apache.felix.examples.spellcheckscr project that uses the
> bundle packaging even if it's in the profile for that uses the
> osgi-bundle packaging. In fact if you look at your repository you may
> find also the wireadmin bundle installed as .osgi-bundle artifact
> instead of .jar due to the famous maven bug ^_^
>
> So we have solved the issue by defining the profiles for the
> examples pom.xml as you have done for the trunk pom.xml
>
> I have tried to send the patch but I get the following error message:
> Sending examples/pom.xml
> svn: Commit failed (details follow):
> svn: CHECKOUT of
> '/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403
> Forbidden (https://svn.apache.org)
>
> So I'll attach the patch :S
>
> Ciao,
> Stefano "Kismet" Lenzi
>
>
Re: UPnP bundles
Posted by Stefano Lenzi <ki...@interfree.it>.
Richard S. Hall wrote:
> Francesco Furfari wrote:
>>
>> Richard S. Hall wrote:
>>> The UPnP bundles were causing my build to fail (as pointed out to me
>>> by Stephane), so I commented them out of the main pom file. Once the
>>> issue is resolved, we need to uncomment them.
>>
>> Sorry to which bundles are you referring to?
>> In the trunk there aren't dependencies between UPnP and MOSGi
>> ... and actually they are not commented !!
>> Are you talking about my sandbox?
>
> I tried to do a clean build of the trunk and I got an error which says
> that it could not resolve a dependency for one of the UPnP bundles...I
> don't remember which. It looked like the dependency was on
> 0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't heard of
> such a version.
>
> Clear your .m2/repository and try to build from scratch using "ant" in
> the trunk and see what happens...that is what I did.
Hi All,
we have just made some tests and we found that the problem resides in
the org.apache.felix.examples.spellcheckscr project that uses the
bundle packaging even if it's in the profile for that uses the
osgi-bundle packaging. In fact if you look at your repository you may
find also the wireadmin bundle installed as .osgi-bundle artifact
instead of .jar due to the famous maven bug ^_^
So we have solved the issue by defining the profiles for the examples
pom.xml as you have done for the trunk pom.xml
I have tried to send the patch but I get the following error message:
Sending examples/pom.xml
svn: Commit failed (details follow):
svn: CHECKOUT of
'/repos/asf/!svn/ver/534951/felix/trunk/examples/pom.xml': 403 Forbidden
(https://svn.apache.org)
So I'll attach the patch :S
Ciao,
Stefano "Kismet" Lenzi
Re: UPnP bundles
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Francesco Furfari wrote:
>
> Richard S. Hall wrote:
>> The UPnP bundles were causing my build to fail (as pointed out to me
>> by Stephane), so I commented them out of the main pom file. Once the
>> issue is resolved, we need to uncomment them.
>
> Sorry to which bundles are you referring to?
> In the trunk there aren't dependencies between UPnP and MOSGi
> ... and actually they are not commented !!
> Are you talking about my sandbox?
I tried to do a clean build of the trunk and I got an error which says
that it could not resolve a dependency for one of the UPnP bundles...I
don't remember which. It looked like the dependency was on
0.1.0-incubator-SNAPSHOT of the maven-osgi-plugin, but I hadn't heard of
such a version.
Clear your .m2/repository and try to build from scratch using "ant" in
the trunk and see what happens...that is what I did.
-> richard
>
> francesco
>
>>
>> Two questions about the pom:
>>
>> 1. MOSGi has a dependency on Java 1.5 which causes the build to fail
>> under 1.4. Can we put MOSGi into a profile that only gets build on
>> > Java 1.5?
>> 2. Is there a way to modify the pom file so that the build does not
>> stop if one of the modules fails? Would this be a better approach?
>>
>> -> richard
Re: UPnP bundles
Posted by Francesco Furfari <fr...@isti.cnr.it>.
Richard S. Hall wrote:
> The UPnP bundles were causing my build to fail (as pointed out to me by
> Stephane), so I commented them out of the main pom file. Once the issue
> is resolved, we need to uncomment them.
Sorry to which bundles are you referring to?
In the trunk there aren't dependencies between UPnP and MOSGi
... and actually they are not commented !!
Are you talking about my sandbox?
francesco
>
> Two questions about the pom:
>
> 1. MOSGi has a dependency on Java 1.5 which causes the build to fail
> under 1.4. Can we put MOSGi into a profile that only gets build on
> > Java 1.5?
> 2. Is there a way to modify the pom file so that the build does not
> stop if one of the modules fails? Would this be a better approach?
>
> -> richard