Something similar happened to me the other day. I resolved it by:
mvn -U clean install
On 04/30/2013 06:18 AM, Romain Grecourt wrote:
> Why did you revert it ? Hudson was all blue right ?
>
> - Tang, your repository/local repository might be outdated since I've
> updated this dependency to match the final version.
> - Marina, did you update your workspace, performed a full build and
> verified it locally ?
>
> Thanks,
> Romain
>
> On 4/30/13 4:11 AM, Jill Sato wrote:
>> Reverted 61734.
>>
>> Thanks.
>>
>> On 4/29/13 6:38 PM, Tang Yong wrote:
>>> Marina,Romain
>>>
>>> javax.ejb-api 3.2.0 's pom should be updated, and I guess
>>>
>>> <dependency>
>>> <groupId>javax.transaction</groupId>
>>> <artifactId>javax.transaction-api</artifactId>
>>> <version>1.2-b03</version>
>>> </dependency>
>>>
>>> should be updated into
>>>
>>> <dependency>
>>> <groupId>javax.transaction</groupId>
>>> <artifactId>javax.transaction-api</artifactId>
>>> <version>1.2</version>
>>> </dependency>
>>>
>>> Because currently, in appserver/pom.xml
>>>
>>> <javax.transaction-api.version>1.2</javax.transaction-api.version>
>>>
>>> So, should be consist with appserver/pom.xml
>>>
>>> Thanks
>>> --Tang
>>>
>>> Marina Vatkina wrote:
>>>> I got:
>>>>
>>>> Caused by: org.osgi.framework.BundleException: Unresolved
>>>> constraint in bundle org.glassfish.main.ejb.gf-ejb-connector [82]:
>>>> Unable to resolve 82.0: missing requirement [82.0]
>>>> osgi.wiring.package;
>>>> (&(osgi.wiring.package=javax.ejb)(version>=3.2.0)(!(version>=4.0.0)))
>>>> [caused by: Unable to resolve 131.0: missing requirement [131.0]
>>>> osgi.wiring.package;
>>>> (&(osgi.wiring.package=javax.transaction)(version>=1.2.0.b03))]
>>>>
>>>> -marina
>>>>
>>>>
>>>
>>
>