IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 2 replies
  • Latest Post - ‏2013-06-25T14:14:32Z by adbdkb
adbdkb
adbdkb
45 Posts

Pinned topic What are the differences between "Build Path ( Project Tab)" "Project References" and "Deployment Assembly"?

‏2013-06-20T23:12:22Z |

What are the differences between "Build Path ( Project Tab )",  "Project References" and "Deployment Assembly"  for a project?

And which should be used for what  purpose?

Thank you

 

 

Updated on 2013-06-25T14:15:20Z at 2013-06-25T14:15:20Z by adbdkb
  • rsanchezh
    rsanchezh
    47 Posts

    Re: What are the differences between "Build Path" "Project References" and "Deployment Assembly"?

    ‏2013-06-24T20:25:07Z  

    Hello,

    I include links to two articles from developer works that can help you understand a little bit more the usage of the Deployment assembly page and its relation with the build path.

    - Java EE Deployment Assembly

    - Understanding class paths in Java EE projects with Rational Application Developer Version 8.0

     

     

  • adbdkb
    adbdkb
    45 Posts

    Re: What are the differences between "Build Path ( Project Tab )" "Project References" and "Deployment Assembly"?

    ‏2013-06-25T14:14:32Z  
    • rsanchezh
    • ‏2013-06-24T20:25:07Z

    Hello,

    I include links to two articles from developer works that can help you understand a little bit more the usage of the Deployment assembly page and its relation with the build path.

    - Java EE Deployment Assembly

    - Understanding class paths in Java EE projects with Rational Application Developer Version 8.0

     

     

    Thank you.  I had seen those documents, they explain the individual purpose but do not explain collectively how these three work together and both of them do not explain how "Project References" are to be / can be used.

    What I have understood so far -

    Build Path - Projects Tab - If you add an existing project from the workspace in the project tab, it is used / added in the classpath, so you can build the project without errors.  But if you export the EAR from RAD, it will have runtime errors as the added project is not part of the runtime classpath

    Deployment Assembly ->  If you add existing projects from the workspace, when exporting the EAR, the references are resolved when building the ear and so it will not have runtime errors

    Do we have to have both of these set-up in RAD to get the project properly compiled and execute with WTE?

    Project References - What role does this play?  What effect / impact does it have on compile time / runtime of the project definition?

     

     

    Updated on 2013-06-25T15:32:12Z at 2013-06-25T15:32:12Z by adbdkb