Brian E. Fox a écrit :
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven
On 4/2/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> I'm getting errors and stack traces from Velocity. Is there a way to
> tell it not to filter certain files? The files it's complaining about
> are release-notes.apt, guide-bash-m2-completion.apt.
The second can be ignored. I don't know abou
On 4/3/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Ok, a little more refactoring. The Custom rules can now get to the
ExpressionEvaluator so they can get pretty much anything a plugin could
get. The sites are updated to contain info about the standard rules and
the custom rule creation:
http://ma
Oh, ya... it works, I got distracted by my rant. Latest snapshot
looks okay to me.
--jason
On Apr 2, 2007, at 8:59 PM, Brian E. Fox wrote:
Looks like enforcer worked :-)
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Monday, April 0
Looks like enforcer worked :-)
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Monday, April 02, 2007 11:49 PM
To: Maven Developers List
Subject: OMG... mvn -X spits out soo much junk
I think its time for a --debug and --trace option to
I think its time for a --debug and --trace option to mvn... as mvn -X
by itself spits out sooo much output that it is almost unusable.
Certainly to get more information out of plugins that are executing
its provides *way, way* to much information.
For example, running `mvn -X -N` from the
+1
On 4/3/07, John Casey <[EMAIL PROTECTED]> wrote:
+1
On 4/2/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
>
> +1
>
> --jason
>
>
> On Apr 1, 2007, at 10:36 AM, Jason van Zyl wrote:
>
> > Hi,
> >
> > The staging repository is here:
> >
> > http://people.apache.org/~jvanzyl/staging-repository/mav
+1 Move to Maven pom
Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xm
I'm in favour of 'moving' it up. I think you'll still need this
site.xml though it'll be mostly empty (maybe add breadcrumbs?). The
TODO's already in there tell that story.
We'll also need to do a maven pom release after that change.
- Brett
On 03/04/2007, at 12:45 PM, Jason van Zyl wrote:
Rahul was having this problem with the achetypeNG with groupId, even
though the original archetype didn't have this problem. I seem to recall
he figured it out, but not the solution.
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Monday, Apr
On 2 Apr 07, at 10:39 PM 2 Apr 07, Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin
project.
Other things like shared get a homely looking default skin. I see two
options here:
1.
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven pom. This is preferred so t
Ok, a little more refactoring. The Custom rules can now get to the
ExpressionEvaluator so they can get pretty much anything a plugin could
get. The sites are updated to contain info about the standard rules and
the custom rule creation:
http://maven.apache.org/plugins/maven-enforcer-plugin/
http://
On 03/04/2007, at 12:17 PM, Wendy Smoak wrote:
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Requires trunk of the site plugin.
Okay. I deployed another snapshot of the site plugin, it was only a
couple of days old but before that, 'mvn site -U' didn't seem to work.
Hmm, I deployed
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Requires trunk of the site plugin.
Okay. I deployed another snapshot of the site plugin, it was only a
couple of days old but before that, 'mvn site -U' didn't seem to work.
I'm getting errors and stack traces from Velocity. Is there a way
That sounds like a great idea...and one less place to visit.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 3:23 PM
To: Maven Developers List
Subject: RE: Creating a schedule for releases
I know the calendar is already out there so this mig
On 2 Apr 07, at 8:37 PM 2 Apr 07, Brett Porter wrote:
On 02/04/2007, at 11:12 PM, Jason van Zyl 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.
Is this documented on the plugin site somewhere? I wasn't able
On 2 Apr 07, at 8:22 PM 2 Apr 07, Carlos Sanchez wrote:
I haven't found a direct way to retrieve the ArtifactMetadataSource
instance to retrieve the list of available versions in the repository,
I have to explicitly look it up in the plexus container.
Did I miss something? if not it would be u
On 02/04/2007, at 11:12 PM, Jason van Zyl 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.
Is this documented on the plugin site somewhere? I wasn't able to
find it.
I can see this doesn't break a lot now
I haven't found a direct way to retrieve the ArtifactMetadataSource
instance to retrieve the list of available versions in the repository,
I have to explicitly look it up in the plexus container.
Did I miss something? if not it would be useful to expose the
ArtifactMetadataSource or add a getAvai
It was working for me for a while... then it stopped. I don't know
why at all. This is install:install-file, not install:install, so
you are expected to configure the artifactId. Its not marked as read-
only. But I've not idea why it just started complaining to me about
it...
:-(
--ja
I thought that had always been the case and was a known issue in the
install plugin.
On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
I all of a sudden started to see this today:
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
On 2 Apr 07, at 5:57 PM 2 Apr 07, Wendy Smoak wrote:
I published the site to update the release notes, and someone on irc
pointed out that the download links are broken:
http://maven.apache.org/download.html
Any ideas? I just did 'mvn site' and 'mvn site:deploy'.
Requires trunk of the s
I published the site to update the release notes, and someone on irc
pointed out that the download links are broken:
http://maven.apache.org/download.html
Any ideas? I just did 'mvn site' and 'mvn site:deploy'.
--
Wendy
-
T
+1
On 4/2/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
+1
--jason
On Apr 1, 2007, at 10:36 AM, Jason van Zyl wrote:
> Hi,
>
> The staging repository is here:
>
> http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
> tasks-2.0.6/
>
> The uber jar that people will want to try is he
I all of a sudden started to see this today:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error configuring: org.apache.maven.plugins:maven-install-
I know the calendar is already out there so this might be late info (I
didn't think of it before), but I thought I'd point out that Jira has
the ability to set release dates and there is a calendar portlet you can
add to show them. It's probably less functionality than the google one,
but it could
+1
--jason
On Apr 1, 2007, at 10:36 AM, Jason van Zyl wrote:
Hi,
The staging repository is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.0.6/
The uber jar that people will want to try is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant
+1
Andy
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
The staging repository is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.0.6/
The uber jar that people will want to try is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
t
+1
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
The staging repository is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.0.6/
The uber jar that people will want to try is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.
On 2 Apr 07, at 2:03 PM 2 Apr 07, Emmanuel Venisse wrote:
Joakim Erdfelt a écrit :
Jason van Zyl wrote:
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
Should this include the
Joakim Erdfelt a écrit :
Jason van Zyl wrote:
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
Should this include the full change log like previous releases?
I added a pointer to
Carlos, this seems to be the same issue with surefire forking and you
previously mentioned that it was because the wrong version of surefire
was being used. Which version should be used with 2.0.6?
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 01, 2
Jason van Zyl wrote:
>
> On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
>
>> On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>> On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
>>> > Should this include the full change log like previous releases?
>>>
>>> I added a pointer to the roa
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
So when they reference bad information in the site you're going to go
back and edit it to make it correct again?
Huh? I want the release notes to be static. Not to change if
something changes in JIRA, and not to disappear (404) if JIRA gets
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
> Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don't think we need to entirely
On 2 Apr 07, at 12:43 PM 2 Apr 07, Carlos Sanchez wrote:
that would be the same case as snapshots, and they are there too
No, they aren't. People are not expected to build against the staging
repositories. They do that with the snapshot repository, snapshots
are still generally consumabl
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
> Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don't think we need to entirely
replicate the list produced by JIRA. But users should be
that's a problem with the surefire version you are using, i updated the jira
On 4/2/07, Cabasson Denis <[EMAIL PROTECTED]> wrote:
Well, I have a got a weird case in MNG-2920.
Can't figure out where it is coming from, but a simple test project is working
fine with 2.0.5 while I'm getting a excep
that would be the same case as snapshots, and they are there too
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 8:43 PM 1 Apr 07, Carlos Sanchez wrote:
> It'd be better somewhere under http://people.apache.org/repo/
>
Why? The intention is for the developers and intereste
Looks like we'll need an new maven-ical-report for the site generation.
To inject the schedule into the site, with links to the live-schedule.
- Joakim
Jason van Zyl wrote:
>
> On 2 Apr 07, at 9:44 AM 2 Apr 07, Brian E. Fox wrote:
>
>> +1. More info helps the users to plan and gives the devs som
+1 Spiffy idea!
- Joakim
Jason van Zyl wrote:
> Hi,
>
> Taking the lead from the Mylar development team, whom I have a great
> deal of respect for, I would like to create a shared Google calendar
> where we can put some releases on schedules. I know at least for Maven
> itself, Doxia, Wagon and s
Jörg Schaible wrote:
> Another regression problem: XDoclet plugin is completly broken. The
> plugin itself was problematic anyway, since it depends on the
> o.a.m.p:maven-anrun-plugin:1.0 (as jar dependency!!!) that prevented the
> version 1.1 from antrun-plugin to work properly already with earlie
On 2 Apr 07, at 12:00 PM 2 Apr 07, Joakim Erdfelt wrote:
Looks like we'll need an new maven-ical-report for the site
generation.
To inject the schedule into the site, with links to the live-schedule.
I think just pointing to the calendar will suffice. I think a lot of
people will just e
After trying to schedule some stuff I noticed without different
calendars the colour of everything is the same so I created separate
calendars for the sub-projects and another for plugins so that folks
can visually distinguish the releases.
Jason.
On 2 Apr 07, at 10:32 AM 2 Apr 07, Emmanue
Another regression problem: XDoclet plugin is completly broken. The plugin
itself was problematic anyway, since it depends on the
o.a.m.p:maven-anrun-plugin:1.0 (as jar dependency!!!) that prevented the
version 1.1 from antrun-plugin to work properly already with earlier Maven
versions (MOJO-64
+1
Emmanuel
Jason van Zyl a écrit :
Hi,
Taking the lead from the Mylar development team, whom I have a great
deal of respect for, I would like to create a shared Google calendar
where we can put some releases on schedules. I know at least for Maven
itself, Doxia, Wagon and some plugins I'm
Well, I have a got a weird case in MNG-2920.
Can't figure out where it is coming from, but a simple test project is working
fine with 2.0.5 while I'm getting a exception with 2.0.6.
The forking command line for surefire booter seems to have changed between the
2 versions and the newer command li
On 02/04/2007, at 11:55 PM, Jason van Zyl wrote:
There is no reason why we shouldn't be able to do this.
Totally agree. And drawing this information into a known, persistent,
and up-to-date location can only help get more people involved. The
most successful releases will come when 3, 4 o
On 2 Apr 07, at 9:44 AM 2 Apr 07, Brian E. Fox wrote:
+1. More info helps the users to plan and gives the devs something to
work towards. I'd like to see some tentative plans for 2.1 also.
2.1-alpha-1 will go on the schedule, the issues are registered for it
and John and I would like to cu
On 2 Apr 07, at 9:44 AM 2 Apr 07, Brett Porter wrote:
+1, I had a draft mail saying roughly the same thing.
We will probably still need to be occasionally flexible depending
on availability of people, too, but as we start whipping out non-
alpha releases of some of the underlying stuff and
+1. More info helps the users to plan and gives the devs something to
work towards. I'd like to see some tentative plans for 2.1 also.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 9:38 AM
To: Maven Developers List
Subject: Creating a schedu
+1, I had a draft mail saying roughly the same thing.
We will probably still need to be occasionally flexible depending on
availability of people, too, but as we start whipping out non-alpha
releases of some of the underlying stuff and increasing the general
amount of testing, it'll be much
Hi,
Taking the lead from the Mylar development team, whom I have a great
deal of respect for, I would like to create a shared Google calendar
where we can put some releases on schedules. I know at least for
Maven itself, Doxia, Wagon and some plugins I'm working on I have a
clear idea of
On 02/04/2007, at 11:04 PM, Jason van Zyl wrote:
On 1 Apr 07, at 7:35 PM 1 Apr 07, Brett Porter wrote:
I couldn't build a correct site out of the box with these changes,
due to:
- using the site plugin latest release (which is the default), I
get ${currentVersion} and other stuff showin
On 2 Apr 07, at 8:46 AM 2 Apr 07, Jörg Schaible wrote:
A dependencyManagement section overwrites the scope of the
currently built artifact (MNG-2919) ... :-/
Assigned to 2.0.7, but it's biting you to work around the transitive
compile scope effect. I'll make an IT with your sample or y
On 1 Apr 07, at 8:43 PM 1 Apr 07, Carlos Sanchez wrote:
It'd be better somewhere under http://people.apache.org/repo/
Why? The intention is for the developers and interested parties and
not attract average users. I don't think putting it with our regular
repositories would be good.
Jas
On 1 Apr 07, at 7:08 PM 1 Apr 07, Brett Porter wrote:
Sounds good to me.
Does the stage-plugin delete the staging repo after successfully
copying it?
No, I'm hesitant to erase it without having another stage of
verifying the contents on the other side so I left it for now.
Jason.
-
On 1 Apr 07, at 8:05 PM 1 Apr 07, Brett Porter wrote:
What was the final verdict on the velocity processing?
Optional.
I can see this doesn't break a lot now because it's only
properties, but I know the next thing someone is going to ask for
is to filter ${project.*} which will break a
On 1 Apr 07, at 7:35 PM 1 Apr 07, Brett Porter wrote:
I couldn't build a correct site out of the box with these changes,
due to:
- using the site plugin latest release (which is the default), I
get ${currentVersion} and other stuff showing up as text
- I tried to build the site plugin snap
A dependencyManagement section overwrites the scope of the currently built
artifact (MNG-2919) ... :-/
Heads-up: 2.0.6 is listed in JIRA still as unreleased ... ;-)
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
> The Apache Maven team would like to announce the availability of
> Maven
ok we keep in touch for the next week.
i'm also working on database support for my dashboard plugin and i'm very
interested by this
Garvin LeClaire-2 wrote:
>
> I know the qalab plugin does this. I was thinking of creating a reporter
> that would put information into a database to report hi
I know the qalab plugin does this. I was thinking of creating a reporter
that would put information into a database to report history.
I am travelling this week and have limited time to work on anything. If
you would like to follow up next week we could discuss this further.
I think a Doxia ex
How can i create a simple parser of the xml result file which can use the
findbugs API or it's already exist ?
For the dashboard plugin, i must read this xml result file to aggregate some
generic indicators or try to compute statistics on it as bugs distribution
by type etc ...
Thanks for your
Try the 1.1-SNAPSHOT as I know it works. I cannot remember if I fixed this
for 1.0.0.
I did not use Findbugs xml because of the way the original Maven 2 plugin
was started. It was easier to write one and I have more options for adding
more wirter the way it is currently written. I was the one
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we can
any news ?
one question, why the ifndbugs-maven-plugin generate its own xml instead of
let findbugs do the job ?
Garvin LeClaire-2 wrote:
>
> Which version of the Findbugs plugin are you using?
> Are you able to send me the findbugs.xml file?
>
>
>
>
> --
> Regards,
>
>
> Garvin LeClaire
Congrats and thanks to all the people working on it! Especially MGN-1577 ...
- Jörg
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
> The Apache Maven team would like to announce the availability of
> Maven 2.0.6. We have closed out 22 issues for this release and the
> upgrade from 2.0.5
68 matches
Mail list logo
