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-currentfor 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 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-unsubscr...@freebsd.org"
smime.p7s
Description: S/MIME cryptographic signature
