Could be a good idea to send on this list, a list of up to date
plugins for those of us who set the plugins dependencies in their
enterprise POM.
2008/7/11 Paul Benedict [EMAIL PROTECTED]:
What will be the procedure going forward to upgrade super POM dependencies?
Before the RC is cut, I'd
Henri Gomez wrote:
Could be a good idea to send on this list, a list of up to date
plugins
Alternatively, just browse:
- http://maven.apache.org/plugins/index.html
- http://mojo.codehaus.org/plugins.html
Benjamin
-
To
I'm redeploying this one : http://maven.apache.org/plugins/index.html
maven-site 2.0-beta-7 was released
You have this page which is more often updated :
http://docs.codehaus.org/display/MAVEN/Releases
Arnaud
On Fri, Jul 11, 2008 at 9:51 AM, Benjamin Bentmann
[EMAIL PROTECTED] wrote:
Henri
Halo!
Maven don't work when In Windows Vista user has ampersand in the name for
example username=TomJerry. Windows allows usernames like this, but Maven
treat ampersand in the name of users main folder as a part of some url (?)
or something . and cannot get path properly. Windows do not allow
2008/7/11 Artur Śmiejowski [EMAIL PROTECTED]:
Halo!
Maven don't work when In Windows Vista user has ampersand in the name for
example username=TomJerry. Windows allows usernames like this, but Maven
treat ampersand in the name of users main folder as a part of some url (?)
or something .
2008/7/11 Artur Śmiejowski [EMAIL PROTECTED]:
Halo!
Maven don't work when In Windows Vista user has ampersand in the name for
example username=TomJerry. Windows allows usernames like this, but Maven
treat ampersand in the name of users main folder as a part of some url (?)
or something .
When we decided to do this originally, I put forth some procedures for
updating the super pom. Just because a plugin has been released does not
mean we want to update automatically. These defaults are supposed to be
safe defaults that we know work because users should upgrade their
versions
no betas and alpha ??
I think we forgot this rule :-)
- Assembly 2.2-beta-2
- Release 2.0-beta-7
- Site 2.0-beta-6
- War 2.1-alpha-1
http://maven.apache.org/release-notes.html
On Fri, Jul 11, 2008 at 2:53 PM, Brian E. Fox [EMAIL PROTECTED]
wrote:
When we decided
Brian, I was planning to upgrade the dependency on Modello in the core,
because of a binary incompatibility [1] [2]. I was waiting for the build
to fail in CI before I fixed it, but it doesn't seem to have failed yet.
The change I was going to make would fix the Modello issue that you
Hi,
I've wanted to pick up my work on this for some time and was prodded
by the [EMAIL PROTECTED] threads to take another crack at this.
http://docs.codehaus.org/display/MAVEN/Repository+Security (the issue
and related branches are linked)
I've created a couple of branches to try
Can I suggest that a phase in the default lifecycle be added after
packaging for signing (somewhere). It can have no default binding
plugin (such as integration-test) but if it's there, it's easier to
hook in things at the correct time.
Or a pre-package and post-package phase which would
The current signing mechanism actually works quite well and I had no
intention of changing that at this stage. I haven't seen any issues
with this, and adding such fine grained lifecycle stages would soon
get out of control (and frequent arguments as to the correct order).
If it were to be
Fair enough, though I think pre and post implicit phases for many of
the normal phases isn't bloat, since it's a regular pattern.
Having said that, one is free to design a custom lifecycle for a
custom type, so I guess it's not that big a deal, and there's
deterministic order of execution
not sure I follow...how would that be different than changing the packaging?
Brett Porter wrote:
Is it possible to shade to something that would be illegal to use
directly, like appending $shade to the class name, and still have it
all work?
- Brett
On 11/07/2008, at 1:08 AM, Jason van Zyl
On Jul 11, 2008, at 9:42 AM, Brett Porter wrote:
Hi,
I've wanted to pick up my work on this for some time and was prodded
by the [EMAIL PROTECTED] threads to take another crack at this.
http://docs.codehaus.org/display/MAVEN/Repository+Security (the
issue and related branches are
it should be using 2.0.9, IIRC.
Brett Porter wrote:
What version of Maven is being used to execute these builds? I can't
see why it successfully downloads two artifacts then fails with a
resolution error on them.
- Brett
On 11/07/2008, at 3:01 PM, Hudson wrote:
See
We had to start somewhere and those versions were all set based on what
was released at the time, since in 2.0.8 that's what they would have
been using anyway. Since it's stable now, we don't need to move them.
Looking quickly at the list, I know the site beta-6 was horribly broken
for multi
Yep, 2.0.9
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 1:17 PM
To: Maven Developers List
Subject: Re: Build failed in Hudson: maven-core-integration-testing #109
it should be using 2.0.9, IIRC.
Brett Porter wrote:
What version of Maven is
Now we have two conflicting versions specified for the surefire plugin -
one in build/pluginManagement and one in build/plugins...
[EMAIL PROTECTED] wrote:
Author: vsiveton
Date: Fri Jul 11 07:49:22 2008
New Revision: 675972
URL: http://svn.apache.org/viewvc?rev=675972view=rev
Log:
o added
Incidentally, I presume that there is a provider for PGP that could be
replaced by an alternate signing system if a provider were written for
it? I didn't see it in the wiki, but I have a client with an industry-
imposed signing regime that I don't think is based in PGP or md5/shaXXX.
Brian E. Fox wrote:
We had to start somewhere and those versions were all set based on what
was released at the time, since in 2.0.8 that's what they would have
been using anyway. Since it's stable now, we don't need to move them.
Looking quickly at the list, I know the site beta-6 was horribly
I feel like we don't really need to fix these methods as they are
supposed to be helper methods anyway. If the modello release is out
before we're ready to cut the RC, then we can pick it up. Otherwise, I
wouldn't lose any sleep over it. Anyone else feel strongly on this
issue?
-Original
Build/plugins will override so it's not really a conflict per se.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 1:22 PM
To: dev@maven.apache.org
Subject: Re: svn commit: r675972 -
Christian, what kind of files are produced with the sig? Are they still
.asc?
-Original Message-
From: Christian Edward Gruber [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 1:24 PM
To: Maven Developers List
Subject: Re: artifact signing feature branches
Incidentally, I presume
Ralph Goers wrote:
Maybe this won't strike you as strange but it did me. I ran a mvn
install on a project using 2.0.9. In the course of that
maven-project-2.0, maven-project-2.0.6, maven-2.0.7, and
maven-project-2.0.9 were downloaded, installed into the local repo and
then used in the build.
Looking at the Clirr violations, it seems that the problem is a change
in the number of parameters to various method in the generated parser
classes:
[ERROR]
org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader:
In method 'public boolean getBooleanValue(java.lang.String,
John Casey wrote:
Looking at the Clirr violations, it seems that the problem is a change
in the number of parameters to various method in the generated parser
classes:
[ERROR]
org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader:
In method 'public boolean
On Jul 11, 2008, at 2:38 PM, Dennis Lundberg wrote:
John Casey wrote:
Looking at the Clirr violations, it seems that the problem is a
change in the number of parameters to various method in the
generated parser classes:
[ERROR]
I will be out of the office starting 12.07.2008 and will not return until
28.07.2008.
I will respond to your message when I return. In urgent cases please refer
to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva
([EMAIL PROTECTED])
Not again ;)
Vincent
2008/7/11, Julia Antonova [EMAIL PROTECTED]:
I will be out of the office starting 12.07.2008 and will not return until
28.07.2008.
I will respond to your message when I return. In urgent cases please refer
to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva
Agree but it could be a misunderstanding. I will correct it.
Vincent
2008/7/11, Brian E. Fox [EMAIL PROTECTED]:
Build/plugins will override so it's not really a conflict per se.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 1:22
Nope. I'd have to check, but they're signatures which are then zipped
up with the code.
What I'm realizing is that this may actually be irrelevant, as their
whole packaging ends up different than a typical jar, and they have
index files and signatures against each .class file, and then
On 12/07/2008, at 3:11 AM, David Jencks wrote:
On Jul 11, 2008, at 9:42 AM, Brett Porter wrote:
Hi,
I've wanted to pick up my work on this for some time and was
prodded by the [EMAIL PROTECTED] threads to take another crack at
this.
I see where you were coming from with the lifecycle now.
Do you also need to veryify them as part of the build process, or only
out of the repository itself?
Cheers,
Brett
On 12/07/2008, at 8:28 AM, Christian Edward Gruber wrote:
Nope. I'd have to check, but they're signatures which are
IIRC, you're not able to use them at compile time with that name
(which is why anonymous inner classes are xxx$1, ...)
On 12/07/2008, at 3:10 AM, John Casey wrote:
not sure I follow...how would that be different than changing the
packaging?
Brett Porter wrote:
Is it possible to shade to
She takes a lot of vacation :-)
--Brian (mobile)
On Jul 11, 2008, at 5:18 PM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Not again ;)
Vincent
2008/7/11, Julia Antonova [EMAIL PROTECTED]:
I will be out of the office starting 12.07.2008 and will not
return until
28.07.2008.
I will
To many people wanted to try this out so this is the first cut of the
Hudson bundle:
http://people.apache.org/~jvanzyl/hudson.zip
It's fairly crude, and Windows users are SOL until Monday (Unless you
have Cygwin). I just wrote some bash scripts to prototype it, but I've
start rewriting it
The result that Brian and I get is the following. Just incase anyone
wants to run them. Brian diddled the scripts so it would run on
Windows, and I ran on OS X. If there's any problems with the bundle
people find. I'll fix them this weekend.
Results :
Tests in error:
testitMNG3380
38 matches
Mail list logo
