On 8/31/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> Yeah, I meant to note that - I was thinking that this should be
> accompanied by a proposal to take care of the id ambiguity problems
> which we've discussed a couple of times before.
>
> I think URLs are still problematic (since you can often h
FYI: I have checked the current maven site with the sandbox linkchecker
and fixed all errors plus a couple of redirect warnings. Below is a list
of links that are still missing and I'm unsure what to do, if someone
could have a look. I have also commented out all links to the jetty home
page (
Brett Porter wrote:
Hi,
I'm looking to do a few things towards getting a 2.1 alpha out, and
wanted to look towards getting 2.1 itself a bit nearer. It seems like
we have too many things scheduled at the moment for 2.1, so here are a
few bits I've been looking at and was going to start running
Hi Brett,
Did you did it for me too?
Cheers,
Vincent
2007/8/30, Brett Porter <[EMAIL PROTECTED]>:
> Done!
>
> On 31/08/2007, at 1:59 AM, Dennis Lundberg wrote:
>
> > Hi
> >
> > Would someone be so kind and add karma for me (dennisl) on
> > maven.zones.apache.org, so that I can run plugin builds
>As I noted before, if the ITs are reasonably under control with a way
>for people to make them and submit them then I will cut alphas
everyday.
>Brian is pretty much done. Is that true Brian on the Archetype front?
The archetypeNG plugin needs to be released before this is truly usable
by our
Comments inline also
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:20 PM
To: Maven Developers List
Subject: Re: [PROPOSAL] Plugin packs and concrete versioning
sorry for the brevity - I'm heading off to bed and am afk for a day
and a b
Thanks Brett!
Brett Porter wrote:
Done!
On 31/08/2007, at 1:59 AM, Dennis Lundberg wrote:
Hi
Would someone be so kind and add karma for me (dennisl) on
maven.zones.apache.org, so that I can run plugin builds from Continuum.
--
Dennis Lundberg
-
Comments inlined
2007/8/31, Jason van Zyl <[EMAIL PROTECTED]>:
>
>
> On 31 Aug 07, at 9:58 AM 31 Aug 07, Raphaël Piéroni wrote:
>
> > Hi guys,
> >
> > Could it be some work done on integrating archetypes for maven 2.1 ?
> >
>
> Archetype should stand completely on its own. Should have nothing to
>
...
> A future enhancement may be to be able to (and if so, require) plugin
> versions to be declared in the Maven settings files.
but in that case it could be interesting to be able to have an extend
mechanism of settings using the repository like a parent pom. The idea
is to be able to defin
On 31 Aug 07, at 9:58 AM 31 Aug 07, Raphaël Piéroni wrote:
Hi guys,
Could it be some work done on integrating archetypes for maven 2.1 ?
Archetype should stand completely on its own. Should have nothing to
do with 2.1.
What i am thinking about is to enhance the settings model to permit
Which new features can we imagine for corporate proxies like archiva,
proximity ? In that case developers often see only one remote
repository which is defined as proxy. How will we know the data come
from ?
Arnaud
On 31/08/2007, Brett Porter <[EMAIL PROTECTED]> wrote:
> See: http://docs.codehaus
On 31 Aug 07, at 9:48 AM 31 Aug 07, Brett Porter wrote:
On 01/09/2007, at 2:27 AM, Jason van Zyl wrote:
As I noted before, if the ITs are reasonably under control with a
way for people to make them and submit them then I will cut alphas
everyday.
There's some known failures I'd like to f
Hi guys,
Could it be some work done on integrating archetypes for maven 2.1 ?
What i am thinking about is to enhance the settings model to permit
plugins to access some configuration when used without a project.
Like the repositories defined in active profiles.
Like plugin configuration like in
On 01/09/2007, at 2:27 AM, Jason van Zyl wrote:
As I noted before, if the ITs are reasonably under control with a
way for people to make them and submit them then I will cut alphas
everyday.
There's some known failures I'd like to fix, that's all. They are all
in JIRA.
Brian is pretty
On 31 Aug 07, at 9:20 AM 31 Aug 07, Brett Porter wrote:
sorry for the brevity - I'm heading off to bed and am afk for a day
and a bit so wanted to get a quick response in...
On 01/09/2007, at 1:45 AM, Jason van Zyl wrote:
A couple notes that you can incorporate from experiences I've had
b
As I noted before, if the ITs are reasonably under control with a way
for people to make them and submit them then I will cut alphas everyday.
Brian is pretty much done. Is that true Brian on the Archetype front?
And you were supposed to figure out the JIRA workflow and I am
supposed to do t
Yeah, I meant to note that - I was thinking that this should be
accompanied by a proposal to take care of the id ambiguity problems
which we've discussed a couple of times before.
I think URLs are still problematic (since you can often have
different ones for the same location), though are
sorry for the brevity - I'm heading off to bed and am afk for a day
and a bit so wanted to get a quick response in...
On 01/09/2007, at 1:45 AM, Jason van Zyl wrote:
A couple notes that you can incorporate from experiences I've had
based on a client setup:
- The enforcer plugin now has a r
looks great.
One comment. "Remote" folder is grouped by repo indentifiers.
Unfortunately these often differ among projects. Results in many
duplicate files and folder structures. Can we go by URL? or have some
means of automatically defining aliases for the same remote repo URL?
Milos
On 8/31/07
Hi,
I'm looking to do a few things towards getting a 2.1 alpha out, and
wanted to look towards getting 2.1 itself a bit nearer. It seems like
we have too many things scheduled at the moment for 2.1, so here are
a few bits I've been looking at and was going to start running
through. Would
A couple notes that you can incorporate from experiences I've had
based on a client setup:
- The enforcer plugin now has a rule to fully lock down all plugin
versions
- You do have to lock down all plugins including things like
"eclipse:eclipse" because these are used extensively by many
I have revised the proposal I made earlier based on Jason and John's
feedback.
See: http://docs.codehaus.org/display/MAVEN/Plugin+packs+and+concrete
+versioning
Text included below for inline comments (which I'll feed back into
the document as needed).
Context
Currently, plugin versions
On 8/31/07, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
>
> Brett Porter wrote:
> > Sorry, I missed that. Your solution is definitely compliant with what
> > the APT "spec" says, so that's good.
> >
> > What might be nice is that doxia keeps track of all the anchor
> > references and throws an excep
On 31/08/2007, at 8:43 PM, Jason van Zyl wrote:
On 31 Aug 07, at 3:18 AM 31 Aug 07, Brett Porter wrote:
Are they still present in recent versions of 2.0.x?
Yup.
I'm fine with them remaining through 2.1.x then. Would be best to
isolate the code that grabs them in the embedder, if it is
On 31 Aug 07, at 3:38 AM 31 Aug 07, Graham Leggett wrote:
On Fri, August 31, 2007 12:10 pm, Jason van Zyl wrote:
As much I don't particularly like them, I've seen so many builds of
late using envars that I don't think we can turn them off in 2.1.x
after people have invested in builds that use
On 31 Aug 07, at 3:18 AM 31 Aug 07, Brett Porter wrote:
Are they still present in recent versions of 2.0.x?
Yup.
On 31/08/2007, at 8:10 PM, Jason van Zyl wrote:
As much I don't particularly like them, I've seen so many builds
of late using envars that I don't think we can turn them off
On Fri, August 31, 2007 12:10 pm, Jason van Zyl wrote:
> As much I don't particularly like them, I've seen so many builds of
> late using envars that I don't think we can turn them off in 2.1.x
> after people have invested in builds that use them. Tonight Vlad and
> I were working on the IDEA inte
Are they still present in recent versions of 2.0.x?
On 31/08/2007, at 8:10 PM, Jason van Zyl wrote:
As much I don't particularly like them, I've seen so many builds of
late using envars that I don't think we can turn them off in 2.1.x
after people have invested in builds that use them. Tonig
As much I don't particularly like them, I've seen so many builds of
late using envars that I don't think we can turn them off in 2.1.x
after people have invested in builds that use them. Tonight Vlad and
I were working on the IDEA integration and there are a few issues
logged that fail beca
Brett Porter wrote:
Sorry, I missed that. Your solution is definitely compliant with what
the APT "spec" says, so that's good.
What might be nice is that doxia keeps track of all the anchor
references and throws an exception if the anchor is never found in the
document - that'll catch th
Sorry, I missed that. Your solution is definitely compliant with what
the APT "spec" says, so that's good.
What might be nice is that doxia keeps track of all the anchor
references and throws an exception if the anchor is never found in
the document - that'll catch these much more easily th
It's part of a bug-fix: external links in apt files (ie links outside
the current source document) have to start with './' or '../', otherwise
I don't see how we could fix http://jira.codehaus.org/browse/DOXIA-47.
We have implemented a hacky workaround for html files to preserve
backward compat
32 matches
Mail list logo
