TL;DR with the 3.4 release Johann has added a dependency to his library (to
essentially use his own version of commons-io's IOUtils.closeQuietly)
This brings a choice...
Do I
a) switch to a complete fork, change the package name, accept some other
pull requests and try and build a community arou
Result
+1: Stephen Connolly, Mikhail Mazursky
0: Fred Cooke
-1:
-Stephen
On 14 February 2013 09:28, Stephen Connolly wrote:
> Hi,
>
> I'd like to release version 1.2.1-1 of Mojo's Cassandra Maven Plugin
> to sync up with the 1.2.1 release of Apache Cassandra.
>
>
Hi,
I'd like to release version 1.2.1-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.2.1 release of Apache Cassandra.
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121&version=19089
Staging Repository:
https://nexus.codehaus.org/content/repositories/o
This vote has passed:
+1: Stephen, Michael, Mikhail
0:
-1:
I will proceed with the promotion of artifacts to central
-Stephen
On 14 February 2013 06:26, Mikhail Mazursky wrote:
> +1. Please, release it.
>
>
> 2013/2/14 Stephen Connolly
>
>> More I'm looking fo
)
On Wednesday, 13 February 2013, Michael Kjellman wrote:
> Considering that 1.2.1 is out, and looking at your project very quickly
> (looks interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :)
>
> From: Stephen Connolly
> <mailto:stephen.alan.conno...
Ping
On Monday, 4 February 2013, Stephen Connolly wrote:
> Hi,
>
> I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin
> to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will
> follow shortly after this release, but it should be po
Hi,
I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will
follow shortly after this release, but it should be possible to use the
xpath://project/build/plugins/plugin/dependencies/dependency override of
cassandra
This vote has passed with the following results
+1: Stephen Connolly (dev@mojo), Colin Tayloy (dev@cassandra), Rick
Shaw (dev@cassandra)
0:
-1:
I will proceed to push the plugin artifacts into central
On 2 May 2012 12:15, Stephen Connolly wrote:
> Hi,
>
> I'd like to release vers
On 3 May 2012 10:04, Radim Kolar wrote:
>
>> I'd like to release version 1.1.0-1 of Mojo's Cassandra Maven Plugin
>
>
> What is this plugin supposed to do?
>
Mojo's Cassandra Plugin is used when you want to control a test
instance of Apache Cassandra from within your Apache Maven build.
Useful
Hi,
I'd like to release version 1.1.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.1.0 release of Apache Cassandra.
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121&version=17926
Staging Repository:
https://nexus.codehaus.org/content/repositories/o
On 25 April 2012 09:00, Stephen Connolly wrote:
> On 25 April 2012 08:39, Matthias Pfau wrote:
>
>> Hi there,
>> yesterday, we noticed that cassandra is currently published with
>> inconsistent dependencies. The inconsistencies exist between the published
>> pom
On 25 April 2012 08:39, Matthias Pfau wrote:
> Hi there,
> yesterday, we noticed that cassandra is currently published with
> inconsistent dependencies. The inconsistencies exist between the published
> pom and the published distribution (tar.gz).
>
> This is a serious issue for us as we are usin
there wasn't a standard: Sun's Java coding convention,
> which already says how to place curly braces correctly.
>
> why deviate from the de facto standard for no reason?
>
> thanks.
>
>
> On 1/27/2012 3:48 PM, Stephen Connolly wrote:
>
>> http://programmer
http://programmers.stackexchange.com/questions/2715/should-curly-braces-appear-on-their-own-line
On 27 January 2012 11:36, bxqdev wrote:
> Hello, Cassandra Developers!
>
> What's the point of the deviation ("important exception") from the Sun's
> Java coding convention in Cassandra's java code S
On 12 January 2012 13:27, Sylvain Lebresne wrote:
> On Thu, Jan 12, 2012 at 12:56 PM, Stephen Connolly
> wrote:
>> -0: H may have to rework somewhat the pom generation now that
>> moved to GIT...
>>
>> e.g. see
>> https://repository.apache.org/content
-0: H may have to rework somewhat the pom generation now that
moved to GIT...
e.g. see
https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-parent/1.0.7/cassandra-parent-1.0.7.pom
at XPath /project/scm
Those are SVN urls... should be git
just the question, where do us contributors who are not committers but have
cla's on file (ie already asf committers) push our changes?
hoping this change will make contributing easier.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsens
Nobody objects, so I will publish the artifacts as Cassandra 1.0.0 is being
released
On 12 October 2011 23:44, Stephen Connolly
wrote:
> Hi,
>
> I'd like to release version 1.0.0-1 of Mojo's Cassandra Maven Plugin
> to sync up with the pending 1.0.0 release of Apache Cassa
Hi,
I'd like to release version 1.0.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the pending 1.0.0 release of Apache Cassandra.
This version needs to be tested in conjunction with the current
staging repo for Cassandra 1.0.0
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.
+1 (non-binding) tested with cassandra-maven-plugin
-Stephen
On 11 October 2011 16:26, Sylvain Lebresne wrote:
> Let's hope third times will be the charm. With #3343, #3345 and #3346 in, I
> propose the following artifacts for release as 1.0.0.
>
> SVN:
> https://svn.apache.org/repos/asf/cassan
+1 (non-binding)
-Stephen
On 10 October 2011 17:24, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch f
Yeah it was my bad... the patch for the build versions included an extra .3...
when reviewing the pom for the 1.0.0 vote I caught the mis-match...
pinged Sylvain on IRC...
should probably have raised a JIRA...
but the issue could at best affect only windows users running
cassandra embedded in t
+1 on the POMs (non-Binding)
-Stephen
On 26 September 2011 13:37, Sylvain Lebresne wrote:
> The first beta played its role well: bugs, small and bigger, were fixed[1].
> We have no ticket left open for 1.0.0 except for a few that are minor, aren't
> regressions and imho are no blocker as far as
This vote has passed:
+1: Me, Colin & Nate
0:
-1:
I will proceed with the release
-Stephen
On 20 September 2011 15:27, Stephen Connolly
wrote:
> Hi,
>
> I'd like to release version 0.8.6-1 of Mojo's Cassandra Maven Plugin
> to sync up with the recent 0.8.6 r
Hi,
I'd like to release version 0.8.6-1 of Mojo's Cassandra Maven Plugin
to sync up with the recent 0.8.6 release of Apache Cassandra.
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121&version=17425
Staging Repository:
https://nexus.codehaus.org/content/repos
+1 (non-binding) on the pom.xml's from me
-Stephen
On 14 September 2011 16:56, Sylvain Lebresne wrote:
> It's been a week since the freeze and we don't have too many open tickets for
> 1.0.0. It seems like a good time to get the first beta out. Note that this is
> not a release candidate yet, so
do a realclean
- 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 7 Sep 2011 19:21, "Jason Rutherglen" wrote:
> Now something is broken, I stopped my laptop while Maven was
>
On 7 September 2011 10:12, Eric Evans wrote:
> On Wed, Sep 7, 2011 at 8:22 AM, Stephen Connolly
> wrote:
>> On 6 September 2011 18:34, Vivek Mishra wrote:
>>> Sounds good moving to github.
>>> 1 quick question, what about JIRAs already raised w.r.t drivers? Not s
On 6 September 2011 18:34, Vivek Mishra wrote:
> Sounds good moving to github.
> 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure but
> is it possible to integrate these new projects with current JIRA flow?
>
> Planning to make these new projects based on maven build proc
On 13 July 2011 00:47, Jonathan Ellis wrote:
> On Sat, Jul 9, 2011 at 8:29 PM, Rick Shaw wrote:
>>
>> On Jul 7, 2011, at 10:53 AM, Eric Evans wrote:
>>
>>> On Wed, 2011-07-06 at 13:33 -0500, Jonathan Ellis wrote:
- the git mirror won't pick up anything under drivers/
>>>
>>> Has there been a
if you need a hand with m-ant-t ping me and i'll try and help. also i have
some simplifications on the deploy to maven central that i just haven't got
around to submitting a patch for (auto-retry failed upload and deploy side
artifacts at the same time... the second one will enable deploying
-SNAPS
munch munch munch... this popcorn is nice... having a hard time keeping
stum... :-)
- 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 10 Jul 2011 04:30, "Rick Shaw" wrote:
>
release=true
> So, why wasn't it included ?!
>
> --
> Sylvain
>
> On Fri, May 13, 2011 at 1:37 PM, Stephen Connolly
> wrote:
> > You appear to be missing the -bin artifacts from the staging repository.
> >
> > On 13 May 2011 10:39, Sylvain Lebresne wrote:
&g
You appear to be missing the -bin artifacts from the staging repository.
On 13 May 2011 10:39, Sylvain Lebresne wrote:
> It's been only a little more than 2 weeks since the release of 0.7.5, but
> since then we have corrected a handfull of fairly important bugs, incuding:
> https://issues.apach
On 11 May 2011 15:16, Eric Evans wrote:
> On Wed, 2011-05-11 at 11:53 +0100, Stephen Connolly wrote:
> > When can we expect to see release votes for CQL (and if you need me to
> > help with getting that into Maven central, just shout)
>
> Not sure what you mean. The driver
The stage artifacts look good from a Maven PoV.
I'll be testing them later.
Hopefully this time you'll not forget to release the staging repo ;-)
[aside]
When can we expect to see release votes for CQL (and if you need me to help
with getting that into Maven central, just shout)
-Stephen
On 11
This vote has passed:
+1: Jonathan Ellis (binding); Eric Evans (binding); Brandon Williams
(binding); mck (non-binding); Stephen Connolly (non-binding)
0:
-1:
I will promote the artifacts to Maven Central
-Stephen
On 26 April 2011 14:44, Stephen Connolly wrote:
> Per the Apache release ru
ping. still waiting for two more +1's from cassandra committers
- 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 29 Apr 2011 14:02, "Stephen Connolly"
wrot
OK CQL has been dropped from this release, I need two more binding +1's to
release what remains (all & thrift)
On 28 April 2011 20:42, Stephen Connolly wrote:
> ok well I will see about deleting it from the staging repo, can I get a
> conditional + 1 on that basis?
>
> - S
, "Eric Evans" wrote:
> On Thu, 2011-04-28 at 16:44 +0100, Stephen Connolly wrote:
>> > Unlike the RPC, CQL is meant to be stable. It is a significant
>> feature
>> > that you should be able to use the same version of a driver across
>> many
>> > ver
On 28 April 2011 15:23, Eric Evans wrote:
> On Thu, 2011-04-28 at 06:52 +0100, Stephen Connolly wrote:
>> On 28 April 2011 00:55, Eric Evans wrote:
>> > On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote:
>> >> * I have given the CQL driver jar the same vers
On 28 April 2011 00:55, Eric Evans wrote:
> On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote:
>> * I have given the CQL driver jar the same version number as
>> everything else, because it is only going to work with the 0.8.0-beta1
>> jars anyway.
>>
22:19, "Eric Evans" wrote:
> On Tue, 2011-04-26 at 13:31 +0100, Stephen Connolly wrote:
>> From what I can see, the intent is to always release lock-step in sync
>> with cassandra, in which case the version number should be the
>> cassandra version number...
>>
staging repo as
appended onto this vote
-Stephen
On 26 April 2011 14:45, Stephen Connolly
wrote:
> I've spotted a minor issue with my CASSANDRA-1851 patch...
>
> I'll raise a JIRA to address, and I will have to attach a staging
> repository to this vote for it to be closed suc
I've spotted a minor issue with my CASSANDRA-1851 patch...
I'll raise a JIRA to address, and I will have to attach a staging
repository to this vote for it to be closed successfully (i.e. we are
missing the cassandra-parent pom that all the 0.7.5 poms inherit from)
On 22 April 2011 18:17, Sylvain
Per the Apache release rules, only artifacts which have been voted on
can be released.
Thus, as I missed the main release vote, I cannot tag onto the end.
The artifacts I want to release are:
https://repository.apache.org/content/repositories/orgapachecassandra-114/
Notes:
* The tar.gz files a
Eric,
In looking at the build, I see that the CQL jar gets its own version number...
Does that make sense?
>From what I can see, the intent is to always release lock-step in sync
with cassandra, in which case the version number should be the
cassandra version number...
unless you are implying t
e a direct result of using swype to type on the
screen
On 26 Apr 2011 00:40, "Jake Farrell" wrote:
> I gave myself a ticket for that and will remove the left over log4j
dependency
>
> - Jake
>
> On Apr 25, 2011, at 6:16 PM, Stephen Connolly wrote:
>
>> No it means t
25 April 2011 23:04, Jake Luciani wrote:
> Does this mean 0.6.1 isn't going to work for 0.8 maven deps?
>
> I need to know because I'll upgrade the version in the source if we are
> going to depend on it.
>
> -Jake
>
> On Mon, Apr 25, 2011 at 2:39 PM, Steph
jars rather than deploying a second set to the m2 repo in the cassandra deps
folder. I looked for a pom or ivy.xml to submit a patch against but couldnt
find it in the trunk, is this checked in?
>
> - Jake
>
>
> org.apache.thrift
> libthrift
> [0.6.1,)
>
>
>
> On
I am in the process of ensuring that the 0.8 poms are correct. it is taking
slightly longer than I expected as I got pulled into firefighting with
aws/skynet
and my wife has banned me from the computer this weekend!
I'll call a vote for them early next week (needs a vote under apache rules,
that
FYI: http://www.apache.org/foundation/voting.html#ReleaseVotes
Releases may not be vetoed
On 19 April 2011 13:42, Shotaro Kamio wrote:
> -1,
> I'd like to make 0.8 to include the fix for CASSANDRA-2406. The fix is
> committed to the 0.8 branch lately. I'll wait for beta2.
>
>
> Regards,
> Shotaro
Sorry never mind the spam... stupid GMail autocomplete!
On 19 April 2011 10:22, Stephen Connolly
wrote:
> Hi Mojo developers,
>
> I'd like to promote the extra-enforcer-rules subproject out of the sandbox and
> release version 1.0-alpha-1
>
> This sub-project is designed
Hi Mojo developers,
I'd like to promote the extra-enforcer-rules subproject out of the sandbox and
release version 1.0-alpha-1
This sub-project is designed to allow for hosting of custom rules for
the enforcer plugin.
The project site is deployed at:
http://mojo.codehaus.org/extra-enforcer-ru
The Maven team is pleased to announce the release of Maven ANT Tasks,
version 2.1.3.
The Mavent Ant Tasks allow several of Maven's artifact handling
features to be used from within an Ant build. These include:
Dependency management - including transitive dependencies, scope
recognition and SNAPSHO
Why should you limit to just one volunteer?
The idea is that the procedure in
http://wiki.apache.org/cassandra/HowToPublishReleases should be
followable by any Cassandra committer.
I would propose that the release manager is the person who steps up to
run the release for that specific release. If
I have created http://wiki.apache.org/cassandra/HowToPublishToMavenCentral
which is involved in relation to
https://issues.apache.org/jira/browse/CASSANDRA-1851
If some committers could give feedback.
I'd like to get the patch to land in 0.7 quickly so I can produce an
updated patch for 0.8 befor
http://wiki.apache.org/cassandra/HowToBuild
A number of people have had issues building Cassandra...
Things like:
1. Not using ANT 1.8 or newer (you might get away with 1.7 though but
1.6 is a no go)
2. Not using JDK 1.6 or newer (you might get part of the way with 1.5
as that is the required min
Just an FYI.
I have the required fixes for Maven ANT Tasks in place:
http://jira.codehaus.org/browse/MANTTASKS-217
http://jira.codehaus.org/browse/MANTTASKS-211
http://jira.codehaus.org/browse/MANTTASKS-210
I plan to run a release of Maven ANT Tasks early next week.
Once the release is place I
OK. I've got internet access and pushed the artifacts to central. should be
available in 4-6 hours
On 13 March 2011 22:38, Stephen Connolly wrote:
> On 12 March 2011 00:50, Eric Evans wrote:
>
>>
>> It's that time again. I propose the following for release as 0.7.4
On 12 March 2011 00:50, Eric Evans wrote:
>
> It's that time again. I propose the following for release as 0.7.4.
> What say you?
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1080811
> 0.7.4 artifacts: http://people.apache.org/~eevans
>
> The vote will be open fo
Not quite.
2298 will allow code coverage to always run while 2258 is a specific failure
On 9 March 2011 13:33, Gary Dusbabek wrote:
> Duplicates CASSANDRA-2258.
>
> On Wed, Mar 9, 2011 at 06:15, Stephen Connolly
> wrote:
> > Hmm failure due to some difference when the co
Thanks
-Stephen
On 9 March 2011 09:27, Stephen Connolly wrote:
> FYI,
>
> I am trialling enabling the Cassandra Coverage job I created on Jenkins.
>
> I'm setting the schedule to daily.
>
> We'll see how it works out
>
> -Stephen
>
FYI,
I am trialling enabling the Cassandra Coverage job I created on Jenkins.
I'm setting the schedule to daily.
We'll see how it works out
-Stephen
On 1 March 2011 19:32, Eric Evans wrote:
>
> Here goes attempt #2 of 0.7.3 (see http://goo.gl/Y1l7n for background);
> I propose the following for release as 0.7.3.
>
> SVN:
>
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.3@r1075977
> 0.7.3 artifacts: http://people.apache.or
I'll see if I can stage while hanging around Dublin Airport after that data
roaming costs are prohibitive
-Stephen
On 1 March 2011 19:32, Eric Evans wrote:
>
> Here goes attempt #2 of 0.7.3 (see http://goo.gl/Y1l7n for background);
> I propose the following for release as 0.7.3.
>
> SVN:
>
> ht
ok, if you are respinning i can restage for central tomorrow. but i am
traveling on wed so it would be better to stage on tuesday (ie have the
respin tonight so a can stage tomorrow)
i will be working on extending maven-ant-tasks on the plane to add the
features required to generate simple poms fo
On 25 February 2011 21:09, Eric Evans wrote:
>
> Shall we? I propose the following for release as 0.7.3.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1074693
> 0.7.3 artifacts: http://people.apache.org/~eevans
>
> The vote will be open for 72 hours.
>
> Thanks.
>
On 16 February 2011 23:53, Eric Evans wrote:
> On Tue, 2011-02-15 at 15:57 -0600, Eric Evans wrote:
>> SVN:
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
>> 0.7.2 artifacts: http://people.apache.org/~eevans
>>
>> The delta here is pretty small, so if no one object
On 15 February 2011 21:57, Eric Evans wrote:
>
> CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
> propose the following for 0.7.2.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
> 0.7.2 artifacts: http://people.apache.org/~eevans
>
> T
On 15 February 2011 22:20, Stephen Connolly
wrote:
> On 15 February 2011 22:19, Stephen Connolly
> wrote:
>> On 15 February 2011 22:18, Stephen Connolly
>> wrote:
>>> On 15 February 2011 21:57, Eric Evans wrote:
>>>>
>>>> CASSANDRA-2165[1]
On 15 February 2011 22:19, Stephen Connolly
wrote:
> On 15 February 2011 22:18, Stephen Connolly
> wrote:
>> On 15 February 2011 21:57, Eric Evans wrote:
>>>
>>> CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
>>> propose the foll
On 15 February 2011 22:18, Stephen Connolly
wrote:
> On 15 February 2011 21:57, Eric Evans wrote:
>>
>> CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
>> propose the following for 0.7.2.
>>
>> SVN:
>> https://svn.apache.org/repos
On 15 February 2011 21:57, Eric Evans wrote:
>
> CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
> propose the following for 0.7.2.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
Minor niggle, that revision has the build.xml with base.
I'll publish to maven central
- 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 14 Feb 2011 19:20, "Eric Evans" wrote:
On 10 February 2011 18:49, Stephen Connolly
wrote:
> I'll restage central artifacts by tommorrow morning. hoping this is the last
> take
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a
I'll restage central artifacts by tommorrow morning. hoping this is the last
take
- 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 10 Feb 2011 17:50, "Eric Evans" wrote:
>
>
On 4 February 2011 19:40, Eric Evans wrote:
>
> Lather. Rinse. Repeat. Ya'll know the drill.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1067260
> 0.7.1 artifacts: http://people.apache.org/~eevans
>
> The vote will be open for 72 hours.
>
>
> [1]: http://goo.gl/a
On 31 January 2011 04:41, David G. Boney wrote:
> I propose a simple idea for compression using a compressed string datatype.
>
> The compressed string datatype could be implemented for column family keys by
> creating a compressed string ordered partitioner. The compressed string
> ordered part
I've re-staged the main artifacts. The javautils stuff did not have
any changes so I've left that staging repository as is from take #1
https://repository.apache.org/content/repositories/orgapachecassandra-015/
Description:
apache cassandra 0.7.1 take #2
Details:
The following artifacts have
ght too!) ;-)
-Stephen
On 28 January 2011 20:34, Stephen Connolly
wrote:
> I'll drop and restage the artifacts for maven central when I get a chance
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense
I'll drop and restage the artifacts for maven central when I get a chance
- 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 28 Jan 2011 20:30, "Eric Evans" wrote:
>
> CASSAND
result of using swype to type on the
screen
On 28 Jan 2011 19:21, "Eric Evans" wrote:
> On Fri, 2011-01-28 at 19:07 +0000, Stephen Connolly wrote:
>> Since there does not seem to be any desire to accept CASSANDRA-1997
>>
>> Can the PMC vote to approve the u
Since there does not seem to be any desire to accept CASSANDRA-1997
Can the PMC vote to approve the use of the Cassandra mark by the
mojo.codehaus.org project for the Cassandra Maven Plugin
+1 Approve
0 don't care
-1 Veto
72 hours
PMC votes only
-Stephen
---
>
> Key: CASSANDRA-1997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1997
> Project: Cassandra
> Issue Type: New Feature
>Reporter: Stephen Connolly
> Attachments: CASSANDRA-1997-v2
seemingly this very reason is why tomcat-maven-plugin is moving from mojo to
tomcat
- 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 27 Jan 2011 17:11, "Eric Evans" wrote:
if 0.7.1 is being respun can we get cassandra-1997 added to contrib so that
I can release it at the same time
if you don't want it as part of cassandra, it would be good to know as I
would either need approval to use the cassandra mark if hosting outside
cassandra (I can't host it at maven as we a
found a NPE
in generating a pom with a parent pom. (And I want to use a parent pom
so that we don't have dependency version details scattered all over
the build.xml)
-Stephen
On 26 January 2011 11:43, Stephen Connolly
wrote:
> Artifacts staged at
>
> https://repository.apac
Artifacts staged at
https://repository.apache.org/content/repositories/orgapachecassandra-080/
https://repository.apache.org/content/repositories/orgapachecassandra-081/
-Stephen
On 25 January 2011 23:00, Stephen Connolly
wrote:
> I'll stage artifacts in central tomorrow AM GMT
&
I'll stage artifacts in central tomorrow AM GMT
On 25 January 2011 23:01, Eric Evans wrote:
>
> Shall we? I propose the following artifacts for release as 0.7.1.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1063491
> 0.7.1 artifacts: http://people.apache.org/~eev
itter
> repo defined in ivysettings.xml. When 0.3.0 is released we'll be able to
get
> it Maven Central.
>
> On Sat, Jan 22, 2011 at 12:40 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> On 22 January 2011 08:20, Stephen Connolly
>> wro
On 22 January 2011 08:20, Stephen Connolly
wrote:
> as part of my work on CASSANDRA-2017 I have been trying to test
> various parts of the cassandra build that use ivy in order to make
> sure that the maven-ant-tasks version works too...
>
> currently "ant build-distributed-te
as part of my work on CASSANDRA-2017 I have been trying to test
various parts of the cassandra build that use ivy in order to make
sure that the maven-ant-tasks version works too...
currently "ant build-distributed-test" is broken for me (because it
uses a -snapshot of whirr)
ivy-retrieve-tes
so to be clear, april 9th is feature complete for 0.8.0 and then start
stabilisation... and when might we see a 0.7.1
or am I completely confused?
...
trying to plan splitting the jar into parts, and delivering ever build
tweaks for allowing abny dev to push release to central repository ;-)
-
On 18 January 2011 14:30, Eric Evans wrote:
> On Tue, 2011-01-18 at 13:13 +0000, Stephen Connolly wrote:
>> Is this something that people are OK with?
>
> Why? What are the advantages?
1. It will make deploying to central easier (as ivy does not deploy
correct poms, and mave
Is this something that people are OK with?
It will result in the version details being specified from the
build.xml and not a separate ivy.xml
Which branch shall I target first... My preference is to target 0.7
and then when the modularization takes place in trunk/0.8 it will be
on top of the mav
On 18 January 2011 03:01, Eric Evans wrote:
> On Mon, 2011-01-17 at 12:12 -0500, Jake Luciani wrote:
>> Some context: We have begun the process of removing Avro from the
>> service layer CASSANDRA-926. We currently use Avro for schema
>> migrations internally, and we have two open items that are u
https://issues.apache.org/jira/browse/CASSANDRA-1997
On 16 January 2011 19:59, Stephen Connolly
wrote:
> it will be an attachment to an as yet un raised jira. look out for it
> tomorrow/tuesday
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mist
FYI,
I have started working on a wiki page for uploading to Maven Central.
http://wiki.apache.org/cassandra/HowToPublishToMavenCentral
There is an open issue: namely where are the public GPG keys of
Cassandra Developers kept so that 3rd parties can verify that the
release they download from cent
it will be an attachment to an as yet un raised jira. look out for it
tomorrow/tuesday
- 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 16 Jan 2011 17:52, "Hellmut Adolphs"
1 - 100 of 134 matches
Mail list logo
