Hi all,
I'm new to maven environment. I've maven 2.0.4 in my system. When I try
to build a project from my CVS ROOT it is happening fine. But now I've
branched out my project. After branching out I tried to build a jar from
the new branch. It is not happening, still my CVS ROOT is working fine
It's already listed as a "new feature". Surely if it's that, and
unscheduled, it's out of the defect filters but the work still there
for anyone that picks it up. I did review the original code, but lost
track of the issue that seems to now have updated patches.
I'd like to reconsider how t
On 3 Jun 07, at 7:52 PM 3 Jun 07, Brett Porter wrote:
I disagree. What sacred ritual must I perform to reopen this?
Write something that works or find someone who will. Most of these
issues are just sitting with no one doing anything. At best put it
somewhere like "nice idea, but no one
On 3 Jun 07, at 7:33 PM 3 Jun 07, Brett Porter wrote:
Cool as this is, I think it's in the wrong place. There's no need
to distribute it as it isn't particularly useful to an end-user.
It's great for writing quick integration tests. When it's finished
I'll put it in a better home but it
How about a vote? ;-)
+1 to reopening of MNG-671
- Joakim
Brett Porter wrote:
I disagree. What sacred ritual must I perform to reopen this?
- Brett
On 03/06/2007, at 7:08 AM, Jason van Zyl (JIRA) wrote:
[
http://jira.codehaus.org/browse/MNG-671?page=com.atlassian.jira.plugin.system.i
Ok, I've updated the prerequisites to 2.0.6.
On 04/06/2007, at 12:01 PM, Vincent Siveton wrote:
Hi Brett,
I think the plugin needs plexus-utils inside.
The built was unable to delete some test directories with all versions
of mvn. So I bumped it.
Thanks,
Vincent
2007/6/3, Brett Porter <[EMA
Hi Brett,
I think the plugin needs plexus-utils inside.
The built was unable to delete some test directories with all versions
of mvn. So I bumped it.
Thanks,
Vincent
2007/6/3, Brett Porter <[EMAIL PROTECTED]>:
Is this just required by the test cases? If the plugin itself
requires it, it may
It looks like that hasn't been released, and so couldn't be used as a
dependency. And a separate plugin wouldn't be able to integrate it
into JXR, would it?
If there's some way it can be reused from there, that'd be great.
Probably worth pinging the forrest team to see what they think too.
Done (Sends 9am Friday CST - just doing a test run now)
On 02/06/2007, at 3:07 AM, Henri Yandell wrote:
All done.
Should we point this subscription (and the upload one) to the new
repository list?
Hen
On 5/31/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
go for it, but keep the poms for the
I disagree. What sacred ritual must I perform to reopen this?
- Brett
On 03/06/2007, at 7:08 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-671?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-671.
---
Is this just required by the test cases? If the plugin itself
requires it, it may not get it in all versions of Maven.
On 04/06/2007, at 2:50 AM, [EMAIL PROTECTED] wrote:
Author: vsiveton
Date: Sun Jun 3 09:50:33 2007
New Revision: 543940
URL: http://svn.apache.org/viewvc?view=rev&rev=54394
Cool as this is, I think it's in the wrong place. There's no need to
distribute it as it isn't particularly useful to an end-user.
Maybe src/examples under the embedder so it is included in an
embedder source distribution is a better place?
- Brett
On 03/06/2007, at 2:31 AM, [EMAIL PROTECT
thanks
On 3 Jun 07, at 12:48 PM 3 Jun 07, Vincent Siveton wrote:
Hi Jason,
2007/6/1, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Author: jvanzyl
Date: Fri Jun 1 14:01:57 2007
New Revision: 543615
URL: http://svn.apache.org/viewvc?view=rev&rev=543615
Log:
MNG-2690 Some maven-project tests fail un
Hi Jason,
2007/6/1, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Author: jvanzyl
Date: Fri Jun 1 14:01:57 2007
New Revision: 543615
URL: http://svn.apache.org/viewvc?view=rev&rev=543615
Log:
MNG-2690 Some maven-project tests fail under maven-surefire-plugin 2.3
Submitted by: Mark Hobson
[SNIP]
@
On 3 Jun 07, at 12:11 PM 3 Jun 07, Stephane Nicoll wrote:
Oups. I thought that the prepare goal was using the embedder (at least
it forks another mvn process).
Yes, one of the many custom executors. We'll line them all up.
Stéphane
On 6/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On
Oups. I thought that the prepare goal was using the embedder (at least
it forks another mvn process).
Stéphane
On 6/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 3 Jun 07, at 5:09 AM 3 Jun 07, Stephane Nicoll wrote:
> Someone working on the embedder can have a look to it? A simple mvn
> r
Hi folks,
Some issues in JXR (JXR-10, JXR-13) could be handled by Forrestdoc
[1], part of the the Apache Forrest project.
Which do you think is the better approach:
* close them
* created a new plugin that include forrestdoc librairies. Maybe we
could work with the Forrest's team?
* other idea
On 3 Jun 07, at 7:13 AM 3 Jun 07, Kenney Westerhof wrote:
I agree, this is definitely an issue.
If you specify the same dep (a:a) twice in the same pom,
maven doesn't say anything, but takes the last one.
In the same model it should crap out. It should be detected in IDE
integration but du
On 3 Jun 07, at 5:09 AM 3 Jun 07, Stephane Nicoll wrote:
Someone working on the embedder can have a look to it? A simple mvn
release:prepare will do it.
Why does the embedder have anything to do with this. The release
plugin started using the embedder in the tests?
This release would be
Hi,
Timothy Reilly wrote:
I'm not sure how to tell what happened, or if this is intended behavior /
keywords in plugin parameters?
Within my FoobarMojo I declare:
/**
* @parameter expression="${ws.config.root" default-value="${was.home}/config"
I agree, this is definitely an issue.
If you specify the same dep (a:a) twice in the same pom,
maven doesn't say anything, but takes the last one.
Brett Porter wrote:
Is this still an issue though? Maybe it should be left open for a
simpler fix.
- Brett
On 01/06/2007, at 2:19 PM, Jason van Zy
Someone working on the embedder can have a look to it? A simple mvn
release:prepare will do it.
This release would be handy btw, it has nice features compared to 2.0
Stéphane
On 5/31/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi
I'm preparing to release maven-idea-plugin, but I ran into t
22 matches
Mail list logo