Hi,
I managed reproduce the problem locally by putting aside the content
of .m2/repository/org/apache/chemistry/opencmis and doing an offline
build:
mvn -DskipTests -o clean package
The issue is due to the new OSGi stuff: the built artifacts actually
use the "bundle" packaging now, and we should specify that somewhere.
This is clear in the error messages:
[INFO] Building OpenCMIS Commons API
... (ok) ...
[INFO] Building OpenCMIS Commons Implementation
[INFO] Failed to resolve artifact.
1)
org.apache.chemistry.opencmis:chemistry-opencmis-commons-api:jar:0.1.0-incubating-SNAPSHOT
Path to dependency:
1)
org.apache.chemistry.opencmis:chemistry-opencmis-commons-impl:bundle:0.1.0-incubating-SNAPSHOT
2)
org.apache.chemistry.opencmis:chemistry-opencmis-commons-api:jar:0.1.0-incubating-SNAPSHOT
1 required artifact is missing.
So it's in the process of building
chemistry-opencmis-commons-impl:bundle and does not find
chemistry-opencmis-commons-api:jar (which is logical since what it
just built is chemistry-opencmis-commons-api:bundle).
I don't have to work on it just now, so if someone wants to have a look...
Florent
On Wed, Aug 4, 2010 at 3:33 PM, Nick Craft <[email protected]> wrote:
> I got the build to work. This required me to do a mvn clean install as
> you suggested, but I had to do it on both the commons-api and the
> commons-impl modules. Only doing it on the commons-api resulted in a
> missing symbol while compiling chemistry-opencmis-server: "- cannot
> find symbol symbol : constructor
> PropertiesImpl(java.util.Collection<org.apache.chemistry.opencmis.commons.data.PropertyData<?>>)
> location: class
> org.apache.chemistry.opencmis.commons.impl.dataobjects.PropertiesImpl".
>
> Thanks for the help with this everyone. Florent - please let me know
> if you still need me to reproduce the issue and run the Maven -X debug
> build, for your own diagnostic purposes - I'd me happy to do so if it
> helps.
>
> Nick Craft
>
> On Wed, Aug 4, 2010 at 4:52 AM, Jens Hübel <[email protected]> wrote:
>> I have seen exactly the same behavior on one machine while it worked on
>> another (even with a mvn clean).
>>
>> I suspect that sometimes during the build the compilation runs against the
>> jars in the maven repository and not against the compiled sources in the
>> subprojects. Then the newly added ExtensionLevel class is missing. Is there
>> an option that forces mvn to ignore the repositories for everything that is
>> part of the current project? Do we have a hidden issue in our dependencies?
>> I worked around by first going to
>> chemistry-opencmis-commons\chemistry-opencmis-commons-api and do a mvn clean
>> install there.
>>
>> Jens
>>
>>
>> -----Original Message-----
>> From: Nick Craft [mailto:[email protected]]
>> Sent: Dienstag, 3. August 2010 23:27
>> To: [email protected]
>> Subject: Error Building OpenCMIS Client - missing ExtensionLevel symbol
>>
>> Hi there,
>>
>> I'm getting the following error when attempting to build the current
>> HEAD of OpenCMIS trunk following the instructions at
>> http://incubator.apache.org/chemistry/opencmis-how-to-build.html
>>
>> Any advice would be appreciated.
>>
>> Thanks,
>> Nick Craft
>>
>> C:\develop\OpenCMIS\trunk-979352\chemistry-opencmis-client\chemistry-opencmis-client-api\src\main\java\org\apache\chemistry\opencmis\client\api\CmisObject.java:[30,51]
>> cannot find symbol
>> symbol : class ExtensionLevel
>> location: package org.apache.chemistry.opencmis.commons.enums
>>
>> C:\develop\OpenCMIS\trunk-979352\chemistry-opencmis-client\chemistry-opencmis-client-api\src\main\java\org\apache\chemistry\opencmis\client\api\CmisObject.java:[160,31]
>> cannot find symbol
>> symbol : class ExtensionLevel
>> location: interface org.apache.chemistry.opencmis.client.api.CmisObject
>>
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
