Re: [tycho-user] product file + eclipse-repository + local application s

[<jan.hofmayer@xxxxxxxxxxxxx>]

Hi Igor,

what do you mean by collocating? Let's say we have the following structure

 sample.plugin
 \- pom.xml: <packaging>eclipse-plugin</packaging>

 eclipse-repository
 |-pom.xml: <packaging>eclipse-repository</packaging>
 \-product.product: <plugins><plugin id="sample.plugin" /></plugins>

If I want to start the rich client out of the Eclipse workspace using that product file, that does not work. At least for me I need to add the eclipse-repository to it:

 eclipse-repository
 |-pom.xml: <packaging>eclipse-repository</packaging>
 \-product.product: <plugins><plugin id="sample.plugin" /><plugin id="eclipse-repository" /></plugins>

Which does not work for Maven, because it cannot resolve the plugin <plugin id="eclipse-repository" />. I tried to separate it but the product file needs to be in the folder where the pom with  <packaging>eclipse-repository</packaging> is. Or are there other ways of separating it, to have something like this:

 eclipse-repository
 \-pom.xml: <packaging>eclipse-repository</packaging>

 eclipse-product
 |-pom.xml: <packaging>eclipse-plugin</packaging>
 \-product.product: <plugins><plugin id="sample.plugin" /><plugin id="eclipse-product" /></plugins>

Hope I could make it clear what I mean ^^

Jan

-----Original Message-----
From: Igor Fedorenko [mailto:igor@xxxxxxxxxxxxxx]
Sent: Donnerstag, 6. September 2012 12:44
To: Tycho user list; Hofmayer, Jan
Subject: Re: [tycho-user] product file + eclipse-repository + local application startup

Are you collocating product and plugin in the same maven module? This is not supported by Tycho. You need separate modules.
--
Sent from my SGS

jan.hofmayer@xxxxxxxxxxxxx wrote:

>Hi,
>
>I've got a multi module rich client build which is based on a product
>file (using Tycho 0.15.0). I now would like to use that product file
>for the Maven build and for local application start up (out of the
>Eclipse workspace).
>
>The problem is, that if you want to start it out of Eclipse, you need
>to have a dependency in the product file to the plug-in where the
>product file is in. If you don't have that, the application crashes at
>start up with
>
>!ENTRY org.eclipse.equinox.app 0 0 2012-09-06 12:06:53.244 !MESSAGE
>Product rc.product could not be found.
>
>.
>.
>.
>
>!ENTRY org.eclipse.osgi 4 0 2012-09-06 12:06:53.275 !MESSAGE
>Application error !STACK 1
>java.lang.RuntimeException: No application id has been found.
>
>
>But if you add that dependency, the Maven build will complain with
>
>[ERROR] Internal error: java.lang.RuntimeException: "No solution found
>because the problem is unsatisfiable.": ["Unable to satisfy dependency
>from rc-eclipse-repository.product 0.0.0 to rc-eclipse-repository
>0.0.0.", "No solution found because the problem is unsatisfiable."] ->
>[Help 1]
>
>I think that is the case because the product file's pom.xml is
>
><packaging>eclipse-repository</packaging>
>
>and not
>
><packaging>eclipse-plugin</packaging>
>
>and therefore it is no plugin for the Maven build when it resolves it
>dependencies.
>
>Of course there's an easy workaround (just tell every developer "fix
>that locally, but don't check it in"), but I was wondering if there is
>a better solution for this?
>
>Thanks,
>Jan
>
>
>________________________________
>This message is for the designated recipient only and may contain
>privileged, proprietary, or otherwise private information. If you have
>received it in error, please notify the sender immediately and delete
>the original. Any other use of the email by you is prohibited.
>
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>tycho-user mailing list
>tycho-user@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-user



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.