That's the defined behaviour.
On 07/11/2006, at 5:27 PM, Hilco Wijbenga wrote:
Hi all,
I have a question about VersionRange in maven-artifact.
Calling createFromVersionSpec with a spec of '1.0' returns a
VersionRange with a recommendedVersion of '1.0' and a restriction list
consisting of Rest
On 07/11/2006, at 4:50 PM, Franz Allan Valencia See wrote:
So the priority now for the maven plugins docs is to mark them up with
@since tags? If im not mistaken, most (if not all) of those docs do
not have the since tags.
It should only be necessary as new features are added.
And if we're
Hi all,
I have a question about VersionRange in maven-artifact.
Calling createFromVersionSpec with a spec of '1.0' returns a
VersionRange with a recommendedVersion of '1.0' and a restriction list
consisting of Restriction.EVERYTHING. As a consequence calling
containsVersion always returns true.
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
On 07/11/2006, at 3:33 PM, Wendy Smoak wrote:
> On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
>
>> I don't think the new plugin docus can be published yet until the
>> plugins themselves are released. Those docus were based o
On 11/6/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Does anyone see a drawback to doing this for maven itself? I'd volunteer
to help make the changes but I don't think I have karma to touch maven
core where the pom seems to live.
The drawback is that it's another jar that has to be released, w
On http://maven.apache.org/wagon/, many of the menu links are broken.
They're relative to /wagon rather than one level up where they belong.
Brett, is this related to your recent navigation inheritance changes?
When I build the site from wagon/wagon-site, I only get the generated
'Project Inform
I just discovered the hard way (on a plane) that maven plugin sites
can't be built offline at all because of the hard reference to the
config file:
maven-checkstyle-plugin
http://svn.apache.org/repos/asf/maven/plugins/trunk/ma
ven-checkstyle-plugin/src/main/resources/con
On 07/11/2006, at 3:33 PM, Wendy Smoak wrote:
On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
I don't think the new plugin docus can be published yet until the
plugins themselves are released. Those docus were based on the
snapshot versions and some information they contain ma
That was something I was intending to do when I first rewrote the m1
documentation, but hit some stumbling blocks and forgot to take it
out of the 404.
- Brett
On 07/11/2006, at 3:13 PM, Wendy Smoak wrote:
The custom 404 page for the Maven site says, "There is no need to
report this broken
On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
I don't think the new plugin docus can be published yet until the
plugins themselves are released. Those docus were based on the
snapshot versions and some information they contain may not be
applicable to the currently released ver
On 11/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Please, let's all help to keep this list up to date, until all plugin
> sites have been published.
Brett posted earlier that he fixed the navigation inheritance problem.
Is there anythin
The custom 404 page for the Maven site says, "There is no need to
report this broken link to the Maven team, as errors are periodically
monitored and repaired."
Is that really true? If so, how does it happen, and who is doing it?
--
Wendy
---
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Please, let's all help to keep this list up to date, until all plugin
sites have been published.
Brett posted earlier that he fixed the navigation inheritance problem.
Is there anything else preventing us from publishing all of the
plugin
Hi,
Maybe you could do a little survey about where the different pieces
of code exist. This is the same sad situation with the invokers and
verifiers where we have 5 and 3 different bits of code respectively.
Let's collect the resource processing code into one place and create
a component
Hi,
I wasn't thinking when I changed the inheritence on the plugin sites,
as it is designed to adjust the path when you inherit according to
the URLs in the POM (which enables you inheriting navigation to a
particular document, not templating the specification of a particular
document whi
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Dennis Lundberg wrote:
> Wendy Smoak wrote:
>> Are all the plugin websites up to date with svn, or is the policy
>> still to only publish them when a release is done?
>>
>> Thanks,
>
> The published plugin sites are unfortunately not in sync
It's working now, thanks.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 5:37 PM
To: Maven Developers List
Subject: Re: parent 4-snapshot
I thought the plugin tools had been deployed. I've done that now -
should be fine.
- Brett
On 07/1
I've gone ahead and create a JIRA item to track it:
http://jira.codehaus.org/browse/MPMD-50
Patch attached.
I've preliminarily put it in the 2.2 Fix version, but I'll leave it up to
the maven folks to determine if it should stay there.
Dan
On Monday November 06 2006 5:19 pm, Mike Perham wrote
I thought the plugin tools had been deployed. I've done that now -
should be fine.
- Brett
On 07/11/2006, at 8:14 AM, Brian E. Fox wrote:
That seems to have fixed the prereq, but now when I gen the site
(maven-dependency-plugin), I get an exception. I ran again with -U to
double check I have
Slow and deterministic always wins over (slightly) faster and
non-deterministic IMO. A sort is negligible compared the acrobatics
PMD performs so I say go ahead and add it.
On 11/6/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
Personally, I prefer the sort. I hate reports and such that would be
Dennis Lundberg wrote:
Wendy Smoak wrote:
Are all the plugin websites up to date with svn, or is the policy
still to only publish them when a release is done?
Thanks,
The published plugin sites are unfortunately not in sync with what is in
svn. The published docs should reflect the current r
> 2) I'm getting a test failure on my machine. I'll look into it a bit
> more this afternoon if I get some time. Stack trace:
I tracked this down
It's a test that relies on a particular behavior that doesn't seem to be
valid 100% of the time.
On line 89 of:
src/main/java/org/apache/
That seems to have fixed the prereq, but now when I gen the site
(maven-dependency-plugin), I get an exception. I ran again with -U to
double check I have the latest snapshots of everything.
[INFO]
[ERROR] FATAL ERROR
[INFO]
I setup a new archetype project in
maven/archetype/maven-archetype-bundles/maven-archetype-catdog . At
maven-archetype-catdog/src/main/resources/archetype-resources/ ...I have
service , data, and web . CatDog is a web project. When I run mvn install
on the archetype generation I get an error wh
I'm deploying a snapshot of the plugin plugin now which hopefully
resolves that.
On 07/11/2006, at 6:50 AM, Brian E. Fox wrote:
Brett, the 4-SNAPSHOT version still seems to want Maven 2.0.5.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, October 27, 200
Well, its up for discussion. I don't like the idea of having separate
docs per release, since some aspects of docs are updated independent
of version. So, we added the @since flag to mojos and parameters so
that you have an accurate reference for all versions. WRT the docs on
the site, it's
Brett, the 4-SNAPSHOT version still seems to want Maven 2.0.5.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, October 27, 2006 6:51 PM
To: Maven Developers List
Subject: Re: parent 4-snapshot
On 26/10/2006, at 7:02 PM, Brian E. Fox wrote:
> All the plugi
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
They are currently at releases. We are now in a position (with
@since), to publish all the time, and I've lined them all up, but it
is currently blocked by a bug in the navigation link generation.
So is the plan to keep all the plugin sites up
I like the suggestion to have a discussion thread before a formal vote.
It gives time for people to voice concerns about a given release before
it becomes stable. (good or bad). It seems like a vote should also be
based on a tag and snapshot so it's more obvious what is actually being
voted on (eff
They are currently at releases. We are now in a position (with
@since), to publish all the time, and I've lined them all up, but it
is currently blocked by a bug in the navigation link generation.
On 07/11/2006, at 6:00 AM, Wendy Smoak wrote:
Are all the plugin websites up to date with svn,
On 07/11/2006, at 5:59 AM, Jason van Zyl wrote:
How so?
I'm not sure what you are referring to. But changing the build to
include license files means we need to check that it's all good
before we can vote on it. And tests not passing is likewise a blocker.
- Brett
-
Is it possible to use versioning on the site? So you can select the
site/documentation for a specific
version of the plugin?
For instance: http://ws.apache.org/jaxme/, on the left there's Documentation
per version.
Something like that would be nice for the plugins.
-- Kenney
Dennis Lundberg w
Wendy Smoak wrote:
Are all the plugin websites up to date with svn, or is the policy
still to only publish them when a release is done?
Thanks,
The published plugin sites are unfortunately not in sync with what is in
svn. The published docs should reflect the current release of the
plugin. T
Are all the plugin websites up to date with svn, or is the policy
still to only publish them when a release is done?
Thanks,
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 6 Nov 06, at 10:33 PM 6 Nov 06, Brett Porter wrote:
We need to have better voting procedures, because it's hard to see
what the official count is amongst the discussion. It seems the
thread where Jason said these were under way was not explicit
enough, so my suggestion is:
1) we stop
Awhile back, I sent out an email asking for use cases where backward
compatibility was broken from 2.1. This is obviously one of those...can we
log a jira for this, so we can incorporate a test case or three to keep it
from happening again?
I've found several issues with backward compatibility si
On 11/5/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
I would like to call a vote for Releasing the Checkstyle Plugin.
As of November 1, source files must have the new header which does not
include the copyright date.
http://www.apache.org/legal/src-headers.html
I checked [1] and the old h
Joakim Erdfelt wrote:
Hi,
It has been 5 months since the last release of the maven-checkstyle-plugin,
Since then, there have been numerous fixes to correct various site
generation failures, updated maven ruleset, some cleanup of the report
layout, header refactoring, revised documentation, align
We need to have better voting procedures, because it's hard to see
what the official count is amongst the discussion. It seems the
thread where Jason said these were under way was not explicit enough,
so my suggestion is:
1) we stop the PMD vote thread now. Daniel's two issues are indeed
On 07/11/2006, at 3:07 AM, Kenney Westerhof wrote:
I don't think rollback is the way to go, but since we're almost
releasing 2.0.5 I'd like
to suggest that we merge the reporting api changes to the 2.0.x
branch.
That might be the best path forward, though I'm generally reluctant
to make
src/site/odt?
One day, we'll be able to convert it automatically and can remove the
target (though currently that requires having Oo2 installed, and
firing it up during the build, so I wouldn't inflict that on us just
yet :)
- Brett
On 06/11/2006, at 11:32 PM, Vincent Siveton wrote:
Hi
Hi,
I just noticed this in the maven-site-plugin pom:
2.1-SNAPSHOT
Here's the log for that revision:
r430446 | kenney | 2006-08-10 19:20:32 +0200 (Thu, 10 Aug 2006) | 11 lines
PR: 2410
Add support for multipl
-1 (non-binding)
Does not have the Apache required notice/license files in the jar.
Dan
On Sunday November 05 2006 10:05 pm, Joakim Erdfelt wrote:
> Hi,
>
> It has been 5 months since the last release of the
> maven-checkstyle-plugin, Since then, there have been numerous fixes to
> correct v
-1 (non-binding) for a different set of reasons:
1) The generated Jar does NOT have the required LICENSE and NOTICE files
in it. That is now (as of Nov 1) a REQUIREMENT of all Apache releases.
I believe this would be considered a show stopper by the board.
2) I'm getting a test failure o
+1
On 11/6/06, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:
+1 !
:o)
Fabrice.
On 11/6/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> It has been 5 months since the last release of the
> maven-checkstyle-plugin,
> Since then, there have been numerous fixes to correct various site
>
+1
On 11/6/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
+1
Emmanuel
Joakim Erdfelt a écrit :
> Hi,
>
> It has been 3 months since the last release of the maven-pmd-plugin,
> Since then, there has been a refactoring of the excludes logic to bring
> harmony to the pmd and cpd reports, been nu
I am running 2.2-SNAPSHOT and will try the HEAD later today.
Cheers,
Stéphane
On 11/6/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
I had the same issue (the second one you mentioned), and I think I fixed it in
revision 466968.
Are you running with HEAD? (2.2 is still at SNAPSHOT).
Let's
I had the same issue (the second one you mentioned), and I think I fixed it in
revision 466968.
Are you running with HEAD? (2.2 is still at SNAPSHOT).
Let's try to find where it broke: can you svn up -r466968 the assembly plugin
and check if that version works?
If so, it must have been broken
Hi brett,
I will change the documentation.
Thanks!
Vincent
2006/11/5, Brett Porter <[EMAIL PROTECTED]>:
This seems less accurate than before. It updates snapshot
dependencies and plugins, and release metadata for both.
It'd be more accurate to say "Forces a check for updated releases and
sna
Hi Brett,
Maybe but I dont know where. Any clues?
However, I think it is not an important requirement: the odt has 16k
size and the pdf 127k. Thoughts?
Cheers,
Vincent
2006/11/5, Brett Porter <[EMAIL PROTECTED]>:
Should we put the odt somewhere that doesn't need to be deployed
every time?
-
Hi,
I don't know if this is made on purpose but I'm really having a hard
time configuring my assembly descriptor with the latest snapshot
version of the assembly plugin (2.2).
The way dependencies are handled has really changed and I am stuck on
a simple use case.
Project A is a simple resource
Thank you. It works.:)
On 11/4/06, Dan Tran <[EMAIL PROTECTED]> wrote:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4/README.txt
may help ;-)
On 11/3/06, Leo Li <[EMAIL PROTECTED]> wrote:
>
> Hi, all
> I encountered a problem when building maven 2.0.4.
> After che
+1 !
:o)
Fabrice.
On 11/6/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
Hi,
It has been 5 months since the last release of the
maven-checkstyle-plugin,
Since then, there have been numerous fixes to correct various site
generation failures, updated maven ruleset, some cleanup of the report
lay
+1
^_^
Joakim Erdfelt wrote:
Hi,
It has been 5 months since the last release of the maven-checkstyle-plugin,
Since then, there have been numerous fixes to correct various site
generation failures, updated maven ruleset, some cleanup of the report
layout, header refactoring, revised documentat
+1
Emmanuel
Joakim Erdfelt a écrit :
Hi,
It has been 3 months since the last release of the maven-pmd-plugin,
Since then, there has been a refactoring of the excludes logic to bring
harmony to the pmd and cpd reports, been numerous fixes to correct various site
generation failures, updates t
+1
Emmanuel
Joakim Erdfelt a écrit :
Hi,
It has been 5 months since the last release of the maven-checkstyle-plugin,
Since then, there have been numerous fixes to correct various site
generation failures, updated maven ruleset, some cleanup of the report
layout, header refactoring, revised doc
> Could it be updated to use PMD 3.8 first? 3.7 is still very buggy with
> JDK 1.5 code. 3.8 has several fixes for that.
I'm using a locally patched version of the PMD plugin which uses 3.8 for
some time now. All you have to do is to change the version number to 3.8.
So I second this reques
Thanks Franz for the info.
Guys, do you think it makes sense to refactor this a bit? I personnaly
do but have no idea in which component.
Thanks,
Stéphane
On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
Good day to you, Stephane,
Don't quote me on this one, but i don't think t
58 matches
Mail list logo
