Hello All, 
 
    I will add the signing and obfuscation pre/post states. I will
commit the changes soon. 
 
Regards, 
 
David Marques 
 
Jon Dearden wrote:
  I am in favor of offering the SDK suppliers all the flexibility that we can within reason. For RIM, our signing process can be a little different, so some extra intervention at this stage may be very useful. 
Cheers,
Jon Dearden
 
----- Original Message -----
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx <dsdp-mtj-dev-bounces@xxxxxxxxxxx>
To: Mobile Tools for The Java Platform mailing list <dsdp-mtj-dev@xxxxxxxxxxx>
Sent: Fri Apr 17 08:59:23 2009
Subject: Re: [dsdp-mtj-dev] Build Hooks commits.
I *think* so, but I'm not the ultimate consumer.  Given that  
deployment packaging invokes most of the same builder code along the  
way, it seems it should also invoke any hooks in the extra build steps.
Anyone else?  Ken?
Craig
On Apr 17, 2009, at 7:14 AM, David Marques wrote:
   
  
    Hi Craig,
  There are two steps that only happen during a deployment package  
(obfuscation and signing). Would it be interesting to add them to  
the hooks ??
Regards,
David Marques
Craig Setera wrote:
    
    
      There are a couple of steps in the build that only happen during a  
deployment package, correct?  (obfuscation for instance).  Will  
those trigger the build hooks?
On Apr 16, 2009, at 12:44 PM, David Marques wrote:
      
      
        Hi Craig,
 I did not get what you mean, could you be more clear ??
Regards,
David Marques
Craig Setera wrote:
        
        
          Where did you net out on build hook calls for deployment  
packaging versus incremental build?
On Apr 16, 2009, at 9:29 AM, David Marques wrote:
          
          
            Hello Everyone,
I have just committed the code of the build hooks and i have  
also updated the requirements (http://wiki.eclipse.org/DSDP/MTJ/Requirements/MTJ_Build#ID 
:_build:FR007_- 
_MTJ_shall_define_an_extension_point_for_build_hooks).
Hope everyone likes it!
Regards,
David Marques
_______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
            
           
          _______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
          
         
        _______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
        
       
      _______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
      
     
    _______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
    
   
  
_______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
   
  
 
_______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
   
 
 
 |