A version is simply the collection of all profiles associated with a fabric. When you create a new version, you are copying all of the profiles from the most recent version—the base version—into the new version. Once that's done, you can upgrade the profiles in the new version by modifying them.
To create a new version:
In Fabric Explorer, select the fabric in which you want to create a new version.
Expand the fabric's tree to the level of Versions, shown in Creating a new profile.
Select a version, and then right-click it to open the context menu.
Select
.In the Create Version wizard, enter a new version or accept the default value.
The default version is always a minor increment of the highest-numbered version. So, if the highest-numbered version is 1.3, the new version will default to 1.4, and all of the profiles in version 1.3 will be copied into version 1.4.
![]() | Important |
---|---|
Version names are important! The developer tools sort version names based on the numeric
version string, according to major.minor
numbering, to determine the version on which to base a new one. You can
safely add a text description to a version name as long as you append it to
the end of the generated default name like this:
|
Click
.The developer tools copy all of the base version's profiles into the new version and display the new version in Fabric Explorer, directly under the base version.
To modify a profile in the new version:
In Fabric Explorer, expand the newly created version.
Select a profile that you want to modify.
The developer tools populate the Properties editor with the profile's details for you to edit.
In the Properties editor, click the Details tab to access the Profiles page.
Make the changes you want to the new profile to configure it.
Changes are automatically saved as you make them.
![]() | Note |
---|---|
In Fuse Integration perspective, you can easily add a Fuse project to the new profile by dragging it from Project Explorer and dropping it onto the new profile in Fabric Explorer. When you do, the developer tools build the project, run all tests, install the project in the new profile, and upload the profile into the fabric's internal Maven repository. Because profiles are stored in a fabric's internal repository, they cannot be shared across other fabrics. |