Re: [JPackage-announce] [RPM (6.0)] [DIST generic] maven3-3.0.3-1.jpp6

On 07/27/2012 02:51 PM, Ralph Apel wrote:
> Hi all,
> 
> I just uploaded one first maven3 release to 6.0/devel.
> 
> Please take note that this is an essentially unmodified maven3 build.
> Besides using aether to resolve dependencies (some differences indeed),
> this release is meant to be used in JPP like
> 
> $ mvn3 -e -o -Dmaven.repo.local=$(pwd)/.m2/repository whatever-goal
> 
> The contents of this local repo should then be set up with symlinks or
> copies according to the transitive requirements of the package you are
> building.

I think that Fedora sets -Dmaven.repo.local automatically in the
scripts. People forgot this option which then sort of violates the jpp mode.

In newer Fedora specs, they leave out %defattr, %clean, rm -rf
%{buildroot} in %install, %post/%postun requires and scriptlets for
maven, etc. I am not sure if our RPM (RHEL 6 level) supports this.
Specifically, maven support could be broken if the maven support is missing.

Finally, the common problem I am running into with
aether+maven-deploy-plugin is that it refuses to allow 'mvn deploy' when
offline. This doesn't make sense to me, as one could use 'file://',
which is a local protocol.

I think that maven-deploy-plugin always did this, but the old jpp patch
was not equivalent to offline mode. Now, Fedora simply puts maven into
offline mode (which is why it doesn't need a patch), but now we can't
deploy. So, what is the best way to make 'mvn deploy' work again?