+1
-john
On Mar 21, 2008, at 5:45 PM, Brian E. Fox wrote:
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore compatibility. This release is dependent
on the
maven-reporting-impl-2.0.4.1 release and 2.0.9 is dependent on this
release.
Staged at
I committed it before I sent the email. Feel free to review it and
request changes, etc. I will check email while I'm gone, but the machine
with my work in progress is on a desktop at home, not on my laptop.
The page modified will be
http://maven.apache.org/guides/introduction/introduction-to-
Ralph, I'll gladly publish the site...just commit the guide and have a
nice vacation! Thanks for pulling it together last minute.
--Brian
-Original Message-
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 6:35 PM
To: Maven Developers List
Subject: Re: Documentati
I updated the introduction to dependency mechanism page and built the
site locally. I then checked it in. The last time I did this was in
September and I can't for the life of me remember how to publish the
site - I remember logging in to people.apache.org and doing some stuff
over there. I've
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore compatibility. This release is dependent on the
maven-reporting-impl-2.0.4.1 release and 2.0.9 is dependent on this
release.
Staged at:
http://people.apache.org/~brianf/staging-repository
There
+1
-john
On Mar 21, 2008, at 5:13 PM, Brian E. Fox wrote:
The old version 2.0.4 is trying to use an obsolete method in the
plugin-plugin tools. This was removed in 1.0-alpha-10 of the
doxia-site-render and causes problems with newer plugin tools and
2.0.9.
This release was cut from the old 2
The old version 2.0.4 is trying to use an obsolete method in the
plugin-plugin tools. This was removed in 1.0-alpha-10 of the
doxia-site-render and causes problems with newer plugin tools and 2.0.9.
This release was cut from the old 2.0.4 tag because it's 2 years old and
the trunk has tons of chang
Yes we should fix the docs. I also think we need to put back the old
behavior but add a deprecation warning. We seriously need to be more
sensitive to randomly breaking builds like this. It's the single biggest
thing we hear from the users.
-Original Message-
From: Dennis Lundberg [mailto:
Hi,
There are still several code spots in Maven that rely on the platform's
default encoding when processing text files which does support build
reproducibility. It could help developers to detect such defects if the CI
machines were configured to run Maven with
MAVEN_OPTS=-Dfile.encoding=U
Another update,
We tracked down the 3473 issue and John made a fix for it because the
change that caused the problem (3426) was correct, but it just exposed
other issues. In the process we found 3 regressions in the plugin tools
[1] that essentially break existing builds and/or are not compatible
w
The new archetype mechanism is different, and the archetypes are
created from existing projects so much of that document is irrelevant.
But archetypes do have their own packaging now, but it's all taken
care of in the background when you use "mvn archetype:create-from-
project".
If you cre
Thanks Jason
So the pom example [1] under "1. Create a new project and pom.xml for
the archetype plugin" should be changed from
maven-plugin
to
jar
[1] http://maven.apache.org/guides/mini/guide-creating-archetypes.html
Jason van Zyl wrote:
It's a set of plexus components that is designed
It's a set of plexus components that is designed to be embedded. One
form is embedding in Maven in the form of a plugin. So it's not a
plugin, but can be accessed through a Maven plugin. Many plugins use
this strategy where they make a set of reusable plexus components and
then provide a mo
Disclaimer: I've never used archetypes before.
I've had a look at http://jira.codehaus.org/browse/MPLUGIN-102
I found the attached example project strange, because the pom specified
maven-plugin
The poster references the example pom on this page:
http://maven.apache.org/guides/mini/guide-cr
I don't think it works with 2.1 (which has the embedder used by M2E and Q4E).
-Original Message-
From: Mark Struberg [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 3:15 AM
To: Maven Developers List
Subject: Re: Relative path to local repository?
I tried the following, and it is w
I tried the following, and it is working:
${env.HOME}/somewhereelse/repository
This is on Linux, but it should be easy to find something which is also working
on Windows and
OsX.
LieGrü,
strub
--- Wayne Fay <[EMAIL PROTECTED]> schrieb:
> My gut is that the configuration in settings.xml shoul
16 matches
Mail list logo
