[ 
http://issues.apache.org/jira/browse/GERONIMO-2358?page=comments#action_12432550
 ] 
            
Jacek Laskowski commented on GERONIMO-2358:
-------------------------------------------

I cannot apply this patch. I'm getting errors about missing files that are to 
be patched, e.g. branches/jee5_exp/geronimo-spec-annotation/NOTICE.txt (which 
seems to be a valid error message since the file has been moved in the first 
step).

I'd like to have it promoted to trunk and thus I'm +1 this. I'll take a look at 
the corresponding commit change to see how it went.

> Move java ee 5 specs into specs trunk
> -------------------------------------
>
>                 Key: GERONIMO-2358
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2358
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: specs
>            Reporter: David Blevins
>         Assigned To: David Blevins
>         Attachments: GERONIMO-2358-1.patch
>
>
> Back in I think March, I created a branch for implementing the Java EE 5 
> specs while the specs were still being defined.  The specs went final in May 
> and several projects need these specs.  We need to get them out of the 
> experimental branch and into trunk.
> The attached patch moves the required specs from branches/jee5_exp to trunk/ 
> and fixes their poms to be consistent with the rest of the poms.
> *Please* note: patch files created with svn *cannot* express 'svn move' 
> commands, in order to apply this patch you must first do the following moves:
>   svn mv branches/jee5_exp/geronimo-jta_1.1_spec trunk/geronimo-jta_1.1_spec
>   svn mv branches/jee5_exp/geronimo-spec-annotation 
> trunk/geronimo-annotation_1.0_spec
>   svn mv branches/jee5_exp/geronimo-spec-ejb trunk/geronimo-ejb_3.0_spec
>   svn mv branches/jee5_exp/geronimo-spec-interceptor 
> trunk/geronimo-interceptor_3.0_spec
>   svn mv branches/jee5_exp/geronimo-spec-jpa trunk/geronimo-jpa_3.0_spec

-- 
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