I think that sounds reasonable, this is a good use case for
importing/exporting the same package...
As Clement noted, you could use the same approach for the log service if
you prefer to have a consistent approach, since I imagine the bloat is
negligible.
Either way, I am fine with it.
-
Carlos Herrando wrote:
Hello,
I've just build the trunk, but the HTTP service bundle isn't created.
Then if I write mvn install inside the http folder I get an error.
Could you help me to build the HTTP bundle?
This is precisely why it isn't being built from the trunk pom file... :-)
The
Carlos Herrando wrote:
OK, many thanks.
Keep in mind, if you want to use it, you might very well just be able to
modify its pom file to depend on a new servlet JAR, since we had been
using it with servlet 2.3 previously, I believe...
- richard
Richard S. Hall escribió:
Carlos Herrando
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
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
It doesn't sound unreasonable. The only slight caveat is that the
LocalRepository cannot really act like a real Repository, because it can
never provide a URL from which to retrieve locally installed bundles.
Perhaps this would never be an issue, thus making the point moot, but if
for some
As a follow up, this link talks a little bit about compatible licenses,
so we have to remember these types of issues when we are creating
dependencies on third-party code in our subprojects:
http://people.apache.org/~cliffs/3party.html
- richard
Richard S. Hall wrote:
Is the gnu.io
Jukka Zitting wrote:
On 5/4/07, stephane frenot [EMAIL PROTECTED] wrote:
There is a bug in the migration
if you co felix root you get an error, it works if you co directly
the trunk
$ svn co https://svn.apache.org/repos/asf/felix
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
I think this situation is not so straightforward.
The issue that we face here is that we have two different actors trying
to control what gets included in the resulting bundle JAR file, i.e.,
BND and Maven.
It is not the case that BND copies the raw resources, the issue is that
BND is
asaf.lahav wrote:
Hi all,
On an effort to migrate an application I have to OSGi model (using felix) I
would like to declare a number of packages as
org.osgi.framework.system.packages.
The question is whether there is a way to declare those packages with
explicitly declaring each.
e.g,
[
https://issues.apache.org/jira/browse/FELIX-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-261.
---
Resolution: Fixed
Assignee: Richard S. Hall
I have applied this patch. I think we can
Matthias,
I am wandering what the current status of your roadmap is?
I've read on some slides that you wanted to go to 1.0 soon?
Yes, we will be working on updating our roadmap very soon (i.e., within
a week)...
If so, what will be the changes to the current version?
As part of the next
[
https://issues.apache.org/jira/browse/FELIX-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497174
]
Richard S. Hall commented on FELIX-285:
---
One thing I was thinking about with respect to this patch
Yes, this is basically my thinking for the roadmap too.
I would prefer to get the installer back working, especially since it
will give us the possibility to install Felix as a daemon.
- richard
Karl Pauls wrote:
Dear Felix Community,
in order to follow-up on recent discussions - and our
Carlos Sanchez wrote:
A release as TLP is very important as it's going to be available in
the main maven repository instead of the incubating one which other
projects can't use to make releases.
I'd love to see the release of the bundle plugin to use it in the
Maven project.
The
[
https://issues.apache.org/jira/browse/FELIX-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-291.
---
Resolution: Fixed
Assignee: Richard S. Hall
I applied the patch. Clement, close
generated artifacts after their own package root in
our repo (e.g., org.apache.felix.bundleplugin-0.9.0.jar).
If the general view is that we should follow this convention (which I
wasn't aware of), then I will change it back.
- richard
Richard S. Hall wrote:
Richard S. Hall wrote:
Carlos Sanchez
[
https://issues.apache.org/jira/browse/FELIX-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-261.
-
Resolution: Fixed
Ok, this seems to be working for me, so I committed it (and am closing
with how Maven handles the
SNAPSHOT repo. I think the question you really mean to ask is, is there
some way I can scope my dependencies in the SNAPSHOT repo so that I only
get what I want from it rather than everything?
- richard
Regards,
Alin Dreghiciu
On 5/21/07, Richard S. Hall [EMAIL
not look
ugly...they perhaps need some work in this area now... :-)
- richard
J Aaron Farr wrote:
Richard S. Hall [EMAIL PROTECTED] writes:
Matthias Luebken wrote:
I suggest that you update the website felix.apache.org so that the
ongoing improvements are reflected on the website. If you
Chris Custine wrote:
I am in the process of reworking the Apache Directory installers,
which the
Felix installers project is based on, so I could see about fixing up the
installers here in the next couple of weeks. Are there any changes
you need
for the setup or do you just need the existing
Carlos Sanchez wrote:
On 5/21/07, Richard S. Hall [EMAIL PROTECTED] wrote:
Personally, I would love for us to have groupId=org.apache.felix and
artifactId=subproject-name, but the reason why we didn't follow this
approach in the first place was that we wanted our artifacts to be named
Carlos Sanchez wrote:
On 5/21/07, Richard S. Hall [EMAIL PROTECTED] wrote:
I don't care how it is stored in the repository. The issue I have is
that the generated artifact in target/ has a name...I don't want to
manually have to change the name after doing mvn clean
install...however
On May 21, 2007, at 5:50 PM, Rick Litton wrote:
Richard S. Hall wrote:
But, ultimately, there is no way to avoid holes.
That's unfortunate. I know it shouldn't bother me but my concern is
that
once we get into the high 2-digit and even triple-digit numbers it will
become too noticeable
. :-)
Feel free to post your thoughts on a solution for input...pesky system
admins...
- richard
-Original Message-
From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 2:56 PM
To: dev@felix.apache.org
Subject: Re: [jira] Commented: (FELIX-285) Make resolver
After thinking about it for a minute, I thought there was a routine
somewhere in Felix to parse delimited quoted strings...turns out there
is in the manifest parser.
I will try to create a patch tomorrow...
- richard
On May 21, 2007, at 6:54 PM, Richard S. Hall wrote:
I think that would
just pull ST into their
bundle. But if everyone were to do this, then the savings we see by not
having ST in the framework JAR would be quickly outweighed by the
multiple copies of ST embedded into all of the bundles that use it.
We'll try it for now and see how it goes! :-)
- richard
Richard S
MO On May 22, 2007, at 18:07 , Richard S. Hall wrote:
Since the overall response has been positive (even though I am
mostly in the excess cruft camp with Eric), I have gone ahead and
added it.
MO I'm also in that camp, but I was at a conference (without internet)
MO
Marcel Offermans wrote:
On May 22, 2007, at 18:07 , Richard S. Hall wrote:
Since the overall response has been positive (even though I am mostly
in the excess cruft camp with Eric), I have gone ahead and added it.
I'm also in that camp, but I was at a conference (without internet)
today, so
Hey everyone,
I just received word that my proposal for ApacheCon on embedding Felix
was accepted. That means I need to get everyone to show up so I am not
talking to an empty room! I guess that also means that I will need to
start working on the slides... :-o
Anyone else make an
Stuart McCulloch wrote:
On 22/05/07, Richard S. Hall [EMAIL PROTECTED] wrote:
Clement Escoffier wrote:
We (in fact, Maxime Vincent) have developed an independent Maven
plugin installing bundles in a local OBR. This plugin is very close to
the Felix-219 patch. However, there is a difference
Niclas Hedhman wrote:
On Monday 21 May 2007 23:23, Richard S. Hall wrote:
The Felix PMC has voted to ask Clement Escoffier to be a committer
He wasn't already?? In that case; PMC, about time! ;o)
Well, you know, he's French, so we had to punish him for a while... ;-)
- richard
info that you need.
Actually, you raise a good point...perhaps we can discuss it offline,
but a real-world usage scenario might be very worthwhile.
- richard
Regards
-- Rob
-Original Message-
From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Tue 22/05/2007 19:51
though if it's
relevant
- and let me know if there's any specific info that you need.
Regards
-- Rob
-Original Message-
From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Tue 22/05/2007 19:51
To: dev@felix.apache.org
Cc:
Subject
Hey everyone,
I will try not to let fame go to my head, but a new Feathercast podcast
was just released featuring an interview with me about Felix... :-)
http://feathercast.org/?p=46
The interview doesn't really say anything new for most of us on the
mailing lists, but perhaps it will
Carlos Sanchez wrote:
it was actually already there
Yeah, I would think so, because it has been building fine for me and I
have wiped out my local repo many times recently...
- richard
On 5/23/07, Carlos Sanchez [EMAIL PROTECTED] wrote:
that repo is not added on purpose to reduce build
I think Alin just wants to create the 300th issue... ;-)
- richard
Alin Dreghiciu (JIRA) wrote:
backport-util-concurrent 3.0 wrapping
-
Key: FELIX-299
URL: https://issues.apache.org/jira/browse/FELIX-299
Clement Escoffier wrote:
Hello,
Tim has made a good and clear comparison. I add some comment on what
we can obtain if we merge all ideas together.
I quickly took a look at what Clement/Maxime has done. This is how I
would compare them. Clement, please correct me if misrepresent
anything.
Alin Dreghiciu wrote:
I've just added some new packages to be wrapped to Felix Commons and I
was
wondering about the deployment strategy/timing on the snapshot repository
for Felix Commons since the latest published artifacts are from 16
March. Is
the build/deploy for Felix Commons run only
[
https://issues.apache.org/jira/browse/FELIX-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-300.
---
Resolution: Fixed
Assignee: Richard S. Hall
I applied the patch. Clement, please close
been edited by Richard
S. Hall (May 29, 2007).
(View
changes)
Content:
Welcome
to Apache Felix
Welcome to the Apache Felix homepage.
News
Felix Feathercast podcast
available. (May 23, 2007)
Felix has graduated
Anyone planning on attending the OSGi Community Event in Munich this
June 26/27th? The agenda is here:
http://www.osgi.org/news_events/2007_06_communities/agenda.asp
I will be there.
- richard
Issue Type: Improvement
Components: Framework
Affects Versions: 1.0.0
Reporter: Richard S. Hall
Priority: Minor
When searching for resources in a bundle for Bundle.getResources(), Felix
searches the bundle class path and returns any matching resources
Hello everyone,
The Felix PMC members offered Niclas Hedhman a spot on the Felix PMC and
he has accepted.
We all appreciate Niclas' active involvement in both OSGi- and
Apache-related issues and look forward to his continued involvement in
making Felix a success.
Congratulations Niclas
Please ignore...
Bundle Plugin
Reporter: Richard S. Hall
Priority: Minor
The bundle plugin appears to be converting version numbers incorrectly. For
example:
0.9.0-incubator-SNAPSHOT
Is being converted to:
0.9.0.incubator_SNAPSHOT
Only the first '-' should be converted
[
https://issues.apache.org/jira/browse/FELIX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504409
]
Richard S. Hall commented on FELIX-38:
--
Yes, you are in the correct place.
Although we are planning to deal
On Jun 15, 2007, at 7:51 PM, Marcel Offermans wrote:
On Jun 15, 2007, at 21:37 , Richard S. Hall wrote:
I, for one, like how the wiki formats code blocks (with syntax
highlighting, etc.) and with more color. Our generated static
pages look cute boring and mundane by comparison.
I think
Components: Maven Bundle Plugin
Reporter: Richard S. Hall
The following is a proposal for how to support embedding dependency JAR files
in the bundle plugin. The general approach is a slightly modified version of a
proposal by Peter Kriens. The idea is to add a mechanism to deal
Well, from my understanding of the situation, I think that embedding the
native library should be reasonably straightforward using the Bundle
Plugin...you just need to copy the native library into your bundle using
Include-Resource, assuming that the native library is a resource in
your
I won't claim to totally understand your scenario, but if your bundles
are using external packages, then the bundle must import them.
Also, it is worthwhile to understand the distinction between the two
configuration properties for dealing with class path packages:
[
https://issues.apache.org/jira/browse/FELIX-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507219
]
Richard S. Hall commented on FELIX-310:
---
Actually, an initial version of such a maven plugin already exists
information I will be glad to hear,
regards,
Kostas
Karl Pauls wrote:
and maybe tell us with which version of Felix you've been trying
(0.8.0 or trunk - if trunk which revision/date)?
regards,
Karl
On 6/21/07, Richard S. Hall [EMAIL PROTECTED] wrote:
Yes.
The biggest issue in switching from Oscar
Todd Nist wrote:
Richard,
Thanks for the follow up and clarification on the two configuration
properties. I like the modularity of OSGi and the enforcement of
defining the precise dependencies.
The thing that really confused me was when I went to boot delegation,
and removed the explicit
got it working! :-)
- richard
Regards,
Todd
-Original Message-
From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 26, 2007 8:23 AM
To: dev@felix.apache.org
Subject: Re: Class load error with embedded bundle
Todd Nist wrote:
Richard,
Sure, I will be glad
Felix,
Did you also deploy main.jar? When framework.jar it generally means
that we should deploy main.jar too, since they are essentially the
same JAR minus the launcher.
- richard
On Jun 29, 2007, at 10:55 AM, Felix Meschberger wrote:
Hi Rajini,
I deployed a new build of the
On Jun 29, 2007, at 3:11 AM, Felix Meschberger (JIRA) wrote:
[ https://issues.apache.org/jira/browse/FELIX-314?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12509034 ]
Felix Meschberger commented on FELIX-314:
-
stephane frenot wrote:
I will have a look at this tomorrow,
I think MOSGi should compile with jdk 1.4
It never has...java.management is not in JDK 1.4...right?
- richard
/stephane
2007/7/2, Richard S. Hall [EMAIL PROTECTED]:
After Stephane converted the MOSGi bundles to the new plugin
Carsten Ziegeler wrote:
Richard S. Hall worte
I know that Enrique is still interested in Felix Commons, but he
doesn't have much time. We really need some interested people to get
involved here...I believe there are a few submitted POM files that
have yet to be committed too...
Looking
Just to let everyone know, I just committed a reasonably major
refactoring of the Felix class. The Felix class now implements the
Bundle interface; thus, when you create an instance of Felix you are
actually creating an instance of the System Bundle. This gives Felix a
nice, standard API for
[
https://issues.apache.org/jira/browse/FELIX-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-309.
---
Resolution: Fixed
Assignee: Richard S. Hall
I have applied this patch. Carlos, please
Karl and I were discussing the maven-bundle-plugin release and a
question came up.
Ultimately, our sub-projects all use the parent Felix pom file, but
unlike most projects our modules do not comprise a single application
that gets released at once. Instead, each sub-project module will be
Pierre Parrend wrote:
Pierre, do you have an ICLA on file at Apache?
not yet. I can make one if necessary, or simply commit my code through
Stephane.
I think Karl will need to look into the patch to see how to incorporate
it into the trunk, no matter what. However, it would probably
Marcel Offermans wrote:
On Jul 9, 2007, at 19:52 , Richard S. Hall wrote:
Since the sandbox is for conducting experiments on code that might
never be officially released into the trunk, perhaps we shouldn't be
using the official package space...for example, we could use
something like
Components: Framework
Affects Versions: 1.0.0
Reporter: Richard S. Hall
Now that the framework implements the Bundle interface, it must also perform
the same security checks as BundleImpl. This results in code duplication. We
should think about how we can factor
[
https://issues.apache.org/jira/browse/FELIX-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-325:
--
Summary: Factor out security checks from the framework/system bundle code
(was: Factory out
Just wanted to let you know that I verified the behavior that you
describe, so now I will look at why it is doing that...
- richard
Rajini Sivaram wrote:
Hello,
I have a test which uses two versions of two bundles:
CustomerV1:
Import-Package: org.osgi.framework,
Niclas Hedhman wrote:
On Tuesday 10 July 2007 01:52, Richard S. Hall wrote:
Should we have an sandbox package name space?
Agree.
Well, it looks like we have Niclas and myself as +1 and Marcel as
-1/0...can we come to a consensus about this?
- richard
Marcel Offermans wrote:
On Jul 11, 2007, at 16:45 , Richard S. Hall wrote:
Niclas Hedhman wrote:
On Tuesday 10 July 2007 01:52, Richard S. Hall wrote:
Should we have an sandbox package name space?
Agree.
Well, it looks like we have Niclas and myself as +1 and Marcel as
-1/0...can we
[
https://issues.apache.org/jira/browse/FELIX-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-324.
-
Resolution: Fixed
Modified the Felix constructor to accept a Map rather than a PropertyResolver
Carsten Ziegeler wrote:
I just wanted to let you know that I'm currently working on an
implementation of the preferences service. I hope to get it finished in
the next days.
There is currently one (minor) point unclear to me. Is it allowed to
call removeNode() on the parent node of the
For those that don't know, these release candidates are just tags in
our SVN repo; they can be found here:
http://svn.apache.org/repos/asf/felix/releases
- richard
On Jul 12, 2007, at 5:25 PM, Karl Pauls wrote:
Hi all,
Rick and I have been working some more on the 1.0.0 release. I
Another possibility is to use Bundle Plugin to suck out the packages you
need from compendium and then you can import whatever version of servlet
you want...
- richard
Clement Escoffier wrote:
Hello,
As the resolving of package versions has been fixed in Felix, it
appears a small problem
Pierre Parrend wrote:
Hello all,
I have made a little patch to enable the execution of Felix with Java
permissions - needed are a java.policy file, and suitable URL handlers for the
'file:' and 'http:' protocols.
Let me know if this can be useful. Is there an open jira issue for this ? I
[
https://issues.apache.org/jira/browse/FELIX-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-327.
---
Resolution: Fixed
Assignee: Richard S. Hall
Yep, that does indeed appear to be a bug. I
+1
I tested the signatures and md5 sums and everything worked for me, but
we can always use more verifications...
- richard
Karl Pauls wrote:
Hi all,
Rick and I woud like to call a vote on the sub-projects for the 1.0.0
release. These sub-project releases are the initial root dependencies
[EMAIL PROTECTED] wrote:
Niclas wrote:
Second thing; The reason for the negative vote is a somewhat non-compliant
release format.
* LICENSE and NOTICE must be in root directory of the tarballs of the
source.
Apache is about Open SOURCE, and there are no requirements to distribute
a
Let me be the first to say, I think it looks great...a big improvement.
And I think I like logo_felix01.png best... :-)
Good work all involved!
- richard
Marcel Offermans wrote:
Since we're close to our first release, it's important our website is
updated. The last couple of weeks we have
BJ Hargrave wrote:
The link for the OSGi spec download on your home page is wrong. The proper
link is http://www2.osgi.org/Specifications/HomePage
Thanks.
- richard
Interesting...for some reason it is tied to JDK 6...
http://davideraccagni.madprogrammers.org/f06/index.html
- richard
Richard S. Hall wrote:
Karl Pauls wrote:
On 7/15/07, Niclas Hedhman [EMAIL PROTECTED] wrote:
On Sunday 15 July 2007 07:56, Karl Pauls wrote:
So how do we proceed from here? I'd personally like to pause the vote
and update the source release artifacts to include the LICENSE and
NOTICE files
+1 again
Karl Pauls wrote:
+1 (restated :-)
On 7/16/07, Marcel Offermans [EMAIL PROTECTED] wrote:
+1 (restated)
Yes, the solution here is Include-Resource...if you look at the
framework pom.xml file you can see that we use this to copy our patches
over the OSGi classes.
Regarding class path ordering, I thought Maven set up the class path so
that dependencies came before the target classes anyway...at
Karl and I were talking about this during the release. We kept things
like this simply because we were following the previous pattern of the
trunk depending on the latest versions. However, we both felt this
wasn't a good idea and that this needed to be changed, we just didn't
want to take the
As part of the incubator process, the Felix project defined a set of
community roles and processes to explain how participation in the Felix
project works. This document needs to be updated now that Felix has
graduated from the incubator. The following is the updated document:
+1
- richard
Richard S. Hall wrote:
As part of the incubator process, the Felix project defined a set of
community roles and processes to explain how participation in the
Felix project works. This document needs to be updated now that Felix
has graduated from the incubator. The following
Niclas Hedhman wrote:
On Tuesday 24 July 2007 00:04, Richard S. Hall wrote:
For the most part, the document is the same as before, but the incubator
references are removed and some points are clarified further. Please
vote on accepting this document:
[x] +1 - Accept community process
Regarding releasing Commons bundles, I share Marcel's concern that we
need to have a controlled release process so that we can have some sort
of quality assurance about what we are releasing.
However, I do agree with Carsten that it makes sense to separate Commons
off from the other
Actually, Commons is the perfect place for javax.servlet, it just didn't
exist at the time.
However, we actually need version 2.1 of javax.servlet for the HTTP
Service, but I imagine that other people might want newer versions of
javax.servlet. Did we devise our approach for maintaining
In the past we voted on contributions, but since this was basically
developed in a Felix sandbox, I do not think a vote is actually
necessary if we have consensus to promote it.
Let's give it a few days for people to voice their opinions and move it.
I guess the likely target package will be:
Yes, I think we need license and notice files for all of them...
- richard
original message:
-
I think we have to add the license and notice file to all commons
modules as well.
WDYT?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/FELIX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-177.
-
Resolution: Fixed
I think this issue can be closed since the contructor for Felix has been
Herko ter Horst wrote:
Hello guys,
The vote is successful. We will make the release artifacts available
as soon as possible.
I've been watching developments on Felix from the sidelines (I've
worked with Oscar OSGi in the past) and I must say I'm impressed by
the progress that's been made.
[
https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517773
]
Richard S. Hall commented on FELIX-308:
---
I think that sounds reasonable. Certainly a good start. :-)
Add
Alan D. Cabrera wrote:
I'm trying to grok what happens to bundles that have sealed packages
which get extended via the split package mechanism. The spec
doesn't seem to address this situation; maybe it does and I missed it.
Can someone explain what should happen?
Just speaking off the top
Stefano Lenzi wrote:
Hi All,
I'd like to know if anyone of you have spent some time on the patch
FELIX-219 available on JIRA. IMHO we should apply it, but before doing
that on my own I'd like to get some feedback from you :)
Please note that the above patch affects also the OBR bundle and
Niclas Hedhman wrote:
On Friday 10 August 2007 23:59, Richard S. Hall wrote:
Another thing is separation of concerns. People may want to make really
fancy launchers, so it make sense to keep the launcher separate. I
prefer a simple launcher, but the idea was that we could also have other
faculty, staff and student body at Tufts. Have an
enjoyable experience!
p.s. it may be a good time to enroll in those additional courses I have been
pondering :)
Best wishes,
-Barron Logan
On 8/14/07, Richard S. Hall [EMAIL PROTECTED] wrote:
I just wanted to let everyone know that I have
Sorry I didn't see this thread before my other reply...anyway...
+1 to what Marcel said. :-)
- richard
Carsten Ziegeler wrote:
Marcel Offermans wrote:
On Aug 15, 2007, at 13:07 , Carsten Ziegeler wrote:
Argh, sure - yes I'll do that - I thought that I had turned off my
Eclipse
Perhaps you should have just revert to the prior revisions, because if
you miss any places like below it could create some difficult bugs to
track down...
- richard
[EMAIL PROTECTED] wrote:
Author: cziegeler
Date: Wed Aug 15 04:42:55 2007
New Revision: 566109
URL:
1 - 100 of 3817 matches
Mail list logo
