I discovered a way around this.  It basically involves coding around the
maven version comparison issue.

I tried it out on the cas-editor, and got it to work.  Here's what's
involved:

In the POM, when you state a dependency:

        <dependency>
            <groupId>org.eclipse.core</groupId>
            <artifactId>resources</artifactId>
            <version>[3.3.0,4.0.0)</version>
            <scope>provided</scope>
        </dependency>

it fails because what's in the repo is 3.3.0-vXXXXXXetc.  To make this
work, just change the dependency to one notch lower:

        <dependency>
            <groupId>org.eclipse.core</groupId>
            <artifactId>resources</artifactId>
            <version>[3.2.9,4.0.0)</version>
            <scope>provided</scope>
        </dependency>

I did this and it *almost* worked - there was one other change needed:
the dependency for SWT win32 support in the main repo has a different
groupId/artifactId and needed to be changed to:

        <dependency>
            <groupId>org.eclipse.swt.win32.win32</groupId>
            <artifactId>x86</artifactId>
            <version>[3.2.9,4.0.0)</version>
            <scope>provided</scope>
        </dependency>

With this change, we can remove all references to a special Eclipse
repository location.  I'm in favor of this; what do others think?

-Marshall

Marshall Schor wrote:
> Jörn Kottmann wrote:
>   
>> Marshall Schor wrote:
>>     
>>> ...  
>>>       
>> Marshall is there anything we can do to avoid this issue ?
>>     
> I learned another maven command-line thing that purges your local
> repository of just the things in a particular Pom.  The command is:
>
> mvn dependency:purge-local-repository
>
>   
>> Maybe we can use another version of eclipse as dependency.
>>
>>     
> I think this is definitely worth investigating.  It's quite possible
> that later version of Eclipse jar uploading to the central maven repo
> have found a way around this.
>   
>> I also noticed that our eclipse plugins depend on different eclipse
>> version, would it be an advantage to only depend on one ?
>>
>>     
> I don't think there's any advantage.  What happens I think, is that
> these jars are used to make the compile step work, but at runtime, these
> jars are all "provided" by the particular Eclipse environment.
>
> -Marshall
>   
>> Jörn
>>
>>
>>     
>
>
>   

Reply via email to