Skip to Content
0
Former Member
Oct 03, 2006 at 08:32 AM

Best practice for handling custom apps tracks with regards to EP upgrade?

27 Views

Hi,

We've are currently in the progress of upgrading from EP 6 to EP 7.0, and in that context we need to "move" our tracks containg development of custom J2EE components.

What we've done so far is :

1.Create a new version 7.00 of each software component we have developed with correct EP 7 dependencies

2. Create a new version 7.00 of our product in the SLD: Bouvet_EP

3. Attached the new versions of the SCs to the new product version

4. Create a new track with the SC of version 7.00 along with relevant dependencies

My question now is how do we get the EP 6 component source code into the new track, so that we can change dependecies of the DCs and build it again for EP 7.0?

Should we somehow export the code from the old track, check in and transport ? (how do we then export the code from the track)

Regards

Dagfinn