----- Original Message -----
> From: "Fernando Nasser" <fnasser@xxxxxxxxxx>
> To: "Mikolaj Izdebski" <mizdebsk@xxxxxxxxxx>
> Cc: java-devel@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Wednesday, February 27, 2013 5:10:57 PM
> Subject: Re: New Java guidelines
>
>
> >
> > > I will only be happy when it goes to
> > > %_javadir/%{groupid}/%{artifactId}/<version>/%{artifactId}-%{version}.jar
> > >
> > > with a link for backwrd compatibility perhaps :-)
> >
> > That's easily doable and up for discussion. Any opinion is
> > valuable. (For compatibility with Debian I would probably create
> > Maven repository in /usr/share/maven-repo/ not in %javadir)
> >
>
> I can live with that.
>
> I have been proposing this change for about 43 years, so please
> consider it "proposed" for appreciation in the mtg :-)
>
> > 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.
Alexander Kurtakov
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel
