looks about right.
The only thing I'm thinking is that the view output step is not
required for all of the steps - just the mvn builds and SCM operations.
Or perhaps it can just be one large output that is a link at the bottom?
Cheers,
Brett
On 29/08/2006, at 2:07 PM, Edwin Punzalan wrote:
I decided to take some time and tackle some of the very large number of
issues in Jira... however I don't have svn commit access.
Is there any particular place I should send patches... and what format
should the patches be in?
- Brill Pappin
I'm getting a number of JPOX errors while trying to write a regression test.
They are mostly to do with what it claims are bad definitions.
Is anybody else getting this, or have I missed something?
- Brill Pappin
Hi Brill,
That's great to hear!
Some things to be aware of with Continuum:
1) A lot of JIRA stuff may now be redundant as trunk (1.1) is based
on webwork, where 1.0.3 was based on plexus-summit.
2) There is a security overhaul going on as you'll see on this list.
So if you are tackling
Thanks all for your help
On 8/28/06, Brett Porter [EMAIL PROTECTED] wrote:
http://maven.apache.org/guides/development/guide-testing-development-
plugins.html
On 25/08/2006, at 10:47 PM, Alexis Midon wrote:
Hi all,
I'd like to use a snapshot version of the assembly plugin, but I
can't
I've deployed the new white site with your suggestion.
Brett Porter wrote:
looks about right.
The only thing I'm thinking is that the view output step is not
required for all of the steps - just the mvn builds and SCM operations.
Or perhaps it can just be one large output that is a link
On 28 Aug 06, at 4:04 PM 28 Aug 06, Dennis Lundberg wrote:
I'll put together a draft for review.
Dennis,
I made a project wide module and placed the KEYS file in it along
with a script to sync the KEYS to the right place on the server:
http://svn.apache.org/repos/asf/maven/project/
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: mardi 29 août 2006 00:03
To: Maven Developers List
Subject: Re: Failing to build 2.1 snapshot from trunk
trunk does not directly reference 2.3-SNAPSHOT so it would only be
used by a plugin repository reference
Sorry, I did walk away there for a little bit.
On 8/27/06, Brett Porter [EMAIL PROTECTED] wrote:
On 28/08/2006, at 7:14 AM, Wendell Beckwith wrote:
Take toady's latest example, say you want to remove an ant build
file and do
things the maven way, so you decide to use the dependency
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
As fix for MSITE-138, I want to build the maven-site-plugin from trunk.
As I figured out, I also need to update maven-plugin-plugin that also requires
me to update maven itself. As suggested by Vincent, I got the latest integration
build
On 29 Aug 06, at 3:32 PM 29 Aug 06, Vincent Massol wrote:
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: mardi 29 août 2006 00:03
To: Maven Developers List
Subject: Re: Failing to build 2.1 snapshot from trunk
trunk does not directly reference 2.3-SNAPSHOT so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
as I promised some time ago, I wanted to provide my work in creating a maven2
plugin for solaris packaging. I uses an ant mojo and only works on a solaris
machine with pkgtools installed.
For the moment I set in the POM
groupId to
Jason van Zyl wrote:
On 28 Aug 06, at 4:04 PM 28 Aug 06, Dennis Lundberg wrote:
I'll put together a draft for review.
Dennis,
I made a project wide module and placed the KEYS file in it along with a
script to sync the KEYS to the right place on the server:
Hi Jörg,
Based on your comments, here are my succesfull steps to build
maven-site-plugin from scratch:
- dwl and install m2-20060828.203000.tar.gz
- removed my repository
- added snapshot repository (see [1])
- build Maven (see [2])
* svn co
Hi
I think the best way is to create an issue for the sandbox component
http://jira.codehaus.org/browse/MNG
Cheers,
Vincent
2006/8/29, Joerg Hohwiller [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
as I promised some time ago, I wanted to provide my work in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Siveton wrote:
Hi Jörg,
Hi Vincent,
thanks for your quick reply...
Based on your comments, here are my succesfull steps to build
maven-site-plugin from scratch:
- dwl and install m2-20060828.203000.tar.gz
ok
- removed my repository
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all
Apache committers would have access to so that experimentation with
Maven projects can happen easily.
Case in point: Jeremy and
Hi All,
I'm not sure if I'm allowed to vote but I will put my two cents in
anyways. I think this would make things a lot easier on those like me
trying to get involved in Continuum and Maven. I spent 2 hours last night
trying to figure out how IntelliJ screwed up my working copy just so I
I just did a clean co of maven 2 and tried to build the site and some
other components. I found that the site pom, like the others that I
looked at, derives from maven-parent, version 4-SNAPSHOT, with a
relative path specified that points to /poms/maven/pom.xml. The
version in the parent itself
On 30/08/2006, at 5:32 AM, Vincent Massol wrote:
Brett, don't you think it would help adding the snapshot repo to
the top
level pom.xml in trunk?
Which snapshot repo? The apache one is already in the parent POM.
There's something else going on here (bearing in mind that this is
working
The children need to be updated for the release. There is a
repository - but its a chicken and egg problem (need the repo to
specify the repo without doing it in every pom :)
The parent should only be set to a snapshot when something is really
needed from the new version, so setting it to
Ugh. I was -1 on the commit that caused this and it hasn't yet been
fixed. I'll be rolling it back later today. IT should build with
Maven 2.0.4 and no changes to the plugin plugin. I can't see that it
needs the latter, but it certainly requires Maven 2.1 which is not good.
- Brett
On
+1 Nice idea.
Regards,
Alan
Jason van Zyl wrote:
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all
Apache committers would have access to so that experimentation with
Maven projects
Good day,
About a couple of months ago, the documentation site of the maven 2
plugins have been revised [1]. Though most have already been reviewed,
they are still not yet out for release.
However, now that the documentation issue have been raised again, I am
wondering of how we are going to go
Hi All,
I've noticed that in
org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler, the
method below:
private void assembleDependencyInheritance( Model child, Model parent )
{
Map depsMap = new HashMap();
List deps = parent.getDependencies();
if (
25 matches
Mail list logo
