[fedora-java] New Java guidelines

[Aleksandar Kurtakov]

----- Original Message -----
> From: "Mikolaj Izdebski" <mizdebsk at redhat.com>
> To: java-devel at lists.fedoraproject.org
> Sent: Wednesday, February 27, 2013 5:22:20 PM
> Subject: Re: [fedora-java] New Java guidelines
> 
> > > > With XMvn this kind of change doesn't require changes to
> > > > packages,
> > > > just approving by Java SIG and implementing this in XMvn
> > > > itself.
> > > > That's one of great advantages of not installing files manually
> > > > but letting a specialized tool care about file installation.
> > > > 
> > > 
> > > Note that we need to handle Ant builds too.
> > 
> > My 2 cents - I suffer enough from maven central containing random
> > stuff under random groupId:artifactId so if upstream doesn't ship
> > pom.xml to define the groupId:artifactId, putting jars in maven
> > repo
> > like structure can only make things worse for cases where upstream
> > hasn't thought about that at all.
> 
> I think we are talking about packages that already have POMs. Maven
> unaware packages can still install stuff in %_javadir.

Well, we speak about cases where the fedora package has a pom.xml. Many times it's simply picked from maven central and has nothing to do with the upstream maintainers (many times this poms are plain wrong too). And this causes problems - ant, rhino, ecj, etc. - we fought problems with all of their maven central pom.xml files (some of them e.g. ant ship their proper pom.xml files now, but many don't).

Alexander Kurtakov
Red Hat Eclipse team