Ok, I'd consider this done now I think. The only things I think might be
missing:
- deleting a build
- stopping a build
- RSS
I'm sure I've missed something else... especially in the configuration
and permissions stuff, but this is a start.
- Brett
Brett Porter wrote:
Hi,
I have put this up
Sorry about this - m2 wasn't actually running the tests locally so I
thought it was all good :)
- Brett
[EMAIL PROTECTED] wrote:
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050812.04.txt
Thanks for the offer David. We've got a bit of an investment in the
current framework, but we are actively discussing options, and are
definitely interested in looking into making it work more ike a portal.
I think we'd defer until after Continuum 1.0 to make this sort of change
if at all, but
Hi,
I've done an update of JIRA. All remaining tasks to sync up to the white
site should now be in there. Let's push on to release alpha-4 :)
- Brett
Actually, funnily enough - I fixed something. It should always have failed.
I've added the necessary code to the plexus plugin for it to operate
correctly inside the reactor. We still need a better way to do this - I
think it is in JIRA, but if not I'll file it.
Hopefully next run will succeed.
Hi,
These are all in JIRA. I've been talking to people setting up an
instance for ActiveMQ and related projects, and I'm thinking these are
the top development priorities for now:
1) Blame mechanism
2) Inclusion of junit test results
3) Security
4) browse working copy
Thoughts?
Also, I think
fyi
---BeginMessage---
Subversion commit messages are sent to different lists
according to the following mapping
# Maven
[/maven]
for_paths = maven/
to_addr = commits at maven.apache.org
suppress_if_match = yes
[/maven/continuum]
for_paths = maven/continuum/
to_addr = continuum-commits at
+1
Emmanuel Venisse wrote:
Hi,
Please vote on releasing continuum 1.0.1
From me, +1
Emmanuel
I've noticed John has posted a number of documents here:
http://docs.codehaus.org/display/CONTINUUM/Continuum+1.1+Design+Discussions
I've provided some feedback - it'd be great if anyone else could take a
look. Before the feature breakdown happens.
Cheers,
Brett
Is this stil lrequired after the other fix?
If so, can we be more specific about the caught exception?
[EMAIL PROTECTED] wrote:
Author: evenisse
Date: Tue Nov 15 08:48:36 2005
New Revision: 344392
URL: http://svn.apache.org/viewcvs?rev=344392view=rev
Log:
Retry the update if derby generate a
Hi,
Thought I'd throw this out for discussion before considering forming it
in JIRA for, say, 1.2.
I was thinking about the process of adding a parent pom and having all
the modules added, and wondered what should happen when a new module is
added, or a module is removed from the parent.
Here,
Carlos Sanchez wrote:
Acegi is based in servlet filters for the protection of urls, so the
web framework used won't impact its use.
That's great. Does it still require spring to be configured though? We
already have a massive download - I'd really like to reduce our
dependency set.
I was in a
+1
John Casey wrote:
Hi,
I'd like to discuss releasing the next version of Continuum: 1.0.2. In
the past few weeks, several critical problems have been resolved,
including various performance and usability improvements. In addition,
other bugs have been resolved to enhance support for the
+1
I'm all for splitting up into action components, but retaining a
Continuum interface as a single entry point to those
- Brett
John Casey wrote:
I think we have to be careful when splitting up a public api like
this. It's possible Continuum may need to be embedded someday, and if
so, it
There's a couple of layers between continuum and the service here. 1)
the windows service mechanism and 2) the java service wrapper code.
One place to look would be the Windows event log, the other would be the
continuum stdout log if it got that far.
- Brett
Graham Leggett wrote:
Hi all,
Seraph also wraps around osuser, I believe.
I think that standalone should be a secondary concern (a nice to have).
I think as long as it can be backed by the same permissions data, the
web part is the hard part we don't want to have to reproduce and maintain.
I'd go with further investigation
any features to be able to
release more promptly and spend more time testing :)
I'm thinking Maven 2.1 and Continuum 1.1 might be less ambitious than
originally, and more about addressing the big issue in usability or
lacking issues, and of course architectural stabilisation.
WDYT?
- Brett
Brett
... and we certainly encourage folks wanting to do that. Even more so if
they want to contribute changes back :) Email customisation would be a
useful feature to have.
I think the main thing we try to discourage is people just wanting to
check out the latest features building from sources -
we should switch to this - not sure if its in the repo yet.
- Brett
-- Forwarded message --
From: Craig L Russell [EMAIL PROTECTED]
Date: Feb 1, 2006 5:47 AM
Subject: [ANN] Apache JDO 2.0 beta released
To: general@db.apache.org
Cc: JDO Expert Group [EMAIL PROTECTED], Apache JDO
Hi,
I implemented CONTINUUM-609 so that, if configured, the built artifact
(roughly) is deployed to a special repository served by Continuum. It
only supports Maven 2 builds and only deploys
${project.build.directory}/${project.final.name}.ext if it exists, so is
a bit limited right now.
The
I've been testing and its looking great, but can we hold off voting
until the final RC is ready? I'd like to follow the lead taken with the
Maven core which has resulted in us delaying the release due to bugs
that otherwise would have got by unnoticed.
- Brett
Emmanuel Venisse wrote:
Hi,
I
Yep, caught your rollback. Thanks for that.
Emmanuel Venisse wrote:
Brett,
we can't use compile class because we don't want jdo stuff in enhanced
classes.
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: brett
Date: Mon Mar 27 08:27:17 2006
New Revision: 389193
URL:
Not at present, but its a good idea. Please make a feature request for
listeners.
However, if you want both success and failure moved to the shared
filesystem - maybe you should just set the working directory to the
shared filesystem?
- Brett
Gautham Pamu wrote:
Hi Everyone,
I am fairly new
Hi,
I've done some investigation.
I was able to run the server where it was just checking for non-existant
updates for some time, and it had no net result on memory usage (it
constantly goes up, gc's back to the same level, etc).
When I ran a build all on cheddar (with no checkouts), net
theoretically it shouldn't have changed since the last tag :)
Trygve Laugstøl wrote:
Brett Porter wrote:
Yep, I agree with you both. Perhaps removing it after the 1.1 release
is the most appropriate.
+1, and include the last known rev in the README.txt :)
--
Trygve
--
Brett Porter
All the integration tests are failing. Is this simply because they rely
on the old webapp?
What needs to happen to get this working again?
- Brett
[EMAIL PROTECTED] wrote:
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060529.22.txt
--
Brett Porter
On 3/07/2006 7:17 PM, Jason van Zyl wrote:
So you're suggesting we not doing any official alpha/beta releases?
Right.
- Brett
--
Brett Porter [EMAIL PROTECTED]
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
*the onlooking crowd gasps* Trygve pulled out the veto!
:)
Regardless, I agree. I'm pretty sure Continuum already has a log4j
configuration in it's application.xml that can include both these
configurations.
On 12/07/2006 5:04 AM, Trygve Laugstøl wrote:
Trygve Laugstøl wrote:
[EMAIL
I had a look at this, and added high next to the ones that I thought
were high, and realised it was all but two.
So I took the column out and moved those two to a 1.2 roadmap. Maybe we
can break that down into 1.2, 2.0, etc. as we go and just keep this page
as the this is what we're doing and
Hi,
I've created a skin (maven-application-skin), which is the
maven-theme.css and images needed to do the Continuum lf with the
normal Maven page layout (ie, css layout, not tables like in Continuum
right now).
Thought this might be worth updating in the Continuum decorator (the
decorator
On 11/08/2006 7:52 AM, Jesse McConnell wrote:
one possible difference I have noticed is that the jdo store is not
loading up until it is first accessed, which is a different behavior
then before, which make senses if its load-on-start...
Right. It also means that no builds will occur until
maven-model-converter is being discussed on dev@ and it already has some
of this I think.
- Brett
On 14/08/2006 3:07 AM, Erik Bengtson wrote:
Hi,
In JPOX we have many projects built by maven, I've created a XQ to transform
project to pom, but dont have one tool to transform properties to
Wouldn't it be better to fix the tests/execution to create this in a
more normal place, like target/plexus.home as it used to be?
- Brett
On 14/08/2006 7:29 AM, [EMAIL PROTECTED] wrote:
Author: carlos
Date: Sun Aug 13 14:29:07 2006
New Revision: 431246
URL:
kind of against the principles of Continuum to sweep things under the
carpet :)
Do you want to create a jira for it?
- Brett
On 14/08/2006 7:49 AM, Carlos Sanchez wrote:
that be great, but in the meantime this is very handy
On 8/13/06, Brett Porter [EMAIL PROTECTED] wrote:
Wouldn't
a jira to put back the right url composition, your changes
won't work in some cases (we just moved all url composition to use
c:url)
On 8/15/06, Brett Porter [EMAIL PROTECTED] wrote:
There are two versions of c: - core, and core_rt. If you are
including a
TLD in the webapp, make sure you have
there's an equivalent in jstl? why not stick to the standard? I'd use
jstl by default and ww tags when there's no jstl equivalent.
On 8/15/06, Brett Porter [EMAIL PROTECTED] wrote:
Since it's an action URL, I strong suggest using ww:url instead.
- Brett
On 16/08/2006 12:04 PM, Carlos Sanchez wrote
Hi,
I've tried to run Continuum from trunk (just the normal svn up, mvn
clean install, cd continuum-webapp, mvn jetty:run), but I get this:
:WARN: /
java.lang.NullPointerException
at
org.mortbay.jetty.servlet.DefaultServlet.passConditionalHeaders
(DefaultServlet.java:485)
The summary page shows only a few of the release parameters. So the
Edit link is there to direct the user to the more detailed
release configuration page. But since we'll be releasing projects
one at a time, I guess I can incorporate what you mean into the new
white-site.
Just to be
With Archiva and Continuum both being webapps now, its should be
straightforward to deploy them both to your favourite container, and
as long as they are configured to utilise the same repository you'll
get what you need.
- Brett
On 25/08/2006, at 5:46 PM, Tomasz Pik wrote:
I'm jumping
Hi,
I've copied trunk at r437501 to:
https://svn.apache.org/repos/asf/maven/continuum/branches/release-
integration
Jeremy and Edwin have access as well as the rest of the Continuum
committers so that they can work on the release proposal that is
being bounced around on the list.
looks about right.
The only thing I'm thinking is that the view output step is not
required for all of the steps - just the mvn builds and SCM operations.
Or perhaps it can just be one large output that is a link at the bottom?
Cheers,
Brett
On 29/08/2006, at 2:07 PM, Edwin Punzalan wrote:
Hi Brill,
That's great to hear!
Some things to be aware of with Continuum:
1) A lot of JIRA stuff may now be redundant as trunk (1.1) is based
on webwork, where 1.0.3 was based on plexus-summit.
2) There is a security overhaul going on as you'll see on this list.
So if you are tackling
Should this have a Submitted By: line? Wondering who you are thanking :)
On 26/08/2006, at 2:29 PM, [EMAIL PROTECTED] wrote:
Author: jmcconnell
Date: Fri Aug 25 21:29:06 2006
New Revision: 437073
URL: http://svn.apache.org/viewvc?rev=437073view=rev
Log:
applied CONTINUUN-819 and CONTINUUM-309
Seems like you are picking up an old version of plexus-utils somewhere.
- Brett
On 31/08/2006, at 9:40 AM, Barrie Treloar wrote:
I am on a Windows XP machine and running build.bat.
Has anyone else seen this error before?
2006-08-31 08:55:49,497 [Thread-2] ERROR Action:execute-builder
- Error
On 03/09/2006, at 12:08 AM, Kenney Westerhof wrote:
For now I'll just add a field to the Schedule, stating max
execution time of a build.
+1, with the default being rather large (but not infinite).
Sounds like we've got some work to do on the scheduling in the next
release :)
--
So, as I understand it - Jeremy and Edwin can continue to work on the
branch and we can merge again as there are more changes?
- Brett
On 18/09/2006, at 11:13 AM, Carlos Sanchez wrote:
I've merged the changes in
https://svn.apache.org/repos/asf/maven/continuum/branches/release-
integration
On 26/09/2006, at 11:05 AM, David Blevins wrote:
Do you guys think it's unreasonable to try and put up an install of
Continuum trunk to run a few projects? Is trunk basically
functional at this point?
+1 to doing this on the zone.
- Brett
I've taken a peek through this to sanity check - there are some
things that look like they've been removed that shouldn't have been,
but I could be wrong and it could have been intentional. Can you
confirm?
On 25/09/2006, at 10:40 AM, [EMAIL PROTECTED] wrote:
Added:
+1 from me too.
I've inspected the original Continuum security, the proposed
continuum-acegi branch and the rbac-integration one. This is
definitely the easiest to understand and work with, and gives us the
best of both worlds - a strong user model and RBAC authorization
framework that
Thanks! Would you mind filing this in JIRA?
On 20/10/2006, at 11:15 PM, Philippe Faes wrote:
Joakim,
I believe I've found the reason why the tests for continuum-release
are
not predictable. The two tests are executed in random order (junit
does
this), but they change the contents of
On 09/11/2006, at 4:17 AM, [EMAIL PROTECTED] wrote:
+!--
dependency
groupIdorg.apache.derby/groupId
artifactIdderby/artifactId
/dependency
+--
+dependency
+ groupIdpostgresql/groupId
+ artifactIdpostgresql/artifactId
+
between this and what used to exist before my group
changes is that it will attempt to order inside the group and build as
opposed to before where it would just failover to building all
projects in whatever order came from the db.
is that where we are with this?
jesse
On 11/8/06, Brett Porter
I see a couple of models in continuum-webapp, which seem to be
partially used. Does anyone know if session-models is used any more?
What about view-models - only the summary parts still seem valid?
- Brett
Hi,
I've started to redevelop the white site, starting with some
configuration changes I'm making today:
http://people.apache.org/~brett/continuum-white-site/admin/
appearance.html
Thoughts?
- Brett
Sounds good, as long as the store remains independent of them. I
don't want to get into the situation like in JIRA where you can't
rename a string key.
Before starting to hack on this, perhaps you could list out all the
keys you think are needed, and some examples? I'm interested in how
On 23/12/2006, at 12:24 AM, Jesse McConnell wrote:
the project.id and projectGroup.id will basically disappear from
continuum, reserved strictly for the underlying store. The store can
do whatever it wants with them.
Ok, so a project(Group)? will have:
id : int
key : String
name : String
Hi,
A few observations on these. Does anyone else have outstanding
todos in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these need to be run regularly to be really useful. They aren't
part of the main build ( a good idea, since it requires a UI
On 27/12/2006, at 2:08 PM, Brett Porter wrote:
Hi,
A few observations on these. Does anyone else have outstanding
todos in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these need to be run regularly to be really useful. They aren't
part
see below
On 27/12/2006, at 3:09 PM, Brett Porter wrote:
On 27/12/2006, at 2:08 PM, Brett Porter wrote:
Hi,
A few observations on these. Does anyone else have outstanding
todos in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these need
Yes, it's fetch groups. The store (pre-groups) took all this into
account, however the lack of central management for some of it caused
it to be pretty error prone. Those problems were related to
Continuum's design, not anything to do with the use of JPOX (and
something that'd be
agree perhaps another temp location is a better candidate for
setting up container installation - may be 'target' directory under
top level root?
Rahul
- Original Message - From: Brett Porter [EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Friday, December 29, 2006 6:56 PM
Great - can the patch be used as a starting point?
On 03/01/2007, at 2:27 AM, Emmanuel Venisse wrote:
Brett Porter a écrit :
Hi Jesse,
I see you took this one a couple of months ago. It looks like a
good feature - is the patch a good enough start to use for now?
It was submitted by John
../mymodule
Emmanuel
Brett Porter a écrit :
Great - can the patch be used as a starting point?
On 03/01/2007, at 2:27 AM, Emmanuel Venisse wrote:
Brett Porter a écrit :
Hi Jesse,
I see you took this one a couple of months ago. It looks like a
good feature - is the patch a good enough start
I saw it yesterday too. I actually had the problem before svn kicked
in, as far as I could tell. ie, retrieving POMs might be the problem.
On 06/01/2007, at 9:30 AM, Wendy Smoak wrote:
The ASF Subversion server limits connections to 10 per IP address, and
with several ASF projects loaded up,
working
copy is up-to-date
Emmanuel
Brett Porter a écrit :
That doesn't actually matter for the client side speed boost. I'm
running 1.4.2 on continuum now.
- Brett
On 15/01/2007, at 2:21 PM, Brian E. Fox wrote:
The svn.apache.org server is a little old too: Powered by Subversion
version 1.3.1
Ok, fair enough. I've left it on, and made it use a different local
repository.
I'd say once we release Continuum 1.1 and are happy it is stable
enough to use, we can turn this off.
On 15/01/2007, at 11:02 PM, Trygve Laugstøl wrote:
Brett Porter wrote:
so... you're saying you don't
Any objections to me moving the configuration service out of the
database (and take some of the bits out of application.xml) and
putting them in the registry? Basically the same thing I've just done
for Archiva.
Docs on the registry are here: https://svn.codehaus.org/plexus/plexus-
Actually, it's continuum-commits. However, I already did the -allow
thing in case she was subscribed under a different address.
On 20/02/2007, at 5:44 PM, Trygve Laugstøl wrote:
your commit emails are beeing moderated.
--
Trygve
Can you do
svn propedit svn:log -r509415 --revprop
And add that to the front?
- Brett
On 20/02/2007, at 8:38 PM, [EMAIL PROTECTED] wrote:
Hi Wendy,
This is for CONTINUUM-1147
Thanks,
Deng
On 2/19/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: oching
Date: Mon Feb 19
Agreed. Someone needs to:
- properly mark up the model as it was for 1.0.3 release
- add methods to continuum-data-management to utilise that and then
make any necessary transformations (c-d-m will do the basic 1-to-1
conversions)
- probably write a little CLI to fire it off.
On 24/02/2007,
I agree with an alpha-1 labelled release.
I think someone will need to flush JIRA before cutting the release
(close things that are no longer relevant, or fixed, or duplicate).
- Brett
On 24/02/2007, at 8:35 AM, Jesse McConnell wrote:
I was talking to trygve a bit on irc and it dovetailed
On 07/03/2007, at 9:52 AM, Jesse McConnell wrote:
Ok, well the little poll thread I made seemed to be strongly in favor
of getting things pulled together to start getting alpha releases out
of continuum. So with that in mind here is a list of a few things
that we need to get in order for an
This was one of the things I was going to try and have done before
alpha-1 - I just forgot.
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
probably appreciate most help in future proofing our jpox use a
potential DB keyword conflicts
jesse
On 4/23/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Can I be sure at least that the DB model won't change as from
alpha-1?
If so I can maybe drop completely my database and recreate my
projects.
Thanks,
Stéphane
On 4/23/07, Brett Porter [EMAIL PROTECTED] wrote
Thanks Erik - I'll give that a try ASAP.
On 24/04/2007, at 7:35 AM, Erik Bengtson wrote:
Quoting Brett Porter [EMAIL PROTECTED]:
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
probably appreciate most
I'm trying to find the official release, and I can only find the file
in Jesse's home directory, and no announcement. Bit lost.
Can we do these?
- put in the main repo
- put in /dist/
- put on the website
- announce to lists / blogs
Cheers,
Brett
On 02/05/2007, at 4:10 PM, Jesse McConnell wrote:
there was discussion on this on another thread on this list...but I
will reiterate here that I feel uncomfortable shoving big war files
and these alpha-1 artifacts into the main repository. No one is
programming against these things in the
the migration tool.
- Brett
On 24/04/2007, at 7:35 AM, Erik Bengtson wrote:
Quoting Brett Porter [EMAIL PROTECTED]:
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
probably appreciate most help in future proofing our
Did you update this particular commit with svn pe --revprop -r535724
svn:log ?
On 09/05/2007, at 7:40 PM, Maria Odea Ching wrote:
Ok, I'll take note of that
Trygve Laugstøl wrote:
[EMAIL PROTECTED] wrote:
Author: oching
Date: Sun May 6 20:34:07 2007
New Revision: 535724
URL:
I don't think it's possible to put it anywhere other than the webapp
META-INF location at this point, without changing the way it's
configured.
- Brett
On 20/05/2007, at 11:24 PM, Wendy Smoak wrote:
In the FAQ [1] we say to uncomment an allowedScheme element in
- I'm honestly not sure.
- Brett
On 21/05/2007, at 6:59 AM, Wendy Smoak wrote:
On 5/20/07, Brett Porter [EMAIL PROTECTED] wrote:
I don't think it's possible to put it anywhere other than the webapp
META-INF location at this point, without changing the way it's
configured.
On the Deploying page
+1.
Gave it a quick fire up on the Mac.
- Brett
On 31/05/2007, at 6:38 AM, Jesse McConnell wrote:
I would like to get alpha-2 released to the community now.
Highlights are:
revamped xml-rpc support
converted to use rebranded plexus-security, aka redback
continuum maven plugin
many bug
If my memory serves, we had decided we were ready to take this step
for the applications, but not Maven itself until the toolchain
support is final.
Any objections?
- Brett
On 05/06/2007, at 2:32 AM, [EMAIL PROTECTED] wrote:
Author: brett
Date: Mon Jun 4 09:32:12 2007
New Revision:
On 13/06/2007, at 5:49 AM, Jason van Zyl wrote:
On 12 Jun 07, at 11:37 AM 12 Jun 07, [EMAIL PROTECTED] wrote:
Author: brett
Date: Tue Jun 12 11:37:19 2007
New Revision: 546588
URL: http://svn.apache.org/viewvc?view=revrev=546588
Log:
other aspect of CORE-3297 requires a patch to OID instead
I believe you can use that configuration, but like you I never have,
just pointing it directly at :8080 from httpd.
On 01/07/2007, at 3:11 PM, Wendy Smoak wrote:
Is the Jetty Configuration section on this page up to date?
http://maven.apache.org/continuum/guides/mini/guide-
On 03/07/2007, at 5:54 AM, Emmanuel Venisse wrote:
Jesse McConnell a écrit :
Just to capture some talk on irc today...
I think the strategy moving forward is going to be get some of jira
cleaned up a la the recent maven jira push and continuum 1.1 is going
to get wrapped up a bit for the
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing modules
to the list of projects in a group? If so, how to handle the edge
cases where extra projects are added to or removed from a group aside
from the modules?
- how
On 11/07/2007, at 5:51 PM, Emmanuel Venisse wrote:
Brett Porter a écrit :
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing
modules to the list of projects in a group? If so, how to handle
the edge cases where
Hi,
I haven't looked beyond this issue - so there may be more - but I see
CONTINUUM-761 is a new feature scheduled for 1.1-beta-2.
Shouldn't this be in beta-1, or a future version?
- Brett
Hi folks,
I'm currently doing the rounds of all the people using Continuum on
VMBuild. The set up on there ballooned despite the box being
underpowered and the installation intended to be experimental, so was
never very well maintained.
We have a new box to move vmbuild to now and with
So, is anyone interested?
On 11/07/2007, at 11:06 PM, Brett Porter wrote:
Hi folks,
I'm currently doing the rounds of all the people using Continuum on
VMBuild. The set up on there ballooned despite the box being
underpowered and the installation intended to be experimental, so
Hi,
I took a look through future for things that could be adjusted, and
came up with the following list. I didn't want to 'just do it', since
I'm not that close to the status of the project right now, so if
someone could review these it'd be much appreciated.
to close:
CONTINUUM-933
Anyone have any thoughts on these, or should I just go ahead and make
the changes?
(Sorry Emmanuel, I know you've been offline a bit recently :)
Cheers,
Brett
On 25/07/2007, at 5:13 PM, Emmanuel Venisse wrote:
Thanks Brett, I'll review them.
Emmanuel
Brett Porter a écrit :
Hi,
I took
On 01/08/2007, at 12:01 PM, Jesse McConnell wrote:
well, 1.1 is in beta now so ideally no more features, but maybe we
just call
this a bug fix for now..
yeah, I'm looking more for a small improvement than a revolution.
Avoiding schema changes and such. I really should have said something
Hi,
I've narrowed down the problem in upgrading from alpha-2 to beta-1 to
the following model change:
field
namebuildDefinition/name
version1.1.0+/version
association xml.reference=true stash.part=true
jpox.dependent=false
On 02/08/2007, at 7:46 AM, Emmanuel Venisse wrote:
For a project notifier, I think we can keep what we have actually,
but for a group notifier, we can send a single mail by project group.
The mail can be sent after the build of the latest project of the
group, I don't think it will be a
Brett Porter a écrit :
Hi,
How do people feel about planning betas to fit into: Aug 15, Aug
29, Sep 12, Sep 26? (for releases, votes are the monday before)
If so, is the current beta-2 list achievable by Aug 15? Looks like
it needs to be trimmed (and we also have 11 unscheduled to find a
home
Hi all,
I already posted this to the users@ list, but I thought some folk
here might be more particularly interested in what Emmanuel had to
say when we talked recently: http://www.devzuz.org/?q=node/12.
Enjoy!
Cheers,
Brett
notifier itself. Default is off for consistency with current
behaviour.
2) add a threshold of messages, particularly for errors - don't send
a message that is identical to one sent in the last X hours.
Cheers,
Brett
On 02/08/2007, at 6:26 PM, Emmanuel Venisse wrote:
Brett Porter a écrit
is this just a bad env on the zone? might be a hint that the release
stuff could have a problem with certain environments too - worth
checking.
On 15/08/2007, at 3:05 AM, [EMAIL PROTECTED] wrote:
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-
1 - 100 of 277 matches
Mail list logo
