FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development Java

 
 
LinkBack Thread Tools
 
Old 06-10-2011, 09:40 AM
Stanislav Ochotnicky
 
Default Getting rid of maven2-depmap.xml

This is just an update on progress on migrating from maven2 to maven
package.

I just committed changes to maven package that will do a few things:
* direct processing of fragment files generated by %add*_maven_depmap
macros
* being able to process fragments in /usr/share/maven-fragments
* being able to resolve pom files in /usr/share/maven-poms

This will mean several things once the whole puzzle is created:
* No need for %update_maven_depmap macro in %post and %postun
* With it - no need for Require(post): jpackage-utils
* No more rpmlint warnings about non-conf file in /etc
* Sane place for pom files :-)
* Simpler packaging (IMO)
* Later on simpler patches to maven once we remove compat code.

For now we are backward compatible, so maven still reads from
/etc/maven/fragments and old _mavenpomdir.

Obviously there is certain performance penalty for processing few
hundred small files instead of one big file. However this performance
hit is rather small and only affects mvn-local and mvn-rpmbuild
so it won't affect users.

Worst case scenario, I'd rather move regenerating of depmaps into
maven shell script (comparing last change of depmap.xml with last
modification of fragments and all that...).

Right now no packaging modifications are necessary, since we don't
want to break maven2 just yet :-)

Next up: jpackage-utils and generation of maven2-depmap.xml even from
/usr/share/maven-fragments (for maven2 compat).


See https://fedoraproject.org/wiki/Migration_from_maven2 for more
details and plan.

--
Stanislav Ochotnicky <sochotnicky@redhat.com>
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc. http://cz.redhat.com
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
 
Old 06-10-2011, 10:05 AM
Alexander Kurtakov
 
Default Getting rid of maven2-depmap.xml

On 01:01:39 PM Friday, June 10, 2011 Stanislav Ochotnicky wrote:
> This is just an update on progress on migrating from maven2 to maven
> package.
>
> I just committed changes to maven package that will do a few things:
> * direct processing of fragment files generated by %add*_maven_depmap
> macros
> * being able to process fragments in /usr/share/maven-fragments
> * being able to resolve pom files in /usr/share/maven-poms
>
> This will mean several things once the whole puzzle is created:
> * No need for %update_maven_depmap macro in %post and %postun
> * With it - no need for Require(post): jpackage-utils
> * No more rpmlint warnings about non-conf file in /etc
> * Sane place for pom files :-)
> * Simpler packaging (IMO)
> * Later on simpler patches to maven once we remove compat code.
>
> For now we are backward compatible, so maven still reads from
> /etc/maven/fragments and old _mavenpomdir.
>
> Obviously there is certain performance penalty for processing few
> hundred small files instead of one big file. However this performance
> hit is rather small and only affects mvn-local and mvn-rpmbuild
> so it won't affect users.
>
> Worst case scenario, I'd rather move regenerating of depmaps into
> maven shell script (comparing last change of depmap.xml with last
> modification of fragments and all that...).
>
> Right now no packaging modifications are necessary, since we don't
> want to break maven2 just yet :-)
>
> Next up: jpackage-utils and generation of maven2-depmap.xml even from
> /usr/share/maven-fragments (for maven2 compat).
>
>
> See https://fedoraproject.org/wiki/Migration_from_maven2 for more
> details and plan.

Everything that simplifies packaging and doesn't degrade performance is an
absolute win .
I'm already impressed with the speed improvements with our packaged version of
maven 3.x (it's few times! faster not few percents) so few percents
performance hit won't be noticed from people moving from maven2 to maven 3.x.

Keep up the good work,
Alex


>
> --
> Stanislav Ochotnicky <sochotnicky@redhat.com>
> Software Engineer - Base Operating Systems Brno
>
> PGP: 7B087241
> Red Hat Inc. http://cz.redhat.com
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
 

Thread Tools




All times are GMT. The time now is 02:14 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org