Jörg Schaible wrote on Thursday, April 05, 2007 8:28 PM:
Daniel Kulp wrote:
Jörg,
With maven 2.0.5, did you try running:
mvn dependency:analyze
to see if it says there are potential problems with versions or
similar? That was supposed to flag potential issues.
I'll try
Hi Brian,
Brian E. Fox wrote on Monday, April 23, 2007 2:42 PM:
Everyone keeps referring to bundles that are known to work together.
Come someone produce an example of plugins that are incompatible with
each other?
Annoying: http://jira.codehaus.org/browse/MOJO-641
I haven't seen this and
Hi devs,
how will Maven handle the problem of a dependency that should be used in two
different versions? This applies to all project that release a new (normally
major) version that can be used with the old version at the same time. This is
currently possible at least with:
jmock 1.x / jmock
Jason van Zyl wrote on Wednesday, April 25, 2007 2:41 PM:
On 25 Apr 07, at 8:09 AM 25 Apr 07, Jörg Schaible wrote:
Hi devs,
how will Maven handle the problem of a dependency that should be
used in two different versions? This applies to all project that
release a new (normally major
Jason van Zyl wrote on Wednesday, April 25, 2007 3:26 PM:
On 25 Apr 07, at 9:00 AM 25 Apr 07, Jörg Schaible wrote:
Jason van Zyl wrote on Wednesday, April 25, 2007 2:41 PM:
On 25 Apr 07, at 8:09 AM 25 Apr 07, Jörg Schaible wrote:
Hi devs,
how will Maven handle the problem
Arik Kfir wrote on Wednesday, April 25, 2007 4:15 PM:
Doesn't the jmock2 contains the classes of jmock1 as well?
No. They should be used side-by-side.
And this is a general problem. No project will change their domain/packages and
adjust artifact names, simply because Maven cannot handle the
Grzegorz Slowikowski wrote on Thursday, April 26, 2007 10:47 AM:
Hi
Look at hibernate2 and hibernate3 artifacts. They have hibernate and
org.hibernate
groupIds respectively, so they can be used together (java package
names are different too).
This is IMO the proper way to do this.
Hi Jason,
Jason van Zyl wrote on Thursday, April 26, 2007 1:52 PM:
On 26 Apr 07, at 6:05 AM 26 Apr 07, Arik Kfir wrote:
IMO, if the project claims to be backwards-compatible, then it should
include the older classes. If they can exist side-by-side, there
should be no issue.
I don't
Jason van Zyl wrote on Thursday, April 26, 2007 3:21 PM:
On 26 Apr 07, at 8:20 AM 26 Apr 07, Jörg Schaible wrote:
[snip]
Therefore the slots. The project itself can introduce them, if two
major versions can be used at same time. Think about a hypothetical
commons-logging 2.0
Jason van Zyl wrote on Thursday, April 26, 2007 4:41 PM:
On 26 Apr 07, at 10:12 AM 26 Apr 07, Jörg Schaible wrote:
Jason van Zyl wrote on Thursday, April 26, 2007 3:21 PM:
On 26 Apr 07, at 8:20 AM 26 Apr 07, Jörg Schaible wrote:
[snip]
Therefore the slots. The project itself can
Andrew Williams wrote on Saturday, April 28, 2007 7:06 PM:
On 26 Apr 2007, at 13:20, Jörg Schaible wrote:
Hi Jason,
Therefore the slots. The project itself can introduce them, if two
major versions can be used at same time. Think about a hypothetical
commons-logging 2.0 (it is discussed
Carlos Sanchez (JIRA) wrote on Wednesday, May 02, 2007 6:53 PM:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1511?page=com.atla
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94828 ]
Carlos Sanchez commented on MAVENUPLOAD-1511:
Folks,
I have a weird problem with this release. In a multi-project setup is one of my
submodules failing, because the surefire plugin is missing classes in the class
path when install is invoked from above. install works fine from the sub
project level though. Now the really weirtd part: I
Jason van Zyl wrote on Friday, June 15, 2007 4:28 PM:
On 15 Jun 07, at 7:22 AM 15 Jun 07, Jörg Schaible wrote:
Folks,
I have a weird problem with this release. In a multi-project setup
is one of my submodules failing, because the surefire plugin is
missing classes in the class path when
Kenney Westerhof wrote:
Hi,
Just did some test wrt MNG-2340 (using maven 2.0.7 and 2.0.6), and this is
what I found:
P with dependencyManagement for lucene 1.3
|
+ my-dep with dependency on lucene 1.4.3
+ my-app with dependency on my-dep
(I modified the attached project locally;
Kenney Westerhof wrote:
[snip]
The meaning of depMgt is different, applied to either local deps or
transitive deps, and it's not consistent.
This somewhat describes the situation:
- depMgt for artifact X is used to provide defaults for direct
dependencies of artifact X,
and for
Cabasson Denis wrote on Tuesday, July 03, 2007 4:57 PM:
About this link, why couldn't we have a consistent behaviour
for javadoc and sources jar?
[snip]
Because here it becomes IDE dependent. Eclipse displays Javadoc automatically
if the sources are available. No need to download Javadocs
Wendy Smoak wrote on Monday, September 03, 2007 7:41 PM:
On 9/1/07, Brett Porter [EMAIL PROTECTED] wrote:
Like the other poll, I'd like to hear from as many people as possible
their opinion this topic (even if you just want to say '0' so we
know where you stand).
[ ] (A) Having a way to
- calling a goal that does not need a POM in the current dir in a multi-project
root
Examples:
mvn install:install-file args
mvn archetype:create args
Maven walks down the complete project hierarchy ...
Brett Porter wrote on Tuesday, September 04, 2007 10:15 AM:
- invalid lifecycle phase
Brett Porter wrote on Tuesday, September 04, 2007 10:31 AM:
On 04/09/2007, at 6:24 PM, Jörg Schaible wrote:
- calling a goal that does not need a POM in the current dir in a
multi-project root Examples:
mvn install:install-file args
mvn archetype:create args
Maven walks down
Mauro Talevi wrote:
- Classloader problems: often difficult to debug them when artifacts are
coming from different
transitive sources. Would be great to have a better way to display a
trace of the dependency
tree, without being swamped by all the non-dependency noise. Maybe a
new debug
Jason van Zyl wrote on Wednesday, September 26, 2007 7:59 AM:
On 25 Sep 07, at 10:21 PM 25 Sep 07, Brian E. Fox wrote:
This is interesting functionality that the dev team should be aware
of. I know it's frequently asked how to extend a plugin.
We could definitely integrate this method,
Folks,
are there any updates for Maven 2.0.8? What's left to finalize the release?
We're still stuck at M205 due to regressions in M206+M207. All of this has been
solved months ago. I face meanwhile quite daily people dropping by in my office
with Maven problems where I have to say, it is
Hi Brian,
Brian E. Fox wrote:
I've posted the snapshot binaries at
http://people.apache.org/~brianf/2.0.8 for testing purposes.
We need to
wait for the release plugin 2.0-beta-7 vote before doing an actual
release on 2.0.8 so in the meantime, I would ask that
everyone give this
a whirl and
Jason Dillon wrote:
So, who put the groovy-all 1.0 pom in the central repository?
This has *broken* a lot of projects and has made many releases
unbuildable...
Who did this and why? Anyone know?
Welcome in the camp ;-)
We switched to 1.1-rc-1, but as stated in one of the issues, the
Milos Kleint wrote:
On Nov 6, 2007 4:35 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 6 Nov 07, at 4:00 AM 6 Nov 07, Milos Kleint wrote:
Hello,
I've got a working prototype of the toolchains proposal. I'm able to
define
the jdk toolchains and have them used in a project. Works
Brian E. Fox wrote:
Yeah that makes sense. Which way is it now?
At least M1 and M205 have test-classes first. The generated Eclipse projects
also. Don't know about other IDEs, but I guess you will get a lot of feedback
if it works the other way round again ;-)
From: Max Bowsher
Sent:
Hi folks,
can someone shed some light onto the release:prepare mechanism?
We use since long ago an own plugin, that accesses a secondary artifact of a
dependency. This worked like charm ... until now. We have now the new
situation, that the secondary artifact is build in the same multi project
Graham Leggett wrote:
On Fri, November 23, 2007 10:30 am, Jörg Schaible wrote:
We use since long ago an own plugin, that accesses a secondary
artifact of a dependency. This worked like charm ... until now. We
have now the new situation, that the secondary artifact is build in
the same multi
yBenjamin Bentmann wrote:
There seems to be resources under:
maven-embedder\src\test\error-reporting-projects\testReportUnr
esolvableArtifactWhileAddingExtensionPlugin\local-repo\org\apa
che\maven\errortest\testReportUnresolvableArtifactWhileAddingE
xtensionPlugin-maven-plugin
that
Well, I'd like to improve rather the dependencies element:
dependencyManagement
dependencies
dependency groupId=javax.activation artifactId=activation
version=1.1/
/dependencies
dependencies groupId=org.apache.maven.archiva version=1.1-SNAPSHOT
dependency
Hello Maven team,
is it possible to sync http://myfaces.zones.apache.org/dist/maven-repository to
ibiblio? It contains newer facelet versions.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Hi Jan,
Jan Nielsen wrote on Friday, August 11, 2006 11:32 PM:
I'm a newbie to Maven and Continuum, so aplogies if this is
obvious. I'm
not sure if this is a Maven question or Continuum question,
or perhaps
both, so I thought I'd try here first.
When dealing with multiple projects which
Hi folks,
can somebody sync the M2 repo from Codehaus please? XStream has released 48h
ago and it does not yet show up at ibiblio ...
Thanks,
Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Vincent Massol wrote on Monday, August 28, 2006 2:00 PM:
Thanks Vincent. You might want to update
http://maven.apache.org/guides/development/guide-building-m2.h tml
(this is what I was looking at).
In addition why not simply add the snapshot repo to the top level
pom.xml in components?
Mike Perham wrote:
That's too bad. I think deps at the same level should pick the
greater, not randomly. MNG-1577 would help a lot here.
I'm also finding that exclusions are insideous - I can't see where an
exclusion is coming from so I can't determine which module is
erroneously
Jason van Zyl wrote:
On 3 Oct 06, at 6:05 AM 3 Oct 06, Jörg Schaible wrote:
Hi folks,
where is the code that defines the different javadoc tags that are
used to
generate the plugin.xml? Especially I am looking for a flat list/array
definition:
Two parameters are arrays, but I do
Nathan Beyer wrote:
Xerces doesn't build with either Maven 1 or Maven 2; everything is
built with a custom Ant script. I created a custom POM and deployed
using deploy:deploy-file for the binary and source JAR to m2 and then
to m1 by setting the repo type to legacy.
I essentially
Carlos Sanchez wrote:
sorry, I forgot, if you build with ant you deploy to the m1 repo. The
m2 is only for m2 builds because it's more accurate and has some
metadata.
Files deployed to any of the repos will be available to both m1 and m2
users, so just deploy to one of them.
Yes, but
Hi Jason,
download of SNAPSHOT dependencies does not work at all in M2.0.4:
http://jira.codehaus.org/browse/MNG-1908
- Jörg
Jason Dillon wrote on Saturday, October 14, 2006 10:17 PM:
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
Running mvn with -U -cpu should fix that (or wait 24
[EMAIL PROTECTED] wrote on Monday, October 16, 2006 9:05 AM:
Joakim Erdfelt [EMAIL PROTECTED] schrieb am 13.10.2006 20:06:51:
==
=
== LICENSE FILE / HEADER
The LICENSE file is a unique monster in the world of
Hi Jason,
Jason Dillon wrote:
I think I have tracked this down... looks like ${pom.version} is
getting resolved to a timestamp version instead of the value it its
parents version element.
Is this expected?
If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
dependency
Hi Dennis,
Dennis Lundberg wrote:
[snip]
==
--- maven/plugins/trunk/maven-clean-plugin/pom.xml (original) +++
maven/plugins/trunk/maven-clean-plugin/pom.xml Mon Oct 16 10:55:07 2006
@@ -9,7 +9,7 @@
Jason van Zyl wrote on Thursday, October 19, 2006 12:48 AM:
On 18 Oct 06, at 4:18 PM 18 Oct 06, Dennis Lundberg wrote:
Jörg Schaible wrote:
Hi Dennis,
Dennis Lundberg wrote:
[snip]
=
=
--- maven/plugins/trunk
Jason van Zyl wrote on Thursday, October 19, 2006 11:14 PM:
I think skipping release numbers is Bad Thing(tm). It would certainly
confuse users if we release Maven 2.0.7 next.
Anything 2.0.4 would be welcome ... hehehe
Technically you could simply use an additional number at the end:
[EMAIL PROTECTED] wrote on Friday, October 20, 2006 11:22 AM:
Jörg Schaible [EMAIL PROTECTED] schrieb am
20.10.2006
10:35:18:
Jason van Zyl wrote on Thursday, October 19, 2006 11:14 PM:
I think skipping release numbers is Bad Thing(tm). It would
certainly confuse users if we release
Matthew Beermann wrote on Thursday, October 26, 2006 5:27 PM:
Are there any plans to release a new version of the Release
plugin any time soon? It's been since last May (!)...
The particular feature we're most interested in is for it to
insert explict versions of the build plugins while
Christoph Kiehl wrote on Tuesday, January 09, 2007 4:28 PM:
Hi,
I was wondering if anyone is working on
http://jira.codehaus.org/browse/MECLIPSE-44 ? I definitely need this
feature, because I got a multimodule project of which I need to keep
multiple versions (branches) in _one_ eclipse
Ralph Goers wrote on Thursday, January 11, 2007 6:38 AM:
Well, if you absolutely positively promise to release 2.0.6 when
MNG-1577 is applied ;-) . Seriously, it has been rather frustrating
as I can't even use Maven 2 without that fix.
Yeah, not another 9 months please, I've reported this
Mark Hobson wrote:
Hi there,
I'd like to add some further goals to help with managing dependencies:
1) List all resolve dependencies for the current project
2) Compare all resolved dependencies between the current project and a
previous release
The question is where should they
Mark Hobson wrote:
On 17/01/07, Jörg Schaible [EMAIL PROTECTED] wrote:
What we have is also a plugin displaying a dep tree for one of
compile/runtime/test dependencies. This is really helpful.
Do you have this internally? I haven't seen that functionality within
the help plugin.
Yes
Hi Mark,
Mark Hobson wrote:
On 17/01/07, Brett Porter [EMAIL PROTECTED] wrote:
[snip]
Is the analyse goal like the dependency convergence report? Can any
of the code be shared?
The analyse goal reports on the dependencies declared in the POM and
the dependencies actually referenced by the
Mark Hobson wrote:
On 17/01/07, Jörg Schaible [EMAIL PROTECTED] wrote:
Yes, it's an own internal plugin. We have
info:deps-scope
Unfortunately it is developed at the office and my employer refused to
sign the CCLA. Therefore the code is tainted for contribution :(
No worries, we have
Hi Mark,
Mark Hobson wrote on Wednesday, January 17, 2007 9:56 PM:
On 17/01/07, Jörg Schaible [EMAIL PROTECTED] wrote:
[snip]
I'll post tomorrow an output from the command line to demonstrate
how it looks like. If your reactor build counts ~100 modules, the
filter is quite helpful
Hi Brian,
Brian E. Fox wrote on Thursday, January 18, 2007 7:53 AM:
I guess I'm a little behind in this thread:
1st, I think dependency:list is effectively the same as the
existing dependency:resolve is it not? The artifacts need to
be resolved if you are going to include transitive stuff.
Mark Hobson wrote on Thursday, January 18, 2007 2:52 PM:
On 17/01/07, Jörg Schaible [EMAIL PROTECTED] wrote:
Perhaps, but I was thinking about the number of goals once we
introduce tree and list goals for every scope. Would we name them
dependency:compile-tree, dependency:compile-list, etc
Brian E. Fox wrote on Thursday, January 18, 2007 3:34 PM:
This is true, I haven't used dependency:resolve until you
mentioned it.
I
guess the only difference is that it doesn't show the scope of the
dependencies, but this could be easily resolved.
Heh, actually I just added that feature
dvicente wrote on Wednesday, January 24, 2007 8:00 AM:
i have many problems with IRC.
In the place where i work, IRC is forbidden and at home, i can't
connect to irc.codehaus.org with mIRC.
i don't know why.
But thanks for your help
Having the same problems, but you may use
Brett Porter wrote:
On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote:
AFAIK the reason the poms are excluded is because they're modified
by the
release process; if the check for local modifications is run after
the pom
is modified, it's impossible to do a release. So this could
probably
Hi Jason,
Jason van Zyl wrote:
Hi,
After looking at MNG-2794 I don't think it's something we should fix
change.
The 2.0.4 release was working in a way contrary to our documentation
in that the nearest with 2.0.4 was not being selected and it is with
2.0.5. So we either fix it and then
Jason van Zyl wrote on Monday, February 12, 2007 7:12 AM:
On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote:
Are there release notes on the major changes or significant fixes
which we might need to adapt to and/or be able to remove local
build hacks? The JIRA road map is kinda hard
Congrats! Really waited long for this. But I know the huge effort and work
behind this - so a biig THANK YOU GUYS!
- Jörg
Jason van Zyl wrote:
The Maven team would like to announce the release of Maven 2.0.5.
You can find the roadmap for the release here:
Mark Hobson wrote:
On 26/02/07, Jason van Zyl [EMAIL PROTECTED] wrote:
If you're an apache committer then you're free to work no it and you
already have permission. If you're not then mojo might be better
where we can give you access to work on it.
I've got mojo rights but not apache
Mark Hobson wrote:
On 26/02/07, Jörg Schaible [EMAIL PROTECTED] wrote:
I can act as relay. Unfortunately I can only work on it in the evening, I
cannot commit from the office (although we need the functionality there
grr).
Oh the irony ;)
The sandbox already contains shared/maven
Brian E. Fox wrote:
Jorg,
Make a branch off of the trunk for now. Since these are separate goals, a
merge will be easy later after the release.
OK!
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Jörg Schaible wrote:
Brian E. Fox wrote:
Jorg,
Make a branch off of the trunk for now. Since these are separate goals, a
merge will be easy later after the release.
OK!
Merged in the sandbox.
- Jörg
Dan Tran wrote:
I think you broke the convention of 2 spaces indentation for xml file ;-)
Well, no. All the lines had tab indention except the new ones I added. So I
converted them into tabs also ;-)
- Jörg
On 2/26/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: joehni
Date: Mon
Jason Dillon wrote:
Ya, having plugins being able to talk to each other in abstract ways
would be very good...
But for this... its should be able to check the last modified + size
to see if it really needs to cp or not. Its a minor detail, but will
help for large projects where seconds
Unfortunately deleting is not enough. Have a look at the change history.
:(
Emmanuel Venisse (JIRA) wrote on Wednesday, February 28, 2007 4:16 PM:
[
http://jira.codehaus.org/browse/CONTINUUM-713?page=com.atlassi
an.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse
Trygve Laugstøl wrote on Thursday, March 01, 2007 12:11 PM:
Jörg Schaible wrote:
Dan Tran wrote:
I think you broke the convention of 2 spaces indentation for xml
file ;-)
Well, no. All the lines had tab indention except the new ones I
added. So I converted them into tabs also
Brian E. Fox wrote:
How close is the dependency analyzer shared piece from coming out of the
sandbox and being released?
It's Mark's code, but from my PoV it simply works. So it should no problem
to release some kind of alpha version, indicating that Mark is going to add
more stuff.
- Jörg
Jason van Zyl wrote on Friday, March 16, 2007 1:33 AM:
Hi,
After working with it a little this week I would like to propose to
make MNG-1577 behavior introduced the default. Builds are completely
and totally unpredictable without this behavior. The behavior in
2.0.5 is fundamentally
It is very unfortunate, that you took the same goal that was introduces by the
maven-dependency-analyzer-plugion, that is currently merged in the sandbox in a
branch.
I am no committer, so my vote is non-binding, but my choice is -1 because of
this.
- Jörg
Brian E. Fox wrote on Sunday,
Max Bowsher wrote on Monday, March 19, 2007 12:00 PM:
Jörg Schaible wrote:
It is very unfortunate, that you took the same goal that was
introduces by the maven-dependency-analyzer-plugion, that is
currently merged in the sandbox in a branch.
TTBOMK,
??
it is not possible for one plugin
Hi Brian,
Brian E. Fox wrote on Monday, March 19, 2007 1:25 PM:
The analyze goal has already been merged into the plugin and
is the same here... it does the class level analysis. There
is also analyze-dep-mgt to do the 1577 check. Analyze will do
both so there's no clash here. Take a look at
Hi Jason,
Jason van Zyl wrote on Saturday, March 24, 2007 2:32 PM:
[snip]
2.) The dao-impl Module depends on Hibernate, but Libraries that
are used by Hibernate (e.g. cglib, asm and antlr) shall not be used
directly in the dao-impl Module but shall only be used at runtime of
tests.
Hi Max,
Max Bowsher wrote on Thursday, March 29, 2007 1:46 PM:
Max Bowsher wrote:
John Casey wrote:
Max: I'm tempted to say that we should look for decimal versions of
common octal expressions, then prefix the rest with '0' to ensure
they're interpreted as octal (unless they have 0x in
Max Bowsher wrote on Thursday, March 29, 2007 3:26 PM:
Jörg Schaible wrote:
[snip]
Note: Integer.decode(String) is not used here because it will not
handle negative hex-coded integer values. With this approach you can
express -1 as 0x ...
The whole point here is to maximize
Congrats and thanks to all the people working on it! Especially MGN-1577 ...
- Jörg
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5
A dependencyManagement section overwrites the scope of the currently built
artifact (MNG-2919) ... :-/
Heads-up: 2.0.6 is listed in JIRA still as unreleased ... ;-)
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
The Apache Maven team would like to announce the availability of
Maven
private version of the plugin, simply
by removing the dep to the antrun plugin and copying that code (into a new
package). That version runs fine. So the problem seems basically a result from
this unfortunat dep to a different plugin instead of a shared component ...
- Jörg
Jörg Schaible wrote
Hi folks,
after some hours testing M206 and looking for solutions, I am quite helpless
with our build that is broken if I run a multi-project build. Part of this
build is the creation of an ejb-client jar and another artifact that is
dependend on it. Unfortunately the dependent artifact cannot
this with one of the staged versions
that were available for over a week.
Make me a test project that displays the problem and I will track it
down.
Jason.
On 5 Apr 07, at 5:04 AM 5 Apr 07, Jörg Schaible wrote:
Hi folks,
after some hours testing M206 and looking for solutions, I am
Piotr Tabor wrote:
Hello,
It can be connected with the bug:
http://jira.codehaus.org/browse/MNG-2871 (it's old bug - since at least
2.0.4).
I will try to repeat it/look at it today evening.
Don't know. If I go back to M205 it works perfectly. So something in M206
triggers this now ...
Daniel Kulp wrote:
Jörg,
With maven 2.0.5, did you try running:
mvn dependency:analyze
to see if it says there are potential problems with versions or similar?
That was supposed to flag potential issues.
I'll try it in a week ;-)
- Jörg
Joakim Erdfelt wrote:
I still use 2.0.5 daily at the office.
I do have 2.0.7 and 2.0.8 installed too, but there's some bad
juju (re:
bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight
http, non-projects (archetype, install-file, deploy-file, eclipse,
etc...) and also
Dennis Lundberg wrote:
Jörg Schaible wrote:
[snip]
Additionally I would really appreciate if the plugin
documentation would also document the minimal Maven version.
Normally you simply notice when the plugin breaks your build
claiming it needs a newer version. This is especially nasty
[EMAIL PROTECTED] wrote:
nicolas,
I won't speak for Brian, but I thought his intention was to lock down
plug-ins that only affect the build cycle.
Shouldn't the generated reports of a release also be reproducable? However,
anone noticed that a plugin with a locked version in the
Works fine for our builds :)
Brian E. Fox wrote:
We made a minor tweak to the dependency order processing. See
http://jira.codehaus.org/browse/MNG-3494 for more details.
RC6 is staged at:
http://people.apache.org/~brianf/staging-repository/org/apache
/maven/apa che-maven/
Hi folks,
developing a new plugin I made usage of plexus-utils 1.5.1. Unfortunately this
fails when I try to run the plugin in a real project, because some classes seem
outdated (missing method in FileUtils):
= %
[FATAL ERROR]
Jörg Schaible wrote:
Hi folks,
developing a new plugin I made usage of plexus-utils 1.5.1.
Unfortunately this fails when I try to run the plugin in a
real project, because some classes seem outdated (missing method in
FileUtils):
= %
[FATAL ERROR
But you have to be aware of the downside: You cannot upgrade the
compiler-plugin anymore without creating a new version of your plugin. Any
plugin is loaded once and the first one wins. Nice effects in reactor builds ;-)
walid joseph Gedeon wrote:
Indeed! Thanks :-)
So, for the summary,
Benjamin Bentmann wrote:
Solved, the dependency was inherited transitively by
maven-artifact-2.0.9.
You should never rely on transitive dependencies if you directly use its
classes/methods in your code but always declare them directly. The goal
dependency:analyze
can help you a big deal
On Mittwoch, 30. April 2008, William Ferguson wrote:
As Benjamin points out at the end of that Jira, the current behaviour is
there to deal with use of libraries containing classes that extend classes in
other libraries.
Seems to me that we need a way to differentiate in our projects which
Stephen Connolly wrote:
On Wed, Jul 23, 2008 at 1:39 AM, Brett Porter
[EMAIL PROTECTED] wrote:
On 23/07/2008, at 1:34 AM, Jason van Zyl wrote:
Ok,
I have a package for the new 140 version as that's what I'm using
but what they have in central currently doesn't use classifiers
which
Stephen Connolly wrote:
On Wed, Jul 23, 2008 at 9:22 AM, Jörg Schaible wrote:
Another prominent use case are ejb-client artifacts. They do
normally not have the same dependencies as the EJB itself.
Is/should that not be more a case of a separate artifact rather than
the same artifact
a)
Hervé BOUTEMY wrote:
Hi,
While working on Report Encoding Configuration proposal [0], 2
options were discussed lately for default value [1]:
a) use fixed UTF-8 encoding
b) use same encoding as source files
Both options seem viable: choosing between them will be a question of
Hi,
John Casey wrote:
Hi,
Here's your daily dose of Maven 2.0.10! I've fixed the regressions
pointed out in RC4, and added integration tests to guard
against their
reintroduction. The new release candidate can be found here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC
Hi Mauro,
Mauro Talevi wrote:
John Casey wrote:
I've checked the maven core and plugins builds, and they're both
running around 30s longer than with 2.0.9, with slightly less memory
consumption. Other builds I've tried are running nearer to +15s over
2.0.9.
Here's a benchmark done on a
Hi Brett,
Brett Porter wrote:
I think it's something to put in the RC post, focus on testing:
- interpolation
- deployment and proxies
- any reproducible, consistent speed degradation
It would probably still be worth inspecting the performance with a
tool sucha s yourkit... Jörg is there
1 - 100 of 421 matches
Mail list logo
