I won't fight about it but I dislike the idea of providing web links in
error messages. In a few years from now they might not exist any more or
provide irrelevant information. A stack trace is not pretty but google
doesn't mind that. At least log the stack trace at debug level if you
prefer.
Hi Benson!
Txs for pushing that, looks really good!.
As for compat:
I read your proposal this way: pom5 projects can only be built with mvn3.1 or
mvn4 (or whatever we call it) but while installing/deploying, a pom-4.0 will be
created which can be _consumed_ as dependencies even by mvn2 and/or
On 27 Jul 2011, at 01:27, Ansgar Konermann > wrote:
Am 26.07.2011 00:56, schrieb Kasun Gajasinghe:
So, doesn't having an intermediary layer that will
point to newer set of plugins is justified?
Sure.
Simplest solution that will work: use your own parent pom with an
updated section.
As I
Hi Benson
Thanks for your proposal!
IMHO the pom5 should include some tags like or
and the javadoc
see MPIR-149 MJAVADOC-32
Cheers,
Vincent
2011/7/24 Benson Margulies :
> Since I can't edit the Wiki, I created:
>
> https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3o
settings.xml can include pluginManagement in a profile? I thought you
could only include a few things like repos and properties, at least
that's what the docs say.
http://maven.apache.org/ref/3.0.3/maven-settings/settings.html
On 07/25/2011 06:43 AM, Benson Margulies wrote:
> I don't know about
maven.mdo**
maven
Maven
It's not a work of art, but it gives us something to elaborate that
isn't just a thread in the email archive.
https://cwiki.apache.org/confluence/display/MAVEN/POM-5+compatibility+design
On Tue, Jul 26, 2011 at 8:23 PM, Benson Margulies wrote:
> Duh. I someone didn't end up watching that issue
Duh. I someone didn't end up watching that issue. Off I go to paste.
On Tue, Jul 26, 2011 at 8:20 PM, Brett Porter wrote:
> Are you sure?
>
> https://issues.apache.org/jira/browse/INFRA-3792
>
> I hadn't read it either, assuming you were about to shortly move it once I
> saw that resolved… I gue
Are you sure?
https://issues.apache.org/jira/browse/INFRA-3792
I hadn't read it either, assuming you were about to shortly move it once I saw
that resolved… I guess the loop wasn't closed.
- Brett
On 27/07/2011, at 10:14 AM, Benson Margulies wrote:
> No. I can't paste anything into our wiki a
No. I can't paste anything into our wiki at ASF. I don't have edit
access, and John asked infra for help in giving me edit access, and I
don't think that any help has been forthcoming so far.
On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg wrote:
> sorry, have no google account (and refuse to crea
sorry, have no google account (and refuse to create one).
Cant you just paste it into our Wiki?
LieGrue,
strub
--- On Wed, 7/27/11, Benson Margulies wrote:
> From: Benson Margulies
> Subject: Re: POM5 proposal
> To: "Maven Developers List"
> Date: Wednesday, July 27, 2011, 12:07 AM
> Ping? an
Ping? anybody read this?
On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies wrote:
> Since I can't edit the Wiki, I created:
>
> https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US
>
-
To
I still need to investigate what's happenning with m-site-p 2.3 and Maven 2.2
yes, it's better to have same behaviour with every Maven version
I'll work on it tomorrow
Regards,
Hervé
Le mercredi 27 juillet 2011, Dennis Lundberg a écrit :
> Hervé,
>
> Do you have an idea how to fix this for Mav
Hervé,
Do you have an idea how to fix this for Maven 2?
If you don't, then I'd like to postpone this change to a time when we
have a solution for Maven 2.
I feel that it is better (and easier) if this version of the plugin
behaves the same (as much as possible) when it is run with Maven 2 and
Ma
did you try what an end-user can see when he tries to use an unavailable
protocol?
I'm ok with more detailed error message.
But the stacktrace, which is the only message which is displayed at the end of
Maven reactor run, stating that protocol could not be found, is not helpful:
the detailed err
Am 26.07.2011 21:14, schrieb Ansgar Konermann:
> Am 26.07.2011 01:27, schrieb Kasun Gajasinghe:
I'm sorry, wrong list.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apac
Am 26.07.2011 00:56, schrieb Kasun Gajasinghe:
> So, doesn't having an intermediary layer that will
> point to newer set of plugins is justified?
Sure.
Simplest solution that will work: use your own parent pom with an
updated section.
Ansgar
-
Am 26.07.2011 01:27, schrieb Kasun Gajasinghe:
> Manually, editing
> the pom with the available plugin versions is much complicated,
http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html
Automate this using a CI server and you're probably mostly done.
Best
Ansgar
--
He could just fork it into the sandbox, and apply the changes there and get
you to merge them back.
All ASF committers have write access to our sandbox.
On 26 July 2011 14:19, Barrie Treloar wrote:
> 2011/7/26 Łukasz Dywicki :
> > Hey Maven developers,
> > I would ask about maven-eclipse plugin
OK,
1. I do not use eclipse... my fingers have learned IntelliJ IDEA, and I am
not switching if I can help it, so these are just general recommendations.
2. Did you patch include tests. Ideally the tests should fail until the rest
of your patch is applied and pass thereafter.
3. Once your patch
2011/7/26 Łukasz Dywicki :
> Hey Maven developers,
> I would ask about maven-eclipse plugin. Seems that source code activity is
> going down. Latest commit in github mirror of maven plugins (and svn
> repository) which changes anything in plugins goals is dated to November 01,
> 2010. It means
Hey Maven developers,
I would ask about maven-eclipse plugin. Seems that source code activity is
going down. Latest commit in github mirror of maven plugins (and svn
repository) which changes anything in plugins goals is dated to November 01,
2010. It means that during last 9 moths there was no
Hello
We only need to be ready to answer to the same question *a lot* :-)
--
Olivier
Le 25 juil. 2011 00:26, "Hervé BOUTEMY" a écrit :
> ok, I added a doc to add a protocol and improved the error message [1]
>
> I think we can safely do the change proposed in MSITE-598: users won't be
lost
> (of
23 matches
Mail list logo
