Hi,
Jesse M (already a plugins committer), has pinged me off list saying he
has some changes to the repository manager that he'd like to commit.
Rather than going through patches, I'd like to suggest we increase his
karma. We need more people working on it :)
Cheers,
Brett
--
Brett Porter <
These are all things I have given thought to and would like to see them
worked on in Maven 2.1/2.2. There are a couple of jira issues already
filed for some of these specifics.
- Brett
Gordon Henriksen wrote:
Since central is usually slow during the day, it can be pretty painful
that Maven's
I disagree in general - it's easier to review smaller, specific patches,
especially if one were to be rejected and the others accepted. Of
course, the danger is that they build on top of each other and then it
gets harder.
That said, I'm not the one who put my hand up to apply the patches
(th
ASs right now you are the only one working on it you should post a
patch every week or so to reduce the amount of effort needed
On 6/2/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hello again
There are now three more patches available in JIRA, for the
maven1-plugin, that needs some tender lov
Hello again
There are now three more patches available in JIRA, for the
maven1-plugin, that needs some tender love and care (i.e. review and
commit) :)
- http://jira.codehaus.org/browse/MNG-2335
- http://jira.codehaus.org/browse/MNG-2336
- http://jira.codehaus.org/browse/MNG-2338
These patche
Since central is usually slow during the day, it can be pretty
painful that Maven's local repository does not cache negative
responses. Maybe Maven could stash away the URL and response date for
404's so that it won't try again for a day or two, unless forced to
refresh? (5xx's should not b
Hi
Yes, I actually had that line in, and it did printed the current directory, not
the one given by the .setBaseDir call. That was why I wrote that something must
be wrong in another bean, and queried about which bean is responsible for
setting the parameters. The odd thing is as I wrote that t
[EMAIL PROTECTED] wrote:
Hi
Something must be wrong in another place. The eclipse:eclipse goal excutes ok
with the supplied (i.e correct) basedir, but the MavenArchetypeMojo for some
reason is supplied the working directory, which is not what is supplied in the
call.
You mean if you add thi
added. Thanks
Emmanuel
Cabasson Denis a écrit :
Just to submit two items for the maven article page:
I have translated to french the article "An introduction to Maven 2" from
Javaworld (of course with full authorization).
http://dcabasson.developpez.com/articles/java/maven/introduction-maven2
Just to submit two items for the maven article page:
I have translated to french the article "An introduction to Maven 2" from
Javaworld (of course with full authorization).
http://dcabasson.developpez.com/articles/java/maven/introduction-maven2/
Would it be possible to add this to the article p
Hi
Something must be wrong in another place. The eclipse:eclipse goal excutes ok
with the supplied (i.e correct) basedir, but the MavenArchetypeMojo for some
reason is supplied the working directory, which is not what is supplied in the
call.
Here is the patch :
Index: MavenArchetypeMojo.java
[EMAIL PROTECTED] wrote:
Hi
Have not had the time before now.
It still does not work. The basedir is still set to the current directory.
The ${basedir} will be set to the value you set in the embedder, this is
working for me in my IDEA plugin where I use the embedder.
Can you include the p
12 matches
Mail list logo
