Anonymous_User Absent Member.
Absent Member.
111 views

Packages and Publishing...


So when you work on your own custom Package, you have sort of three
options.

1) Build - make a JAR file out of it, importable into other Designer
projects.
2) Release - A tick box during build step, that locks it so no further
changes allowed.
3) Publish - After built (might need Release too, I forget) you can
'publish' to a directory.

The difference is that #1 and #2 give you a series of JAR files.
Excellent.

If you want to set up an Import source that Designer can check for
updates (as it does at startup) you need to Publish it to a directory.

This splits the JAR files into really three things.

a) Features directory
b) Plugins directory
c) site.xml file with the list of packages on this site.

If one had say 10-20 packages built and never published them, and wanted
to suddenly convert them all into a Publish site, and get them all split
up right, and site.xml updated.

Any simple way, short of right clicking them all one by one, and
updating them into one file system directory.


--
BraveBraveSirRobin
------------------------------------------------------------------------
BraveBraveSirRobin's Profile: https://forums.netiq.com/member.php?userid=2812
View this thread: https://forums.netiq.com/showthread.php?t=46080

Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: Packages and Publishing...

On 11/5/2012 11:34 AM, BraveBraveSirRobin wrote:
>
> So when you work on your own custom Package, you have sort of three
> options.
>
> 1) Build - make a JAR file out of it, importable into other Designer
> projects.
> 2) Release - A tick box during build step, that locks it so no further
> changes allowed.
> 3) Publish - After built (might need Release too, I forget) you can
> 'publish' to a directory.
>
> The difference is that #1 and #2 give you a series of JAR files.
> Excellent.
>
> If you want to set up an Import source that Designer can check for
> updates (as it does at startup) you need to Publish it to a directory.
>
> This splits the JAR files into really three things.
>
> a) Features directory
> b) Plugins directory
> c) site.xml file with the list of packages on this site.
>
> If one had say 10-20 packages built and never published them, and wanted
> to suddenly convert them all into a Publish site, and get them all split
> up right, and site.xml updated.
>
> Any simple way, short of right clicking them all one by one, and
> updating them into one file system directory.


One reason this would be important is that it differs on where your
packages are stored, depending on how they are imported.

If you import, right click Package Catalog, import packages, the list of
Packages you see, comes from the Designer install directory path.

When you click Browse, it looks fro JAR files, unpacks them, and
includes the contents in your catalog of this one project, but does NOT
copy them to the Designer install directory.

If you add a new import source (via Published packages, i.e. with
site.xml somewhere) then the import done by Check for Packages actually
copies it to the Designer install directory, and now in your catalog,
the import shows them in that list.

Where this really matters is when you change Workspaces/projects. If
they are in your Designer install dir, no issues. if not, you get
prompted, and may or may not have an easy time finding them.

Even if you imported from a JAR, and then switch to a new workspace, you
have to go find the JAR again.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.