On 27/12/2006, at 7:10 PM, Rahul Thakur wrote:
Updates to any children hanging off key entities should cascade.
This makes sense if and only if the children are dependent. So, for
build definitions - that's right. Profiles and such are all 'links'
and so will be managed by the normal for
On 27/12/2006, at 8:28 AM, Jesse McConnell wrote:
Rahul is going to mail on how this can be cleaned up in the store api,
but I question why we want these methods on the Continuum interface at
all?
I think it's there as the application interface - for use from the
webapp and the xmlrpc inter
On 12/28/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Fabrizio,
Slight delay but I'll have to release the Eclipse plugin from Window.
The forked test that you're using won't pass on any system properties
so I can't skip the tests. They all fail on OS/X and on Linux. I
think that's a clear sign
How about committing this to the Maven sandbox? It's open to all
apache committers.
You might like to discuss this at (and subscribe to) doxia-
dev@maven.apache.org - it's low traffic compared to this list and
more on topic.
Cheers,
Brett
On 28/12/2006, at 8:41 AM, Henning P. Schmiedehaus
Fabrizio,
Slight delay but I'll have to release the Eclipse plugin from Window.
The forked test that you're using won't pass on any system properties
so I can't skip the tests. They all fail on OS/X and on Linux. I
think that's a clear sign we have some problems with the testing.
I will
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (22 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1288Request to upload RCFaces jars : html
http://jira.codehaus.org/browse/MAVENUPLOAD-1288
MAVENUPLOAD-1287Request to upload RCFaces jars
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (40 issues)
Subscriber: mavendevlist
Key Summary
MEV-479 Invalid POI POM
http://jira.codehaus.org/browse/MEV-479
MEV-478 jakarta-poi requires commons-lang as dependency
http://jira.co
On 12/27/06, Brett Porter <[EMAIL PROTECTED]> wrote:
6) we should use dbunit or something similar to set the database up
into a consistent state for the respective tests, and tear it down
again. Running through the web interface in tearDown is time
consuming, and error prone (if you add a new tes
Jason, I will commit the necessary code before the end of the week.
I'll explain you how you can reproduce it.
Thanks a lot
arnaud
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Arnaud,
Let me know how the alpha-15-SNAPSHOT went and then once we are
sync'd up andy and I will track do
6) we should use dbunit or something similar to set the database up
into a consistent state for the respective tests, and tear it down
again. Running through the web interface in tearDown is time
consuming, and error prone (if you add a new test that doesn't tear
itself down, then a differe
Hi Natalie,
The logo is somewhat separate - it is part of the overall site
configuration, not a part of the report. This sample from John is
just using the current default.
I agree it is a good idea for our little built by logo to default to
one that matches the main logo on the site, it'
This is the fruit of some toying with Doxia, Plexus, the various
different ways to write annotations, Plugins and some general maven
hacking. And a lot of frustration about the state of general and
specific Maven 2 documentation.
It allows you to do things like
http://svn.apache.org/viewvc/db/site
+1
Stephane Nicoll wrote:
+1
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Ok, headers updated.
This release contains the changes required for deploying to staging
repositories. So I would like to release this so that I can remove
the SNAPSHOT from the profile that will be u
changes.xml is also very useful where module:JIRA project is not 1:1.
We have jira projects for each subsystem, not module.
On 12/27/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE tracking system has the details for the
initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>:
> On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >
>
John
What about updating the "Built with Maven" logo? I will send to you in separate
email. Thanks!
Natalie
--- Original Message ---
From: "John Tolentino" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Date: Sat, 23 Dec 2006 07:13:20 +0800
Subject:
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
If you're sure they work I can do the release. Looks like the EAR
plugin is ready now too.
It is. I have tested on both windows/linux. I don't have macOSx (yet ;-)) )
We need to seriously all the testing stuff.
This is where having 5 diffe
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I never really understood the changes.xml myself, as I don't want to
keep things in an issue tracking system and changes.xml or is this
for folks who don't employ an issue tracking system?
Yes and no. I've always seen it as a "technical" ch
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 27 Dec 06, at 6:15 AM 27 Dec 06, Stephane Nicoll wrote:
> I have applied a little hack, let's make sure we fix this in the
> verifier directly.
>
Can you stick something in JIRA or a TODO in the verifier code so
that I don't forget. I stil
Jason van Zyl wrote:
On 27 Dec 06, at 7:17 AM 27 Dec 06, Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state.
But it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
The main hurdle that I have seen is that the pl
On 27 Dec 06, at 4:22 AM 27 Dec 06, Fabrizio Giustina wrote:
Hi Jason,
from what I can see in the log the only error for the eclipse plugin
is the same we saw before:
"Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-ec
On 27 Dec 06, at 6:15 AM 27 Dec 06, Stephane Nicoll wrote:
Jason,
The ear ITs are now fixed on linux. It's what I thought (the process
exit code being different on linux and Windows).
I have applied a little hack, let's make sure we fix this in the
verifier directly.
Can you stick something
On 27 Dec 06, at 7:17 AM 27 Dec 06, Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state.
But it has been going on for too long, I did however manage to get
a 2.0-beta-2 out there.
The main hurdle that I have seen is that the plugin does too much
On 12/26/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
hehe, please file jira issue
Done. This one is http://jira.codehaus.org/browse/CONTINUUM-1085, and
most of 1082-1093 are related.
--
Wendy
Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state. But
it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
I just checked to see if there were any differences between 2.0-beta-2
and the current SVN trunk. The chan
Hi
I've been trying to get the changes plugin into a releasable state. But
it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
The main hurdle that I have seen is that the plugin does too much at the
same time. This has also been seen on the user list where
Jason,
The ear ITs are now fixed on linux. It's what I thought (the process
exit code being different on linux and Windows).
I have applied a little hack, let's make sure we fix this in the
verifier directly.
Cheers,
Stpéhane
On 12/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: s
Hey,
I was about to start working on an issue on my linux box and the
idea:module goal was unavailable. Then I executed maven with the -U
flag and it suddently downloaded a released version of the plugin.
How come it was not downloaded by default? See below
[EMAIL PROTECTED] maven-ear-plugin]$
I have reproduced the EAR test issue on fedora. I am working on it.
Cheers,
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Guys,
I just did a clean install of CentOS (redhat linux), a fresh download
of 2.0.4, no existing local repository, with java 1.5 and I get
failures in bo
Definitely +1
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like
+1
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Ok, headers updated.
This release contains the changes required for deploying to staging
repositories. So I would like to release this so that I can remove
the SNAPSHOT from the profile that will be used for release staging.
Re
I will reboot on Fedora and see what's going on.
Cheers,
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Guys,
I just did a clean install of CentOS (redhat linux), a fresh download
of 2.0.4, no existing local repository, with java 1.5 and I get
failures in both the EAR and Ecli
Hi Jason,
from what I can see in the log the only error for the eclipse plugin
is the same we saw before:
"Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse."
Another thing I see in the log is t
Store updates:
I am taking a stab at refactoring the current ContinuumStore into
RefactoredContinuumStore as a p-o-c for a couple of things.
1) Idea basically is that the Store interface should provide (lookup,
save
and delete) operations on key 'application' entities. I gather these are
o Pro
34 matches
Mail list logo
