On 21/03/2012, at 8:54 AM, Stephen Connolly wrote:
> My point is that even if you were a committer, the Apache by-laws
> state that the PMC must vote at least 3 x +1 to release a binary, so
> if you cannot find 3 of the current 24 who are even willing to
> consider voting on RPMs then you are not
http://svn.apache.org/repos/asf/maven/sandbox/trunk/rpm
$ mvn install
$ sudo rpm -ivh
~/.m2/repository/org/apache/maven/rpm/maven/3.0.4/maven-3.0.4.rpm
Tested on CentOS 6.0.
It installs to /usr/local/maven and /usr/local/bin/mvn. It also adds
/etc/profile.d/maven.sh to add the bin directory t
On 22/03/2012, at 1:01 AM, Brian Fox wrote:
> Has anyone considered making an rpm/deb bundle that essentially
> contains a script which can fetch the associated tar.gz from the
> apache site and unpack it?
We've had one at MaestroDev for a while. I'll clean it up, give it a spin, and
put it in
You can use this plugin for a wide range of version changes:
http://mojo.codehaus.org/versions-maven-plugin/
For automatic incrementing, you might look at the release plugin:
http://maven.apache.org/plugins/maven-release-plugin/
If neither of those do what you want, then it would probably be easi
Hi all,
I'm wondering if it would be possible/feasible to write a plugin that:
1. Looks up the LATEST version of the current project
2. Does some splitting on that version string to increment the minor
revision by one
3. Modifies the logical representation of the POM to the new versio
Has anyone considered making an rpm/deb bundle that essentially
contains a script which can fetch the associated tar.gz from the
apache site and unpack it?
It seems like this would be the best of both worlds. Hardly anything
ever changes in the package, people get easy access to "sudo apt get
inst
On Wed, Mar 21, 2012 at 4:35 AM, Sascha Scholz wrote:
> Hi,
>
> On Tue, Mar 20, 2012 at 11:28 PM, Olivier Lamy wrote:
>> BTW do we consider adding a warning in 3.0.5 if id != host and fail in 3.0.6
>> or fail directly in 3.0.5
>
> Why not deprecate the id entry then instead of forcing users to se
Hi,
On Tue, Mar 20, 2012 at 11:28 PM, Olivier Lamy wrote:
> BTW do we consider adding a warning in 3.0.5 if id != host and fail in 3.0.6
> or fail directly in 3.0.5
Why not deprecate the id entry then instead of forcing users to set
both to the same value?
BTW, I don't see that preemptive authe
