[ 
http://issues.apache.org/jira/browse/JDO-374?page=comments#action_12377048 ] 

Craig Russell commented on JDO-374:
-----------------------------------

Just one comment. The scripts now copy three TCK source artifacts to the 
releases/xxx/dist directory:
-rw-r--r--   1 clr  staff  1799038 Apr 28 17:33 
jdo2-tck-SNAPSHOT-src-28_Apr_2006.zip
-rw-r--r--   1 clr  staff   866691 Apr 28 17:33 jdo2-tck-SNAPSHOT-src.tar.gz
-rw-r--r--   1 clr  staff  1799038 Apr 28 17:33 jdo2-tck-SNAPSHOT-src.zip

But thinking a bit more about this, the reason we had the funnny name in the 
first place was to match the JCP naming conventions. But now it looks like we 
don't need the JCP to distribute it, so we can go back to the "real" naming 
conventions. What do you think?

> 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

Reply via email to