Assuming your ORM has a Maven plug-in,
      I recommend you to configure it in the pom.xml files.
      Then when you import the projects in Eclipse using m2e, m2e will
      perform some analysis of the Maven plug-ins configured and will
      run those. When m2e analyzes the plug-ins two things can happen:
          1 - the maven plug-in is understood by default, nothing needs
      to be done
          2 - the maven plug-in requires a specific Eclipse plug-in
      called a connector
      (
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html)
      to be installed in which case two things can happen
              a - an eclipse plug-in exists for this maven plug-in and
      all is good
              b - no eclipse plug-in exists  <<-- this will likely
      be your case
      
      So the bottom line is if you want to use the ORM and have it just
      work for Maven and Eclipse, you will likely have to write a
      connector.
      
      If you don't feel like doing this connector authoring, you may
      want to try to add a Builder to the project (right click >
      Builders).
      
      HTH
      
      Pascal
      
      On 02/11/2015 09:43 PM, Jim Klo wrote:
    
 
    
      
      Greetings,
      
      
      I’m using EBean ORM within one my plug-ins which
        requires some Enhancement to be done to the persistent beans.
         This can be usually done at runtime, however it requires the
        JDK, which may not be present (and I’m not sure what the
        redistribution rules on the JDK is since we already package with
        JRE).
      
      
      One solution to my problem is that I can pre-enhance
        the beans to generate the class files using an ant task or maven
        plugin, however - this kind of makes developing the app inside
        the IDE a PITA because each time something get’s modified one
        would have to run the maven goal to generate the code, refresh
        eclipse, then launch the debugger from within eclipse.
      
      
      Since I’m assuming others have run into similar
        situations in working with tycho, can anyone recommend a
        solution that allow me to do something to the plugin.xml,
        manifest, etc that would make the development cycle more
        pain-free that would permit me to execute some custom build step
        before compilation of the classes, and is either complimentary
        or integrates with tycho?
      
      
      Thanks,
      
      
      Jim
      
        
          
            
                
                    
                        
                            
                                
                                    Jim Klo
                                    Senior Software Engineer
                                    Center for Software
                                      Engineering
                                    SRI International
                                   
                               
                           
                       
                   
               
            
              
             
         
        
       
      
      
      
      _______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user