Just coming back to this - it is working for me now.
(Perhaps this is because the site plugin was downgraded again, since
the docs were broken with the latest release)
On 31/12/2007, at 6:06 AM, Wendy Smoak wrote:
I'm having trouble running 'mvn site' from archiva/trunk. (Also from
the
Hey guys,
Just wanted to help kick off our way to a 1.1 release
Here have been a few things that have been at the back of my mind. I
think this is a list we should pick and choose from:
* Reduce memory consumption
* Preemptive artifact synchronisation
* Eliminate client side blocking when
Hello Jason,
Please revert this change or make it backward comaptible. Removing
getArtifactHandler() from Artifact interface might be conceptually
right, but it breaks lots of thing.
1. a few tests are broken in the maven components.
2. More important is that every plugin have ever made that
Thanks for the tip Brian. You lead be on a path to find the answer,
which was not obvious to me before I dove into the dependency-plugin
code. I couldn't understand why I always got 0 artifacts back from
project.getArtifacts(). Finally I found the answer:
@requiresDependencyResolution
Hi.
In our work projects, we're *constantly* being bitten by the 'first
version of a plugin used wins' problem, which seems variously
described in particular MNG JIRA items, mine in particular being
MNG-3284.
I've had a go at fixing it as it didn't seem that complicated - but -
some of the
On 3-Feb-08, at 3:45 AM, Milos Kleint wrote:
Hello Jason,
Please revert this change or make it backward comaptible. Removing
getArtifactHandler() from Artifact interface might be conceptually
right, but it breaks lots of thing.
Not intentional, I ran everything on this side and the ITs so
I rolled them back for the time being and put them on a branch as I'm
headed out today. I'll put an aspect in, and then add a test for the
artifact handler use in maven-artifact and make an IT like one of the
plugins. I've got a few branches here in GIT, that didn't go in
correctly but I
This is fixed in 2.1, but if you are constantly having this problem, it
sounds like maybe you need to use pluginManagement in a corp pom to
resolve this issue.
-Original Message-
From: Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 03, 2008 8:44 AM
To: dev@maven.apache.org
The problem is that putting it in pluginManagement doesn't help
because the builds genuinely do want to use different versions,
particularly of internally-developed mojos that change in different
(and sometimes incompatible ways).
A typical case is a base library uses a fixed, stable release, but
Hi,
The current trunk of verifier is 1.2-SNAPSHOT, and a 1.1 release was
tagged here: http://svn.apache.org/viewvc?view=revrevision=573467
However, I see no vote for it in Nov and it never made it to the
release repository. Jason? Should we just roll back the tag?
- Brett
You have a log in on the machine so should be able to install it - ore
are you referring to have it included in the Continuum profiles?
- Brett
On 02/02/2008, at 8:01 AM, Arnaud HERITIER wrote:
Nobody ? No idea ?
I would like to be sure that the build is good before to release the
plugin
Hi,
I realize that the fix for MPLUGIN-40 (All plugins should by default
have an auto-generated goal 'help') is definitely *not* intuitive for
the end user.
Background:
I created a plugin-plugin goal which generates an Help mojo. This
generated mojo just displays the goals and their
Hi Brett,
What do you propose for cmd line switch?
Personally, I am fine with mvn my-plugin:help which seems more common.
A lot of tools (all?) have an help option.
Cheers,
Vincent
2008/2/3, Brett Porter [EMAIL PROTECTED]:
Would a different lifecycle or command line switch be more intuitive
Something like
mvn -H idea:idea or mvn -H idea
which is akin to what Subversion has, for example.
this would allow the CLI to translate to the appropriate help:describe
goal and then exit, which is pretty clean, as compared to modifying
the lifecycle executor.
- Brett
On 04/02/2008, at
yep, the second one. I would like to be able to configure the eclipse plugin
to use it when I'll install it.
Arnaud
On Feb 3, 2008 11:43 PM, Brett Porter [EMAIL PROTECTED] wrote:
You have a log in on the machine so should be able to install it - ore
are you referring to have it included in
Would a different lifecycle or command line switch be more intuitive
than this?
On 04/02/2008, at 9:55 AM, Vincent Siveton wrote:
Hi,
I realize that the fix for MPLUGIN-40 (All plugins should by default
have an auto-generated goal 'help') is definitely *not* intuitive for
the end user.
Finally I already did it but I have a question about continuum.
Can I ask to one project to use a different profile of the one defined in
the group ?
It seems to not be possible.
I can add a new build for the eclipse plugin with this profile but it will
continue to be built (and to fail) with
yes it's good, I can administrate profiles.
thanks. I'll do the setup tomorrow
cheers
On Feb 4, 2008 1:28 AM, Brett Porter [EMAIL PROTECTED] wrote:
you should be able to add that now
On 04/02/2008, at 10:29 AM, Arnaud HERITIER wrote:
yep, the second one. I would like to be able to
It's kind of like Maven inheritence, you can't block inheriting things
from the group.
I would be ok with building all the plugins with 2.0.8 as the latest
release...
On 04/02/2008, at 11:47 AM, Arnaud HERITIER wrote:
Finally I already did it but I have a question about continuum.
Can I
you should be able to add that now
On 04/02/2008, at 10:29 AM, Arnaud HERITIER wrote:
yep, the second one. I would like to be able to configure the
eclipse plugin
to use it when I'll install it.
Arnaud
On Feb 3, 2008 11:43 PM, Brett Porter [EMAIL PROTECTED] wrote:
You have a log in on the
Everybody is ok to upgrade the version of maven used to build all our
plugins on maven.zones.apache.org (from 2.0.7 to 2.0.8) ?
Arnaud
On Feb 4, 2008 1:50 AM, Brett Porter [EMAIL PROTECTED] wrote:
It's kind of like Maven inheritence, you can't block inheriting things
from the group.
I would
Hi Everyone,
The Maven Archiva team is pleased to announce the release of Archiva 1.0.1
Archiva is a build artifact repository manager for use with build tools such
as Maven, Continuum and Ant.
It has features like repository search and browse, securing repositories,
identifying unknown
Below are the results of this vote:
+5 Binding Votes (Brett, Fabrice, Arnaud, Wendy and Myself)
+1 Non-binding Vote (Nicolas)
I'll finalize the release and will send an update again.
Thanks,
Deng
On Jan 29, 2008 7:11 PM, Maria Odea Ching [EMAIL PROTECTED] wrote:
Hi Everyone,
The Archiva
I think keeping this out of the core, be that the lifecycle executor
or the CLI would be a far better option.
Vincent, just to be clear you have taken the logic that already exists
in the help plugin?
On 3-Feb-08, at 3:17 PM, Brett Porter wrote:
Something like
mvn -H idea:idea or mvn -H
On 3-Feb-08, at 2:55 PM, Vincent Siveton wrote:
Hi,
I realize that the fix for MPLUGIN-40 (All plugins should by default
have an auto-generated goal 'help') is definitely *not* intuitive for
the end user.
Background:
I created a plugin-plugin goal which generates an Help mojo. This
generated
25 matches
Mail list logo
