[ http://issues.apache.org/jira/browse/JDO-374?page=all ]
Michael Bouschen updated JDO-374:
---------------------------------
Attachment: JDO-374-mbo.patch
Please review the patch JDO-374-mbo.patch. I understand these changes should go
into the trunk and into braches/2.0.
It adds a goal tck20.dist to maven.xml on the trunk or branches/2.0 level. I
think it is not necessary to call tck20.defualt from this goal, since maven
dist takes care of compiling all the sources.
It also adds a postGoal to the maven dist goal that copies the distribution and
the files for the remote maven repositories to the releases directory parallel
to trunk and branches.
There is an issue with automatically signing these files, because it requires
typing in the passphrase and I could not convince maven to accept input for a
script called from a goal. So I propose we use a script like the sign-directoy
script Craig attached to JDO-365. I also propose
to create scripts to push the artifacts to the staging area and the
mirror-accessible Apache server and not use maven goals for this.
> Add a maven target to create distribution artifacts for all subprojects of
> tck20
> --------------------------------------------------------------------------------
>
> Key: JDO-374
> URL: http://issues.apache.org/jira/browse/JDO-374
> Project: JDO
> Type: Improvement
> Components: tck20, api20, core20, enhancer20
> Versions: JDO 2 rc1
> Reporter: Craig Russell
> Priority: Minor
> Fix For: JDO 2 final
> Attachments: JDO-374-mbo.patch, JDO-374.patch
>
> There are several maven tck20 build targets. I propose to add a target that
> builds the distribution targets for all subprojects of tck20.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
