MxUpdate is a deployment tool for the Enovia PLM platform to handle administration objects as single update files (configuration items). Due to license an usage in productive system is not possible.
Home Page: https://github.com/MxUpdate
License: Other
MxUpdate is a deployment tool for the Enovia PLM platform to handle administration objects as single update files (configuration items).
For more information see the Wiki Start Page page.
The Wiki pages itself are concatenated to one PDF manual. The manual could be downloaded.
USAGE IS NOT ALLOWED IN PRODUCTIVE SYSTEMS.
Development is stopped. Recommendation is to use the Spinner tool from Dassault System.
From [email protected] on May 24, 2009 10:26:03
With V6 MX supports also interfaces for relationships. This must also supported for MxUpdate.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=14
From [email protected] on June 13, 2009 06:11:39
Current MX has also "page" objects. They are like programs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=24
From [email protected] on May 03, 2009 14:37:35
The related JPO is org.mxupdate.install.InstallDataModel
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=8
From [email protected] on June 16, 2009 15:07:16
What steps will reproduce the problem? 1. execute MQL command:
add policy MxUpdate_Test type all state Pending ;
2. export policy:
exec prog MxUpdate --export --policy MxUpdate_Test --path /tmp; What is the expected output? What do you see instead? In the exported policy TCL update file is no type assigned:
:
type {}
:
but correct is:
:
type {all}
:
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=30
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=25
From [email protected] on July 16, 2009 08:01:19
What steps will reproduce the problem? 1. Download zip-file
2. Installed as described What is the expected output? What do you see instead? The installation should work, but the following error occured:
update jpo 'org.mxupdate.install.Insert'
could not read "D:/mxupdate.V0.5.2/org/mxupdate/util/MqlUtil_mxJPO.java":
no such file or directory
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=47
From [email protected] on June 23, 2009 13:38:05
What steps will reproduce the problem? 1.export all admin or data model objects
exec prog MxUpdate --export --admin *
or
exec prog MxUpdate --export --datamodel * What is the expected output? What do you see instead? The interfaces are not exported)
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=39
From [email protected] on July 16, 2009 09:18:42
What steps will reproduce the problem? 1. Try to export program with "-" in the name, e.g. "Test-Name" What is the expected output? What do you see instead? "Test-Name" should become "Test_Name" because "-" is an illegal character
in java-classes.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=48
From [email protected] on May 01, 2009 06:41:08
What steps will reproduce the problem? 1. MxUpdate must be installed the first time
2. update a type, relationship or policy (admin object which are using the JPOCaller class) What is the expected output? What do you see instead? The update failed if the error that the JPO caller instance is not defined for the instance. Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=1
From [email protected] on June 22, 2009 13:52:41
What steps will reproduce the problem? 1. create policy with a state and symbolic name for the state:
add pol Test state create property state_create value create property state_exists value create
2. export the policy
exec prog MxUpdate --export --policy Test --path c:/temp What is the expected output? What do you see instead? The TCL update file should look like this:
updatePolicy "${NAME}" {
:
state "create" {
registeredName "state_create"
registeredName "state_exists"
:
}
}
Currently only one registered name is exported!
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=34
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=20
From [email protected] on May 25, 2009 03:19:10
E.g. if for a XML file which is created as program in MX some properties must be defined than this is only possible via a separate MQL script.
Because the syntax itself depends on the language (XML, TCL, MQL), the line prefixes must be defined for each file suffix. e.g.:
In XML the same syntax than in JPOs is possible, because they can embedded in a comment:
In TCL this is not possible because there no TCL start and end comment exists. Instead a line prefix '#' should be defined:
if a comment is wanted than two ## must be defined.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=18
From [email protected] on July 02, 2009 06:16:14
What steps will reproduce the problem? 1. update of a policy with a signature branching to a non existing state What is the expected output? What do you see instead? An error is thrown, but without any information about the name of the signature and the state. This
means that a correction of the update file is not easy.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=44
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=17
From [email protected] on May 03, 2009 13:26:32
To use the feature of the parameter definitions (and maybe as parameter...).
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=6
From [email protected] on June 22, 2009 15:52:22
What steps will reproduce the problem? 1. export in MX V6 a web table What is the expected output? What do you see instead? In the MQL console "unkown parsing url: /derivedtable(null)" is written (but should not)
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=35
From [email protected] on July 06, 2009 14:13:16
Simplify the JPO installation with:
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=46
From [email protected] on June 12, 2009 02:33:43
What steps will reproduce the problem? 1. make an update of a JPO or program object What is the expected output? What do you see instead? Programs should be registered. Test with:
list property to program ...
But no registration was done.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=22
From [email protected] on May 03, 2009 11:25:05
What steps will reproduce the problem? If e.g. a name of a MX admin object includes the special character " and ' the MQL commands does
not work correctly. What is the expected output? What do you see instead? Use escaped MQL commands, e.g.
escape mod .......
escape print ...... Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=3
From [email protected] on June 16, 2009 14:36:48
What steps will reproduce the problem? 1. Make an update for given Policy definition What is the expected output? What do you see instead? After the update is run a property without name but with value "Rejected" exists. This happens
because for all states are properties (as symbolic names) defined.
Attachment: POLICY_MxUpdate_Test.tcl
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=29
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=9
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=10
From [email protected] on May 24, 2009 04:16:57
The installed version is required for the MxUpdate eclipse plugin to know if the version of the
MxUpdate eclipse plugin is compatible with the MxUpdate Update deployment tool.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=13
From [email protected] on June 22, 2009 15:55:09
What steps will reproduce the problem? 1. assign to a type a program as method
2. export the type What is the expected output? What do you see instead? In the MQL console following output is shown:
unkown parsing url: /methodList(..
unkown parsing url: /methodList/programRef(...
But nothing should be shown.
In the created TCL update file the method is not assigned to the type, but should be assigned.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=36
From [email protected] on June 13, 2009 06:09:33
MX V6 supports also applications.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=23
From [email protected] on June 21, 2009 03:15:48
To use maven build tools, the source code structure should be more like maven requires:
src/main/java
src/test/java
If this is done the automatic tests could be run by maven.... Including site structure etc.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=31
From [email protected] on May 20, 2009 14:16:46
What steps will reproduce the problem? 1. create a definition file for a policy where symbolic names for states are defined
2. make an update What is the expected output? What do you see instead? for each state where the symbolic name is defined a property on the policy must be defined (must
no changed is done)
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=11
From [email protected] on June 14, 2009 11:35:40
What steps will reproduce the problem? 1. assign a person to an application "mod person creator application APPLNAME"
2. export person creator "exec prog MxUpdate --export --person creator --path C:\TEMP" What is the expected output? What do you see instead? Export should be done without "unknown parsing url" message and the application name should be
defined in the update file.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=27
From [email protected] on June 22, 2009 13:50:29
What steps will reproduce the problem? 1. create policy with a state and symbolic name for the state:
add pol Test state create property state_create value create;
2. export the policy
exec prog MxUpdate --export --policy Test --path c:/temp What is the expected output? What do you see instead? The TCL update file should look like this:
updatePolicy "${NAME}" {
:
state "create" {
registeredName "state_create"
:
}
}
Without(!)
mql add property "state_create"
on policy "${NAME}"
value "create"
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=33
From [email protected] on July 16, 2009 09:22:01
What steps will reproduce the problem? 1. Export program containing "" What is the expected output? What do you see instead? "" should stay "" and not become ""
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=49
From [email protected] on May 30, 2009 07:05:14
A new parameter --compile should be defined for the MxUdpate Update deployment tool so that
JPOs are automatically compile.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=21
From [email protected] on May 24, 2009 10:53:21
What steps will reproduce the problem? 1. use MX V6
2. define a role type
3. export the role What is the expected output? What do you see instead? Output is:
unkown parsing url: /roleType(4)
The role type must must be supported and written to the TCL update file.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=15
From [email protected] on June 22, 2009 15:59:33
What steps will reproduce the problem? 1. assign a filter to a role
2. export the role 3. What is the expected output? What do you see instead? The MQL console shows the output:
unkown parsing url: /filterList
:
:
But nothing should be shown.
The filter itself is not assigned in the TCL update file to the role. Instead it should
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=38
From [email protected] on June 16, 2009 14:20:38
What steps will reproduce the problem? 1. create policy:
add policy MxUpdate_Test state Pending property "" value Test
2. call MxUpdate What is the expected output? What do you see instead? A java.lang.NullPointerException is thrown, but should be updated...
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=28
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=43
From [email protected] on July 02, 2009 06:17:32
In some cases a normal compile does not compile all JPOs and that means that old compiled classes
could exists within MX.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=45
From [email protected] on June 21, 2009 04:14:54
What steps will reproduce the problem? 1. execute in the MQL shell:
list property to program MxUpdate; What is the expected output? What do you see instead? Expected is:
program_MxUpdate on program eServiceSchemaVariableMapping.tcl to program MxUpdate
But the MxUpdate JPO is not registered with a symbolic name Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=32
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=42
From [email protected] on July 16, 2009 09:39:41
Add new command to the MxUpdate-Console to auto-create all directories and
sub-directories of dbschema (like export but without files).
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=50
From [email protected] on June 24, 2009 09:13:02
If a state symbolic name is defined for a non existing state, the export will write them in the TCL
update file as property definition:
mql add property "state_NotExists" value "NotExists"
In this case a warning should be shown that the developer could change the related TCL update
code (and maybe remove the property definition or change the name of the mapped state).
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=40
From [email protected] on May 03, 2009 12:26:31
What steps will reproduce the problem? 1.try to export a dimenstion
2.try to update a dimension What is the expected output? What do you see instead? Should be supported Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=5
From [email protected] on May 03, 2009 12:24:57
What steps will reproduce the problem? 1. assign a relationship as from / to in a relationship
2. try to export or update What is the expected output? What do you see instead? This must be supported. Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=4
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=19
From [email protected] on May 03, 2009 14:09:34
The property definition in the mapping must be changed to the same format than all other
definitions. E.g.:
PropertyDef.InstalledDate.PropertyName = installed date
PropertyDef.InstalledDate.AttributeName = MxUpdate Installed Date
Also:
Enumeration for the property names should be defined as supertype (and not within the mapping
class).
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=7
From [email protected] on May 03, 2009 11:23:00
What steps will reproduce the problem? If multiple user are using the same web application instance (instead of JNI) MxUpdate Update uses
caches from other users. What is the expected output? What do you see instead? Caches must be only used within one calling instance. So static caching is not allowed. Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=2
From [email protected] on June 24, 2009 11:35:29
Use good Java coding style guide and best practice.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=41
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=16
From [email protected] on June 22, 2009 15:57:32
What steps will reproduce the problem? 1. assign a icon for a type
2. export the type What is the expected output? What do you see instead? In the MQL console following output is shown:
unkown parsing url: /adminProperties/icon(....
Nothing should be shown.
Also no icon is assigned within the TCL update file. This should be done.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=37
Skipping this issue number to maintain synchronization with Google Code issue IDs.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=12
From [email protected] on June 14, 2009 02:16:13
If a JPO includes packages the JPO is not exported into related directory. This happens because the
slashes (/) are translated to @2f.
Original issue: http://code.google.com/p/mxupdate/issues/detail?id=26
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
