The central repository shall now contain correct checksums for all 1.8
plexus-compiler* artifacts. Sorry for the trouble.
Milos
On Wed, Apr 21, 2010 at 2:11 AM, Brett Porter br...@apache.org wrote:
Hi Milos,
I'm not sure if you did the plexus-compiler release in conjunction with
this or if
+1
works fine on my test-projects
2010/4/22 Igor Fedorenko i...@ifedorenko.com
+1
Works for Tycho (although I had to fix a couple of sloppy tests) and few
our internal projects I work on.
--
Regards,
Igor
Benjamin Bentmann wrote:
Hi,
We solved 39 issues:
Last night I was looking at an irc user's pom for a parsing error:
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdorg.lwjgl/groupId
artifactIdlwjgl-linux-64/artifactId
version2.4.2/version
repositories
repository
idnewdawnsoftware/id
Hi,
The jing-20030619.jar is available in the central maven repository.
But I cannot find the jing-2009. Is it possible to get this jar
from the central maven repo?
Thanks,
Norbi
-
To unsubscribe, e-mail:
That's up to whomever produces these artifacts, not the Maven developers.
Justin
On 4/22/10 8:52 AM, Norbert Bátfai wrote:
Hi,
The jing-20030619.jar is available in the central maven repository.
But I cannot find the jing-2009. Is it possible to get this jar
from the central maven
Hello ,
I wanted to include IBM MQ jar to include in pm project. I have included
following dependencies under the dependency section, but it unable to get
them and saying
22/04/10 15:24:52 BST: Missing artifact
com.ibm:com.ibm.mq:jar:5.3.07:compile
22/04/10 15:24:52 BST: Missing artifact
Because MQ is proprietary software, most likely you will only be able
to get the jars if you have the product on your machine or within your
organization. If you have the software, you'll need to install those
jars into your repository.
On Thu, Apr 22, 2010 at 9:48 AM, Srini97
+1
I downloaded the source tarball, checked the signature, and built from sources.
Used that to build a few projects.
I still have some niggles (the same as previous alphas), I just need to
articulate them into JIRA before it goes final...
On 20/04/2010, at 3:50 AM, Benjamin Bentmann wrote:
Brian Fox:
I put this on my desktop and ran:
c:\Users\brianf\Desktopmvn help:effective-pom
And it started downloading all updated versions of the
plugins...plugins that aren't being used in this execution and aren't
referenced in the pom directly.
In short, the plugin JARs (and only those)
3.0-beta-1 being a beta release, it's getting close to GA. I was
wondering can MNG-4483 be addressed? I don't think Maven can keep the
.m2 user directory exclusively -- it could be a good fallback for
compatibility -- but it should be looking for .m3 or .mvn.
Paul
Ok I think I understand now. The project.build.plugins are searched so
that they would override the pluginGroup metadata for the prefix...AND
all the default plugins are now in project.build.plugins instead of
pluginManagement. This is the bigger change here but the upshot is
that effective-pom
+1
- Message d'origine
De : Paul Benedict pbened...@apache.org
À : Maven Developers List dev@maven.apache.org
Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s
Objet : MNG-4483
3.0-beta-1 being a beta release, it's getting close to GA. I was
wondering
can MNG-4483 be addressed?
+1 for .mvn and backward compatibility with .m2 if not found
2010/4/22 Julien HENRY henr...@yahoo.fr
+1
- Message d'origine
De : Paul Benedict pbened...@apache.org
À : Maven Developers List dev@maven.apache.org
Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s
Objet :
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Thu, Apr 22, 2010 at 6:00 PM, nicolas de loof
nicolas.del...@gmail.comwrote:
+1 for .mvn and backward compatibility with .m2 if not found
2010/4/22 Julien HENRY
On Thu, Apr 22, 2010 at 12:00 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
+1 for .mvn and backward compatibility with .m2 if not found
Wouldn't it _create_ .mvn if it's not found? Otherwise what's going
to happen the first time you use m3 on a new machine?
--
Wendy
This sounds easy on the maven side, but what are the ramifications for
all the tools that would have to be updated. Is it worth it?
On Thu, Apr 22, 2010 at 11:14 AM, Paul Benedict pbened...@apache.org wrote:
3.0-beta-1 being a beta release, it's getting close to GA. I was
wondering can MNG-4483
Brian,
What ramifications could exist if .m2 is the fallback? It would be an
easy upgrade path. My point is, it's odd Maven 3 has an m2 user
directory -- nothing technically incorrect; just a vestigial of
progress.
Paul
On Thu, Apr 22, 2010 at 11:35 AM, Brian Fox bri...@infinity.nu wrote:
This
1) check if .mvn exists
2) if .mvn doesn't exist then check if .m2 exists
3) if .m2 doesn't exist then create .mvn and use it
++
Julien
- Message d'origine
De : Wendy Smoak wsm...@gmail.com
À : Maven Developers List dev@maven.apache.org
Envoyé le : Jeu 22 avril 2010, 18 h 16 min
What ramifications could exist if .m2 is the fallback? It would be an
easy upgrade path. My point is, it's odd Maven 3 has an m2 user
directory -- nothing technically incorrect; just a vestigial of
progress.
Because now every tool that cares about this folder needs to implement
that same
Just to play devil's advocate, if you run maven then sync your tool, maven
will use .mvn, the IDE/tool will only check .m2.
[]s Gus
On Thu, Apr 22, 2010 at 9:45 AM, Paul Benedict pbened...@apache.org wrote:
Brian,
What ramifications could exist if .m2 is the fallback? It would be an
FAIL! I was a bit too late :)
On Thu, Apr 22, 2010 at 10:04 AM, Brian Fox bri...@infinity.nu wrote:
What ramifications could exist if .m2 is the fallback? It would be an
easy upgrade path. My point is, it's odd Maven 3 has an m2 user
directory -- nothing technically incorrect; just a
Brian,
Then the current situation should be viewed as acceptable? The .m2
directory, although an artifact of Maven 2, continues to be the home
directory for Maven 3.
Paul
On Thu, Apr 22, 2010 at 12:04 PM, Brian Fox bri...@infinity.nu wrote:
What ramifications could exist if .m2 is the
The neat-nick in me says no, but I'm also not going to rename
repo1.maven.org/maven2 to /maven3 either. I'm just playing devil's
advocate here to point out that there are additional considerations
than simply changing the maven core logic.
On Thu, Apr 22, 2010 at 2:36 PM, Paul Benedict
this can be done simply by adding a profile activated with ${basedir} property:
I just added instruction at the end of Wiki page [1]
Regards,
Hervé
[1] https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
Le jeudi 22 avril 2010, Niall Pemberton a écrit :
On Tue, Apr
Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Lukas Theussl, Olivier Lamy, Hervé Boutemy
+1 (non binding): Stephen Connolly, Raphaël Piéroni
I will promote the artifacts to the central repo.
Regards,
Hervé
On 23/04/2010, at 5:08 AM, Brian Fox wrote:
The neat-nick in me says no, but I'm also not going to rename
repo1.maven.org/maven2 to /maven3 either. I'm just playing devil's
advocate here to point out that there are additional considerations
than simply changing the maven core logic.
Same
Issue Subscription
Filter: Design Best Practices (22 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
27 matches
Mail list logo
