Resolved MC in eclipse.passage
Change-Id: Ib1bebffc9a67f32dd40bb2e9028af292d3421f83
Signed-off-by: Sergei Kovalchuk <sergei.kovalchuk@arsysop.ru>
diff --git a/images/snapshot.png b/images/snapshot.png
new file mode 100644
index 0000000..a8ca82d
--- /dev/null
+++ b/images/snapshot.png
Binary files differ
diff --git a/images/snapshots.png b/images/snapshots.png
deleted file mode 100644
index c326b31..0000000
--- a/images/snapshots.png
+++ /dev/null
Binary files differ
diff --git a/index.php b/index.php
index 33c60ee..5961013 100644
--- a/index.php
+++ b/index.php
@@ -1,17 +1,17 @@
<?php
require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
- require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
- require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
+ require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
$App = new App();
$Nav = new Nav();
$Menu = new Menu();
include($App->getProjectCommon());
-
+
$localVersion = false;
-
- $titlePage = "Eclipse Technology Passage";
-
+
+ $titlePage = "Eclipse Technology Passage";
+
// # Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="bigbuttons">
@@ -31,34 +31,35 @@
<h3>Eclipse Passage (Licensing Tooling)</h3>
<div id="introText">
-<p>The Eclipse Passage project aims to provide rich and easily adoptable capabilities to define and control licensing constraints.
- The usage story starts in Licensing Operator client:
- Define a product you would like to ship
- Generate a pair of keys for defined product
- Send the public key and product description to your development team
- Discuss the features with your marketing and map the features to the product
- Send the descriptions of the features to your development team
- Then development team needs to do the following:
+<p>
+ The Eclipse Passage project aims to provide rich and easily adoptable capabilities to define and control licensing constraints.
+ The Eclipse Passage represent several components for licensing processing:
+ <li>Licensing Operator Client</li>
+ <li>Licensing Runtime Interfaces</li>
+ <li>Licensing Backend Server</li>
+ Eclipse Passage technology offer to use API for:
+ <li>Licensing product definition</li>
+ <li>Key pair generation for defined product</li>
+ <li>Public key intedification in the user/product locations</li>
+ <li>User(profile) definition for the licensing</li>
+ <li>Feature and action definition for licensing purpose</li>
+ <li>Fuctionality resctriction based on licensing parameters</li>
- Embed the public key to your product
- Bind functionality to feature identifiers
- Include Licensing Runtime bundles to the product
- Well, you are ready for the product shipment, at least from Passage point of view. After some time you hopefully will have fantastic download rate and a lot of requests to obtain a license, you need to use Licensing Operator client again:
+ Any licensing subsystem in general present API (low API) for external usage based on any scpecific language, which
+ as common needs to be covered by plugins and as usual could not be used due to external dependencies exists, theuse
+ are qute hard for integration and require additional level of licensing layer.
+ On other side the Eclispe Passage which offer licensing system implenetation in Eclipse terminology way,
+ operates with known identifiers for products, features, commands and other eclipse platform structure nodes.
- Register licensee: either user or company
- Formulate the license conditions: allow a set of features for particular node or for some period or whatever you would like
- Encrypt the license file and send it to the user: you will need a product private key for it - but we hope you still have it in some safe place
- Finally, the Licensing Runtime is starting its work inside your product deployed to the customer environment using the simple algo:
+ Simple for usage, simple for integrationg, simple for maintaince.
- Collect the configuration requirements (feature identifiers to be controlled)
- Mine the license conditions using different approach, the default may be to inspect a subfolder @user.home
- Evaluate the mined conditions against current environment state (time now, running node id) to obtain feature permissions tickets
- Put both configuration requirements and feature permission tickets to the examiner to receive verdict (restrictions)
- Call restriction executors to have desired effect: show status bar reminder or block everything
</p>
-
-
-<img class="displayed" src="/passage/images/snapshots.png" height="550" alt="Eclipse Passage Snapshots" border="0"/>
+<img
+ class="displayed"
+ src="/passage/images/snapshot.png"
+ height="550"
+ alt="Eclipse Passage Snapshots"
+ border="0"/>
</div>
</div>
@@ -69,18 +70,13 @@
<h3>Current Status</h3>
<p></p>
</div>
-
<div id="headlines">
-<h3>Eclipse Passage 0.3.3 Now Available</h3>
-<p><i>March 07, 2019 -</i> Passage 0.3.3 for Eclipse 2018-12. Check the <a href="downloads.php">Download</a> link on how to get yours.</p>
+<h3>Eclipse Passage on the development</h3>
</div>
-
-
</div>
EOHTML;
-
# Generate the web page
- $App->AddExtraHtmlHeader('<link rel="stylesheet" type="text/css" href="/passage/style.css"/>');
+ $App->AddExtraHtmlHeader('<link rel="stylesheet" type="text/css" href="/passage/style.css"/>');
$App->generatePage($theme, $Menu, null, $pageAuthor, $pageKeywords, $titlePage, $html);
?>
