Marina,
Yes, you are right. This glassfish-api version is changing too fast :)
Everytime it changes, even though the bits will be fine, the
ResolveError still comes up. Thats why we need to be able to specify
a range of version as dependency. An email has sent out to the alias
and Sahoo, (as attached) on how to specify it, we haven't heard
anything and are still struggling on this.
Anissa.
Marina Vatkina wrote:
> It's on the latest and greatest ws.
>
> console-plugin-service can't start because it depends on the old (i.e.
> rev4) glassfish-api version.
>
> Regards,
> -marina
>
> Anissa Lam wrote:
>>
>> This has been fixed couple days ago. Please make sure you update
>> distributions/web/pom.xml and rebuilt.
>> Anissa.
>>
>> Marina Vatkina wrote:
>>
>>> Admin GUI has its own dependency: ResolveError: Failed to start
>>> org.glassfish.admingui:console-plugin-service:1.0
>>>
>>> :(
>>> -marina
>>>
>>> Marina Vatkina wrote:
>>>
>>>> Bhakti,
>>>>
>>>> You probably needed to change the jruby-connector's version as
>>>> well. I needed to remove that part of my local repository to get
>>>> the changed version.
>>>>
>>>> thanks,
>>>> -marina
>>>>
>>>> Bhakti Mehta wrote:
>>>>
>>>>> Marina,
>>>>> QL are failing too.We are having a discussion about this . Vivek
>>>>> has rebuilt the jruby-connector with rev5 version and pushed it
>>>>> out on maven , see if the latest would help. I agree this is
>>>>> definitely an issue if we need to republish artifacts if the
>>>>> version of some other component changes
>>>>> Regards,
>>>>> Bhakti
>>>>>
>>>>> Marina Vatkina wrote:
>>>>>
>>>>>> On the latest ws (don't know how QL passes), I'm getting the
>>>>>> following error
>>>>>> that is caused by the wrong version ref for the
>>>>>> org.glassfish.common.glassfish-api (either from deploying a
>>>>>> web+JPA example or trying to access admingui):
>>>>>>
>>>>>> ResolveError: Failed to start
>>>>>> org.glassfish.scripting:gf-jruby-connector:1.0
>>>>>> ...
>>>>>> Caused by: org.osgi.framework.BundleException: Unresolved package
>>>>>> in bundle 8: module;
>>>>>> (&(bundle-symbolic-name=org.glassfish.common.glassfish-api)(bundle-version>=10.0.0.rev4)(bundle-version<=10.0.0.rev4))
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> The rev is already rev5 for the glassfish-api :(
>>>>>>
>>>>>> thanks,
>>>>>> -marina
>>>>>>
attached mail follows:
How can I specify version ranges in the pom.xml file such that those
ranges persist to the MANIFEST.MF? I tried:
<project xmlns="
http://maven.apache.org/POM/4.0.0"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.glassfish</groupId>
<artifactId>glassfish-parent</artifactId>
<version>10.0-SNAPSHOT</version>
</parent>
<groupId>org.glassfish.admingui</groupId>
<artifactId>console-plugin-service</artifactId>
<packaging>hk2-jar</packaging>
<name>Admin GUI Integration</name>
<description>Glassfish V3 Admin Console Integration</description>
<dependencies>
<dependency>
<groupId>com.sun.enterprise</groupId>
<artifactId>hk2</artifactId>
<version>${hk2.version}</version>
</dependency>
<dependency>
<groupId>org.glassfish.common</groupId>
<artifactId>glassfish-api</artifactId>
* <version>[10.0*,11.0)</version>*
</dependency>
</dependencies>
...
Which gave me this in the MANIFEST.MF file:
bundle-version="[10.0.0.tp-2-SNAPSHOT, 10.0.0.tp-2-SNAPSHOT]
This was the first of several available versions available, however, I
don't want 1 version, I want "[10.0,11.0)". How can I do this?
Ken