I'm little confused by the target file.
I've define a p2 mirror defined in my settings and use target-platform-configuration in my pom. When I build maven uses nexus p2 repo repo to calculate the target platform and I'd rather did this one and from then on used local files. If I run mvn --offline it still goes out to nexus to computer the platform. It is as if
tycho.localArtifacts is begin set
I must be missing a configuration option because this seems like incorrect behavior.
From my pom
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho-version}</version>
<configuration>
<resolver>p2</resolver>
<ignoreTychoRepositories>true</ignoreTychoRepositories>
<pomDependencies>consider</pomDependencies>
<environments>
<environment>
<os>win32</os>
<ws>win32</ws>
<arch>x86_64</arch>
</environment>
<environment>
<os>linux</os>
<ws>gtk</ws>
<arch>x86_64</arch>
</environment>
</environments>
<target>
<artifact>
<groupId>myapp</groupId>
<artifactId>targetplatform</artifactId>
<version>1.0.0-SNAPSHOT</version>
</artifact>
</target>
</configuration>
</plugin>
From my settings.xml
<mirrors>
<mirror>
<id>internal-repository</id>
<name>Maven2 Public Group</name>
<url>
http://mynexus/nexus/content/groups/public</url>
<mirrorOf>*</mirrorOf>
</mirror>
<mirror>
<id>p2-internal-repository</id>
<name>P2 Public Group</name>
<url>
http://mynexus/nexus/content/groups/p2.group.public/</url>
<layout>p2</layout>
<mirrorOfLayouts>p2</mirrorOfLayouts>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
Please let me know if you see an important item out of order.
FYI - I switched to nexus pro because they only support p2 repositories on pro. I tried getting them to work on OSS by adding plugins but it never worked. Pro has some other benefits too like staging with should allow me to automate more of my release process.
