sort of... you'll actually stage the artifacts and vote for three release
and the staged artifacts at the same time.
the patch is my diff... as a record of what I have done... not for
committing yet. when I have a patch for commuting I'll raise a jira and
attach it... or hey if you want to make me
So, for clarification, you're holding this vote for the 7.0 rc4
artifacts because the build.xml changes are as-of-yet uncommitted (and
too late for 7.0). Once our build system has caught up, this is
something we'll be able to do after a successful release vote, and using
the same artifacts. Is t
+1
On Sun, Jan 2, 2011 at 2:50 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> As I am not a cassandra committer I'd rather do the promotion with a vote.
>
> There are two staging repositories:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-065/
>
> Whi
+1
On Mon, Jan 3, 2011 at 8:52 AM, Gary Dusbabek wrote:
> +1. I didn't test the artifacts, but any effort to get mvn artifacts
> published that doesn't force mvn on the entire project gets my vote.
>
> Gary.
>
> On Sun, Jan 2, 2011 at 14:50, Stephen Connolly
> wrote:
>> As I am not a cassandra
maven-ant-tasks would allow what you want, no install of maven (unless
publishing to central, in which case the install is hidden in ~/m2) and all
dependency info in the build.xml
I'll work on a patch to show how that would look like (on trunk, leave 0.7.0
as it is, less risk)
- Stephen
---
Sent
On Mon, Jan 3, 2011 at 9:01 AM, Gary Dusbabek wrote:
> Voted and moved this discussion to a different thread.
>
> My goal (other devs please chime in because I'm interested) would be
> to still rely on ant for building and generating a pom, without the
> requirement to explicitly install maven.
Voted and moved this discussion to a different thread.
My goal (other devs please chime in because I'm interested) would be
to still rely on ant for building and generating a pom, without the
requirement to explicitly install maven. If we could get rid of
ivy.xml by having the relevant details in
+1. I didn't test the artifacts, but any effort to get mvn artifacts
published that doesn't force mvn on the entire project gets my vote.
Gary.
On Sun, Jan 2, 2011 at 14:50, Stephen Connolly
wrote:
> As I am not a cassandra committer I'd rather do the promotion with a vote.
> There are two stag
voting options are:
+1 - publish
0 - don't care
-1 - there's a problem with the poms
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 2 Jan 2011 20:50, "Stephen Connolly"
w
(battery on laptop died)
... move to a consolidated set of dependencies.
Also did you forget to vote?
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 3 Jan 2011 14:16, "St
Yep I'd ditch ivy and the lib folder for maven-ant-tasks...
After battling with ivy for ages I have come to the conclusion that it's
trying to be too smart... [when trying to generate pom files] but you should
not confuse how you have done things...
the runtime dependencies of cassandra are all i
Stephen,
Please lay down some mvn/ant wisdom on us... Is there a way to
link/include the dependency logic from the 'pom' target and the
ivy.xml file we use? It would be great if the dependency information
could be consolidated in one place.
Great work, btw.
Gary.
On Sun, Jan 2, 2011 at 14:50,
12 matches
Mail list logo
