+1
Arnaud
On 07/09/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would like to release the maven-verifier as it's used as part of
> Maven's integration tests and would like to stop using the snapshot
> in order to prepare for the 2.1-alpha-1.
>
> The staging area is here:
>
> http://pe
Hi,
I would like to release the maven-verifier as it's used as part of
Maven's integration tests and would like to stop using the snapshot
in order to prepare for the 2.1-alpha-1.
The staging area is here:
http://people.apache.org/~jvanzyl/maven-verifier-1.1-staging-repository/
There are
On 6 Sep 07, at 12:17 PM 6 Sep 07, Brett Porter wrote:
Jason - you're aware of this?
Builds fine in Hudson and on my machine, you sure this isn't a
Continuum error?
It would also be a lot more helpful to turn on the blame mechanism.
Turn that on to mail/IM developers individually and i
Hi,
FYI I reported this as a Jira issue almost a year ago:
http://jira.codehaus.org/browse/MNG-2576
oh. I just saw your comment on the issue referring to this.
Yes, this is exactly the same issue ;)
-- Kenney
Brian E. Fox wrote:
http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode
On 07/09/2007, at 2:00 PM, Jason van Zyl wrote:
On 6 Sep 07, at 12:17 PM 6 Sep 07, Brett Porter wrote:
Jason - you're aware of this?
Builds fine in Hudson and on my machine, you sure this isn't a
Continuum error?
This morning - no, it failed on my machine as well when I
bootstrapped
Issue Subscription
Filter: Design & Best Practices (29 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
So in the end, I just separated my wrapper utility into a small maven
project upon which the plugin depends. I was hoping not to do it,
since it's basically two classes, but it's likely the right way to
handle it anyway. Thanks for the suggestions.
Incidentally, the plugin expression is b
Yep, I try to release ones I'm comfortable with but it's hard when
you're working in free time and bouncing across many plugins in core. I
definitely want to release more often, but find it's often many months
between getting releases out. I guess if you see a plugin that is really
ready to go and
I guess it's just a matter of bugging the developers that work on
those plugins to get the released. I try to do it as often as
possible, but sometimes oyu move on to other things and you forget.
On 9/6/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Hello,
>
> First be sure I've lot's of respect
Dennis Lundberg wrote:
nicolas de loof wrote:
Hello,
First be sure I've lot's of respect for maven developpers and the
work they
offer to the community.
I'm just curious about WHY there is so fiew releases of maven
plugins, even
when there is JIRA issues with patches avilable or SNAPSHOTS s
nicolas de loof wrote:
Hello,
First be sure I've lot's of respect for maven developpers and the work they
offer to the community.
I'm just curious about WHY there is so fiew releases of maven plugins, even
when there is JIRA issues with patches avilable or SNAPSHOTS solving them.
The hudson pr
Jason - you're aware of this?
- Brett
Begin forwarded message:
From: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
Date: 7 September 2007 4:48:51 AM
To: [EMAIL PROTECTED]
Subject: [continuum] BUILD FAILURE: Maven Project Builder
Reply-To: dev@maven.apache.org
Reply-To: "[EMAIL PROTECTED]"
<[EMAI
Done.
Emmanuel
Emmanuel Venisse a écrit :
I found the problem with the exception, NEXT_VAL in SEQUENCE_TABLE is
wrong, I'll fix it today then I'll readd components/trunk
Emmanuel
Emmanuel Venisse a écrit :
Maven Artifact is already in Continuum :
http://maven.zones.apache.org/continuum/proj
Hello,
First be sure I've lot's of respect for maven developpers and the work they
offer to the community.
I'm just curious about WHY there is so fiew releases of maven plugins, even
when there is JIRA issues with patches avilable or SNAPSHOTS solving them.
The hudson project uses to publish rel
NEXT_VAL values must be checked in SEQUENCE_TABLE before to to restart continuum
Emmanuel
Emmanuel Venisse a écrit :
Without sql command:
1- with data-management: export the db
java -Xmx512m -jar data-management-cli-1.1-beta-2-app.jar -buildsJdbcUrl
jdbc:derby:path_continuum_old_db -mode EXPO
I found the problem with the exception, NEXT_VAL in SEQUENCE_TABLE is wrong,
I'll fix it today then I'll readd components/trunk
Emmanuel
Emmanuel Venisse a écrit :
Maven Artifact is already in Continuum :
http://maven.zones.apache.org/continuum/projectGroupSummary.action?projectGroupId=30
an
I'm currently trying to write a provider for Dimensions. Whit this tool, a
checkout operation will result in multiple commands sent to the scm client
(one per file).
How should I place the result in the CheckOutResult?
I thought to place only the commands & provider messages for the commands
tha
Maven Artifact is already in Continuum :
http://maven.zones.apache.org/continuum/projectGroupSummary.action?projectGroupId=30
and the class you search is in the working copy:
http://maven.zones.apache.org/continuum/workingCopy.action?projectId=442&projectName=Maven+Artifact&userDirectory=src/mai
18 matches
Mail list logo