This is filed under MNG-3694.
I think I have a solution now, and I've written an integration test that
fails under 2.0.10-RC4...I'm running the test now vs. the fixed version,
and then I'll verify that I didn't break anything else.
-john
Brett Porter wrote:
Yeah, I spoke too soon.
getSourc
I'm tracking this under http://jira.codehaus.org/browse/MNG-3693
I've already got the fix in place in RC5-snapshot, but it's going to
take a little while to produce a self-contained integration test for it.
-john
Mauro Talevi wrote:
John Casey wrote:
Hi,
I've got a new release candidate fo
Yeah, I spoke too soon.
getSourcePaths() in the javadoc plugin now ends up with:
[${project.basedir}/src/main/java, ${project.basedir}/src/main/java]
ie, uninterpolated. the prune method them removes them since they
aren't found, and so it does nothing (as there are no sourcePaths).
So, basi
it'd be a simple enough operation to lookup the timestamp on the RCs on
my staging repo, and do a date-based search using those values...
What's the value in providing this level of resolution, though?
Paul Benedict wrote:
Brett, I know those discussions existed. I was apart of them :-) and I
Hi Brett,
Unfortunetely, under windows, ITs fail again.
I flag the debug mode for invoker plugin so I guess it could be useful
for John or others.
Thanks a lot Brett for your support.
Vincent
2008/8/1 Brett Porter <[EMAIL PROTECTED]>:
>
> On 01/08/2008, at 8:03 AM, John Casey wrote:
>
>> Until
Hmm, I don't remember taking that out. I'll have to check it out.
You're right, we need to make it consistent.
-j
Brett Porter wrote:
On 01/08/2008, at 8:03 AM, John Casey wrote:
Until I can get the javadoc plugin working on OS X there's nothing I
can do to even peek at this.
Fixed (it wa
On 01/08/2008, at 8:03 AM, John Casey wrote:
Until I can get the javadoc plugin working on OS X there's nothing I
can do to even peek at this.
Fixed (it was relying on tools.jar, I made the behaviour the same as
javac).
Why is it failing? Can you formulate a MNG issue with the relevan
No more problem - builds fine on my projects.
:-)
- Fabrice
[EMAIL PROTECTED]
On Thu, Jul 31, 2008 at 10:50 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've got a new release candidate for people to try out:
>
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apac
John Casey wrote:
Hi,
I've got a new release candidate for people to try out:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
Major changes:
- Bumped wagon version to 1.0-beta-4
- Improved handling of mirror definitions without an
Arnaud HERITIER wrote:
What are the errors in javadoc tests ?
MJAVADOC-210, the plugin was searching for tools.jar which isn't found
on Mac, so the unit test to check the auto-detection of taglets failed.
I'm building it successfuly on Mac OS X.
Strange. How about the ITs, do they fail f
What are the errors in javadoc tests ?
I'm building it successfuly on Mac OS X.
I remember I had to add the JAVA_HOME
(JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home)
and tests passed
Arnaud
On Thu, Jul 31, 2008 at 10:50 PM, John Casey <[EMAIL PROTECTED]> wrote:
>
Ah :)
perhaps "fixed in RCx" as the last comment is enough?
- Brett
On 01/08/2008, at 1:35 PM, Paul Benedict wrote:
Brett, I know those discussions existed. I was apart of them :-) and I
recommended we should not create extra JIRA versions for 1 and 2
tickets. My
question this time, however
Brett, I know those discussions existed. I was apart of them :-) and I
recommended we should not create extra JIRA versions for 1 and 2 tickets. My
question this time, however, is a bit different. I just wanted to know if we
should somehow mark the ticket with RC1, RC2, etc. within the version just
To: Maven Developers List
Subject: Re: Maven 2.0.10-RC4
Yes, I believe this would be a good candidate to push to [EMAIL PROTECTED] I'll
put together the message now.
It's worth remembering that we may have a problem expressed somewhere in
the javadoc plugin, so this may not be the last R
Hi Benjamin,
For the first one, I guess that javadoc:javadoc was not call from core.
For jdk6, I have no clue about BSH but I noticed that
maven-javadoc-plugin version is 2.4 and not 2.5-snap.
Thanks to have a glance :)
Vincent
2008/7/31 Benjamin Bentmann <[EMAIL PROTECTED]>:
> Vincent Siveton
Vincent Siveton wrote:
I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
MJAVADOC-180 is a strange one: The IT's verify.bsh is run only if
System.getProperty( "java.specification.version" ).equals( "1.5" )
??
Anyway, I run "mvn
We already had that discussion and decided it would be overkill - once
2.0.10 is released nobody will be concerned with the difference
between these release candidates (And they won't be available for
download any more anyway). There are few enough changes between each
that you can use time
Yes, I believe this would be a good candidate to push to [EMAIL PROTECTED] I'll
put together the message now.
It's worth remembering that we may have a problem expressed somewhere in
the javadoc plugin, so this may not be the last RC. But it's becoming
must more stable with this RC.
-john
B
Until I can get the javadoc plugin working on OS X there's nothing I can
do to even peek at this.
Why is it failing? Can you formulate a MNG issue with the relevant
details that are causing the ITs to fail? If I had some sort of set of
steps to reproduce the problem, it would help a lot.
-jo
OTOH, there is a 'Fix Version' property in JIRA that you can use to
assign a release/build/version id.
Rahul
On Fri, Aug 1, 2008 at 9:28 AM, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2,
> etc.? I liked how Bugzilla had fla
Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2,
etc.? I liked how Bugzilla had flags to mark items. Anything like that in
JIRA?
Paul
On Thu, Jul 31, 2008 at 4:16 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Would this be a good one to push to users@, particularly hi
Would this be a good one to push to users@, particularly highlighting
the need to test projects with creative uses of interpolation and
various deployment setups?
Cheers,
Brett
On 01/08/2008, at 6:50 AM, John Casey wrote:
Hi,
I've got a new release candidate for people to try out:
http:/
Hi John,
I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
Cheers,
Vincent
2008/7/31 John Casey <[EMAIL PROTECTED]>:
> Hi,
>
> I've got a new release candidate for people to try out:
>
> http://people.apache.org/~jdcasey/stage/apac
23 matches
Mail list logo
