Carlo Salinari wrote:

> Being maven-ignorant (I'll study it. Promise.) I need a little hand
> building branches\release-1.3\swt under windows 7 64bit.
> My mvn -version says:
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_23
> Java home: C:\Program Files\Java\jdk1.6.0_23\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
> following I
> tried adding this to release-1.3\swt\pom.xml:
>    <profile>
>      <id>windows_64</id>
>      <activation>
>        <os>
>          <family>windows</family>
>          <arch>amd64</arch>
>        </os>
>      </activation>
>      <properties>
>        <swt.groupId>org.eclipse.swt.win32.win32</swt.groupId>
>        <swt.artifactId>x86_64</swt.artifactId>
>      </properties>
>    </profile>
>    <profile>
> but it didn't make the trick. I guess I also have to tell maven where to
> fetch swt.win32.win32.x86_64, right? Should I modify the parent pom?

I don't believe this should be necessary.  The mess with Mac OSX is
because there are carbon and cocoa and ppc and intel versions of SWT
and maven profiles can't properly distinguish between them.

Our issue

links to Maven and Eclipse issues.

Try these and post here

$ mvn enforcer:display-info
$ mvn help:active-profiles

> Btw: why is the dependency
>      <version>[3.3.0-v3346,)</version>
> so strict?

Eclipse artifacts currently don't play nice with the Maven world, and
3.3.0-v3346 is the latest version in the Maven central repository.
Most SWT users would want to build against a more recent version,
which can be installed manually using something like

$ mvn install:install-file -Dfile=./swt.jar \
  -DartifactId=macosx \
  -Dversion=XXX \


Piccolo2D Developers Group:

Reply via email to