[Bug 648945] Review Request: maven - Java project management and project comprehension tool

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=648945

--- Comment #5 from Deepak Bhole <dbhole at redhat.com> 2010-11-26 09:23:25 EST ---
(In reply to comment #4)
> (In reply to comment #3)
> > ----------------------------------------------------------------------
> > 
> > maven.noarch: W: non-conffile-in-etc /etc/maven/fragments/maven
> > 
> > It is safe to mark the above as %config(noreplace). The user should never
> > modify the above file anyway, and even if they do, it should be overridden when
> > the rpm is updated/re-installed.
> 
> %config(noreplace) does exactly the opposite as I understand it. If user
> modifies the file it won't be replaced on update.
> 

Doh! Sorry :( you are right. I mean it should be just %config

> > How does this hook into the new resolver, and where can I find the code for it?
> 
> I started working on new resolver in custom repository [1]. It will most
> probably be rolled into main maven package. Original idea was to have a
> separate package (something like maven-fedora), but maven package itself would
> still have to carry patches to actually use it[2]. So that's why it will be
> shipped similarly to how jpp resolver was packaged for maven2. The code is
> more-less copied from maven2 resolver, with changes needed because of maven
> architecture changes.
> 
> > Also, what are the plans to make it buildable with mvn3 itself?
> 
> mvn3 is actually buildable with mvn2 already. It won't be able to build itself
> unless all bugs in listed in [3] are closed (incorrect pom file names). mvn2
> seems to have used pom file from jar file itself if it was available. mvn3
> doesn't so pom files have to have correct filenames. 
> 
> Plan is to have maven (maven 3) and maven2 packages installable in parallel
> until time when we feel m3 is ready to Obsolete m2 (definitely not before
> F-16).
> 
> [1] git://fedorapeople.org/~sochotni/maven-javadir-resolver.git
> [2] http://sochotni.fedorapeople.org/0003-Use-custom-resolver.patch
> [3]
> https://bugzilla.redhat.com/buglist.cgi?quicksearch=installs+pom+with+incorrect+filename

Alright so the package is largely fine. Since it cannot be used to build
itself, I assume it can't build anything else either? Is there a way to test it
in that case, just to make sure all is ok?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.