Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Question on Maven/Tycho target mechanism using .target file

relativePath is not supported for target GAVs, version is required.

you need to specify the full GAV.

This kind of incomplete configuration should actually fail the build with a clear error message:


From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Geyer-Blaumeiser Lars (ETAS/ESW ETAS/ESW5)
Sent: Freitag, 20. Februar 2015 08:10
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] Question on Maven/Tycho target mechanism using .target file

Hello all,

I have a problem with the Maven/Tycho mechanism to resolve a .target file. I followed the information on, but do not get the expected results. Here are some facts:

Target file:

<target name="Eclipse Kepler Target" sequenceNumber="1424335573">
    <location includeMode="slicer" includeAllPlatforms="false" includeSource="false" includeConfigurePhase="false" type="InstallableUnit">
        <unit id="" version="0.0.0"/>
        <unit id="" version="0.0.0"/>
        <unit id=""  version="0.0.0"/>
        <repository id="kepler" location=""/>
    <location includeMode="slicer" includeAllPlatforms="false" includeSource="false" includeConfigurePhase="false" type="InstallableUnit">
        <unit id="ch.qos.logback.classic" version="0.0.0"/>
        <unit id="ch.qos.logback.classic.source" version="0.0.0"/>
        <unit id="ch.qos.logback.core" version="0.0.0"/>
        <unit id="ch.qos.logback.core.source" version="0.0.0"/>
        <unit id="ch.qos.logback.slf4j" version="0.0.0"/>
        <unit id="ch.qos.logback.slf4j.source" version="0.0.0"/>
        <unit id="org.slf4j.api" version="0.0.0"/>
        <unit id="org.slf4j.api.source" version="0.0.0"/>
        <repository id="orbit" location=""/>

The pom-File for the target module:

<?xml version="1.0" encoding="UTF-8"?>
       xmlns=""; xmlns:xsi="";>

I do not have a version in here, because I found a page in the web which told the story that a version in the pom for the eclipse-target-packaging does not work and in fact, specifying a version resulted in not resolving the following configuration in the parent pom used for all other maven modules:


With this in place I get the following error message during the maven build:

[INFO] Scanning for projects...
[INFO] Computing target platform for MavenProject: com.etas.congra.releng:com.etas.congra.log:0.1.0-SNAPSHOT @ D:\ConGra_IDE_Luna_win64\git\congra\plugins\com.etas.congra.log\pom.xml
[INFO] Resolving dependencies of MavenProject: com.etas.congra.releng:com.etas.congra.log:0.1.0-SNAPSHOT @ D:\ConGra_IDE_Luna_win64\git\congra\plugins\com.etas.congra.log\pom.xml
[INFO] Cannot complete the request.  Generating details.
[INFO] Cannot complete the request.  Generating details.
[INFO] {, osgi.os=win32, osgi.arch=x86_64, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR]   Software being installed: com.etas.congra.log 0.1.0.qualifier
[ERROR]   Missing requirement: com.etas.congra.log 0.1.0.qualifier requires 'bundle ch.qos.logback.classic 1.0.7' but it could not be found

It cannot resolve dependencies from the target, although the target works properly in the eclipse workspace and if all repositories mentioned in the target files are expressed as repository tags in the pom file, the build works.

Has anybody an idea what is wrong in my configuration?

Thanks and best regards,

Mit freundlichen Grüßen/Best Regards,
Lars Geyer-Blaumeiser


Dr. Lars Geyer-Blaumeiser

Senior Engineer
Borsigstr. 14
70469 Stuttgart

Phone +49 172 4815079

Managing Directors: Friedhelm Pickhard, Bernd Hergert, Christopher White
Chairman of Supervisory Board: Dr. Walter Schirm
Registered Office: Stuttgart; Registration Court: Amtsgericht Stuttgart HRB 19033

Back to the top