It is very unfortunate, that you took the same goal that was introduces by the
maven-dependency-analyzer-plugion, that is currently merged in the sandbox in a
branch.
I am no committer, so my vote is non-binding, but my choice is -1 because of
this.
- Jörg
Brian E. Fox wrote on Sunday, March
Hi Brian,
Brian E. Fox wrote on Saturday, March 17, 2007 6:11 AM:
> I whipped up a mojo to test a build for cases where the resolved
> dependency is different than what is set in the dependencyManagement
> section. Use maven-dependency-plugin 2.0-alpha-3-SNAPSHOT (deployed to
> snapshot repo) run
Hi Raphael,
Sounds like you are doing some terrific work.
If you have time, could you please take a look at this bug:
http://jira.codehaus.org/browse/MNG-2856
When the current archetype plugin processes png images, it changes them,
and makes the unreadable.
I think if we add a element (pos
Hi,
I put in some site stuff into the core which are the site modules
which I will take out before 1.0, but I see some indexing stuff as
was wondering if that's book specific, or site specific or can it be
used by both?
Jason.
-
i'm -0 about having it in 2.0.6
I still think this is the kind of thing that would make sense in a 2.1
release having into account our version guidelines.
On 3/18/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Brett, Carlos,
Have you looked at the issue/code and do your -1s still hold or can
we
On 18 Mar 07, at 8:49 PM 18 Mar 07, Brett Porter wrote:
On 19/03/2007, at 7:59 AM, Jason van Zyl wrote:
- [ ] Doxia Refactor for 1.0
- [ ] Separate the basic parser/sink framework from any site and
book related code. Strip it down to the basic parser/sink
framework, m
Kenny, when you get a chance I'd love to see an example of the maven-
it-plugin in action.
For now, I've just configured my projects to use install:install-
file, which appears to be working fine (at the cost of a bit more
complicated configuration).
--jason
On Mar 16, 2007, at 3:58 AM, K
On 19/03/2007, at 7:59 AM, Jason van Zyl wrote:
- [ ] Doxia Refactor for 1.0
- [ ] Separate the basic parser/sink framework from any site and
book related code. Strip it down to the basic parser/sink
framework, modularize the code and create tests for each
modu
On 19/03/2007, at 11:36 AM, Jason van Zyl wrote:
Yah, I saw the logging which is why I used the network monitors so
the only thing I could think of is a plugin grabbing the
WagonManager and turning it back online which I consider someone
else's problem.
I think from the test below it's c
On 19/03/2007, at 11:27 AM, Jason van Zyl wrote:
You mean in a separate subproject of doxia. I can change the
directory so how about:
doxia
doxia-site (sub project)
doxia-book (sub project)
These sound fine to me.
- start a new thread on the broader question of how we manage our
subpr
On 18 Mar 07, at 8:19 PM 18 Mar 07, Brett Porter wrote:
It's just a logging problem.
Yah, I saw the logging which is why I used the network monitors so
the only thing I could think of is a plugin grabbing the WagonManager
and turning it back online which I consider someone else's problem
On 18 Mar 07, at 8:10 PM 18 Mar 07, Brett Porter wrote:
On 19/03/2007, at 10:37 AM, Jason van Zyl wrote:
We extracted it out and then put it back in?
I'm not really sure what you mean here. All I was saying was the
the site stuff was already wound in, I pulled most out to a
separate m
It's just a logging problem.
I just did mvn -o -X clean install on archiva, and see this:
--->8---
[INFO] snapshot org.codehaus.plexus:plexus-appserver-maven-plugin:2.0-
alpha-8-SNAPSHOT: checking for updates from apache.snapshots
[DEBUG] System is offline. Cannot resolve metadata:
Repositor
On 19/03/2007, at 10:37 AM, Jason van Zyl wrote:
We extracted it out and then put it back in?
I'm not really sure what you mean here. All I was saying was the the
site stuff was already wound in, I pulled most out to a separate
module, but there are probably still things that could be im
Hi,
Just seeing if anyone can reproduce this:
http://jira.codehaus.org/browse/MNG-2433
I can't so I want to close it. I've used truss, TPIMon, and ktrace on
the Linux, Window, and OS X and I see no network traffic on a simple
project but I'm wondering if it's some plugin turning on the Wago
+1
On 19/03/2007, at 10:43 AM, Jason van Zyl wrote:
Hi,
Any object to removing the ITs from 2.0.x and relying on our new
setup here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/
Jason.
-
To unsub
Hi,
Any object to removing the ITs from 2.0.x and relying on our new
setup here:
http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
On 18 Mar 07, at 7:06 PM 18 Mar 07, Brett Porter wrote:
On 19/03/2007, at 9:42 AM, Jason van Zyl wrote:
On 18 Mar 07, at 5:52 PM 18 Mar 07, Brett Porter wrote:
What was your justification for removing them?
Actually, as a follow up to show why what we have currently as not
being ide
On 19/03/2007, at 9:42 AM, Jason van Zyl wrote:
On 18 Mar 07, at 5:52 PM 18 Mar 07, Brett Porter wrote:
What was your justification for removing them?
Actually, as a follow up to show why what we have currently as not
being ideal is the XhtmlSink. This is something I started and was a
I think they are already deprecated, but not removed. I couldn't tell
you off the top of my head which reports/versions of Maven would be
affected by removing it, though I would feel it would be fairly safe
now - wse'd just need to figure out which reporting-impl version and
maven version a
Hi,
Do we still need the codehaus references in the site plugin for any
reports? This is a 2.0 so can we kill those or have we still versions
of reports floating around that use it?
Just wanted to expunge those for the 2.0 release of the maven-site-
plugin if possible.
Jason.
--
On 18 Mar 07, at 5:52 PM 18 Mar 07, Brett Porter wrote:
What was your justification for removing them?
Actually, as a follow up to show why what we have currently as not
being ideal is the XhtmlSink. This is something I started and was a
mistake in the form that I did it because I did m
On 18 Mar 07, at 6:24 PM 18 Mar 07, Brett Porter wrote:
Yes, I'm happy with where we got to with the discussion and
withdraw that. I don't think it landing in 2.0.6 is ideal, but I
think it's the best solution available to us today.
(sorry, got confused about the process - thought my -1 wa
Yes, I'm happy with where we got to with the discussion and withdraw
that. I don't think it landing in 2.0.6 is ideal, but I think it's
the best solution available to us today.
(sorry, got confused about the process - thought my -1 was only a
vote, not a veto)
On 19/03/2007, at 9:19 AM, J
Brett, Carlos,
Have you looked at the issue/code and do your -1s still hold or can
we put this through in the 2.0.6 release?
Carlos you did not specifically use -1, but I consider your object to
be the same.
I would like to stage a build for people to try.
Jason.
---
Thanks :)
On 19/03/2007, at 9:12 AM, Jason van Zyl wrote:
On 18 Mar 07, at 5:53 PM 18 Mar 07, Brett Porter wrote:
You appear to have deleted the moved tools off the face of the map
- I see no corresponding add for this remove.
I'd suggest using server-side moves for this type of thing in
On 18 Mar 07, at 5:53 PM 18 Mar 07, Brett Porter wrote:
You appear to have deleted the moved tools off the face of the map
- I see no corresponding add for this remove.
I'd suggest using server-side moves for this type of thing in
future - large local moves tend to get messy :)
http://
On 18 Mar 07, at 5:52 PM 18 Mar 07, Brett Porter wrote:
-1 on this change.
I apologise - I was sure I responsed to your mail saying you were
going to do this yesterday saying that I objected, but it never
made it to the list.
I can't see any reason to remove these 2 modules from Doxia -
You appear to have deleted the moved tools off the face of the map -
I see no corresponding add for this remove.
I'd suggest using server-side moves for this type of thing in future
- large local moves tend to get messy :)
- Brett
On 19/03/2007, at 5:58 AM, [EMAIL PROTECTED] wrote:
Auth
-1 on this change.
I apologise - I was sure I responsed to your mail saying you were
going to do this yesterday saying that I objected, but it never made
it to the list.
I can't see any reason to remove these 2 modules from Doxia - I
believe Doxia should be capable of generating a fully d
this question was raised in commons when they thought about changing
their groupIds ot org.apache.commons
http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg90223.html
Let's clarify one thing, when you say your build broke due to a
relocation, you mean your build broke when you upgrad
Hi,
Here are some notes on the Doxia refactor for 1.0. Also if anyone can
look at any of the remaining issues that would be good, but I'm going
to put up a vote for the 1.0-alpha-9 shortly. Here are the notes.
Nothing drastic and no API changes really just some decoupling and
reorganizati
>>+1 - looking forward to dependency plugin that uses this.
The maven-dependency-plugin 2.0-alpha-3 is also up for vote in another
thread. It may be confusing because the subjects look similar.
-
To unsubscribe, e-mail: [EMAIL PRO
+1,
I might give it a try to reuse it for the IDE integration.
Milos
On 3/18/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
+1 - looking forward to dependency plugin that uses this.
Dan
On Saturday 17 March 2007 11:03, Brian E. Fox wrote:
> I'd like to release the alpha 1 version of this shared
On 3/17/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
I don't understand the second option: if you stop relocating
(not done by maven, but by the pom deployers, right?) when a version exists,
that means you can never relocate. It's no use to
relocate unreleased poms since they won't be present
Jason van Zyl wrote:
Looks like we're all set here too. I'll take care of Ralph's karma.
Thanks, Jason. I look forward to helping out!
Ralph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAI
+1 - looking forward to dependency plugin that uses this.
Dan
On Saturday 17 March 2007 11:03, Brian E. Fox wrote:
> I'd like to release the alpha 1 version of this shared component. The
> analyzer scans through your class files and produces a list of
> dependencies declared but not used, depen
Looks like we're all set here too. I'll take care of Ralph's karma.
Jason.
On 18 Mar 07, at 10:32 AM 18 Mar 07, Stephane Nicoll wrote:
+1
Stéphane
On 3/17/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
As part of the massive overhaul that was MNG-1577 I wanted to also to
ask for commit p
+1
Stéphane
On 3/17/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
As part of the massive overhaul that was MNG-1577 I wanted to also to
ask for commit privs for Ralph. Much of my recent work has been with
Patrick on getting MNG-1577 into the codebase, but Ralph also did a
great deal of work
39 matches
Mail list logo
