+1
I'm using archiva snapshot as a maven1&2 proxy to repo1.apache.org.
I entoutered the OutOfMemory issue and had to setup a cron to stop/restart
tomcat every night.
2007/2/22, Arnaud HERITIER <[EMAIL PROTECTED]>:
+1
Great work !!
Arnaud
On 2/22/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
we are having to use starteam...so good to know that it works on svn...what's
the component that is responsible for it so I can debug it?
-Original Message-
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 6:42 AM
To: continuum-dev@maven.apache.org
Subject:
That's odd. Mine doesn't build a project if there are no SCM changes.
The projects in my Continuum instance are from an SVN repo. Maybe its
an SCM-related problem. What's your SCM provider? Are you sure there
aren't any changes?
[EMAIL PROTECTED] wrote:
can I configure that a clean in
I'm attempting to inject attributes into the site plugin like so in my pom:
bar
bar
site.vm
there is an ear pluginif you rework that patch to be another
module all together and generate that artifact with the ear plugin
then I'll be happy to take a look and apply it I think...but its not
standard practice to have a war artifact producing and ear :)
out of curiousity, what are you ad
Issue Subscription
Filter: Design & Best Practices (37 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
htt
Ok - that's planned work for TestNG too - so I'll defer it until the
next one.
I'll start planning the 2.3 release.
On 23/02/2007, at 10:25 AM, Tom Huybrechts wrote:
I'm using it in production without issues.
One thing that could be improved is that the junit4 provider now looks
at the file
I'm using it in production without issues.
One thing that could be improved is that the junit4 provider now looks
at the filename to find tests, instead of looking for @Test
annotations.
Tom
On 2/22/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 22 Feb 07, at 5:00 PM 22 Feb 07, Brett Porter
On 22 Feb 07, at 5:11 PM 22 Feb 07, Joakim Erdfelt wrote:
Just some thoughts.
I would like to change wagon-webdav's protocol definition.
Currently it is "dav:http://"; and "dav:https://"; both of which are
technically invalid protocols.
It should be "dav://" and "davs://".
As long as you s
It works in some instances, with certain versions of testNG. But
there are a number of problems, especially with newer versions.
On 23/02/2007, at 9:15 AM, Brian E. Fox wrote:
I haven't been tracking the testNG support in detail but does this
mean
it's currently still not working? It's been
Ok, I think that's a pre-existing problem though.
So unless I hear any objections, I'l call a vote for surefire 2.3
(including junit4) later today.
On 23/02/2007, at 9:12 AM, Arnaud HERITIER wrote:
We use it actually, and we didn't find real problems.
Just one annoying : If there's no depen
I haven't been tracking the testNG support in detail but does this mean
it's currently still not working? It's been a while since we tried
it...currently we are launching via ant but this is less than optimal
because it doesn't work with reports and things like cobertura.
-Original Message---
Nice work!
We use it actually, and we didn't find real problems.
Just one annoying : If there's no dependency for a test framework in the
project, we receive a NPE. I don't yet open an issue about this.
Arnaud
On 2/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Good idea.
Does anyone know if the junit4
Just some thoughts.
I would like to change wagon-webdav's protocol definition.
Currently it is "dav:http://"; and "dav:https://"; both of which are
technically invalid protocols.
It should be "dav://" and "davs://".
I've wanted to make the wagon's register URL handlers for themselves too.
That w
On 22 Feb 07, at 5:00 PM 22 Feb 07, Brett Porter wrote:
Good idea.
Does anyone know if the junit4 support is 'production ready'?
I think if anyone can find Tom he's been using it as he made the
initial patches but have not used it myself.
jason.
- Brett
On 23/02/2007, at 3:39 AM, Jas
+1
On 23/02/2007, at 5:00 AM, Jason van Zyl wrote:
There we go, Dan has access now. The PMC folk voted and we all love
the Kulp so I know there will be no objections.
Free work! Yay!
Jason.
On 22 Feb 07, at 10:01 AM 22 Feb 07, Jason van Zyl wrote:
Hi,
Dan has been consistently working o
On 22 Feb 07, at 4:34 PM 22 Feb 07, Eric Brown wrote:
Hi Jason,
On Feb 15, 2007, at 3:55 PM, Jason van Zyl wrote:
Hi,
So that no one can accuse of resting on our laurels time to start
planning for 2.0.6. Not sure what the best way is to gather the
issues to work on but it would be nice
Good idea.
Does anyone know if the junit4 support is 'production ready'?
- Brett
On 23/02/2007, at 3:39 AM, Jason van Zyl wrote:
Hey Brett,
If you are going to do a push for TestNG do you think you might be
able to push out a release to get the 20 or so issues out into the
wild before di
I've just added an updated patch on
http://jira.codehaus.org/browse/CONTINUUM-1167. Continuum will now
successfully send emails under JBoss.
The patch also contains a new module to create an ear file for the war. This
is only activated through a profile named "ear", so to create the ear file
you
Hi Jason,
On Feb 15, 2007, at 3:55 PM, Jason van Zyl wrote:
Hi,
So that no one can accuse of resting on our laurels time to start
planning for 2.0.6. Not sure what the best way is to gather the
issues to work on but it would be nice to gather them in the next
week or so, and then work th
+1
Great work !!
Arnaud
On 2/22/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
I would like to merge the archiva-MRM-239 branch back to trunk.
Not sure how long I should wait for the vote replies, but I'll do the
usual 72.
- Joakim
It'd be good to have the tool that checks for API changes between
versions in the parent pom.
I agree with John in pushing towards final releases, I already said
several times that all these alpha/betas are an excuse to make
dramatic changes while we are actually using them as final.
my 0.02 EUR
How do you mean? What else is there to be concerned about WRT backward
compat?
BTW, I don't think dropping the method entirely is a good course of
action...but we do need to adjust the code to accommodate wagon providers
that don't have it.
I think the wagon API is probably stable enough to talk
Done.
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-transaction/
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-artifact-converter/
Though I haven't moved them out of Archiva yet.
Waiting to get authorization to merge the branch back into trunk first.
- Joakim
Jason van Z
The Wagon.getProtocol() method could probably be dropped.
But that won't address the bigger concern. Backwards compatibility.
- Joakim
John Casey wrote:
> Also, to be clear, in the past I've broken things massively in Maven and
> other places. Almost without fail, someone has tracked me down, a
Also, to be clear, in the past I've broken things massively in Maven and
other places. Almost without fail, someone has tracked me down, and waited
while I stopped everything I was doing, and fixed the problem...with tests,
if possible.
On 2/22/07, John Casey <[EMAIL PROTECTED]> wrote:
Just to
Just to be clear - did I miss a volley of emails on these topics?
-j
On 2/22/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
The changes to wagon are ... (just to make sure they show in john's
gmail account)
1) Timeouts
2) Streaming Wagon
3) Limited Transactions
- Joakim
John Casey wrote:
> H
The changes to wagon are ... (just to make sure they show in john's
gmail account)
1) Timeouts
2) Streaming Wagon
3) Limited Transactions
- Joakim
John Casey wrote:
> Hi all,
>
> I have something to point out that I think the entire Maven development
> community needs to hear. I've been doing a
Hi all,
I have something to point out that I think the entire Maven development
community needs to hear. I've been doing a lot of work recently with Maven
trunk, so I notice any (perhaps inevitable) instability that comes down the
pike from dependency APIs. Recently, I've been having a LOT of tro
There we go, Dan has access now. The PMC folk voted and we all love
the Kulp so I know there will be no objections.
Free work! Yay!
Jason.
On 22 Feb 07, at 10:01 AM 22 Feb 07, Jason van Zyl wrote:
Hi,
Dan has been consistently working on the remote resources plugin
for more then a month,
+1 to someone that at least tangentially understands the importance of "The "
On 2/22/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 22 Feb 07, at 11:30 AM 22 Feb 07, Brian E. Fox wrote:
> +1 based on the new permissions, this is effectively a vote for
> maven karma in general, not maven-plug
Hell yes, I'm all for the changes, especially the ability to clean the
repository of snapshots!! Ideally, I would like to have archiva
periodically keep the last x snapshots and delete the rest. The only other
thing I think is sorely missing is LDAP intregration. Jira, Confluce,
Pulse, Jive, an
On 22 Feb 07, at 11:30 AM 22 Feb 07, Brian E. Fox wrote:
+1 based on the new permissions, this is effectively a vote for
maven karma in general, not maven-plugins only right? (just for
clarification)
Yes, it's now the maven free-for-all.
Jason.
-Original Message-
From: Emmanue
Hey Brett,
If you are going to do a push for TestNG do you think you might be
able to push out a release to get the 20 or so issues out into the
wild before digging in?
Thanks,
Jason.
-
To unsubscribe, e-mail: [EMAIL PR
+1 based on the new permissions, this is effectively a vote for maven karma in
general, not maven-plugins only right? (just for clarification)
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 10:08 AM
To: Maven Developers List
Subject
+1
Emmanuel
Jason van Zyl a écrit :
Hi,
Dan has been consistently working on the remote resources plugin for
more then a month, organized the release and called for the vote and
took care of all the organizational bits.
He's shown he can take care of this stuff from one end to the other.
Hi,
Dan has been consistently working on the remote resources plugin for
more then a month, organized the release and called for the vote and
took care of all the organizational bits.
He's shown he can take care of this stuff from one end to the other.
Let's give him access.
+1
Thanks,
-1 for me
i put a new issue today : http://jira.codehaus.org/browse/MCHANGELOG-54
MCHANGELOG-54 which is blocker for me and i don't know when the next
release will be published.
if it can be fixed as soon as possible.
dennisl-2 wrote:
>
> Hi,
>
> I'd like to release the maven-changelog-pl
Hi,
I think the main Proximity developer is here, and I was wondering if
you would like to work with us on Maven Enterprise (ME)? Essentially
this means us putting a small wrapper around Proximity and firing it
up from the ME server? I'm not sure what the licensing is on
Proximity but if
40 matches
Mail list logo
