Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361033

Summary:

Support <copyright>, <provider> and <description> in a product definition file (.product)

Product:

[Eclipse Project] PDE

Reporter:

Nick Boldt <nboldt>

Component:

Assignee:

PDE-UI-Inbox <pde-ui-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

aleksandr.kravets, bohacekm, curtis.windatt.public, d_a_carver, gschaffran, martin.karpisek, mknauer, psuzzi, pwebster, remy.suen, Vikas.Chandra, wayne.beaton

Version:

3.7.1

Keywords:

helpwanted

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

stalebug

Attachments:

Description	Flags
screenshot showing missing copyright info for the epp.package.jee product	none

Description Nick Boldt

2011-10-14 16:23:04 EDT

Realized today while pursuing https://issues.jboss.org/browse/JBDS-1882 that our top-level product fails to provide (and also to display) copyright information, and there's no provider or description shown for the installation.

Steps to repro:

1. install Eclipse SDK, JEE or JS bundle. Or any product, like the one mentioned in the JIRA above. I was testing w/ Indigo SR1.

2. Help > About > Installation Details > select a product* > Properties 

* - eg., Eclipse IDE for Javascript Developers (epp.package.javascript), Eclipse Platform (org.eclipse.platform.ide), etc.

3. Look at the Copyright tab: it's empty. "No copyright information has been provided."

4. Look at the General Information tab: no Description or Provider - only Name, Identifier, and Version.

5. Look at the License Agreement tab: license provided (as defined by the <license> node in the .product file.) (This is working.)

Can the missing pieces of information be added to the spec of the .product file, supported in the Product Configuration Editor, and (while I'm asking for the moon here) can a .xsd be provided somewhere, like help.eclipse.org, for the spec of a .product file so that validation can be done?

Comment 1 Nick Boldt

2011-10-14 16:25:03 EDT

Created attachment 205235 [details]
screenshot showing missing copyright info for the epp.package.jee product

Comment 2 Nick Boldt

2011-10-14 16:26:16 EDT

Moving to Version = 3.7.1 as that's where I'm reporting it (not 4.2, the default).

Comment 3 Aleksandr Kravets

2011-10-17 11:41:46 EDT

Added myself to cc list

Comment 4 Eric Moffatt

2011-10-18 15:26:18 EDT

Nick, do other EPP packages show more info and, if so, how ?

I'm not familiar with this area an I'm just trying to figure out where to triage this one...

Comment 5 Martin Bohacek

2014-02-12 03:36:17 EST

Is there any update on this? I can confirm that the problem is still there.

Comment 6 Curtis Windatt

2014-02-12 10:46:22 EST

(In reply to Martin Bohacek from comment #5)
> Is there any update on this? I can confirm that the problem is still there.

No one is currently working on this issue.

Comment 7 Wayne Beaton

2015-01-16 13:55:24 EST

Products lacking a description is a cause for some confusion/concern when updating.

e.g. 

http://jdevelopment.nl/mysterious-44120150109-eclipse-luna-update-sr1a/

Comment 8 Eclipse Genie

2018-12-24 19:36:22 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 9 Lars Vogel

2019-09-02 15:02:12 EDT

This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.

Comment 10 Lars Vogel

2019-09-02 15:08:28 EDT

This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.