2011/12/17 Olivier Lamy ol...@apache.org
2011/12/17 Antonio Petrelli antonio.petre...@gmail.com:
Hi all
Can you help me convincing the Tomcat team to switch to Maven?
why ?
As long as tomcat core dev are more comfortable with something else
what will be the gain for us ?
Perso I have
2011/12/17 Benson Margulies bimargul...@gmail.com
well, not every problem is well-solved by maven.
In fact yes. If something is missing, writing a plugin could be an idea.
Antonio
Here is my golden rule of builds.
If it ain't broke, don't fix it.
By the sounds of it, the tomcat developers have a build that they do
not see as broken. They are happy with it. If you cannot show how
their build is broken for _them_ (not broken for you or broken for
others) *and* how maven (or
Also, keep in mind that ANT was spun out from Tomcat IIRC, so there is
a long history of Tomcat being built with ANT
On 19 December 2011 08:55, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Here is my golden rule of builds.
If it ain't broke, don't fix it.
By the sounds of it, the
2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com
Here is my golden rule of builds.
If it ain't broke, don't fix it.
I don't know it is broke, however it is flawed.
They are deploying Maven artifacts too using pom.xml files, so there is a
mix with Maven/Ant.
In fact, everything
2011/12/19 Antonio Petrelli antonio.petre...@gmail.com:
2011/12/17 Olivier Lamy ol...@apache.org
2011/12/17 Antonio Petrelli antonio.petre...@gmail.com:
Hi all
Can you help me convincing the Tomcat team to switch to Maven?
why ?
As long as tomcat core dev are more comfortable with
2011/12/19 Olivier Lamy ol...@apache.org
BTW again as tomcat core dev are more confident using something else
why change ?
The most important is to have bug fixed and new features added.
Tools are companion to help the project they must not be the central
point to take care.
At least using
someone to test and add some votes ?
2011/12/15 Olivier Lamy ol...@apache.org:
Hello,
I'd like to release Apache Maven Wagon 2.2
We fixed 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335version=18090
The staged repo is available here:
can test this in the evening.
LieGrue,
strub
pretty busy atm :(
- Original Message -
From: Olivier Lamy ol...@apache.org
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Monday, December 19, 2011 11:13 AM
Subject: Re: [VOTE] Apache Maven Wagon 2.2
someone to test and
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated to the real URL, that is when I invoke release:prepare
with
a URL
On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated
some scm providers have something implemented.
for git it's : git rev-parse --verify HEAD
for svn: svn info
for hg: hg id
more details on those providers in various Info command impls.
2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com:
On 19 December 2011 10:45, Mirko Friedenhagen
Hey all,
Is there anyway that a Maven Mojo can have different run-time dependencies
based on the goal that runs?
Just trying to work around some class loader issues with two libraries
embedded different versions of rhino :(
I'd rather not make a separate plugin if possible... Is there anything
2011/12/19 Mark Derricutt m...@talios.com
Just trying to work around some class loader issues with two libraries
embedded different versions of rhino :(
You could try to create a shaded artifact with the Maven Shade plugin for
one of the two versions:
you could have two profiles if the goals are orthogonal ie if you do
mvn -Prun-v6-its verify
mvn -Prun-v7-its verify
but if you want both goals part of the default lifecycle you may be out of
luck abduction have to resort to other tricks
- Stephen
---
Sent from my Android phone, so random
Antonio, you have to solicit the developers of Tomcat not us. You also have to
convince the users of Tomcat because those are the only people who should be
influencing the decisions of the developers. Maven developers telling Tomcat
developers to switch is something at least within Apache I
2011/12/19 Jason van Zyl ja...@tesla.io
Antonio, you have to solicit the developers of Tomcat not us. You also
have to convince the users of Tomcat because those are the only people who
should be influencing the decisions of the developers. Maven developers
telling Tomcat developers to switch
On 2011-12-19 10:02, Antonio Petrelli wrote:
2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com
Here is my golden rule of builds.
If it ain't broke, don't fix it.
I don't know it is broke, however it is flawed.
They are deploying Maven artifacts too using pom.xml files, so
Only had the chance to give it a quick run. Looks good so far, but I by only
had the chance to do a few very basic operations.
Artifacts look good so far.
+1
LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: Maven Developers List dev@maven.apache.org
+1
On Mon, Dec 19, 2011 at 3:45 PM, Mark Struberg strub...@yahoo.de wrote:
Only had the chance to give it a quick run. Looks good so far, but I by only
had the chance to do a few very basic operations.
Artifacts look good so far.
+1
LieGrue,
strub
- Original Message -
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
(org.apache.maven.shared.release.phase.RewritePomsForReleasePhase).
Two problemes I encountered now:
- The maven-scm-plugin does not seem to implement the equivalent of
scm:info
Then it will have to be the tag name so...
On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
+1
Hervé
Le Jeudi 15 Décembre 2011 16:07:43 Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven Wagon 2.2
We fixed 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335version=180
90
The staged repo is available here:
Hi
I tried to upgrade my org.apache.maven.wagon:wagon-webdav:1.0-beta-2
extension to
org.apache.maven.wagon:wagon-webdav-jackrabbit:2.2 but without luck.
It does not work with Maven 2.2.1 at all (versions 2.0 and 2.1 don't
work too).
Log:
...
SLF4J: Failed to load class
24 matches
Mail list logo
