Hello Maven developers,
I'd like just to inform you that while checking out maven archetype I've
noticed that there is a maven-archetype-2.0-alpha-5 tag created in April
2009; most recent release is 2.0-alpha-4 from September 2008, and current
trunk is 2.0-alpha-5-SNAPSHOT, so this existing
2009/11/10 Vincent Siveton vsive...@apache.org:
The vote has passed with the following result :
+1 Benjamin, Lukas, Dennis, Hervé, Vincent
I will promote the artifacts to the central repo.
Have the artifacts been promoted to central? I can't see them:
Nice catch, I've removed it.
On 12/11/2009, at 7:22 PM, Stevo Slavić wrote:
Hello Maven developers,
I'd like just to inform you that while checking out maven archetype I've
noticed that there is a maven-archetype-2.0-alpha-5 tag created in April
2009; most recent release is 2.0-alpha-4
Great!
Debugged 2.0-alpha-4, and I think I've solved
ARCHETYPE-220http://jira.codehaus.org/browse/ARCHETYPE-220issue. Can
someone with enough privileges please flag the issue that it
contains a patch (no additional tests, yet), and if agreed to increase issue
priority from Minor to Major as IMO
Hi Mark,
It seems that we changed the groupid/artifactid in the past. Here the
right link:
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/
Cheers,
Vincent
2009/11/12 Mark Hobson markhob...@gmail.com:
2009/11/10 Vincent Siveton vsive...@apache.org:
The vote has
+1
I downloaded the source tarball and verified the signature matches KEYS. I
built from source, then rebuilt the source with itself without error on a clean
repository. I'll do some more testing, but that's sufficient for an alpha
release. Nice work!
Cheers,
Brett
On 10/11/2009, at 3:39 AM,
+1
Vincent
2009/11/9 Benjamin Bentmann benjamin.bentm...@udo.edu:
Hi,
OK, here we go, another alpha release of Maven, for all those brave guys
that want to take it for a test drive ;-)
We solved many issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719
Hi,
I ran the ITs against 3.0-alpha-3 and got a number of failures.
Several of those are because they are fixed in 3.0-alpha-4 but marked to run
for all versions:
- mng4412OfflineModeInPlugin
- mng4433ForceParentSnapshotUpdate
Before correcting anything I would like to check I understand the
That sounds like the one that is supposed to be fixed in alpha-4
On Thu, Nov 12, 2009 at 8:20 AM, Brett Porter br...@apache.org wrote:
Doesn't affect my vote, but I noted that this IT fails on 3.0-alpha-3, even
though it is marked as fixed in JIRA:
- mng4361ForceDependencySnapshotUpdate
There should be a start and end range for the tests. These new ones
start in alpha-4-snapshot and end ]
On Thu, Nov 12, 2009 at 8:20 AM, Brett Porter br...@apache.org wrote:
Hi,
I ran the ITs against 3.0-alpha-3 and got a number of failures.
Several of those are because they are fixed in
You should use the inherited element of the execution for that.
On Wed, Nov 11, 2009 at 4:43 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Just thought of a use-case for listing the same plugin twice in the
one plugins section namely inheritedtrue/inherited and
On 13/11/2009, at 1:08 AM, Brian Fox wrote:
There should be a start and end range for the tests. These new ones
start in alpha-4-snapshot and end ]
ok, I've fixed these 2 and 4361 based on your other comment (though I haven't
changed the JIRA version of that issue).
I also included all
but what if you want to configure the defaults for all executions, and for
the child module executions, and you want the defaults for the child modules
to be different from the defaults for this module.
e.g.
turn skip on for this module, but off for child modules
2009/11/12 Brian Fox
+1, seems to run well here.
Benjamin Bentmann wrote:
Hi,
OK, here we go, another alpha release of Maven, for all those brave guys
that want to take it for a test drive ;-)
We solved many issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719
There are
Ah great, thanks :)
Mark
2009/11/12 Vincent Siveton vsive...@apache.org:
Hi Mark,
It seems that we changed the groupid/artifactid in the past. Here the
right link:
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/
Cheers,
Vincent
2009/11/12 Mark Hobson
Another issue I have with Maven 3: trying to deploy an artifact with
release:perform, I get the following error:
[INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': Cannot
find wagon which supports the requested protocol: dav - [Help 1]
[INFO] [ERROR]
Is it a known issue?
I've upgraded maven-reporting-impl now that it has been released.
The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1].
Can this be resolved quickly or shall we defer it until 2.5?
Cheers,
Mark
[1] http://jira.codehaus.org/browse/MCHECKSTYLE-123
2009/11/4 Mark Hobson
wagon weddav is not any more included in the distrib.
You have to add it in your pom.
--
Olivier
2009/11/12 Julien HENRY henr...@yahoo.fr:
Another issue I have with Maven 3: trying to deploy an artifact with
release:perform, I get the following error:
[INFO] [ERROR] Error deploying
Hi,
Move it to 2.5.
I wanted to work on some refactoring on the plugin.
But the best is to do it after the release :-)
--
Olivier
2009/11/12 Mark Hobson markhob...@gmail.com:
I've upgraded maven-reporting-impl now that it has been released.
The only unresolved issue destined for 2.4 is now
OK, thanks
- Message d'origine
De : Olivier Lamy ol...@apache.org
À : Maven Developers List dev@maven.apache.org
Envoyé le : Jeu 12 Novembre 2009, 16 h 58 min 00 s
Objet : Re: Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3
wagon weddav is not any more included in the distrib.
+1
Hervé
Le lundi 09 novembre 2009, Benjamin Bentmann a écrit :
Hi,
OK, here we go, another alpha release of Maven, for all those brave guys
that want to take it for a test drive ;-)
We solved many issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14
719
Great, thanks Olivier.
I'll start the vote for 2.4.
Cheers,
Mark
2009/11/12 Olivier Lamy ol...@apache.org:
Hi,
Move it to 2.5.
I wanted to work on some refactoring on the plugin.
But the best is to do it after the release :-)
--
Olivier
2009/11/12 Mark Hobson markhob...@gmail.com:
Hi,
The big new feature in this release is an upgrade to Checkstyle 5.0,
which brings Java 5 compatibility.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=15336
There are still a couple of issues left in JIRA:
Just to follow up on this, it looks like the two main options are:
1) Add an endorsed scope. What would be involved with that? What would
happen when a 2.0.10/2.2.1 maven version hits such a scope?This seems to
be a maven core thing with updates needed to a bunch of core things. Not
Is it possible to add endorsed libraries programatically? I thought
the JDK grabbed all its endorsements from jdk_home\lib\ext
Paul
On Thu, Nov 12, 2009 at 12:48 PM, Daniel Kulp dk...@apache.org wrote:
Just to follow up on this, it looks like the two main options are:
1) Add an endorsed
On Thu November 12 2009 2:22:51 pm Paul Benedict wrote:
Is it possible to add endorsed libraries programatically? I thought
the JDK grabbed all its endorsements from jdk_home\lib\ext
When you fork a jvm (javac fork or surefire set to fork), you can specify a
system property of other places to
Yes, then it is probably appropriate for the Maven Compiler plugin to
support endorsed libraries. I can't remember if it always forks, but
if forking isn't specified, an error should be thrown when endorsed
libraries are used.
Paul
On Thu, Nov 12, 2009 at 3:19 PM, Daniel Kulp dk...@apache.org
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.2.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Arnaud Héritier, Olivier Lamy, Jason
van Zyl, Stéphane Nicoll, Dan Fabulich, Brian Fox, Brett Porter, Vincent
Siveton, John Casey, Hervé Boutemy
+1 (non-binding): Stephen Connolly, Stuart McCulloch, Paul
Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven
site. How do we want to go about that with alpha-3?
To attract more testers, I think we should have this alpha listed in the
download section. E.g. some structure like
* Stable Releases
2.2.1
2.1.0
2.0.10
*
Can't hurt. I have no problem promoting alpha-3. It's the best Maven
that's existed. I say go for it.
On 2009-11-13, at 12:59 AM, Benjamin Bentmann wrote:
Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven
site. How do we want to go about that with alpha-3?
To
On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote:
Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven site.
How do we want to go about that with alpha-3?
To attract more testers, I think we should have this alpha listed in the
download section. E.g. some
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
On 13/11/2009, at 11:28 AM, Brett Porter wrote:
On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote:
Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven site.
How do we want to go about that with alpha-3?
To attract more testers, I think we should have this
+1
2009/11/12 Mark Hobson markhob...@gmail.com
Hi,
The big new feature in this release is an upgrade to Checkstyle 5.0,
which brings Java 5 compatibility.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=15336
There are still a couple of
IMO 2.1.0 should stay as it is, if I'm not mistaken, most recent stable
release of maven which is compatible with Java 1.4. When maven 2.2.1 is
configured as default external maven installation m2eclipse 0.9.9 refuses to
build projects (like maven core plugins) which still require Java 1.4. Maybe
36 matches
Mail list logo
