Fwd: [fedora-java] Maven upgrade to version 3.1.0
by Peter MacKinnon
FYI
-------- Original Message --------
Subject: [fedora-java] Maven upgrade to version 3.1.0
Date: Thu, 18 Jul 2013 07:46:42 +0200
From: Mikolaj Izdebski <mizdebsk(a)redhat.com>
To: Fedora Java Development List <java-devel(a)lists.fedoraproject.org>
Version 3.1.0 of Apache Maven was recently released. It is a
long-awaited release which brings numerous new features and fixes many
bugs. A full list is available in Maven 3.1.0 release notes [1].
I think it's important for Fedora to switch to new Maven as soon as
possible. Unfortunately there are signifficant incompatibilities
between Maven 3.1.0 and 3.0.5 which make this process non-trivial.
Maven 3.1.0 switched from Sonatype Aether to Eclipse Aether and from
Sonatype Sisu to Eclipse Sisu. Plugins that directly depend on Aether
or Sisu may no longer work with Maven 3.1.0. Upstream lists [2] some
plugins that were or need to be updated to work with Maven 3.1.0.
I have created a tracker bug [3] which is intended to lists tasks
needed to be done in order to migrate to Maven 3.1.0 as well as any
bugs related to the migration. I have populated the tracker with all
changes needed that I am aware of at the moment, but feel free to add
more bugs if you find them.
This is fairly complicated process as there are circular package
dependencies because of which several packages need to be updated at the
same time. I will ask release engineering to create a dedicated Koji
tag in order not to break rawhide during the process.
[1] http://maven.apache.org/docs/3.1.0/release-notes.html
[2] http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
[3] http://bugzilla.redhat.com/985674
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
--
java-devel mailing list
java-devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
10 years, 9 months
Re: Mesos Packaging
by Tim St. Clair
Thanks Igor!
Currently we'll need to bundle their dependencies prior to the main package. I'm just about done with stout, but I could use some help with their (libprocess https://github.com/3rdparty) library prior to mundging the mesos package.
&& of course the main mesos package too, but we have a couple of preliminary specs already.
Cheers,
Tim
----- Original Message -----
> From: "Igor Gnatenko" <i.gnatenko.brain(a)gmail.com>
> To: devel(a)lists.fedoraproject.org
> Sent: Saturday, July 20, 2013 1:35:27 AM
> Subject: Re: Mesos Packaging
>
> On Fri, 2013-07-19 at 15:14 -0400, Tim St Clair wrote:
> > For folks who are watching, we are assisting the upstream Mesos
> > project(https://issues.apache.org/jira/browse/MESOS-543) and there is
> > interest from multiple parties to get the package and it's dependencies
> > into the Fedora &| EPEL channels.
> >
> > If you are interested, please feel free to ping me and we can coordinate,
> > as there is a fair amount to be done.
> >
> > Cheers,
> > Tim
>
> I would gladly to packaging it or help to packaging.
> --
> Igor Gnatenko
> Fedora release 19 (Schrödinger’s Cat)
> Linux 3.9.9-302.fc19.x86_64
>
> --
> devel mailing list
> devel(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
10 years, 9 months
Re: Mesos Packaging
by Tim St. Clair
Thanks Mikolaj,
That is good to know, b/c I know some folks in their community would like to bring it to EPEL, but my first step will be Fedora, then let the community drive.
Cheers,
Tim
----- Original Message -----
> From: "Mikolaj Izdebski" <mizdebsk(a)redhat.com>
> To: devel(a)lists.fedoraproject.org
> Sent: Monday, July 22, 2013 12:07:08 AM
> Subject: Re: Mesos Packaging
>
> On 07/19/2013 09:14 PM, Tim St Clair wrote:
> > For folks who are watching, we are assisting the upstream Mesos
> > project(https://issues.apache.org/jira/browse/MESOS-543) and there is
> > interest from multiple parties to get the package and it's dependencies
> > into the Fedora &| EPEL channels.
> >
> > If you are interested, please feel free to ping me and we can coordinate,
> > as there is a fair amount to be done.
>
> If you need any help with the Java parts, feel free to contact me.
>
> There is no Maven in EPEL so the Java parts would need to be disabled in
> EPEL or built with a different build system (like Ant).
>
> --
> Mikolaj Izdebski
> Software Engineer, Red Hat
> IRC: mizdebsk
> --
> devel mailing list
> devel(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
10 years, 9 months
Re: mesos
by Tim St. Clair
Thanks Gil!
Currently I was bootstrapping their sub-elements:
stout - almost done
libprocess - on Deck
mesos - merge w/the multiple specs, and update upstream to not try to suck in it's tarball dependencies.
Cheers,
Tim
----- Original Message -----
> From: puntogil(a)libero.it
> To: "Tim St Clair" <tstclair(a)redhat.com>
> Sent: Friday, July 19, 2013 4:38:22 PM
> Subject: mesos
> hi
> sketched the least worst one spec file (attached) regards
> gil
> --
> I do not trust something that bleeds for 5 days and does not die ...
10 years, 9 months
Mesos Packaging
by Tim St. Clair
For folks who are watching, we are assisting the upstream Mesos project(https://issues.apache.org/jira/browse/MESOS-543) and there is interest from multiple parties to get the package and it's dependencies into the Fedora &| EPEL channels.
If you are interested, please feel free to ping me and we can coordinate, as there is a fair amount to be done.
Cheers,
Tim
10 years, 9 months
Jetty 9 implications for Hadoop 2.x in Fedora
by Peter MacKinnon
FYI,
The Fedora Hadoop 2.x initiative began development several months ago
based on the stability of the released F18 distro. Now that F19 is
released we have rebased the packaging work on the various newer
dependencies offered by F19. One significant change is that Jetty 8.1.x
is no longer available and has made way for the latest version (9.0.x).
This has introduced several API changes, particularly in the SSL API. It
also has some benefit in that Jetty 9 incorporates a JSP compilation
maven plugin which is required by the Hadoop build. The upstream version
of Hadoop relies on a combination of Tomcat 5.5, Jetty 6.1.x, and the
Codehaus jspc plugin for this step. However, F19 provides Tomcat 7 which
is incompatible for this scenario with the Jetty container. The Jetty 9
version is Glassfish-based.
An important consideration for this change is that Jetty 9 is
_completely incompatible with Java 6_ and only supported on Java 7,
obviously the only version available in the current Fedora package
repositories. Thus, the forthcoming Hadoop packaged jars for Fedora will
also only be incompatible with the now EOL Oracle JRE 6 that Apache
upstream uses for its current baseline.
The Hadoop packaging team feels that the reasonable path forward is to
adapt the Hadoop build for Jetty 9 and eschew any and all Java 6 support
for those bits. However, it does carry the caveat that there may be
corner cases of behavioral or JVM-related differences in certain tests
and use cases. The packaging team continually examines the Fedora Hadoop
builds for "correctness" using the source tree JUnit test suite as well
as basic smoke testing. Test-related problems have been identified and
compensated for already once they are comprehended.
Fedora Software Collections
<https://fedoraproject.org/wiki/SoftwareCollections> are of interest to
the Hadoop packaging team but their suitability for this project and the
current FPG policies regarding their official usage require further
investigation.
Please let us know if you have any questions or concerns regarding this
proposed direction.
\Pete
https://fedoraproject.org/wiki/Changes/Hadoop
--
Peter MacKinnon
MRG Grid/Big Data
Red Hat Inc.
Raleigh, NC
10 years, 9 months
Re: Server subpackage for ZooKeeper
by Tim St. Clair
Yup I will look into it today.
Cheers,
Tim
----- Original Message -----
> From: "gil" <puntogil(a)libero.it>
> To: "Tim St Clair" <tstclair(a)redhat.com>
> Sent: Wednesday, June 26, 2013 2:14:06 PM
> Subject: Server subpackage for ZooKeeper
>
> hi
> can you take this issue
> https://bugzilla.redhat.com/show_bug.cgi?id=978518
> i have no confidence with systemd
> thanks
>
>
10 years, 9 months