Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] p2 update

Note that the spec of the 'classic' Update does not force artifact to be on
the same server as site.xml. That was simply the most common case. You can
use the 'archive' tag to map the symbolic name of the artifact and its
physical location that can be a full URL.


Dejan Glozic, Ph.D.
Manager, Eclipse Development 1A
IBM Canada Ltd.
Tel. 905 413-2745  T/L 969-2745
Fax. 905 413-4850

             <wgp010@motorola.                                          To
             com>                      "Cross project issues"          
             Sent by:                  <cross-project-issues-dev@eclipse.o
             cross-project-iss         rg>                             
             ues-dev-bounces@e                                          cc
                                       RE: [cross-project-issues-dev] p2
             03/27/2008 02:09          update                          
             Please respond to                                         
               Cross project                                           

During the p2 talk at eclipsecon, I understood that the server side would
also be impacted by it (for example, the metadata and the artifacts servers
might be on different locations). But looking at the documentation now,  it
seems to me that the format of the site.xml was not changed and all updates
servers will be used on the same way. Is that right? If it is not, is there
any documentation on the server-side impacts?


-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal
Sent: quinta-feira, 27 de mar├žo de 2008 15:04
To: Cross project issues
Subject: Re: [cross-project-issues-dev] p2 update

The advantages are that you now have more flexibility to organize your
plugins ( but
more importantly it allows you to not mix-up the plug-ins you want to try
with the plug-ins you know already runs well. One of the typical problem
users had in the past was that after having unzipped random stuffs in the
plugins folder, their eclipse install would no longet start and they would
not know what to delete and therefore ended up trashing everything. With
the dropins you can simply delete its content, or if you have organized the
content of the dropins you can just delete what you believe broke your

All that said, one of the goal of p2 is to get people out of the file
system by offering more appealing installation metaphors such as d&d of zip
files, URLs, etc onto the installation UI.


  From:       David Olsen <David.Olsen@xxxxxxxxxx>

  To:         Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

  Date:       03/27/2008 12:33 PM

  Subject:    Re: [cross-project-issues-dev] p2 update

Pascal wrote on 03/27/2008 07:25:00:
>       - p2 is now capable of discovering plugins dropped in the
> plugins folder, like you have always been able to do. That said, going
> forward we still recommend people to use the dropins folder

What advantages does using the dropins folder have?  What will go wrong if
we continue to drop things in the plugins folder?

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list
cross-project-issues-dev mailing list

Back to the top