I have no idea how to apply PLXUTILS-25 to try it :-(
--jason
On Apr 22, 2007, at 10:33 PM, Jerome Lacoste wrote:
On 4/23/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Anyone have any idea why this is happening?
not sure but I have posted a potential idea for a fix in PLXUTILS-25.
Could you
On 4/23/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Anyone have any idea why this is happening?
not sure but I have posted a potential idea for a fix in PLXUTILS-25.
Could you try it ?
J
-
To unsubscribe, e-mail: [EMAIL PROTE
On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
So if I say BETA then no alpha bundle (a bundle
containing alpha software) will be selected.
Who exactly decides what the quality is for a given release? Outside
of a handful (literally) of major apps/projects (Linux kernel and
Apach
Jason,
Out of curiosity, how does the "create a new pom" thing work?
I'm mostly just curious in regards to the gpg signing. I want to make
sure the pom that is deployed matches what is signed.
Dan
On Sunday 22 April 2007 20:36, Jason van Zyl wrote:
> Hi,
>
> In the shade plugin I've add
On 4/23/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> What's the best way to sort out communication amongst interested
> parties?
>
Asking here, but if you're not going to have time to actually develop
then it's really a matter of waiting until we start working on it again.
> My first problem
Anyone have any idea why this is happening?
--jason
On 4/20/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Hi folks, I keep seeing an evil IllegalStateException (randomly) when
mvn exists.
[INFO]
[INFO] BUILD SUCCESSFUL
[I
Sure. I started to fix them before but got through 4-5 before I got
sidetracked. I think I need to tweak the analyze plugin to output the
xml you should use so it's easy to copy and paste into the pom. Then
it's a piece of cake to update the poms.
-Original Message-
From: Jason van Zyl [ma
Hi,
In the shade plugin I've added the capability to create a POM that
reflects what has been shaded. To correct the problem with the two
plexus JARs, I shaded one into the other so I have the single plexus-
default-container artifact again. So the idea being during
development modules are
I'm also highly interested in this and can help out. I found when
writing the dependency plugin that I needed to write a lot of mock
objects. The nice thing about Maven is that almost everything is an
interface, which makes it fairly trivial to implement anything you need
to fully exercise your cod
On 22 Apr 07, at 7:30 PM 22 Apr 07, Barrie Treloar wrote:
On 4/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I was going to take a stab at writing the definitive "how to write
plugin integration tests" document when I did it for surefire (after
I get back from holidays still another week
On 4/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I was going to take a stab at writing the definitive "how to write
plugin integration tests" document when I did it for surefire (after
I get back from holidays still another week + conferences to go
yet :) I'm not going to complain if someo
On 22 Apr 07, at 5:23 PM 22 Apr 07, gilclark wrote:
There is some work being done to the shade plugin so that might be
it. I
froze the version of that plugin to 1.0-alpha-4 which helped me.
The shade plugin wouldn't have anything to do with the assembly
plugin build. It's not used the
There is some work being done to the shade plugin so that might be it. I
froze the version of that plugin to 1.0-alpha-4 which helped me.
Jose Alberto Fernandez wrote:
>
> Hi guys, I posted this on the user list but got no answers. It is an
> urgent matter as it is affecting some of our develo
Hey Brian,
Do you think you could publish a list of all the Maven projects/
plugins that need to be fixed insofar as needing to state a direct
dependency on plexus-utils?
I'm just going back to 2.1 and I'm using a shaded JAR which hides p-u
so I need to hunt everything down and release eve
On 22 Apr 07, at 3:26 PM 22 Apr 07, Wendy Smoak wrote:
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 8:05 PM 1 Apr 07, Brett Porter wrote:
> What was the final verdict on the velocity processing?
>
Optional.
It seems to be on by default, and it's breaking the plugin
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 8:05 PM 1 Apr 07, Brett Porter wrote:
> What was the final verdict on the velocity processing?
>
Optional.
It seems to be on by default, and it's breaking the plugin docs when I
publish them with maven-site-plugin 2.0-SNAPSH
On 4/21/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Now that, theoretically, the plugins are all documented up to their
current release and improvements in docs can wait until the next
release, this sounds fine to me.
Thanks. (I want the snapshot docs published as well, just not linked
promin
+1
Generated docs look good.
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 20, 2007 5:49 PM
> To: Maven Developers List
> Subject: [vote] maven-model 3.0.2 for maven 1.1
>
> Hi team,
>
> We finalized the new version of maven-model 3.0.2 f
Do people use the SSH deployment frequently? The documentation says
SSH deployment is supported but the 2.0.4-based tasks don't contain
any of the requirements for that.
Jason, you were talking to the Tomcat folks and I assume they will
need the SSH goodies to deploy so I can put the requir
Hi,
I just copied the staged repo for the clover plugin over and I used
the following:
mvn stage:copy -Dsource="http://people.apache.org/~vmassol/maven-
staging" -Dtarget="scp://people.apache.org/www/people.apache.org/repo/
m2-ibiblio-rsync-repository" -Dversion=2.4
Just for the folks who
On 22 Apr 07, at 3:58 AM 22 Apr 07, Hervé BOUTEMY wrote:
Le dimanche 22 avril 2007 08:42, Hervé BOUTEMY a écrit :
I'll work on documentation enhancement, to reflect new features on
http://maven.apache.org/ant-tasks.html
work done: a patch has been added to MANTTASKS-64
as written in the comm
On 21 Apr 07, at 4:57 PM 21 Apr 07, Brett Porter wrote:
Hi,
I thought to gather up that massive thread I've just read, I could
throw out a quick proposal that might summarise it and serve as a
discussion point.
Things we know:
- the current situation is problematic
- we can't require ver
Hi,
I thought to gather up that massive thread I've just read, I could
throw out a quick proposal that might summarise it and serve as a
discussion point.
Things we know:
- the current situation is problematic
- we can't require versions for everything (particularly, the implied
plugins f
Now that, theoretically, the plugins are all documented up to their
current release and improvements in docs can wait until the next
release, this sounds fine to me.
However, I'm not sure how this helps the current situation, since
assembly 2.2-beta-1 is a release. It should document the pl
This is what the release poms feature was meant to do - take a
snapshot of what was actually resolved and use that for the release
(and in the future).
The difficulty with it came in that what gets deployed is not what
you want then (as it was also resolving the dependencies, etc). But
th
I was going to take a stab at writing the definitive "how to write
plugin integration tests" document when I did it for surefire (after
I get back from holidays still another week + conferences to go
yet :) I'm not going to complain if someone starts it first :)
Between yourself, Brian,
On 12/04/2007, at 8:49 PM, Wayne Fay wrote:
I'd also suggest that it might be helpful for someone to track the
fundamental reason(s) behind emails to the Users list for a period of
time (1-2 weeks) and then pick the top recurring reasons, and add them
to the FAQ. It would be nice if there was a
On 12/04/2007, at 4:15 PM, John Casey wrote:
1. Locking down on release is dangerous IMO, because it implies
that you
might be making a change to the build behavior at release time.
I don't think that was the intent. It was intended to capture exactly
what you used at release time. The pr
Le dimanche 22 avril 2007 08:42, Hervé BOUTEMY a écrit :
> I'll work on documentation enhancement, to reflect new features on
> http://maven.apache.org/ant-tasks.html
work done: a patch has been added to MANTTASKS-64
as written in the comment: "My (fr)english is not so good, you'll probably
need
29 matches
Mail list logo
