Date: Wed, 23 Dec 2015 12:35:17 +0100 From: horst leitenmueller <horst.leitenmueller@it4health.at> To: Alexander Yerenkow <yerenkow@gmail.com> Cc: freebsd-java@freebsd.org, Ports FreeBSD <freebsd-ports@freebsd.org> Subject: Re: java/wildfly discussion Message-ID: <8EE770E3-A19A-4034-B79C-C7BECF880423@it4health.at> In-Reply-To: <CAPJF9wnVQktf4VmeWbJpLEe%2BKgsGu%2B-Ew0sU85vKuA=y90xmTA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
hi all,
i'm using also the old versions because of stability of these, also if not supported. problem is that the new versions are different and it's impossible to change all few month's the version (and reconfigure everything), i have also running versions 4.x and 5.x.
also if compliance is written this is not true (just an example: small changes in security can bring a project to fail very fast, means the dependencies of the jar files which are used to compile)
at the moment the versions are
9.0.2 Final 15/10
9.0.1 Final 15/07/23
9.0.0 Final 15/07/02
8.2.1 Final 15/07
8.2.0 Final 14/11
8.1.0 Final 14/05
Start was 2013
my question is it hurting to keep them in the svn ? better would be a subdirectory for ever major release and subdirectories for the minor releases
like /usr/ports/java/
wildfly9/
wildfly9-current for the very optimistic once's
wildfly9.0.1
wildfly9.0.2
wildfly8/
i also would keep it about 3 years than a deprecation and later deletion can be done…
and really I’m working with jboss 2000 / and then with wildfly and it never worked to upgrade without problems en recompilation/remerging/reconfiguriing of the running apps
i have seen there are packages for upgrade from 9.0.1 to 9.0.2 for example, but i’m not sure if would be easy to integrate this into the ports system ?! this would be another chance to resolve too much ports
(but also with the same problems apps running on the app server will fail… )
br horst
> On 23 Dec 2015, at 12:09, Alexander Yerenkow <yerenkow@gmail.com> wrote:
>
> Hello all.
> Seems that I've created too many ports for wildfly, let's discuss sanation
> :)
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205490
>
>
> --
> Regards,
> Alexander Yerenkow
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
[-- Attachment #2 --]
0 *H
010 + 0 *H
00{a0
*H
0y10U
Root CA10Uhttp://www.cacert.org1"0 UCA Cert Signing Authority1!0 *H
support@cacert.org0
151107141600Z
160505141600Z0K10UCAcert WoT User1/0- *H
horst.leitenmueller@it4health.at0"0
*H
0
ح#B|ǃ;'^Iyi<n˺wk[D>oNjB`mTrUymgEAdUCL{Yʁ"UeFuymϔ y
(2ЏяX+٨(kHYh
;١MeqmG͙|"9+
%r2F|[4=p,%SiXͩ>eb죒{HȲ8NX=iW,h%&jǴ* P0L0U0 0V `HB
IGTo get your own certificate for FREE head over to http://www.CAcert.org0U0@U%907++
+7
+7
`HB02+&0$0"+0http://ocsp.cacert.org01U*0(0&$" http://crl.cacert.org/revoke.crl0+U$0" horst.leitenmueller@it4health.at0
*H
i~/Uށh7#14X/]i`DOY_)Ail-Gx~تJoolEM+YnݩvJPe2RP6y6LΕ^t22# 2bew[|i#QUc؏_` y\BK(73D՞+<F0D6"tB$atMO<fgL@LfYQ/Z9݇U
kAT*45t,pk"ا*խzRDA%}X&_+9* ,JEu~fDG06ïY<qyR>F6oH:SMaXHҲ;,Zs.FbvqcG.7hHgU-wcЗ{1SqF-xxRZ(h%<6W
/o˿%ҹ$#{`vٚJ4n+
;xweP\%CXhy? ~9yHSظ~%&130/00y10U
Root CA10Uhttp://www.cacert.org1"0 UCA Cert Signing Authority1!0 *H
support@cacert.orga0 + 0 *H
1 *H
0 *H
1
151223113517Z0# *H
1dhJ'IL5>Z9&0 +7100y10U
Root CA10Uhttp://www.cacert.org1"0 UCA Cert Signing Authority1!0 *H
support@cacert.orga0*H
10y10U
Root CA10Uhttp://www.cacert.org1"0 UCA Cert Signing Authority1!0 *H
support@cacert.orga0
*H
_P8_BZܔ5tu0ud ߙ,]vDؚCsvU,v=ÂE@I H3t&}<ueT42K5gRo@{lB&q8pOL3 +=4\2gi/qWȆqB'aBűK#[=*6SDC]\ҮXٞXKԾN`TRFzےzWtQҋ]L-
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8EE770E3-A19A-4034-B79C-C7BECF880423>
