agent
(e.g. New Equinox Provisioning, OBR, old Eclipse Update Manager etc.). I
do not think Initial Provisioning implementation should depend on the
Equinox provisioning work. Thoughts?
Tom
Jeff McAffer [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/08/2007 04:50 PM
Please respond
i thought we were all already doing #2...
Jeff
Thomas Watson [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/11/2007 01:42 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] What to do with 3.3.1 candidate bugs
I released some changes to the way that the metadata generator is run as
well as some refactorings of Repo abbreviations and inconsistencies in
class names. Generator is now a real application (no longer used the
system properties) and should be somewhat simpler to run/manage. If you
have
Now onto the answers to the questions:
This appears to be where install handler equivalent functionality would
be
performed
This would only be true if what you were trying to achieve in the
install handlers were OS level things. Other things may need to be done
by
other touchpoints.
Great! Thanks Tom. Can someone do this for the provisioning projects as
well? Some of them have the some of the right settings but it would be
good to have a complete pass over them to ensure consistency etc.
Jeff
Thomas Watson [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08/21/2007
I see.
- A user installs both CDT and DSDP at the same time and sees this set as
C tooling. An entry points named C tooling is created.
Who picked the name C tooling (and when)? if the user in this scenario
originally picked CDT and DSDP then they must have picked the overall
name.feels
I think I am more confused now. On the one hand it seems that the name of
the entry point is picked at install time by the user but later you say
entry points are just IUs with a special tag that the UI decides to show
by default. And further contradictory As for the name of entry point
As Labour (or Labor) Day looms on the horizon signalling the end of summer
it is time to start planning that Fall travel schedule. What schedule
would be complete without a trip to Ottawa at the end of September for the
Equinox Summit?
http://wiki.eclipse.org/Equinox_Summit_2007
The
I thought we already had this. The current profile was called this I
think (or perhaps self). I recall adding the function when I did the
provisioning helper etc.
Jeff
Pascal Rapicault/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08/27/2007 09:16 PM
Please respond to
Equinox
I finally did something that has been on my list for quite some time.
Inspired by Peter Kriens' FileInstall bundle, I made a DirectoryWatcher
that, as the name implies, watches a directory and installs, uninstalls,
configures, ... things that are dropped into/removed from/changed in the
dir.
for this
project :-)
PaScaL
From: Jeff McAffer/Ottawa/[EMAIL PROTECTED]
To: Equinox development mailing list equinox-dev@eclipse.org
Date: 08/30/2007 08:58 AM
Subject:Re: [equinox-dev] [prov] directory watcher
For the most part
: |
|
--|
|Jeff McAffer/Ottawa/[EMAIL PROTECTED
looking through the artifact repo code I noticed that the way it is now,
MirrorRequests get/are given a RequestHandler and then that is used to do
the actual file transfer. Is there a usecase that drives the repo
communication policy to be externally defined? That is, is there a reason
that
that delivers updates like torrents do? ECF can
do that, but can the current ECFHandler do it?
So my conclusion is that it would be good to have a solution that allow
to define request handlers externally.
Stefan
Jeff McAffer wrote:
looking through the artifact repo code I noticed that the way
the current ECFHandler do it?
So my conclusion is that it would be good to have a solution that allow
to define request handlers externally.
Stefan
Jeff McAffer wrote:
looking through the artifact repo code I noticed that the way it is
now, MirrorRequests get/are given a RequestHandler
Thanks for all the comments and info Scott (and others). First, this
thread started with something completely unrelated to ECF. I was just
interested in whether the call to RequestHandler.download() happen in the
MirrorRequest or somewhere in the ArtifactRepository (or elsewhere). In
the
equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] [prov] ECF in P2, was request handler orientation
Jeff, shall I start to revive the push model? I think I have some backups
;-)
Stefan
Jeff McAffer wrote:
Thanks for all
I've found
were dead.
OSGi services and the whiteboard pattern sounds to me like a natural
replacement for things like the CallbackHandler extension point. But I
don't know the other approaches (yet).
Regards
Arthur
Jeff McAffer wrote:
All of the standard discussions should follow here
We are three weeks from the Equinox Summit (see
http://wiki.eclipse.org/Equinox_Summit_2007) and the Foundation events
team needs to start finalizing catering and other arrangements. I know
that there are several people who have said they would like to come but
have not yet registered. If you
.
dj
Jeff
McAffer/Ottawa/IB
[EMAIL PROTECTED]
To
Sent by: Equinox development mailing list
equinox-dev-bounc equinox-dev
Thanks to Stefan we have been introducing the notion of ProcessingSteps
to munge the content as it is downloaded from an artifact repository. This
allows for things like inline MD5 digest checking, unpack200 processing,
delta merging, signature checking, ... All great stuff. Pascal just
As you may know, we used to have the JARProcessor embedded in the bowels
of Update manager. Turns out that there are several uses for the
processor (pack200 support, signing, verifying, ...) and having this
function as a stand-alone bundle would be a good thing(tm). So in the
p2 work we did
Just to nip this in the bud...
The proposed, voted on and approved name is p2 not P2.
Jeff
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
BJ Hargrave wrote on 09/12/2007 03:33:59 PM:
I am not sure this is true. According to portal.eclipse.org, I am a
committer on eclipse, eclipse.equinox and eclipse.incubator. Thus it
would
seem to me we only need to elect one to eclipse.equinox to have commit
rights to all the framework
yes but under the new plan you pointed out, the commit rights will be
managed by groups and groups will have a 1:1 relationship to components
and components will have associated leads, bugzilla entries, websites, ...
This is alot of infrastructure to put in place for each bundle.
We did
: +1 386 848 1781
mobile: +1 386 848 3788
From:
Jeff McAffer [EMAIL PROTECTED]
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
2007-09-12 16:03
Subject:
Re: [equinox-dev] Equinox-Bundles component is getting crowded
yes but under the new plan you pointed out, the commit
BJ Hargrave wrote on 09/13/2007 03:13:56 PM:
Why not reify the structure we think we have?
I think part of the issue is that there is no common view of the
structure
we think we have to reify it.
I agree that there is likely no common view currently. That does not mean
there cannot be
and back end and not in itself guarantee that people would easily
find what they are looking for.
Arthur
Jeff McAffer wrote:
to me it is neither of these options. It is about community and
clarity
for our consumers. Walking up to Equinox you just have a sea of
bundles. Add in the p2
Great. I will request a move review. Likely it will not happen for a
couple weeks because of ESE etc. In the mean time, if someone wants to
look at/use the code they can go to OHF and play as they do today. I
agree with Simon coming on as a committer.
Jeff
Grahame Grieve [EMAIL
I'd suggest you try using the PDE manifest clean up wizard as well. It
should detect all the right imports and uses required by the code in your
bundle.
In the future look also for some help from the PDE API tools. These will
be able to report on what exactly your bundles consume from and
As Pascal mentioned SAT would be just one element available from the
Equinox project. Felix has ipojo, jmood, mosgi, ... and other things that
are add-on elements people can use in developing their bundles. SAT is no
different. If (and I mean if) SAT is adopted by parts of the Eclipse
: |
|
--|
|Jeff McAffer/Ottawa/[EMAIL PROTECTED
.
Jeff McAffer/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/12/2007 04:05 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev][prov] Staged update
Thanks
updates automatically (yes/no), etc.
Jeff McAffer/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/14/2007 11:08 AM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev
for use on the web could make this more intuitive.
(Susan, I haven't looked at the new UI yet, so please forgive me if some
of this is no longer
applicable)
-Brett
Jeff McAffer wrote:
I agree that forcing people to browse via Elcipse is unfortunate. It
will address some of the usecases
have a stable metadata file format. The launcher metadata
could be authored at develop time, and checked into CVS alongside the
actual launcher files.
Jeff McAffer/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/23/2007 02:44 PM
Please respond to
Equinox development mailing list
Please add it to both PSF files. I noticed it in one but not the other.
As a point of interest, we should try to keep things sorted in the PSFs so
they are easier to read/manage. The new test entry seems to have been
inserted somewhat randomly.
Jeff
Pascal Rapicault/Ottawa/[EMAIL
One of the things that I learned at ESE was that the Target Management
folks in DSDP have a number of interesting infrastructure bits for talking
to and manipulating remote systems. Some of these might be interesting
for us in implementing bootstrap agents or direct transfer/communications
would it be hard to continue to produce the server downloads? I'm
tihnking that if someone wants to test but not hit eclipse.org it would be
good ot have the content local.
Jeff
DJ Houghton/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/26/2007 03:15 PM
Please respond to
Equinox
Just to be really clear, the presence of javax.* package is not
necessarily an EE issue. As an example, javax.management (JMX API) is
part of Java 1.5 but there are third party implementations available that
allow JMX to be used on Foundation 1.0 systems. As such, one can run a
bundle that
. This will be more of an issue when
we are running on the Eclipse project test machines that have various OSes
and file system layouts.
Jeff McAffer/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/12/2007 08:53 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
are converting an existing Update site
2) should we provide a similar mechanism in p2
3) if so, where does this play in the UI
Jeff
- Forwarded by Jeff McAffer/Ottawa/IBM on 12/04/2007 10:04 PM -
Dejan Glozic/Toronto/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
12/04/2007 11:00 AM
Please
It may be interesting to consider that during the provisioning operation,
we do (may) know enough context to describe updates vs. uninstall/install.
The problem we have now is that we lose information between the
Director/Engine and the simple configurator. Not sure exactly how to
retain the
pages appear under /Equinox or /Eclipse/Equinox would
make sense to me.
Jeff McAffer/Ottawa/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/17/2007 04:55 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] Fw
Hey James, this is alot of good information. Would you have a chance to
update the shared install scenarios document to highlight some of the
points? My gut feeling from reading your comments is that most of what
you suggest is do-able wrt the underlying infrastructure but the current
Dave,
Try and get the stuff from Eclipse rather than Maven. We have no idea
what is in that maven repo nor do we have any control over the form of the
dependencies that might be listed in the maven markup. Teh commons logging
bundle that comes from Eclipse does have version numbers so I
Subject
Re: [equinox-dev] Jetty and commons logging
Jeff McAffer wrote:
Try and get the stuff from Eclipse rather than Maven.
Oops, my apologies. Where is the Maven repo at Eclipse then? That one at
repo1.maven.org was the nearest thing I could find.
Dave.
--
View this message
mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] Jetty and commons logging
On Jan 5, 2008 2:38 PM, Jeff McAffer [EMAIL PROTECTED] wrote:
Dave, there isn't one. For the most part Eclipse teams use the PDE
tooling
/2008 01:35 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] Jetty and commons logging
On Jan 6, 2008 1:18 AM, Jeff McAffer [EMAIL PROTECTED] wrote:
I won't disagree
://www.apache.org/dev/release-publishing.html
Although this wouldn't be what you'd be doing, I'm fairly certain the
process would be similar.
Hope this helps all involved...
On Jan 6, 2008, at 5:29 PM, Jeff McAffer wrote:
Hey Alex,
Please note that I started my reply by saying I don't disagree. The
point
by: [EMAIL PROTECTED]
01/08/2008 04:21 AM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] Maven and all that [was: Jetty and commons logging]
On Jan 7, 2008 10:33 PM, Jeff
adaptor for p2. Would you agree that the simplest way to do
that is probably to write it on top of the OBR API's and the Felix
bundle repository implementation?
- thomas
Jeff McAffer wrote:
We currently do host an OBR repo with the major releases. Don't
remember the URL but the required
could detect that the API package has
changed since last release and needs to be incremented. Does the new API
tooling currently do something like this for Bundle-Version?
Tom
Jeff McAffer ---01/11/2008 02:17:11 PM---Tom raises a good point that we
keep letting slide. Are we going to ensure
that the API package has
changed since last release and needs to be incremented. Does the new API
tooling currently do something like this for Bundle-Version?
Tom
Jeff McAffer ---01/11/2008 02:17:11 PM---Tom raises a good point that we
keep letting slide. Are we going to ensure that all export
Recently I was reviewing the Equinox project, the direction and the
community around it. One of the things that stood out for me is that Tom
Watson has been quietly leading vast swaths of the activity in Equinox
from the framework and service implementations to the OSGi spec work and
areas in
From Ian in the committer list. There might be some input needed here
from p2 if we are going to produce installers etc.
Jeff
Dear Eclipse Committers
We would like to encourage more participation in the creation of the
packages created by the Eclipse Packaging Project. The goal is to 1)
In case you do not read my blog or PlanetEclipse...
http://dev.eclipse.org/blogs/jeff/2008/01/24/movin-on-well-sorta/
One thing to add the message is my new coordinates. My new email
address is first name at code9.com (the source of this message).
Note also that my bugzilla id will change
right but there is the practical detail that the exe you need comes with
Java 5 or later and the licensing does not likely allow you to ship just
the unpack200 exe. But that is a matter for someone's legal team. As
John says, the unpack support simply cares whether or not the exe is
there.
dependent (require Java 1.5 or higher) would be
ideal here. Those who run lower then Java 5 simply would not have
pack200 which is kind of natural isn't it?
- thomas
Jeff McAffer wrote:
right but there is the practical detail that the exe you need comes
with Java 5 or later and the licensing
does this affect PDE at all when targetting something installed using
p2? That is, do you still get the source in the IDE ?
Jeff
Pascal Rapicault wrote:
Earlier today I have released support to ensure that the source bundles
would not get added to the bundles.txt (and therefore not installed
: Jeff McAffer [EMAIL PROTECTED]
To: Equinox
somewhere else and give it another
name,
except merging it with bundles.txt or putting it next to it.
PaScaL
From: Jeff McAffer [EMAIL PROTECTED]
To: Equinox development mailing list equinox-
[EMAIL PROTECTED]
Date
I forgot to ask during the call. Can we have one installer per EPP
package? That is, one installer that would work for multiple platforms
or do we have to have one installer for per EPP per platform?
Jeff
___
equinox-dev mailing list
*Jeff McAffer [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
02/04/2008 01:13 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
Subject
[equinox-dev] [prov] EclipseCon
Tom and I just submitted an Equinox BoF proposal for EclipseCon.
https://eclipsecon.greenmeetingsystems.com/submissions/view/579
Hope to see you there.
Jeff
___
equinox-dev mailing list
equinox-dev@eclipse.org
alternatively is it possible to have the installer configure the
launcher with the right splash? of course that assumes that the NL is
fixed from install time. Just a thought
Jeff
Andrew Niefer wrote:
James,
The native code that is showing the early splash screen does not have
support to
only need one bmp.
Inactive hide details for Jeff McAffer [EMAIL PROTECTED]Jeff McAffer
[EMAIL PROTECTED]
*Jeff McAffer [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
02/07/2008 07:50 AM
Please
Unless it has changed since I messed with it, that FileServerApplication
was some hacky attempt at putting an HTTP server on front of some
repos. It may be an ok starting point but i'd not put too much weight
on it. Perhaps we should just have one thing that exposes a set of
repos through
of getting this in. Having said
that, we can always have another route that is less well integrated and
comes from the incubator at the beginning and then gets integrated over
time.
Jeff
Scott Lewis wrote:
Hi Jeff,
Jeff McAffer wrote:
Unless it has changed since I messed
Remy, excuse me if this is really basic and naïve. I've only used bittorent
to download large single wad files...
Would it be reasonable to use bittorent to download *parts* of things? For
example, if you look at an entire repo as one file then when you want just
one of the artifacts in the
In the past couple days there have been at least three cases of code
problems that where either code from J2SE was being used or dependencies
were spec'd incorrectly because stuff was coming for free from the JRE. We
can avoid these simply by installing and configuring a Foundation 1.1 JRE.
See
What policy should be used when installing IUs that have been removed?
Say we have a metadata repo M and some IU A that gets installed into profile
P. The agent may cache A in a metadata cache or some such. Then we remove
M (or remove A from M). Now there are two choices -- either A is no
: |
|
---
---|
|Jeff McAffer [EMAIL PROTECTED
There are several projects in p2 currently that list J2SE 1.4 and Foundation
1.1 in the BREE for the bundle. This is good but they list them in that
order. The net result is that J2SE 1.4 is used to compile the code. What
happens in some cases people don't have 1.4 so PDE uses the next best thing
with BREE J2SE 1.4. I
think if you simply reorder the BREEs we will get a build failure for bundles
needing XML stuff to compile. We would need an XML bundle to be available at
build time also.
Tom
Inactive hide details for Jeff McAffer ---02/19/2008 07:57:02 AM---There are
several projects
Feels like a missing Update classpath or some such. This all works fine
for me though I do have foundation 1.1 installed.
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:equinox-dev-
[EMAIL PROTECTED] On Behalf Of Timothy Webb
Sent: Thursday, February 21, 2008 6:07 PM
To:
The RCP downloads from Eclipse have update.configurator in them. This is
convenient because that configurator automatically discovers and installs
all the bundles so people getting started with RCP do not need to
laboriously list out the things they need. It is however unfortunate in the
case of
+1
This fits well with investigations we need to do for e4 as well as the SAT
work and some discussions with James Branigan from the Jazz team around
stuff they have been doing.
Need a pithy name for the workarea. component programming model (CPM)
perhaps? As Oleg points out, it is
This is likely related to ProvisioningHelper which is another interesting
utilty class. It would be good to factor things to provide a simple API to
much of this function. Helmut, can you synthesize the ProvisioningUtil and
ProvisioningHelper classes to make something that you think makes sense?
Integration work
+1 from me too, and I would be interested in participating. How does
this work? Will initial committers be nominated?
Boris
On Thu, Mar 27, 2008 at 1:04 PM, Jeff McAffer [EMAIL PROTECTED] wrote:
+1
This fits well with investigations we need to do for e4
Michael,
Plugins == bundles. There is nothing special in the generator that could
distinguish between the two ('cause there is no difference). What are you
doing that is not working?
Jeff
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hampel, Michael
Sent: Wednesday,
Hey Emmanuel,
Great to see you using Equinox. These kinds of questions are best asked on
the Equinox newsgroup
http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.equino
x
There you will find a diverse user community who may have had the same issue
and have solutions
We can copy the Apache code and include it in the touchpoint bundle (as one
option). Either way, I would suggest contributing the tarball code to the
p2 incubator. If someone wants/needs to use it or has some time to do
integration then they can do so.
Eventually agents should be able to
Agreed we can talk about this tomorrow. In the mean time, my 2c is that we
call it 1.0. It is a release and we are believing that it is useful/works/.
It would be strange IMHO to have the SDK based on something that we don't
feel good enough about to call 1.0.
As for JSCH, we do not control
] On Behalf Of Jeff McAffer
Sent: Sunday, April 13, 2008 8:00 PM
To: 'Equinox development mailing list'
Subject: RE: [equinox-dev] [prov] Auto installing touchpoint
I'm not a big incubator kind-a guy so I'll probably wait for the 3.5
stream to open up to work on this. In the meantime I've cloned
Thanks John, this is a good start. I wonder if there is something we can
harvest from the Orbit IP log structure. DJ? Thoughts?
It would be generally useful to have the CQ numbers associated with the
third party code.
One important not is that I believe we have a policy about protecting
I think the EPP team is interested in doing this. Do you see any technical
reasons why it cannot be done or is this mainly a coordination/timing issue?
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:eclipse-dev-
[EMAIL PROTECTED] On Behalf Of Pascal Rapicault
Sent:
for EPP packages, since this is where bundle pooling across applications
really comes into play.
Jeff McAffer [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/26/2008 11:38 AM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
'General development mailing list
Ideally people would not have to copy the repos somewhere else just to get
Maven integration. Perhaps someone in the community can provide/point to an
update site/p2 adapter for Maven? That way you would just point Maven at
the main Eclipse repos (or a mirror).
Jeff
-Original Message-
+1 I annotated the bug with more thoughts
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Timothy Webb
Sent: Thursday, May 15, 2008 5:17 PM
To: Equinox development mailing list
Subject: [equinox-dev] [p2] Milestone update site for 3.4
Apologies for the persistence on this
to
Equinox development mailing list equinox-dev@eclipse.org
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] Commit rights for Rafael Chaves have been expired
eclipse.equinox Committers,
Jeff McAffer has expired the commit rights for Rafael Chaves (rchaves
Dunno Alex. This works fine for me on windows but I see your point on the Mac.
I had a look at the p2installer.ini:
-showsplash
org.eclipse.platform
-vmargs
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-
From: [EMAIL PROTECTED] [mailto:equinox-dev-
[EMAIL PROTECTED] On Behalf Of Jeff McAffer
Sent: Wednesday, May 21, 2008 12:18 AM
To: 'Equinox development mailing list'
Subject: RE: [equinox-dev] Is the P2 installer supposed to work?
Dunno Alex. This works fine for me on windows but I see
It was the joint decision of the team and the PMC that p2 would not have any
API. By definition, anything that is not API is marked as x-internal =
true. As a result, and by design, you get a warning that you are using
something that is not API. I agree that this is annoying however, no one
I fyou run the installer in shared mode it uses one profile registry and
creates a new profile for every different thing you install.
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:equinox-dev-
[EMAIL PROTECTED] On Behalf Of Thomas Hallgren
Sent: Friday, May 30, 2008 5:38 PM
As discussed in the planning call this morning our feature names are all
over the map. Here is a sample of some I see in the current testUpdates
repo
Eclipse Project Equinox bundle feature
Eclipse P2 Developer Resources
Equinox bundle source feature
Equinox Provisioning Director
them all to be consistent in 3.5 if we don't do it earlier.
Jeff McAffer [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
06/11/2008 11:51 AM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
'Equinox development mailing list' equinox-dev@eclipse.org
cc
Heiko,
This is great. Thanks. some suggestions
- It would be great to have the quick start and demo somewhere in a
permanent location on the main page. These items will not be new
forever and the what's new section is not where people would look to get
started. Perhaps a whole Getting
in
incubation?
Am 14.06.2008 um 02:58 schrieb Jeff McAffer:
On a side note, I'm not 100% but there may be an issue with calling
the Aspects stuff 1.* when it is incubation.
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman
Craig,
Thanks for taking the time to report this. Can I ask you to enter a
bug report at
https://bugs.eclipse.org/bugs/
That helps us track and address these issues.
Jeff
Craig Phillips wrote:
Hi,
If someone wants to take a deeper
look... Stack trace at bottom of this post...
1 - 100 of 180 matches
Mail list logo
