Building 4.2 Amp as part of 5.0 all in one

[georgera]

I have an amp project that I made as part of a 4.2 all in one maven archetype project and it works fine there. Now I'm trying to build it as part of 5.0 all in one and it gets a bunch of package does not exist errors.

Such as:
package org.apache.commons.logging does not exist
package org.springframework.extensions.webscripts does not exist
package org.json does not exist

Other packages is doesn't complain about

javax.naming.NamingEnumeration
java.io.IOException
java.util.Hashtable

for example.

I didn't do anything special to include those packages in the 4.2 project so I would think I wouldn't have to in 5.0 either.

4.2 was built with the 1.1.1 SDK and the 5.0 was built with the 2.0.0 sdk

[gravitonian]

Hi,

This has not changed, the amp pom brings in the following dependency:

<dependencies>
        <dependency>
            <groupId>${alfresco.groupId}</groupId>
            <artifactId>alfresco-repository</artifactId>
        </dependency>
    </dependencies>
‍‍‍‍‍‍‍‍

Which has transient dependencies to the other libraries you were mentioning.

So should work the same in 5.0 with SDK 2.0.0.

[mrogers]

It will/may need to change on HEAD/5.1.    But you say you are building with 5.0 so that should work.