On 25/01/2008, Patrick Shea <[EMAIL PROTECTED]> wrote:
>
> Unless I don't fully understand, when I deploy my bundle to my maven
> remote repository, the repository.xml file still refers to the file in my
> local repository.
>
> So when I try to install my bundle through servicemix runtime it gets t
On 25/01/2008, Patrick Forhan <[EMAIL PROTECTED]> wrote:
>
> On Jan 24, 2008 11:49 AM, Stuart McCulloch <[EMAIL PROTECTED]>
> wrote:
> \> ok, the OBR exception is caused by the custom localRepository setting:
> >
> >file://c:/bjc/javadown/m2repository
> >
> > for now changing this to use three
Richard S. Hall wrote:
Stefano Lenzi wrote:
Sahoo wrote:
Earlier I sent a mail to users alias, but I guess that email thread
was not appropriate for this issue.
I would like to know the license under which the following two
artifacts are distributed in Maven2 standard
repository(http://repo1.
Stefano Lenzi wrote:
Sahoo wrote:
Earlier I sent a mail to users alias, but I guess that email thread
was not appropriate for this issue.
I would like to know the license under which the following two
artifacts are distributed in Maven2 standard
repository(http://repo1.maven.org/maven2/) :
*o
Unless I don't fully understand, when I deploy my bundle to my maven remote
repository, the repository.xml file still refers to the file in my local
repository.
So when I try to install my bundle through servicemix runtime it gets the
repository.xml and tries to get the file from the uri that p
Sahoo wrote:
Earlier I sent a mail to users alias, but I guess that email thread was
not appropriate for this issue.
I would like to know the license under which the following two artifacts
are distributed in Maven2 standard
repository(http://repo1.maven.org/maven2/) :
*org.osgi:osgi_R4_core*
Earlier I sent a mail to users alias, but I guess that email thread was
not appropriate for this issue.
I would like to know the license under which the following two artifacts
are distributed in Maven2 standard
repository(http://repo1.maven.org/maven2/) :
*org.osgi:osgi_R4_core* and *org.osgi:
Sahoo wrote:
Hi,
The following line in section #3.7 (Resolving Process) in R4 spec is
not clear to me. I appreciate if someone can explain it.
/A bundle can be resolved if the following conditions are met:
All its mandatory imports are wired
All its mandatory required bundles are available an
On Jan 24, 2008 11:49 AM, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
\> ok, the OBR exception is caused by the custom localRepository setting:
>
>file://c:/bjc/javadown/m2repository
>
> for now changing this to use three slashes after file: should fix the
> exception:
>
>file:///c:/bjc/jav
Hi,
The following line in section #3.7 (Resolving Process) in R4 spec is not
clear to me. I appreciate if someone can explain it.
/A bundle can be resolved if the following conditions are met:
All its mandatory imports are wired
All its mandatory required bundles are available and their export
On 25/01/2008, Patrick Forhan <[EMAIL PROTECTED]> wrote:
>
> > Could you provide the output from "mvn -X ...etc..." as this will turn
> on
> > the maven debug and show what versions of plugins/deps are being
> resolved.
ok, the OBR exception is caused by the custom localRepository setting:
fi
On 25/01/2008, Patrick Forhan <[EMAIL PROTECTED]> wrote:
>
> Is this normal? I get a bunch of "Exception while updating OBR" and
> then a missing on
> org.apache.felix:org.apache.felix.shell:jar:1.1.0-SNAPSHOT. The first
> step, "mvn -Dpackaging=plugins install" seemed to work just fine.
Could
Is this normal? I get a bunch of "Exception while updating OBR" and
then a missing on
org.apache.felix:org.apache.felix.shell:jar:1.1.0-SNAPSHOT. The first
step, "mvn -Dpackaging=plugins install" seemed to work just fine.
Thanks,
Pat.
--
Defy mediocrity.
C:\Documents and Settings\paf2009\Desk
Patrick Forhan wrote:
On Jan 21, 2008 9:11 AM, Richard S. Hall <[EMAIL PROTECTED]> wrote:
Reading that whole thread, though, it goes on to say that this appears
to be an issue that impacts Felix, KF, and Equinox when run from
Eclipse, no? Do we have more issue to believe that this is now a Fe
> We are actually running 1.0.0 of felix. I hope to get the latest
> trunk and try it today. I'm also trying to put the tui bundle last to
> see if I can avoid the problem.
Related note: I should mention that activation seems to work just
fine. All our gui stuff, however, happens due to Declara
On Jan 21, 2008 9:11 AM, Richard S. Hall <[EMAIL PROTECTED]> wrote:
> Reading that whole thread, though, it goes on to say that this appears
> to be an issue that impacts Felix, KF, and Equinox when run from
> Eclipse, no? Do we have more issue to believe that this is now a Felix
> issue?
I did re
> Karl Pauls wrote:
> >> Hi,
> >>
> >> Are the release schedule and criteria for upcoming release (major or
> >> minor) of Felix published any where? The roadmap page does not say much.
> >>
> >
> > True. This is a good reminder for me to updated it.
> >
> >
> Looking forward to the update.
> >
> >
Karl Pauls wrote:
Hi,
Are the release schedule and criteria for upcoming release (major or
minor) of Felix published any where? The roadmap page does not say much.
True. This is a good reminder for me to updated it.
Looking forward to the update.
When is the next major release of
> Hi,
>
> Are the release schedule and criteria for upcoming release (major or
> minor) of Felix published any where? The roadmap page does not say much.
True. This is a good reminder for me to updated it.
> When is the next release, which I think is 1.0.2, scheduled to come out?
I plan to cut t
Hi,
Are the release schedule and criteria for upcoming release (major or
minor) of Felix published any where? The roadmap page does not say much.
When is the next release, which I think is 1.0.2, scheduled to come out?
When is the next major release of Felix happening and what are the
drivers
20 matches
Mail list logo
