Discussion:
[tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository
Oliver Pfau
2011-12-07 09:58:01 UTC
Permalink
Hi,

my build work fine with tycho 0.12.0. After migration to 0.13.0 no more. My with eclipse.exe generated p2 repository (contains 3rd party libraries which are not available from a public repository) is defined in the parent pom defined as repository. With 0.13.0 this no more works. So I thought I use my eclipse target Definition file as tycho input, but my local p2 repository is added as directory in the target definition and tycho tells me that it does not support this type. Is there any solution for this?

Regards
Oliver
Igor Fedorenko
2011-12-07 12:32:42 UTC
Permalink
What were exact problems when you switched from 0.12 to 0.13?

You should be able to use Update Site location type in .target file,
Directory is indeed not supported.

--
Regards,
Igor

On 11-12-07 4:58 AM, Oliver Pfau wrote:
> Hi,
>
> my build work fine with tycho 0.12.0. After migration to 0.13.0 no
> more. My with eclipse.exe generated p2 repository (contains 3rd party
> libraries which are not available from a public repository) is
> defined in the parent pom defined as repository. With 0.13.0 this no
> more works. So I thought I use my eclipse target Definition file as
> tycho input, but my local p2 repository is added as directory in the
> target definition and tycho tells me that it does not support this
> type. Is there any solution for this?
>
> Regards Oliver _______________________________________________
> tycho-user mailing list tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Oliver Pfau
2011-12-07 12:49:26 UTC
Permalink
Switching from 0.12.0 to 0.13.0 end with build failed because such a 3rd party library could not be resolved for compilation.

If I try to add my p2 repository in the target platform dialog in eclipse, it does not work because there is no category defined.

Yesterday I defined a new project and added a feature which combines this 3rd party jars, added a category.xml and tried to export it as deployable feature to get a update site which I can use as target platform entry and not as directory. Unfortunately eclipse stopped with an error on the resolvement. I do not know exactly why...it was the hamcrest core bundle for jmock bundle from springsource. I stopped at this point...
When I have time, I will the approach to generate the p2 repository mention by Markward Schubert.


-----Ursprüngliche Nachricht-----
Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
Gesendet: Mittwoch, 7. Dezember 2011 13:33
An: tycho-***@eclipse.org
Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository

What were exact problems when you switched from 0.12 to 0.13?

You should be able to use Update Site location type in .target file,
Directory is indeed not supported.

--
Regards,
Igor

On 11-12-07 4:58 AM, Oliver Pfau wrote:
> Hi,
>
> my build work fine with tycho 0.12.0. After migration to 0.13.0 no
> more. My with eclipse.exe generated p2 repository (contains 3rd party
> libraries which are not available from a public repository) is
> defined in the parent pom defined as repository. With 0.13.0 this no
> more works. So I thought I use my eclipse target Definition file as
> tycho input, but my local p2 repository is added as directory in the
> target definition and tycho tells me that it does not support this
> type. Is there any solution for this?
>
> Regards Oliver _______________________________________________
> tycho-user mailing list tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Igor Fedorenko
2011-12-07 12:55:16 UTC
Permalink
It maybe easier for you to wait until I resolve [1] and go from 0.12 to
0.14.0-SNAPSHOT without any changes.

.target file still should work, but it is indeed tedious to setup for
artifacts that are not already available from p2 repositories.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=351842

--
Regards,
Igor

On 11-12-07 7:49 AM, Oliver Pfau wrote:
> Switching from 0.12.0 to 0.13.0 end with build failed because such a 3rd party library could not be resolved for compilation.
>
> If I try to add my p2 repository in the target platform dialog in eclipse, it does not work because there is no category defined.
>
> Yesterday I defined a new project and added a feature which combines this 3rd party jars, added a category.xml and tried to export it as deployable feature to get a update site which I can use as target platform entry and not as directory. Unfortunately eclipse stopped with an error on the resolvement. I do not know exactly why...it was the hamcrest core bundle for jmock bundle from springsource. I stopped at this point...
> When I have time, I will the approach to generate the p2 repository mention by Markward Schubert.
>
>
> -----Ursprüngliche Nachricht-----
> Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
> Gesendet: Mittwoch, 7. Dezember 2011 13:33
> An: tycho-***@eclipse.org
> Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository
>
> What were exact problems when you switched from 0.12 to 0.13?
>
> You should be able to use Update Site location type in .target file,
> Directory is indeed not supported.
>
> --
> Regards,
> Igor
>
> On 11-12-07 4:58 AM, Oliver Pfau wrote:
>> Hi,
>>
>> my build work fine with tycho 0.12.0. After migration to 0.13.0 no
>> more. My with eclipse.exe generated p2 repository (contains 3rd party
>> libraries which are not available from a public repository) is
>> defined in the parent pom defined as repository. With 0.13.0 this no
>> more works. So I thought I use my eclipse target Definition file as
>> tycho input, but my local p2 repository is added as directory in the
>> target definition and tycho tells me that it does not support this
>> type. Is there any solution for this?
>>
>> Regards Oliver _______________________________________________
>> tycho-user mailing list tycho-***@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Oliver Pfau
2011-12-07 14:20:07 UTC
Permalink
Ok...thanks for the hint, I will do so. I have some optional dependencies because the client is build as eclipse rcp and as eclipse rap web client both.

-----Ursprüngliche Nachricht-----
Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
Gesendet: Mittwoch, 7. Dezember 2011 13:55
An: tycho-***@eclipse.org
Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository

It maybe easier for you to wait until I resolve [1] and go from 0.12 to
0.14.0-SNAPSHOT without any changes.

.target file still should work, but it is indeed tedious to setup for
artifacts that are not already available from p2 repositories.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=351842

--
Regards,
Igor

On 11-12-07 7:49 AM, Oliver Pfau wrote:
> Switching from 0.12.0 to 0.13.0 end with build failed because such a 3rd party library could not be resolved for compilation.
>
> If I try to add my p2 repository in the target platform dialog in eclipse, it does not work because there is no category defined.
>
> Yesterday I defined a new project and added a feature which combines this 3rd party jars, added a category.xml and tried to export it as deployable feature to get a update site which I can use as target platform entry and not as directory. Unfortunately eclipse stopped with an error on the resolvement. I do not know exactly why...it was the hamcrest core bundle for jmock bundle from springsource. I stopped at this point...
> When I have time, I will the approach to generate the p2 repository mention by Markward Schubert.
>
>
> -----Ursprüngliche Nachricht-----
> Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
> Gesendet: Mittwoch, 7. Dezember 2011 13:33
> An: tycho-***@eclipse.org
> Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository
>
> What were exact problems when you switched from 0.12 to 0.13?
>
> You should be able to use Update Site location type in .target file,
> Directory is indeed not supported.
>
> --
> Regards,
> Igor
>
> On 11-12-07 4:58 AM, Oliver Pfau wrote:
>> Hi,
>>
>> my build work fine with tycho 0.12.0. After migration to 0.13.0 no
>> more. My with eclipse.exe generated p2 repository (contains 3rd party
>> libraries which are not available from a public repository) is
>> defined in the parent pom defined as repository. With 0.13.0 this no
>> more works. So I thought I use my eclipse target Definition file as
>> tycho input, but my local p2 repository is added as directory in the
>> target definition and tycho tells me that it does not support this
>> type. Is there any solution for this?
>>
>> Regards Oliver _______________________________________________
>> tycho-user mailing list tycho-***@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Davy Meers
2011-12-07 12:56:59 UTC
Permalink
Hello,
This probably won't solve all your problems but the jmock and hamcrest core bundles are available in an eclipse update site so you don't have to create your own update site for them.The update site can be found as part of the Eclipse orbit project (see http://download.eclipse.org/tools/orbit/downloads/drops/S20111201180206/).

Regards,Davy
> From: ***@scalaris.com
> To: tycho-***@eclipse.org
> Date: Wed, 7 Dec 2011 13:49:26 +0100
> Subject: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository
>
> Switching from 0.12.0 to 0.13.0 end with build failed because such a 3rd party library could not be resolved for compilation.
>
> If I try to add my p2 repository in the target platform dialog in eclipse, it does not work because there is no category defined.
>
> Yesterday I defined a new project and added a feature which combines this 3rd party jars, added a category.xml and tried to export it as deployable feature to get a update site which I can use as target platform entry and not as directory. Unfortunately eclipse stopped with an error on the resolvement. I do not know exactly why...it was the hamcrest core bundle for jmock bundle from springsource. I stopped at this point...
> When I have time, I will the approach to generate the p2 repository mention by Markward Schubert.
>
>
> -----Ursprüngliche Nachricht-----
> Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
> Gesendet: Mittwoch, 7. Dezember 2011 13:33
> An: tycho-***@eclipse.org
> Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository
>
> What were exact problems when you switched from 0.12 to 0.13?
>
> You should be able to use Update Site location type in .target file,
> Directory is indeed not supported.
>
> --
> Regards,
> Igor
>
> On 11-12-07 4:58 AM, Oliver Pfau wrote:
> > Hi,
> >
> > my build work fine with tycho 0.12.0. After migration to 0.13.0 no
> > more. My with eclipse.exe generated p2 repository (contains 3rd party
> > libraries which are not available from a public repository) is
> > defined in the parent pom defined as repository. With 0.13.0 this no
> > more works. So I thought I use my eclipse target Definition file as
> > tycho input, but my local p2 repository is added as directory in the
> > target definition and tycho tells me that it does not support this
> > type. Is there any solution for this?
> >
> > Regards Oliver _______________________________________________
> > tycho-user mailing list tycho-***@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Oliver Pfau
2011-12-07 12:52:39 UTC
Permalink
Forgot, this was the exception:

[ERROR] GenericObjectPool cannot be resolved to a type
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.13.0:compile (defa
lt-compile) on project com.scalaris.prointra.icrmonitor.common: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure
at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:409)
at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:162)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]

-----Ursprüngliche Nachricht-----
Von: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] Im Auftrag von Igor Fedorenko
Gesendet: Mittwoch, 7. Dezember 2011 13:33
An: tycho-***@eclipse.org
Betreff: Re: [tycho-user] Migration from 0.12.0 to 0.13.0 with local p2 repository

What were exact problems when you switched from 0.12 to 0.13?

You should be able to use Update Site location type in .target file,
Directory is indeed not supported.

--
Regards,
Igor

On 11-12-07 4:58 AM, Oliver Pfau wrote:
> Hi,
>
> my build work fine with tycho 0.12.0. After migration to 0.13.0 no
> more. My with eclipse.exe generated p2 repository (contains 3rd party
> libraries which are not available from a public repository) is
> defined in the parent pom defined as repository. With 0.13.0 this no
> more works. So I thought I use my eclipse target Definition file as
> tycho input, but my local p2 repository is added as directory in the
> target definition and tycho tells me that it does not support this
> type. Is there any solution for this?
>
> Regards Oliver _______________________________________________
> tycho-user mailing list tycho-***@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tycho-user
Loading...