On 12/7/06, Jason van Zyl [EMAIL PROTECTED] wrote:
Define nice? If it's an installation that is different then something
standard that users typically get then it is a not a good thing. I
can just see the threads now:
I put my global stuff in the /etc/maven/settings.xml and blah blah
blah
In
Jason,
I don't think this page is the good one for the gpg plugin.
Emmanuel
Added: maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/site/apt/usage.apt?view=autorev=482476
A few hints which might help:
1. Maven 2.0.4 has a bug when it comes to resolving dependencies. If a
parent POM defines the version to 1.0 and your POM wants 1.1, the parent
wins.
2. Can you download the missing POM? Sometimes, Maven believes the POM
can't be downloaded because it tries to
User vote (non-binding, on first sight):
+1 for an RPM (because as a non-maven-developer I like it that there can
only be one maven version installed). I am tired of telling people how
to install maven and setting their JAVA_HOME etc.
+1 for writing/stabilizing an RPM plugin that builds
On 12/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
A few hints which might help:
1. Maven 2.0.4 has a bug when it comes to resolving dependencies. If a
parent POM defines the version to 1.0 and your POM wants 1.1, the parent
wins.
Hmm, will need to think about this one.
2. Can you
3. Have you tried to delete your local Maven repo? Or at least the
maven-metadata-*.xml files?
No, this was a last resort.
I'm trying to build from home and see what happens there.
Hmm, I have a clean machine at home and it build fine (except for test
failures...)
Yup, these changes are in trunk now :)
Andy
Jason van Zyl wrote:
On 6 Dec 06, at 8:18 PM 6 Dec 06, Brett Porter wrote:
DefaultPluginManager is the place to look. You are looking for the
creation of a child plexus container, and jar resources being added
to that.
On the code we're about to
Barrie Treloar [EMAIL PROTECTED] schrieb am 07.12.2006 10:50:33:
3. Have you tried to delete your local Maven repo? Or at least the
maven-metadata-*.xml files?
No, this was a last resort.
I'm trying to build from home and see what happens there.
Hmm, I have a clean machine at
Jason van Zyl wrote:
On 6 Dec 06, at 11:38 AM 6 Dec 06, Carl Trieloff wrote:
I have spoken with a few committers over IRC, ApacheCon etc about this
so here it comes. Some of us would like to include maven into Fedora
distributions. There are two components to this, one technical and the
Jesse Kuhnert wrote:
Right. I forgot to mention in my last email that in a good 98% of the
cases the only reason we've ever found out that dojo users install ant
via a package manager is because they are having conflicting library
classpath problems. (related to rhino)
oh, you get those
I played around with this a while back and it appeared that the action
messages were getting dropped in the redirect strategy that we are
using in p-sec to get control back to the users application...
we should flag this as something to review though
jesse
On 12/6/06, Brett Porter [EMAIL
On 6 Dec 06, at 9:41 PM 6 Dec 06, Brett Porter wrote:
Cool. What's next?
1. Make sure that any fixes from the 2.0.x branch are present in
trunk. I've seen a few discrepancies so I would just like to match
those up.
2. Make another drop for the embedder so that Milos and Eugene can
On 6 Dec 06, at 11:14 PM 6 Dec 06, Brett Porter wrote:
On 07/12/2006, at 2:25 PM, Jason van Zyl wrote:
On 6 Dec 06, at 8:16 PM 6 Dec 06, Brett Porter wrote:
I generally agree with what John has said in the thread so far. I
think this is a good thing: a nice out of the box installation
Hi,
What I'm reading below looks exactly like Maven, except for the scope of the
dependencies.
Just for fun, I'll try to make the differences in your system and maven
more concrete. Correct me if I get anything wrong.
In Maven we have 2 types of 'dependencies': artifact dependencies, which
Jason van Zyl wrote:
If the RPM rolled out something that had the same structure as
everywhere else then fine. Limitless options at the infrastructural
level does not help anyone, it's a massive hinderance.
We do already have near limitless options in proxy setup, for better or
worse.
Hey Guys,
I'm seeing some really strange JUnit behavior in
combination with the testing harness and Eclipse EMF.
Someone from the JUnit list suspected that it might be
due to a static in the harness setup.
Here's the scenario:
I'm testing a method, testLoadPomResource()
When I have the
Jason van Zyl wrote:
On 6 Dec 06, at 3:02 PM 6 Dec 06, Carl Trieloff wrote:
John Casey wrote:
Let's start with: What are the requirements?
Regards,
John
yes that is good - I would not see the patches set as something to
commit as is but a prototype to see if it could
be done. we now
Jason van Zyl wrote:
I don't remember a specific instance, but I'm sure there are some who
would like them. Either way, we need to consider Fedora as a consumer
of Maven and that they know what their users want, which apparently is
Maven bundled with Fedora.
I doubt they have asked but I
Rafael Schloming wrote:
Jason van Zyl wrote:
I don't remember a specific instance, but I'm sure there are some who
would like them. Either way, we need to consider Fedora as a consumer
of Maven and that they know what their users want, which apparently
is Maven bundled with Fedora.
I
OK - Got it.
Apparently Eclipse EMF likes
each resourceSet = createResourceSet()
method inside each test case.
Cheers,
- Ole
--- Ole Ersoy [EMAIL PROTECTED] wrote:
Hey Guys,
I'm seeing some really strange JUnit behavior in
combination with the testing harness and Eclipse
EMF.
Ole Ersoy wrote:
OK - Got it.
Apparently Eclipse EMF likes
each resourceSet = createResourceSet()
method inside each test case.
Cheers,
- Ole
you should do all junit setup in setUp() , not the ctor. JUnit creates
all instances in advance and stores them somewhere. This is a fact you
can
It's been a few months now, I would like to release Wagon WebDAV 1.0-beta-2.
There are some URL baseline bugs with creation of collections present in
1.0-beta-1 that have been addressed in 1.0-beta-2-SNAPSHOT.
Usual +1/0-1 (72 hours)
- Joakim
+1
On 7 Dec 06, at 2:39 PM 7 Dec 06, Joakim Erdfelt wrote:
It's been a few months now, I would like to release Wagon WebDAV
1.0-beta-2.
There are some URL baseline bugs with creation of collections
present in
1.0-beta-1 that have been addressed in 1.0-beta-2-SNAPSHOT.
Usual +1/0-1 (72
I would like to get maven-dependency-tree out of SNAPSHOT mode.
I'm proposing making it 1.0-alpha-1.
Found at
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree
It is used by maven-project-info-reports-plugin (2.1-SNAPSHOT) and
archiva (1.0-SNAPSHOT).
Usual voting rules.
Hello,
I did not test this provider, but I'll soon have to use it.
Does it support http/s proxy ?
Thomas
2006/12/7, Joakim Erdfelt [EMAIL PROTECTED]:
It's been a few months now, I would like to release Wagon WebDAV 1.0-beta-2.
There are some URL baseline bugs with creation of collections
In preparation for maven 2.1 and maven-project-info-reports-plugin.
I'd like to see wagon api 1.0-beta-2 released.
And all of the providers based on it.
That would mean the following releases.
1) wagon-provider-api 1.0-beta-2
2) wagon-provider-test1.0-beta-2
3) wagon-file
We use http and https based repositories with wagon-webdav already.
I have no access to a proxy that does https to test that specific
functionality.
Can you assist?
- Joakim
Thomas Recloux wrote:
Hello,
I did not test this provider, but I'll soon have to use it.
Does it support http/s
On Thursday 07 December 2006 16:42, Joakim Erdfelt wrote:
I would like to get maven-dependency-tree out of SNAPSHOT mode.
I'm proposing making it 1.0-alpha-1.
Found at
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree
It is used by maven-project-info-reports-plugin
We use http and https based repositories with wagon-webdav already.
I have no access to a proxy that does https to test that specific
functionality.
Can you assist?
If you mean a proxy serving an https webdav server = Yes
--
Thomas Recloux a.k.a Karmelitre
http://karmelitre.tartachuc.org
This has been corrected in subversion.
[maven-dependency-tree]$ mvn -PsharedResources clean package
...(snip) ...
[maven-dependency-tree]$ jar -tvf
target/maven-dependency-tree-1.0-SNAPSHOT.jar
0 Thu Dec 07 17:38:32 EST 2006 META-INF/
125 Thu Dec 07 17:38:30 EST 2006
2006/12/7, Joakim Erdfelt [EMAIL PROTECTED]:
5) wagon-http-lightweight 1.0-beta-2
Would it be possible to push this patch ?
http://jira.codehaus.org/browse/WAGONHTTP-6
--
Thomas Recloux a.k.a Karmelitre
http://karmelitre.tartachuc.org
+1
Emmanuel
Joakim Erdfelt a écrit :
In preparation for maven 2.1 and maven-project-info-reports-plugin.
I'd like to see wagon api 1.0-beta-2 released.
And all of the providers based on it.
That would mean the following releases.
1) wagon-provider-api 1.0-beta-2
2) wagon-provider-test
+1
Emmanuel
Joakim Erdfelt a écrit :
I would like to get maven-dependency-tree out of SNAPSHOT mode.
I'm proposing making it 1.0-alpha-1.
Found at
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree
It is used by maven-project-info-reports-plugin (2.1-SNAPSHOT) and
+1
(we always release all of wagon together, so only one vote is really
needed)
- Brett
On 08/12/2006, at 8:57 AM, Joakim Erdfelt wrote:
In preparation for maven 2.1 and maven-project-info-reports-plugin.
I'd like to see wagon api 1.0-beta-2 released.
And all of the providers based on
+1 now. (non-binding)
Dan
On Thursday 07 December 2006 17:43, Joakim Erdfelt wrote:
This has been corrected in subversion.
[maven-dependency-tree]$ mvn -PsharedResources clean package
...(snip) ...
[maven-dependency-tree]$ jar -tvf
target/maven-dependency-tree-1.0-SNAPSHOT.jar
On 7 Dec 06, at 6:07 PM 7 Dec 06, Brett Porter wrote:
+1
(we always release all of wagon together, so only one vote is
really needed)
Is that ifNewer thing fixed? The thing causing problems with
deployments?
Jason.
- Brett
On 08/12/2006, at 8:57 AM, Joakim Erdfelt wrote:
In
On Wed, 2006-12-06 at 14:45 -0500, John Casey wrote:
I think it might be smarter to start from first principles on this stuff,
and attempt to create a toolset that would allow us to make RH/Debian/etc.
compatible packages from all maven builds, including Maven itself an Maven's
dependencies.
On 12/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Barrie Treloar [EMAIL PROTECTED] schrieb am 07.12.2006 10:50:33:
3. Have you tried to delete your local Maven repo? Or at least the
maven-metadata-*.xml files?
No, this was a last resort.
I'm trying to build from home and see
About to see if I can use NTLMAPS and instead of using mvn-proxy
I should have just turned on NTLMAPS and re-run the same command,
instead of also adding -cpu -U, but this has now sorted out the issue.
So it looks like mvn-proxy has got garbage data somewhere and causing
maven to fail.
I
on the wagon side, yes. I added getIfNewer to the scp wagon and it
just calls get().
However, we should put additional exception handling into maven-2.0.5
so that it doesn't freak out on older wagon releases. It's on my list.
- Brett
On 08/12/2006, at 10:50 AM, Jason van Zyl wrote:
On 7
+1 (non-binding)
Yes, please!
-Original Message-
From: Joakim Erdfelt [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2006 3:57 PM
To: wagon-dev@maven.apache.org
Subject: [vote] release wagon api and providers
In preparation for maven 2.1 and maven-project-info-reports-plugin.
On 12/8/06, Barrie Treloar [EMAIL PROTECTED] wrote:
About to see if I can use NTLMAPS and instead of using mvn-proxy
I should have just turned on NTLMAPS and re-run the same command,
instead of also adding -cpu -U, but this has now sorted out the issue.
So it looks like mvn-proxy has got
Hi all,
An FYI for those who are interested - the PMC have voted to accept
NMaven (.NET support for Maven) into the incubator, and to work to
incorporate all our existing sandbox efforts into it.
The proposal is here: http://maven.apache.org/proposals/incubator/
nmaven.html
The lists
My vote is for: UR
Cheers,
Rahul
Brett Porter wrote:
FYI. You can vote over at archiva-dev@maven.apache.org
- Brett
Begin forwarded message:
From: Brett Porter [EMAIL PROTECTED]
Date: 13 November 2006 10:34:20 AM
To: archiva-dev@maven.apache.org
Subject: Re: [vote] Archiva Logo
On 11/6/06, Brett Porter [EMAIL PROTECTED] wrote:
Well, its up for discussion. I don't like the idea of having separate
docs per release, since some aspects of docs are updated independent
of version. So, we added the @since flag to mojos and parameters so
that you have an accurate reference
+1
On 12/7/06, Daniel Kulp [EMAIL PROTECTED] wrote:
+1 now. (non-binding)
Dan
On Thursday 07 December 2006 17:43, Joakim Erdfelt wrote:
This has been corrected in subversion.
[maven-dependency-tree]$ mvn -PsharedResources clean package
...(snip) ...
[maven-dependency-tree]$ jar
Issue Subscription
Filter: Design Best Practices (37 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
Ok, this was tough to reach consensus on. Obviously, I waited a lot
more than 72 hours to try and reach it :)
Here is how it panned out:
TL - CS, JL (2 - 1 PMC, 1 User)
UR - NB, JM, BP, EP, EV, JC, TL, DL, JvZ, VS, RT (11 - 8 PMC, 2 Com,
1 User)
LL - RP, WB, MK, HY, NdL, MC, AH, AW, WS, MP,
On Thu, Nov 30, 2006 at 04:26:04PM +0200, Jukka Zitting wrote:
Hi,
On 11/30/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Yep, I know Jason did the change today
What's the plan on resolving the issue? Will the redirect be reverted,
or should I work around the issue for example by explicitly
Running junit test
EclipsePluginUnitTest.testBuildDirectoryList_ShouldUseTestOutputDirFromProjectWhenBuildOutputDirIsStandard
returns results:
Can't canonicalize system path:
C:\TEMP\EclipsePlugin.unitTest.1165557188766\D:\ide\workspace\maven\maven-eclipse-plugin\target\main-output
50 matches
Mail list logo
