]
Rob Stryker commented on JBIDE-20194:
-------------------------------------
There seems to have been some confusion on how to verify, so I've updated both this
jira and the devdoc with some more specific steps to replicate, rather than just
"make sure it looks good".
See above in jira description, or at the devdoc.
For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 /
JBDS 9
-------------------------------------------------------------------------
Key: JBIDE-20194
URL:
https://issues.jboss.org/browse/JBIDE-20194
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Labels: task
Fix For: 4.3.0.CR1
For JBIDE 4.3.0.CR1: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly
upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to
1.1.0 or 1.0.100.
2. Switch to using the new o.j.t.foundation.license.feature. Instructions here:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to...
2. Resolve this JIRA when done. QE can then verify and close it later.
[Search for all task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-3481
STEPS TO VERIFY THAT IT WORKED:
Rebuild your features (eg., with mvn clean install -DskipTests)
Verify new features exist in the site/target/repository/features/* folder.
Install the newly created features into Eclipse
Once the workbench is restarted, select Help → Installation Details
On the Installed Software tab, select your feature, and click Properties
In the Properties dialog, select License Agreement and verify there is text there.
Close the Properties dialog.
Switch to the features tab and select your feature
Click the License button, and verify your license appears in an external browser