User defined fields read from P6, Asta and GanttProject schedules are now represented by instances of UserDefinedField. They will no longer be mapped to custom field instances.
Enterprise Custom Fields read from MPP and MSPDI files are now represented by instances of UserDefinedField.
When writing MSPDI files, UserDefinedField instances which were originally read from enterprise custom fields will be written to the MSPDI file as enterprise custom fields.
When writing MSPDI files, UserDefinedField instances which were from applications other than Microsoft Project will automatically be mapped to available custom fields.
When writing MPX files, UserDefinedField instances will automatically be mapped to available custom fields.
The UserDefinedField type implements the FieldType interface and so can be used with the FieldContainerget and set methods to work with the contents of the user defined fields.
The ProjectFile.getUserDefinedFields() method has been added to provide access to all user defined fields defined in the project.
The CustomFieldContainer returned by ProjectFile.getCustomFields() will contain entries for all UserDefinedField instances.
The various getFieldTypeByAlias and getFieldByAlias methods will retrieve user defined fields by name.
Added the convenience method ProjectFile.getPopulatedFields() to retrieve details of all populated fields across the project. This avoids the caller having to individually retrieve the populated fields from the tasks container, resource container and so on.
Updated the getPopulatedFields methods to return a Set of FieldType rather than a Set of TaskField, ResourceField etc.
The various getPopulatedFields methods will include instances of UserDefinedField in the returned collection if relevant.
All ENTERPRISE_CUSTOM_FIELDn values have been removed from the TaskField, ResourceField, AssignmentField and ProjectField enumerations.
The getEnterpriseCustomField and setEnterpriseCustomField methods have been removed from ProjectProperties, Task, ResourceandResourceAssignment`.
Project UDFs are now read from P6 schedules.
Project UDFs are now written to PMXML files.
All code previously marked as deprecated has been removed.
Version 10.16.2
Updated to improve reading resource attributes from certain MPP14 files.
Version 10.16.1
Updated to make resource curve definitions (work contours) available in the WorkContourContainer. This container is accessed using the ProjectFile.getWorkContours() method.
Version 10.16.0
Improve accuracy when normalising timephased data.
Add support for reading activity steps from XER files, PMXML files and Primavera databases.
Add support for writing activity steps to PMXML files.
Updated PMXML schema to version 22.12.
Updated methods in the GanttBarCommonStyle and GanttBarStyle classes to use a FieldType instance rather than a TaskField instance to allow more flexibility. (Note: this may be a breaking change if you are currently using these classes.)
Optionally include some Microsoft Project layout data in JSON output.
Version 10.15.0
Avoid wrtiting invalid characters to PMXML, MSPDI and Planner XML files.
Improve handling of slack values for schedules which only contain a value for total slack.
Add support for reading constraint type and constraint date from Phoenix schedule (based on a contribution by Rohit Sinha).
Improve timephased data calculation when assignment has zero units.
Improve handling of very large duration values when reading and writing MSPDI files.
Ensure the Task attributes Active, Constraint Type, Task Mode, and Type always have a value.
Ensure the Resource attributes Type, Calculate Costs from Units, and Role always have a value.
Ensure the Resource Assignment attributes Calculate Costs from Units, Rate Index, and Rate Source always have a value.
Add version number constant to the Java source, accessible as MPXJ.VERSION.
Ensure that UDF values are read for WBS entries in PMXML files.
Avoid writing duplicate resource assignments to MPX files.
Version 10.14.1
Fix CVE-2022-41954: Temporary File Information Disclosure Vulnerability (Contributed by Jonathan Leitschuh)
User defined fields read from P6, Asta and GanttProject schedules are now represented by instances of UserDefinedField. They will no longer be mapped to custom field instances.
Enterprise Custom Fields read from MPP and MSPDI files are now represented by instances of UserDefinedField.
When writing MSPDI files, UserDefinedField instances which were originally read from enterprise custom fields will be written to the MSPDI file as enterprise custom fields.
When writing MSPDI files, UserDefinedField instances which were from applications other than Microsoft Project will automatically be mapped to available custom fields.
When writing MPX files, UserDefinedField instances will automatically be mapped to available custom fields.
The UserDefinedField type implements the FieldType interface and so can be used with the FieldContainerget and set methods to work with the contents of the user defined fields.
The ProjectFile.getUserDefinedFields() method has been added to provide access to all user defined fields defined in the project.
The CustomFieldContainer returned by ProjectFile.getCustomFields() will contain entries for all UserDefinedField instances.
The various getFieldTypeByAlias and getFieldByAlias methods will retrieve user defined fields by name.
Added the convenience method ProjectFile.getPopulatedFields() to retrieve details of all populated fields across the project. This avoids the caller having to individually retrieve the populated fields from the tasks container, resource container and so on.
Updated the getPopulatedFields methods to return a Set of FieldType rather than a Set of TaskField, ResourceField etc.
The various getPopulatedFields methods will include instances of UserDefinedField in the returned collection if relevant.
All ENTERPRISE_CUSTOM_FIELDn values have been removed from the TaskField, ResourceField, AssignmentField and ProjectField enumerations.
The getEnterpriseCustomField and setEnterpriseCustomField methods have been removed from ProjectProperties, Task, ResourceandResourceAssignment`.
Project UDFs are now read from P6 schedules.
Project UDFs are now written to PMXML files.
All code previously marked as deprecated has been removed.
10.16.2 (2023-01-29)
Updated to improve reading resource attributes from certain MPP14 files.
10.16.1 (2023-01-26)
Updated to make resource curve definitions (work contours) available in the WorkContourContainer. This container is accessed using the ProjectFile.getWorkContours() method.
10.16.0 (2023-01-24)
Improve accuracy when normalising timephased data.
Add support for reading activity steps from XER files, PMXML files and Primavera databases.
Add support for writing activity steps to PMXML files.
Updated PMXML schema to version 22.12.
Updated methods in the GanttBarCommonStyle and GanttBarStyle classes to use a FieldType instance rather than a TaskField instance to allow more flexibility. (Note: this may be a breaking change if you are currently using these classes.)
Optionally include some Microsoft Project layout data in JSON output.
10.15.0 (2023-01-11)
Avoid writing invalid characters to PMXML, MSPDI and Planner XML files.
Improve handling of slack values for schedules which only contain a value for total slack.
Add support for reading constraint type and constraint date from Phoenix schedule (based on a contribution by Rohit Sinha).
Improve timephased data calculation when assignment has zero units.
Improve handling of very large duration values when reading and writing MSPDI files.
Ensure the Task attributes Active, Constraint Type, Task Mode, and Type always have a value.
Ensure the Resource attributes Type, Calculate Costs from Units, and Role always have a value.
Ensure the Resource Assignment attributes Calculate Costs from Units, Rate Index, and Rate Source always have a value.
Add version number constant to the Java source, accessible as MPXJ.VERSION.
Ensure that UDF values are read for WBS entries in PMXML files.
Avoid writing duplicate resource assignments to MPX files.
10.14.1 (2022-11-25)
Fix CVE-2022-41954: Temporary File Information Disclosure Vulnerability (Contributed by Jonathan Leitschuh)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps net.sf.mpxj:mpxj from 10.14.0 to 11.0.0.
Release notes
Sourced from net.sf.mpxj:mpxj's releases.
Changelog
Sourced from net.sf.mpxj:mpxj's changelog.
Commits
c6117fdUpdate documentation52650daUpdate versiondf61a5eUpdate Field Guide (#432)8c5a7f6Clean up source8c230d9Remove deprecated code (#431)c7a4df0UDF Refactor (#430)c607d20Don't write empty lists (#429)6b6a9e9Add outline codese4b8a88Tidy up constants7ee3538Improve method implementationsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)