groupId. I can help prepare a package that
they'd only need to unpack in
.../m2-ibiblio-rsync-repository/org/apache/hadoop/ on
people.apache.org.
BR,
Jukka Zitting
run it from
the command line to deploy the artifact. Note that this artifact only
needs to be uploaded once, not per each Mahout release.
BR,
Jukka Zitting
is better than each downstream project deploying their own
copies.
BR,
Jukka Zitting
svn.apache.org mirror causes such
problems every now and then. Luckily the release plugin can fairly
well deal with such problems. Simply rerun mvn release:prepare a bit
later, possible with an svn update in between, to continue the
process.
BR,
Jukka Zitting
plugin, you can test the basic functionality by explicitly specifying
the passphrase on the command line:
mvn clean install -Papache-release -Dgpg.passphrase=your passphrase
BR,
Jukka Zitting
at some point. In Jackrabbit we copy only the
project source archive and a few standalone binaries to the
public_html directory that'll eventually be copied to
www.apache.org/dist. Other release artifacts are made available only
through the Maven repository.
BR,
Jukka Zitting
the parent POM settings work
correctly also in your build processes.
repository.apache.org maintainers - that would be in...@apache, namely
INFRA-1896, right?
Yes. Adding a subtask of INFRA-1896 is the recommended way to move
forward with this.
BR,
Jukka Zitting
of an existing POM.
[1] http://maven.apache.org/developers/release/releasing.html
[2] http://repo1.maven.org/maven2/org/apache/apache/6/apache-6.pom
BR,
Jukka Zitting
Hi,
On Wed, Apr 22, 2009 at 6:20 PM, Grant Ingersoll gsing...@apache.org wrote:
Context please? Last night's talk?
+1
And why is this on mahout-dev@ instead of gene...@?
BR,
Jukka Zitting
forward to their
continued contribution and hope you all will join me in congratulations.
+1 Congratulations, and keep up the good work!
BR,
Jukka Zitting
/mahout/mahout/0.1/
Ah, my mistake! It looks like I was looking at
mahout-0.1-project.tar.gz.asc.md5 and
mahout-0.1-project.tar.gz.asc.sha1. Not sure why there are checksums
for the PGP signature.
With that cleared, here's my +1 to release these packages as Mahout 0.1.
BR,
Jukka Zitting
Maven jetty plugin has been relocated
-
Key: MAHOUT-112
URL: https://issues.apache.org/jira/browse/MAHOUT-112
Project: Mahout
Issue Type: Bug
Affects Versions: 0.1
Reporter: Jukka Zitting
[
https://issues.apache.org/jira/browse/MAHOUT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated MAHOUT-113:
-
Attachment:
org.apache.mahout.ga.watchmaker.cd.tool.CDInfosToolTest-output.txt
Attached test
+1 even without a
new release candidate if the checksum issues can be tracked down and
fixed. The PGP signatures seem to be correct.
BR,
Jukka Zitting
candidate.
But as mentioned in the Nutch release vote, that's just a preference,
not something over which I'd -1 a release.
BR,
Jukka Zitting
the nature of source releases. For me the source release is not
one release artefact among many, but the *source* of any other release
artefacts.
BR,
Jukka Zitting
---
Test set
16 matches
Mail list logo
