product export issue

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

product export issue

Jayet, Patrick
Hi All,

I have an Eclipse RCP app using the new Groovy Eclipse feature 2.0 (see [1]).

Unfortunately I am having issues exporting my product from Eclipse as well as running a pdeBuild using maven. I am getting the same error message in both cases, which is:

  Bundle org.eclipse.jdt.core_3.5.1.v_972_R35x failed to resolve.:
      Another singleton version selected: org.eclipse.jdt.core_3.5.1.xx-20100115-0900-e35-RELEASE

This is actually normal, since although the Groovy Eclipse plug-ins were bundled with a new version of org.eclipse.jdt.core [2], the original feature of org.eclipse.jdt coming with Eclipse 3.5.1 requires the jdt.core plug-in version [3]. Hence the product cannot be exported since a dependency is missing.

I am aware of a comment thread where Ajay mentions a very similar problem [4], although there seems to be no proper solution presented.

Is there a solution for that product export issue?

For now, the only thing I see is to modify manually the referenced version of org.eclipse.jdt.core in the stock org.eclipse.jdt feature (although this sucks somehow + I will probably run into the security issues that Ajay mentions on the comment thread).

Any suggestion appreciated.
Cheers,

Patrick


[1] My app includes the Groovy Eclipse Feature in one of its feature:
org.codehaus.groovy.eclipse.feature version 2.0.0.xx-20100115-0900-e35-RELEASE
[2] org.eclipse.jdt.core_3.5.1.xx-20100115-0900-e35-RELEASE

[3] org.eclipse.jdt.core_3.5.1.v_972_R35x

[4] http://contraptionsforprogramming.blogspot.com/2009/09/groovy-eclipse-plugin-now-supports.html


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

AW: product export issue

Jayet, Patrick
Hi All,

Feedback about my last post:
- Apparently the solution I mentioned (see [1]) is working. After changing the version to the new jdt.core plug-in in the org.eclipse.jdt feature, I am able to do a product export from Eclipse as well as a maven pdeBuild. I don't get any error so far.

It would be nice though if the Groovy Eclipse plug-ins would come with a feature update for org.eclipse.jdt, so we don't need to do that step manually.

At least I am glad it is running now.

Cheers,
Patrick


[1] For now, the only thing I see is to modify manually the referenced version of org.eclipse.jdt.core in the stock org.eclipse.jdt feature (although this sucks somehow + I will probably run into the security issues that Ajay mentions on the comment thread).
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: [groovy-eclipse-plugin-dev] AW: product export issue

Andrew Eisenberg
It shouldn't be necessary for you to edit the jdt feature.  I can see
2 possibilities, neither of which I have tried out, but I would
imagine could work:

1. Include the org.codehaus.jdt.core feature in your target
environment as well as the org.eclipse.jdt feature.

2. If that doesn't work, you could try provisioning your target
environment just before the build.   I am attaching an ant script that
you can use to install the feature from the update site before your
build.

Let me know if this works for you.  What kind of product are you working on?

On Thu, Jan 21, 2010 at 8:52 AM, Jayet, Patrick <[hidden email]> wrote:

> Hi All,
>
> Feedback about my last post:
> - Apparently the solution I mentioned (see [1]) is working. After changing the version to the new jdt.core plug-in in the org.eclipse.jdt feature, I am able to do a product export from Eclipse as well as a maven pdeBuild. I don't get any error so far.
>
> It would be nice though if the Groovy Eclipse plug-ins would come with a feature update for org.eclipse.jdt, so we don't need to do that step manually.
>
> At least I am glad it is running now.
>
> Cheers,
> Patrick
>
>
> [1] For now, the only thing I see is to modify manually the referenced version of org.eclipse.jdt.core in the stock org.eclipse.jdt feature (although this sucks somehow + I will probably run into the security issues that Ajay mentions on the comment thread).
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

get-dependencies.xml (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

AW: [groovy-eclipse-plugin-dev] AW: product export issue

Jayet, Patrick
Hi Andrew,

> 1. Include the org.codehaus.jdt.core feature in your target
> environment as well as the org.eclipse.jdt feature.

This solution is not working. I had already in my configuration org.codehaus.jdt.patch, but I was getting the error reported in my original e-mail.

> 2. If that doesn't work, you could try provisioning your target
> environment just before the build.   I am attaching an ant script that
> you can use to install the feature from the update site before your
> build.

Sounds complicated. Additionnaly not sure how to integrate the solution into maven's pdeBuild. I will stick to my org.eclipse.jdt tempering solution.

Cheers,
Patrick
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: [groovy-eclipse-plugin-dev] AW: product export issue

Andrew Eisenberg
This will likely work, but if you are redistributing Groovy-Eclipse,
users will not be able to upgrade (either JDT or groovy-eclipse).  The
product will be stuck on whatever version of Groovy-Eclipse is
currently installed, rather than being able to choose based on
previous releases.

PDE builds are not easy and so you shouldn't expect things to work
correctly out of the box.  I don't know anything about maven's pde
build, but I do know that the standard way of performing a pde build
is to provision your target workspace with all dependencies before
each build.  So, the steps would be:

1. Download the Eclipse version you require
2. unzip it
3. Run the p2 director application to install all the additional
plugins and features required to build against
4. run the headless pde build.

It sounds complicated (and it is), but there are quite a few
applications that work this way and from which you can borrow.  For
example, I just finished updating the build scripts for AJDT, that
does exactly this.  You can have a look at them here:

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ajdt/AJDT_src/org.eclipse.ajdt.releng/?root=Tools_Project

On Fri, Jan 22, 2010 at 12:44 AM, Jayet, Patrick <[hidden email]> wrote:

> Hi Andrew,
>
>> 1. Include the org.codehaus.jdt.core feature in your target
>> environment as well as the org.eclipse.jdt feature.
>
> This solution is not working. I had already in my configuration org.codehaus.jdt.patch, but I was getting the error reported in my original e-mail.
>
>> 2. If that doesn't work, you could try provisioning your target
>> environment just before the build.   I am attaching an ant script that
>> you can use to install the feature from the update site before your
>> build.
>
> Sounds complicated. Additionnaly not sure how to integrate the solution into maven's pdeBuild. I will stick to my org.eclipse.jdt tempering solution.
>
> Cheers,
> Patrick
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email