the GEP 2.1.0 Staging site
(i.e., GERONIMODEVTOOLS-291)
> Eclipse as a top-level directory in GEP zip file
>
>
> Key: GERONIMODEVTOOLS-323
> URL:
> https://issues.apache.org/jira/browse/GE
one, but what we have now
doesn't work.
> Eclipse as a top-level directory in GEP zip file
>
>
> Key: GERONIMODEVTOOLS-323
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTO
s a top-level directory in GEP zip file
>
>
> Key: GERONIMODEVTOOLS-323
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-323
> Project: Geronimo-Devtools
>
Eclipse as a top-level directory in GEP zip file
Key: GERONIMODEVTOOLS-323
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-323
Project: Geronimo-Devtools
Issue Type: New Feature
On Thu, Apr 3, 2008 at 11:41 PM, Tim McConnell <[EMAIL PROTECTED]> wrote:
> FYI, a good article on the subject that I used to learn about Eclipse
> links.
...is here - Zarządzanie wtyczkami w Eclipse - Extension Location [1].
Sorry it's in Polish, though so learn Polish or find another article
FYI, a good article on the subject that I used to learn about Eclipse links.
Jacek Laskowski wrote:
On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker <[EMAIL PROTECTED]> wrote:
It is also nice to have just plugins and features rather than
eclipse\plugins and eclipse\features when you have diffe
Jacek Laskowski wrote:
The real solution to the issue is to use Eclipse's extension locations
so you define a link file in links directory (beneath the Eclipse home
directory) where you point out the directory with plugins to be
included, i.e.
[EMAIL PROTECTED] /cygdrive/c/apps/eclipse
$ ls -l l
Yes, I use this function as well and it simplifies management of my various
Eclipse plugins much simpler.
Jacek Laskowski wrote:
On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker <[EMAIL PROTECTED]> wrote:
It is also nice to have just plugins and features rather than
eclipse\plugins and eclipse
On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker <[EMAIL PROTECTED]> wrote:
> It is also nice to have just plugins and features rather than
> eclipse\plugins and eclipse\features when you have different versions of
> eclipse and change the directory to eclipse3.2 eclipse3.3 eclipse7.1 etc.
The real so
Jacek Laskowski wrote:
Just noticed that all Eclipse plugins I've recently worked with had
their deployable zip files with eclipse as the top-level directory. I
think we should change how GEP is assembled with eclipse as its
top-level directory. What do you think?
It is also nice to have just p
I too agree. Would be consistent across other plug-ins.
On Thu, Apr 3, 2008 at 2:06 AM, Jacek Laskowski <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Just noticed that all Eclipse plugins I've recently worked with had
> their deployable zip files with eclipse as the top-level directory. I
> think we shoul
On Thu, Apr 3, 2008 at 3:34 AM, Tim McConnell <[EMAIL PROTECTED]> wrote:
> Hi Jacek, just to be certain I fully understand what you're asking. Are you
> suggesting that when the deployable.zip (or updatesite.zip) is unzipped it
> would create this directory structure ??
>
> \eclipse\feature
Hi Jacek, just to be certain I fully understand what you're asking. Are you
suggesting that when the deployable.zip (or updatesite.zip) is unzipped it would
create this directory structure ??
\eclipse\features
\eclipse\plugins
instead of:
\features
\plu
Hi,
Just noticed that all Eclipse plugins I've recently worked with had
their deployable zip files with eclipse as the top-level directory. I
think we should change how GEP is assembled with eclipse as its
top-level directory. What do you think?
Jacek
--
Jacek Laskowski
http://www.JacekLaskowsk
14 matches
Mail list logo
