Under whose control are these, Oracle I assume?
Unless this is restricted to java.net/Oracle staff, I am more than happy to
help with setting up jobs for Soteria, etc.
That (with Jenkins) is my day job, and I also deal with Hudson via Eclipse
projects like UMo.
Kind Regards,
Werner
On Thu, Feb 4, 2016 at 12:06 PM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
> On Wed, Feb 3, 2016 at 6:36 PM, Werner Keil <werner.keil_at_gmail.com> wrote:
>
>> I know, OpenJDK (8) had this https://adopt-openjdk.ci.cloudbees.com/ but
>> I can't say, if CloudBees or JCP/Oracle would also do this kind of stuff
>> for Java EE (would be nice though;-)
>>
>
> Every commit to Mojarra (within a timeframe) triggers a rather large set
> of Hudson based jobs for building and running all tests (multiple
> permutations), and then eventually the TCK and somewhat after that (in a
> different department) something called "ADF tests". The results of each
> such build can be found here:
> https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.faces/
>
> Whether anyone wants or can set this up for Soteria is perhaps not a given
> though.
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
>> I hope, some container vendors involved may help. Looking at e.g.
>> DeltaSpike in the Apache Jenkins CI server:
>> https://builds.apache.org/view/A-D/view/DeltaSpike/ you can see, how
>> many variations and different containers (mostly through Arquillian, I
>> guess unless you already use it here it could help) it builds against.
>>
>> If we found a friendly CI place and container host in the "cloud" we
>> could try something similar, easily showing which participating servers
>> still have problems (and it would be in the best interest of the provider
>> more than the EG to make it work sooner or later;-)
>>
>> Regards,
>> Werner
>>
>> On Wed, Feb 3, 2016 at 6:24 PM, arjan tijms <arjan.tijms_at_gmail.com>
>> wrote:
>>
>>> Would be cool if someone could setup a CI container for them. I'll add
>>> the actual tests in the near future (hopefully next week at the latest).
>>>
>>> I also added a compatibility note:
>>>
>>> Soteria currently fully runs on Payara 4.1.1.161 and JBoss WildFly 10,
>>> and mostly on GlassFish 4.1.1. Soteria unfortunately does not run on
>>> Liberty 8 or 9 at the moment due to missing support for CDI in server
>>> authentication modules. Soteria does not run at all on WebLogic 12.2.1 due
>>> to a problem with server authentication modules working at all.
>>>
>>> Btw, no issues with the error messages here (yet)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Feb 3, 2016 at 6:20 PM, Werner Keil <werner.keil_at_gmail.com>
>>> wrote:
>>>
>>>> Ok, if those are integration tests, not just sample apps, then it makes
>>>> sense in a separate module under the RI repo.
>>>> Especially for those it would be awesome, if we could automate and run
>>>> them in a CI container somewhere (maybe aside from Oracle other corporate
>>>> EG members like TomEE or Red Hat/JBoss/OpenShift might be able to help with
>>>> that?;-)
>>>>
>>>> Btw. I keep getting strange error messages when the mailing list tries
>>>> to auto-forward from "experts" to "users" since around noon CET. Anybody
>>>> else also faces the same?
>>>>
>>>> Kind Regards,
>>>> Werner
>>>>
>>>> On Wed, Feb 3, 2016 at 6:15 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>>> wrote:
>>>>
>>>>> On Wed, Feb 3, 2016 at 6:06 PM, Werner Keil <werner.keil_at_gmail.com>
>>>>> wrote:
>>>>>
>>>>>> A small detail, but wondering, if example apps should be in
>>>>>> https://github.com/javaee-security-spec/soteria/tree/master/test
>>>>>> rather than
>>>>>> https://github.com/javaee-security-spec/javaee-security-examples ?;-)
>>>>>>
>>>>>
>>>>> I put them in soteria/test just like
>>>>> https://github.com/spericas/ozark/tree/master/test does.
>>>>>
>>>>> If you look closer at each entry in ozark/test, then it becomes clear
>>>>> that each one is a separate (war) app. The integration (not unit) test then
>>>>> simply uses HTML unit to request a URL from the deployed war and makes some
>>>>> assertions. See eg
>>>>> https://github.com/spericas/ozark/blob/master/test/facelets/src/test/java/org/glassfish/ozark/test/facelets/FaceletsIT.java
>>>>>
>>>>> It's the same approach as uses in the Java EE 7 samples project, and
>>>>> actually Mojarra. The IT tests are both examples/sampels as tests.
>>>>>
>>>>>
>>>>> Oh and btw, "and RI implementation" sounds redundant, as "RI" already
>>>>>> stands for "Reference Implementation" but that's even smaller, just
>>>>>> cosmetic;-)
>>>>>
>>>>>
>>>>> Hmmm, indeed ;) It's a bit like saying EJB bean. You do see this a lot
>>>>> though, but I've changed it nevertheless. Thanks!
>>>>>
>>>>> Kind regards,
>>>>> Arjan Tijms
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Werner
>>>>>>
>>>>>> On Wed, Feb 3, 2016 at 6:03 PM, Werner Keil <werner.keil_at_gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> It will if at all require help by the PMO. Let's see, how that goes,
>>>>>>> otherwise we could always use one of two options, either the "gh_pages"
>>>>>>> branch (see the same for JSR 363 API:
>>>>>>> http://unitsofmeasurement.github.io/unit-api/ its primary goal is
>>>>>>> to hold JavaDoc or Maven site, which is why the entry page is still rather
>>>>>>> basic ;-) in the new Soteria repo or an organization-wide GitHub site
>>>>>>> (similar to http://unitsofmeasurement.github.io/) on GitHub, too.
>>>>>>>
>>>>>>> Kind Regards,
>>>>>>> Werner
>>>>>>>
>>>>>>> On Wed, Feb 3, 2016 at 5:53 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I think the management spec lead mentioned not being able to create
>>>>>>>> projects on java.net either.
>>>>>>>>
>>>>>>>> Anyway, I've created the soteria repo at
>>>>>>>> https://github.com/javaee-security-spec/soteria
>>>>>>>>
>>>>>>>> It contains the upstream api, the RI implementation and the example
>>>>>>>> apps in the test module. These apps can be used in a later stage to
>>>>>>>> function as actual tests. I pretty much followed the template from MVC.
>>>>>>>>
>>>>>>>> I also followed JSF and MVC with using "m01" as the version instead
>>>>>>>> of the previous edr1. That way we can release milestones if needed and then
>>>>>>>> a specific milestone can be submitted as an EDR.
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>> Arjan Tijms
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>