On 7 April 2011 03:12, Olivier Lamy ol...@apache.org wrote:
So this can wait early next week : no rush (I'm the only user who see
those issue :-) ).
Incidentally, it was also reported on the testng-users list.
2011/4/6 Kristian Rosenvold kristian.rosenv...@gmail.com:
I have fixes in
Hi,
The vote has passed with the following result :
+1 (binding):
Brian Fox
Arnaud Héritier
Hervé Boutemy
+1 (non binding):
Tamás Cservenák
Jesse Glick
I will promote the artifacts to the central repo.
-
To
The Maven team is pleased to announce the release of the Maven
Indexer, version 4.1.0
This project creates portable indexes from maven repositories, which
can be used to search for artifacts.
You should specify the version in your project's dependency configuration:
dependency
Hi Guys
I've written a plugin that creates a new packaging type which creates
a *.zip and a *.jar artefacts. Dependencies of the same packaging type
are deployed together.
The problem is that while the code is deployed together, adding this
dependency to my POM means that the same JAR file is
Brand new tree; is this known, or should I make a JIRA?
---
Test set:
org.apache.mahout.cf.taste.impl.similarity.jdbc.MySQLJDBCInMemoryItemSimilarityTest
wrong list?
On 4/7/11 11:41 AM, Benson Margulies wrote:
Brand new tree; is this known, or should I make a JIRA?
---
Test set:
org.apache.mahout.cf.taste.impl.similarity.jdbc.MySQLJDBCInMemoryItemSimilarityTest
Issue Subscription
Filter: Design Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
