[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-build] org.glassfish.main.security:security:jar:5.1.0 missing from staging
|
Hello,
It looks like the issue is caused by the HK2 modules which were moved
from HK2 in https://github.com/javaee/hk2/pull/373 to GlassFish in
https://github.com/javaee/glassfish/pull/22373, which causes projects to
depend on internal GlassFish code to do HK2 stuff. They don't appear to
depend on any part of GlassFish, so I don't know why they were moved
into GlassFish in the first place as that breaks other projects. Perhaps
those modules should be moved back to HK2?
Jonathan
On 13/12/2018 11:14, Lukas Jungmann wrote:
> On 12/12/18 10:08 PM, Romain Grecourt wrote:
>> On 12/12/18 12:58 PM, arjan tijms wrote:
>>> Hi,
>>>
>>> From the top of my head, Metro unfortunately has a dependency on it.
>>> This is because if contains the JAuth API, on which the "SAM"
>>> com.sun.xml.wss.provider.ServerSecurityAuthModule depends.
>>>
>>> There are indeed many levels of wrongness here. JAuth is the
>>> precursor of JASPIC (you clearly see it's very similar), so it
>>> shouldn't be used anymore in the first place. Indeed, there's a
>>> bunch of comments in the GF code that say the WebServices/SOAP code
>>> should be rebased on the standard API (JASPIC).
>
> Arjan, do you have transition path? If so, maybe you could file an
> issue @ https://github.com/eclipse-ee4j/metro-wsit/issues ...
>
>>>
>>> For some reason that never happened.
>>>
>>> I don't know the rest of the history (maybe Ron and Lukas can
>>> enlighten us), but the current situation is less than ideal; Metro
>>> depends on GF internal jars, and GF depends on Metro, obviously.
>> Yikes.
>> We should at least avoid the chicken-and-egg with Metro and GF 5.1.0
>>
>> There is an 5.1.0-RC1 build that's available, can metro depend on that ?
>
> No, it can not. This is what I get after changing version from 5.1.0
> to 5.1.0-RC1:
>
> [ERROR] Failed to execute goal on project wssx-impl: Could not resolve
> dependencies for project
> org.glassfish.metro:wssx-impl:jar:2.5.0-SNAPSHOT: The following
> artifacts could not be resolved:
> org.glassfish.hk2:config-types:jar:5.1.0-RC1,
> org.glassfish.hk2:hk2-config:jar:5.1.0-RC1: Could not find artifact
> org.glassfish.hk2:config-types:jar:5.1.0-RC1 in sonatype-nexus-staging
> (https://oss.sonatype.org/content/repositories/staging) -> [Help 1]
>
> ...which means that the GlassFish 5.1.0-RC1 in central is not
> complete. Or am I misinterpreting what I see?
>
> thanks,
> --lukas
>
>>>
>>> Kind regards,
>>> Arjan
>>>
>>>
>>>
>>> On Wed, Dec 12, 2018 at 9:33 PM Romain Grecourt
>>> <romain.grecourt@xxxxxxxxxx <mailto:romain.grecourt@xxxxxxxxxx>> wrote:
>>>
>>> Maxim, what project has a dependency on
>>> org.glassfish.main.security ? It feels wrong.
>>> Also org.glassfish.main.security is part of GlassFish not Soteria,
>>> so I'm following why Dmitry is asking Arjan to re-release.
>>>
>>> Unless I'm mistaking we are still working on 5.1.0, these
>>> artifacts are probably in OSSRH staging because of the release
>>> work that Vinay was doing.
>>> I don't think anyone should be depending on that.
>>>
>>>
>>> On 12/12/18 5:21 AM, arjan tijms wrote:
>>>> Hi,
>>>>
>>>> It looked like Soteria was there all along still, but just to be
>>>> sure I re-staged it anyway.
>>>>
>>>> See:
>>>> https://oss.sonatype.org/content/repositories/staging/org/glassfish/soteria/jakarta.security.enterprise/1.0.1/
>>>>
>>>> Kind regards,
>>>> Arjan
>>>>
>>>> On Wed, Dec 12, 2018 at 1:46 PM arjan tijms
>>>> <arjan.tijms@xxxxxxxxx <mailto:arjan.tijms@xxxxxxxxx>> wrote:
>>>>
>>>> Yes, will do.
>>>>
>>>> On Wed, Dec 12, 2018 at 1:17 PM Dmitry Kornilov
>>>> <dmitry.kornilov@xxxxxxxxxx
>>>> <mailto:dmitry.kornilov@xxxxxxxxxx>> wrote:
>>>>
>>>> Arjan,
>>>>
>>>> Can you please re-release Soteria? It’s been deleted.
>>>>
>>>> Thanks,
>>>> Dmitry
>>>>
>>>> > On 12 Dec 2018, at 13:10, Maxim Nesen
>>>> <maxim.nesen@xxxxxxxxxx <mailto:maxim.nesen@xxxxxxxxxx>>
>>>> wrote:
>>>> >
>>>> > Hello,
>>>> >
>>>> >
>>>> > Could please someone re-stage
>>>> org.glassfish.main.security:security:jar:5.1.0 artifact
>>>> to staging? It's missing for some reason.. security-ee as
>>>> well...
>>>> >
>>>> >
>>>> > Thank you
>>>> >
>>>> > Maxim
>>>> >
>>>> > _______________________________________________
>>>> > ee4j-build mailing list
>>>> > ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
>>>> > To change your delivery options, retrieve your
>>>> password, or unsubscribe from this list, visit
>>>> > https://www.eclipse.org/mailman/listinfo/ee4j-build
>>>>
>>>>
>>>> _______________________________________________
>>>> ee4j-build mailing list
>>>> ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
>>>> To change your delivery options, retrieve your password, or
>>>> unsubscribe from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/ee4j-build
>>>
>>
>>
>>
>> _______________________________________________
>> ee4j-build mailing list
>> ee4j-build@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/ee4j-build
>>
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-build