Re: [iam-dev] Including P2 metadata in Q4E of update site

["Andrew Eisenberg" <andrew@xxxxxxxxxxxx>]

>From an OSGi/Eclipse POV, turning off the issingleton bit on the
aspectj runtime bundle will allow multiple versions to run at the same
time (and according to documentation, P2 respects the issingleton flag
in MANIFEST.MF, but I haven't tried this out yet).  I'm not sure what
the behavior would be if an older version is a singleton, but a newer
version is not.

I have changed the org.aspect.runtime bundle to *not* be a singleton.
You can add this version to your repository (and re-generate the
metadata), or you can change the manifest file of the version you
currently have.

However, as I said, there is no difference in the code between aspectj
runtime versions going back several years now.  And there will always
be backwards compatibility.  So, I am not sure what the benefit of
having multiple versions would be.

--a


On Thu, Jan 8, 2009 at 11:34 AM, Joakim Erdfelt
<joakim.erdfelt@xxxxxxxxx> wrote:
> Do you know how to get P2 to (allow?) install 2 versions of the same plugin?
> We know this is possible from an OSGi / Eclipse point of view, and want to
> allow that scenario.
>
> The divergence in versions between maven embedder and ajdt will just grow
> over time, we would like to keep the embedder locked to a specific version,
> and have another aspectj present for AJDT to use as well.  We've hit
> compatibilty problems (forwards and back) with having just 1 active
> org.aspectj.runtime bundle (similar issues with lucene also), and want to
> utilize the multiple versions of a bundle in OSGi better, but within the
> constraints of P2.  Can you help?
>
> Having 2 installed / active org.aspectj.runtime bundles is what we think we
> need.  what do you think?
>
> - Joakim
>
> 2009/1/8 Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>>
>> I manually edited the content.jar from
>> http://q4e.googlecode.com/svn/trunk/updatesite-dev/ so that it is more
>> forgiving on the versions of apsectj.runtime bundle that it accepts.
>> This seems to work for installing AJDT when I was installing it from a
>> local repository.  Just replace the existing content.jar with this
>> one.
>>
>> It's not the ideal solution.  Better would be to update the
>> MANIFEST.MF for org.apache.maven.embedder such that the imported
>> packages contain version numbers on them (something like min version
>> 1.2, and no max version).  Then recreate the repository from there.
>>
>> org.aspectj.runtime has not changed since version 1.2.  The only
>> reason that version numbers keep changing is to keep it aligned with
>> the version of the weaver.
>>
>> On Thu, Jan 8, 2009 at 1:02 AM, Carlos Sanchez <carlos@xxxxxxxxxx> wrote:
>> > Please see this and related issues
>> > http://code.google.com/p/q4e/issues/detail?id=539
>> >
>> > the update sites are in svn at
>> > http://q4e.googlecode.com/svn/trunk/updatesite/
>> > http://q4e.googlecode.com/svn/trunk/updatesite-dev/
>> >
>> > any help is greatly appreciated
>> >
>> > On Thu, Jan 8, 2009 at 1:16 AM, Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>> > wrote:
>> >> Hi all,
>> >>
>> >> The update site available at
>> >> http://q4e.googlecode.com/svn/trunk/updatesite/ does not have P2
>> >> metadata in it.  This is causing problems for users who want to
>> >> install other versions of plugins provided by this update site.
>> >>
>> >> Specifically, it is not possible to install both AJDT and Q4E.  This
>> >> is because you provide AspectJ runtime bundle version 1.5.4 (we are
>> >> currently at 1.6.3).
>> >>
>> >> Is there somewhere else to go for Q4E that has P2 metadata available?
>> >> This is fairly high priority for us and I am willing to help out.  If
>> >> someone can send me a zip of the update site, then I will look into
>> >> adding the P2 metadata.
>> >>
>> >> thanks,
>> >> --andrew eisenberg
>> >> http://eclipse.org/ajdt
>> >> _______________________________________________
>> >> iam-dev mailing list
>> >> iam-dev@xxxxxxxxxxx
>> >> https://dev.eclipse.org/mailman/listinfo/iam-dev
>> >>
>> >
>>
>> _______________________________________________
>> iam-dev mailing list
>> iam-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>>
>
>