Home » Eclipse Projects » Oomph » Custom product launcher name(There is a way to set custom product launcher name?)
|
| Re: Custom product launcher name [message #1703667 is a reply to message #1703655] |
Tue, 04 August 2015 05:33   |
 Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Claudio,
The launcher name is determined by the p2 metadata itself, i.e., by the
product definition you use to build your update site. You can look at
Oomph itself to see how it defines its launcher product where the name is
<launcher name="eclipse-inst">
Via a branding info annotation you can specify other things like the
name of the folder which we do like this for our installer product:
<?xml version="1.0" encoding="UTF-8"?>
<base:Annotation
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:base="http://www.eclipse.org/oomph/base/1.0"
source="http://www.eclipse.org/oomph/setup/BrandingInfo">
<detail key="imageURI">
<value>http://www.eclipse.org/downloads/images/oomph-42x42.png</value>
</detail>
<detail key="folderName">
<value>eclipse-installer</value>
</detail>
<detail key="folderName.macosx">
<value>Eclipse Installer</value>
</detail>
</base:Annotation>
On 03/08/2015 11:51 PM, Claudio Weiler wrote:
> Hi,
>
> There is a way to set custom product launcher name on Oomph .setup files?
>
> Explaining... I'm defining a custom product setup, with predefined
> plugins, location, some preferences, etc., and I like to define the
> launcher name from "eclipse.exe" to "myproduct.exe" (Windows setup,
> ignore .exe if you like :p ).
>
> Thanks!!!
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: Custom product launcher name [message #1703821 is a reply to message #1703753] |
Wed, 05 August 2015 08:36 |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Claudio,
Comments below.
On 05/08/2015 4:25 AM, Claudio Weiler wrote:
> Hi great Ed,
>
> Sorry, I didn't catch this one.
>>> The launcher name is determined by the p2 metadata
> This is not "p2 director" properties right? On these I find ID,
> Description, Lavel, License Confirmation Disabled and Merge Disabled.
No, the p2 metadata itself determines the name of the executable that it
installs.
>
>>> by the product definition you use to build your update site
> So, I need to make a update site to set launcher name?
You need one or more update sites to create an installation in the first
place. That's where all the bundles and features come from and that's
where the instructions for installing the executable are located.
>
>>> You can look at Oomph itself to see how it defines its launcher
>>> product where the name is
> I looked at Oomph.setup and OomphInstaller.setup, could not find this
> definition...
A product definition looks like this:
http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/products/org.eclipse.oomph.setup.installer.product/Installer.product
This is how you define a product; it's what produces (during a build),
the p2 update site information. The information here determines the
name of the executable and the name of the corresponding *.ini.
>
>>> Via a branding info annotation you can specify other things...
> That's ok...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Custom product launcher name [message #1703893 is a reply to message #1703821] |
Wed, 05 August 2015 16:32 |
Claudio Weiler
Messages: 31
Registered: August 2015
Location: Brazil |
Member |
|
|
So what I understand is:
1. I can not use Oomph to change the launcher name for a product
2. If I want a eclipse with custom launcher name I need a different setup based on something different, not Oomph
Also, this is the same concept for launcher icon? I defined "BrandingInfo" with "imageURI" and noted that it's only for catalog listing inside eclipse installer.
What I like (most) in Oomph is:
- the ability to directly install different sets of plugins (product), with predefined adjustments (many of them) need to development team environment
- p2 pool
A different launcher name is just cosmetic, if it is not possible with Oomph I'm ok with this...
Thanks!!
[Updated on: Wed, 05 August 2015 17:02] Report message to a moderator |
|
|
| Re: Custom product launcher name [message #1703948 is a reply to message #1703893] |
Thu, 06 August 2015 04:48 |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Claudio,
Comments below.
On 05/08/2015 6:32 PM, Claudio Weiler wrote:
> So what I understand is:
>
> 1. I can not use Oomph to change the launcher name for a product
Oomph does not determine the launcher name. Your product definition
determines that.
> 2. If I want a eclipse with custom launcher name I need a different
> setup based on something different, not Oomph
>
No, you need to define your product definition such that your launcher
name is what you want it to be.
>
> What I like (most) in Oomph is:
> - the ability to directly install different sets of plugins (product),
Doesn't confuse the two terms: a plugin is not a product. A product is
a very specific type of thing. I've shown you how one is defined. One
can certainly install different sets of plugins, but one can install
only one product. The product you install has well defined metadata for
the icon, splash screen, executable name, ini name, and so on, so if you
want specialized such things, you must create your own specialized
product definition.
> with predefined adjustments (many of them) need to development team
> environment
> - p2 pool
>
> A different launcher name is just cosmetic, if it is not possible with
> Oomph I'm ok with this...
You can define your own product, many companies do, but if it's purely
for the cosmetic purpose of renaming the *.exe (and *.ini) and making
sure that this renaming is properly reflected in any of the other
metadata within the installation, I doubt that's worth the effort.
>
> Thanks!!
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Custom product launcher name [message #1704018 is a reply to message #1703948] |
Thu, 06 August 2015 17:38 |
Claudio Weiler
Messages: 31
Registered: August 2015
Location: Brazil |
Member |
|
|
Ed,
>> Doesn't confuse the two terms: a plugin is not a product. A product is...
Maybe we have different points of view that are makings things more difficult, and my poor English do not help on this...
I'm based on this page https://wiki.eclipse.org/Eclipse_Oomph_Authoring. But using "Setup Product Model" wizard. That is what I'm calling "product". I find this page https://wiki.eclipse.org/FAQ_What_is_an_Eclipse_product%3F, that is what I think you are calling "product". Two different concepts with same name... 
From now I will call these as "product setup" and "eclipse product", respectively.
I tried to find how to build a custom eclipse product, but no luck til now...
Sadly Oomph is too new and my findings on internet is not helping me to put the pieces together. I git cloned https://git.eclipse.org/r/oomph/org.eclipse.oomph and studied a bit this structure, but it's hard to understand without a guideline, and it is too "eclipse installer"!! I tried to find some "eclipse.product" but failed...
Will continue to try to create a custom eclipse product, but what I understand is that for each new eclipse distro (luna, mars, ...) is launched I will need to recreate my custom eclipse product, what is not necessary in Oomph, where I just need to adjust my custom product setup...
Thanks!!
[Updated on: Thu, 06 August 2015 17:47] Report message to a moderator |
|
|
| Re: Custom product launcher name [message #1704067 is a reply to message #1704018] |
Fri, 07 August 2015 06:50 |
|
Hi Claudio,
Comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 06.08.2015 um 19:38 schrieb Claudio Weiler:
> Ed,
>
>>> Doesn't confuse the two terms: a plugin is not a product. A product is...
> Maybe we have different points of view that are makings things more difficult, and my poor English do not help on this...
>
> I'm based on this page https://wiki.eclipse.org/Eclipse_Oomph_Authoring. But using "Setup Product Model" wizard. That
> is what I'm calling "product". I find this page https://wiki.eclipse.org/FAQ_What_is_an_Eclipse_product%3F, that is
> what I think you are calling "product". Two different concepts with same name... :(
Clearly we suffer from the fact that there are more concepts (or variations thereof) in the world than short names for
them. The word "product" serves even more purposes in the Eclipse world. It refers to the project in your workspace that
contains your artifacts (especially the .product file) that specify a product. It refers to the p2 metadata (i.e.,
installable unit) that's derived from those artifacts and lives in a p2 repository or p2 profile. It refers to the
executable installation that's created by the p2 director from that metadata. And so on...
>
> From now I will call these as "product setup" and "eclipse product", respectively.
That seems okay if the context doesn't disambiguate the word product enough.
>
> I tried to find how to build a custom eclipse product, but no luck til now...
Oomph is *not a build technology*, so you won't find that in our documentation, but the article you mentioned above
directly links to https://wiki.eclipse.org/FAQ_How_do_I_create_an_Eclipse_product%3F and the web is full of tutorials on
that topic: http://lmgtfy.com/?q=eclipse+product+build
>
> Sadly Oomph is too new
By now Oomph is more than two years old.
> and my findings on internet is not helping me to put the pieces together.
Nobody said that it's simple, but the information is all publicly available (not in Oomph of course) and you should
first learn how to *build* an Eclipse product. Then you can learn how to create an Oomph setup to make it easier to
install this Eclipse product.
> I git cloned https://git.eclipse.org/r/oomph/org.eclipse.oomph and studied a bit this structure, but it's hard to
> understand without a guideline,
That's certainly a subjective statement, but I doubt that the Oomph sources would help you understand how to build an
Eclipse product.
> and it is too "eclipse installer"!!
Whatever that means. But yes, Oomph is an Eclipse installer; it can only install Eclipse products.
> I tried to find some "eclipse.product" but failed...
>
> Thanks!!
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: Custom product launcher name [message #1704154 is a reply to message #1703655] |
Fri, 07 August 2015 17:43 |
Claudio Weiler
Messages: 31
Registered: August 2015
Location: Brazil |
Member |
|
|
Hi Eike,
>> Sadly Oomph is too new
>By now Oomph is more than two years old
Sorry, I didn't mean to be impolite.
>> but the article you mentioned above directly links to
>> https://wiki.eclipse.org/FAQ_How_do_I_create_an_Eclipse_product%3F
I tried to use that wiki article, it do not work or there are subjective info needed to make it work that I do not have.
But, this thread is going too offtopic, and to make clear to visitors of this thread I like to make clear my beginning question:
Claudio Weiler wrote on Mon, 03 August 2015 18:51There is a way to set custom product launcher name on Oomph .setup files?
No, there isn't. Oomph creates a product setup that is based on an available eclipse product. Launcher name, icons and other brandings must be defined on custom eclipse products, see in this wiki article.
|
|
|
Goto Forum:
Current Time: Sun Dec 08 05:54:21 GMT 2024
Powered by FUDForum. Page generated in 0.04633 seconds |
] 
Search
Help
Register
Login
Home
