You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/11/28 00:11:00 UTC
[jira] [Commented] (DERBY-7020) Fix release targets to account for
modularization changes
[ https://issues.apache.org/jira/browse/DERBY-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701196#comment-16701196 ]
Rick Hillegas commented on DERBY-7020:
--------------------------------------
Attaching derby-7020-01-ab-updateReleaseMachinery.diff. This patch adjusts the release targets and support programs to account for the migration of various files to different locations in the sandbox as a result of the modularization work. With these changes, I was able to build a release and install its artifacts into my local maven repository.
Tests passed cleanly with the classpath and the modulepath.
Touches the following files:
{noformat}
-------------------------------
M NOTICE
Update the copyright year. This file is re-generated by the release targets.
-------------------------------
M build.xml
M java/build/org/apache/derbyBuild/maintversion2props.java
M java/build/org/apache/derbyPreBuild/ReleaseProperties.java
M java/build/org/apache/derbyPreBuild/build.xml
The pre-build programs weren't being built. The input
file needed to produce the release properties was moved. Fixed both of
these problems.
-------------------------------
M java/demo/build.xml
The nserverdemo sample program wasn't being built. Now it is.
-------------------------------
M java/org.apache.derby.client/module-info.java
M java/org.apache.derby.commons/module-info.java
M java/org.apache.derby.engine/module-info.java
M java/org.apache.derby.optionaltools/module-info.java
M java/org.apache.derby.runner/module-info.java
M java/org.apache.derby.server/module-info.java
M java/org.apache.derby.tests/module-info.java
M java/org.apache.derby.tools/module-info.java
Corrected a badly formatted <b> element which was cut-and-pasted into
the header javadoc for all the module descriptors.
-------------------------------
M maven2/README.txt
M maven2/SetDerbyVersion.java
A maven2/commons
A maven2/commons/pom.xml
Added a maven module for the new derbyshared.jar file. Removed a check
for the presence of SanityManager.class (in SetDerbyVersion). That
check was failing because the generated class is now included in the shared
module. I have verified that insane builds are still built without the
sanity checks.
-------------------------------
M tools/release/build.xml
Updated the location of the demo programs and the test source.
{noformat}
> Fix release targets to account for modularization changes
> ---------------------------------------------------------
>
> Key: DERBY-7020
> URL: https://issues.apache.org/jira/browse/DERBY-7020
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Priority: Major
> Attachments: derby-7020-01-ab-updateReleaseMachinery.diff
>
>
> Modularization has introduced a new jar file (derbyshared.jar) and some new template policies. We should make sure that all of these assets end up in the release distributions. The maven publishing logic will need to be adjusted to handle derbyshared.jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)