On Sat, Mar 15, 2008 at 9:29 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
With Maven 2.0.8, it fails after ~15 min complaining that the
archiva-docs zip file is missing.
And once I get past that, assuming the plexus runtime standalone app
is still *supposed* to work, it won't start because...
On 17/03/2008, at 5:11 AM, Wendy Smoak wrote:
On Sat, Mar 15, 2008 at 9:29 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
With Maven 2.0.8, it fails after ~15 min complaining that the
archiva-docs zip file is missing.
And once I get past that, assuming the plexus runtime standalone app
is still
On Sun, Mar 16, 2008 at 1:56 PM, Brett Porter [EMAIL PROTECTED] wrote:
I'm expecting we will distribute based on the jetty + war runtime instead
for 1.1.
And does that work? I see archiva-standalone/archiva-jetty, and
MRM-688 but not much else. Executing ./archiva start makes it print a
Oh?
Didn't know that spring-test even existed.
Once we start migrating away our plexus scaffolding to spring, wouldn't
we need spring too?
-Joakim
Brett Porter wrote:
On 16/03/2008, at 2:15 PM, [EMAIL PROTECTED] wrote:
* Adding spring as default dependency.
Why is this needed? I would
On 17/03/2008, at 2:05 PM, Wendy Smoak wrote:
On Sun, Mar 16, 2008 at 7:13 PM, Maria Odea Ching
[EMAIL PROTECTED] wrote:
Hmm, the jetty bundle should be working.. it already worked for me
before. I
tried it again today and was able to start it. I'm running on Linux
btw.
Wendy, did you
On Mon, Mar 17, 2008 at 11:53 AM, Brett Porter [EMAIL PROTECTED] wrote:
On 17/03/2008, at 2:05 PM, Wendy Smoak wrote:
On Sun, Mar 16, 2008 at 7:13 PM, Maria Odea Ching
[EMAIL PROTECTED] wrote:
Hmm, the jetty bundle should be working.. it already worked for me
before. I
tried it again
2008/3/16, Joakim Erdfelt [EMAIL PROTECTED]:
The approach nicolas took in MNG-3407 is strange. I don't understand
the whole {0} idea. Wouldn't it make more sense to base mirrorOf on
host or url instead?
That way the mirror section can be wrangled in a more sane way?
The idea is to force
I've been using the snapshot for quite a while, and it works very well.
So here's my +1!
Thanks Arnaud :-)
--
Fabrice
- [EMAIL PROTECTED] -
On Sat, Mar 15, 2008 at 1:30 AM, Arnaud HERITIER [EMAIL PROTECTED]
wrote:
Hi,
We solved more than 50 issues:
Hi,
today I learned that plexus-utils is not fully shaded in the core (MNG-2898,
r522313). While I can understand the requirement to share Xpp3Dom and the
Xml* APIs, I wonder why the MX* implementation classes cannot be shaded.
These aren't part of any public method signatures shared with
Quick update
To get this working correctly for CXF, I need to release new versions of
three things:
1) apache-jar-resource-bundle - contains the new resources. (thanks
David)
2) maven-shade-plugin (1.0.1) - very minor bug fix to the transformer
that merges the NOTICE files together.
+1
fabrizio
On Sat, Mar 15, 2008 at 1:30 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=HtmlprojectId=11133
Important changes are :
- Add support for WTP 2.0
- Add support for
+1
On Fri, Mar 14, 2008 at 5:30 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=HtmlprojectId=11133
Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
+1
Le samedi 15 mars 2008, Arnaud HERITIER a écrit :
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=Ht
mlprojectId=11133 Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
- Improve RAD6 support
-
I've never thought it was sane in the first place...
I don't understand why the artifact servers (archiva et al) can't just
respond in the same way that an ordinary proxy server does, without
all this mirrorOf mucking about. Working on two or three independant
projects and my settings.xml is a
On 16-Mar-08, at 11:39 AM, Nigel Magnay wrote:
I've never thought it was sane in the first place...
It is. Ultimately a repository manager should requires users to point
at one URL, period. All control must reside in the repository manager
or it's a configuration nightmare. Even if you
Have you got a description of how you think it ought to work?
I quite like the ability of downloading projects that rely on 3rd
party repos, and having them magically work without having to do
anything (which is why I have a distaste for having to go through a
On 17/03/2008, at 6:03 AM, Jason van Zyl wrote:
All control must reside in the repository manager or it's a
configuration nightmare.
Sorry, but I have to disagree. A repository manager is an optimisation
(and best practice) in using Maven, but not a pre-requisite. Let's not
forget the
On 16-Mar-08, at 1:25 PM, Nigel Magnay wrote:
Have you got a description of how you think it ought to work?
I will do a demo sometime this week at EclipseCon, and I'm happy to
share the configuration I have. But it should be as simple as
described. One place to go, at least in a
On 16-Mar-08, at 3:28 PM, Brett Porter wrote:
On 17/03/2008, at 6:03 AM, Jason van Zyl wrote:
All control must reside in the repository manager or it's a
configuration nightmare.
Sorry, but I have to disagree. A repository manager is an
optimisation (and best practice) in using
The 'id' concept in Maven is fundamentally broken because it's not a
unique ID. It should be something specified in the repository itself
and validated against.
That said, the URL isn't a perfect replacement - for one it's longer,
secondly it may not be unique (such as mirrors, eg. ibiblio
On 16-Mar-08, at 3:28 PM, Brett Porter wrote:
On 17/03/2008, at 6:03 AM, Jason van Zyl wrote:
All control must reside in the repository manager or it's a
configuration nightmare.
Sorry, but I have to disagree. A repository manager is an
optimisation (and best practice) in using
Not that it's entirely relevant, but making the assumption this is
archiva motivated is not completely out of the blue. The unit test
mentions archiva, the jira mentions archiva, the only site docs I
noticed being updated showed how this was used with archiva, the
developer that wrote committed
On 17/03/2008, at 9:44 AM, Jason van Zyl wrote:
On 16-Mar-08, at 3:28 PM, Brett Porter wrote:
On 17/03/2008, at 6:03 AM, Jason van Zyl wrote:
All control must reside in the repository manager or it's a
configuration nightmare.
Sorry, but I have to disagree. A repository manager is
Forking the other thread.
Maven still needs to work properly without a repository manager (even
if it is a good practice to use one). In my opinion, that means:
- proper unique identifiers for repositories (my preference would
actually be to control this by group ID, but I see too many
Nicolas', I liked change as it allows you to be more concise in
settings while still getting all the benefits, though it does assume a
1-for-1 proxying of remote repositories in your repository manager,
which is a good practice to follow anyway IMO. If you hit an id that
you haven't
On Sun, Mar 16, 2008 at 10:35 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 16-Mar-08, at 1:25 PM, Nigel Magnay wrote:
Have you got a description of how you think it ought to work?
I will do a demo sometime this week at EclipseCon, and I'm happy to
share the configuration I have.
On 17/03/2008, at 9:49 AM, Brian E. Fox wrote:
Not that it's entirely relevant, but making the assumption this is
archiva motivated is not completely out of the blue. The unit test
mentions archiva, the jira mentions archiva, the only site docs I
noticed being updated showed how this was used
On 17/03/2008, at 10:20 AM, Nigel Magnay wrote:
I get the central place to go, but I'm still having a hard time
getting why a repository manager couldn't do all that, today, by
acting as an HTTP proxy for all requests. It can look a the URL it's
being requested, and say 'hmm, I cache that
For those who have the time to review it I deployed the web site here :
http://people.apache.org/~aheritier/stage/sites/maven-eclipse-plugin-2.5/index.html
cheers
Arnaud
On Sat, Mar 15, 2008 at 1:30 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi,
We solved more than 50 issues:
Frankly, I think you should have given Nicolas the benefit of the
doubt before charging forth to rollback his commit, and just asked the
question here like I did in February when I had a suggestion about the
original implementation.
Given that the change amounted to about 3 lines of code and
That sounds good to me, and I see where the identifiers have come in;
I think you could do without them though, and just use the repository
URI as the identifier :-
For 'external' mirrors, accessed directly and not through a repo manager:
Say you have repo1.maven.org/maven2, and global mirrors of
Hey John,
I can't see a problem one way or the other here, I just noticed you
moved the caching - can you elaborate a bit on why that was necessary,
and are you sure it won't cause any problems with caching resolved
information? It looks like it is now after interpolation, and ISTR
that
I think there are two mutually exclusive things : 1) in an enterprise
with a repo man and 2) not
So 1) If a repo manager is declared, that url is used for all lookups
regardless of defined repos on settings or poms. Perhaps a translation
to url like Nicolas' feature is used here for repo
33 matches
Mail list logo
