Thanks John - good catch.
The proposal did intend to encompass that version problem (I took a
lead from other projects that have done that successfully, for
example httpd). But that covers previous releases and trunk only.
What we really need is for, in the proposal below, versioned to
re
Le mercredi 23 mai 2007, Jason van Zyl a écrit :
> On 22 May 07, at 5:10 PM 22 May 07, Hervé BOUTEMY wrote:
> > Here is a little patch for the 3 pages that have to be updated in
> > maven-site
> > and published.
> >
> > The binaires are not yet in the distribution library
> > http://www.apache.org/
I'm happy to apply this to a subproject and see how it works. We
were discussing it in Archiva, so maybe there. But I think the best
candidate is SCM. Between the two we cover the two basic types of
subprojects (a framework and an application), so hopefully we can
bounce that around and
On 5/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I think it's just a matter of configuration at this point. So I'll
get started with SCM. Emmanuel - interested?
I'm also calling on Tim O'Brien and Henri Yandell here since I saw
them at JavaOne and they said they'd help out in some way (even
On 23/05/2007, at 2:10 PM, Jason van Zyl wrote:
That's what the taxonomy is supposed to be: a hierarchy. But given
that documents were lost in the wiki I put them all on that page so
that I could see them all and try to organize and cull them.
Whatever I saw I quickly tried to categorize.
On 23 May 07, at 12:53 AM 23 May 07, Brett Porter wrote:
On 23/05/2007, at 2:48 PM, Jason van Zyl wrote:
On 23 May 07, at 12:38 AM 23 May 07, Brett Porter wrote:
Got it: "labelText:artifacts OR labelText:taxonomy"
is that what you needed?
I actually want to do something with a result
On 23/05/2007, at 2:48 PM, Jason van Zyl wrote:
On 23 May 07, at 12:38 AM 23 May 07, Brett Porter wrote:
Got it: "labelText:artifacts OR labelText:taxonomy"
is that what you needed?
I actually want to do something with a result set ideally. To make
views that are actually useful and no
On 23 May 07, at 12:38 AM 23 May 07, Brett Porter wrote:
Got it: "labelText:artifacts OR labelText:taxonomy"
is that what you needed?
I actually want to do something with a result set ideally. To make
views that are actually useful and not just lists of things.
On 23/05/2007, at 2:34 P
Got it: "labelText:artifacts OR labelText:taxonomy"
is that what you needed?
On 23/05/2007, at 2:34 PM, Brett Porter wrote:
Yeah, I'm sure they have a thing you can search by, but I can't
find it. There is just: http://docs.codehaus.org/label/MAVEN/
repositories
On 23/05/2007, at 2:32 PM,
Yeah, I'm sure they have a thing you can search by, but I can't find
it. There is just: http://docs.codehaus.org/label/MAVEN/repositories
On 23/05/2007, at 2:32 PM, Jason van Zyl wrote:
On 23 May 07, at 12:19 AM 23 May 07, Brett Porter wrote:
On 23/05/2007, at 2:16 PM, Jason van Zyl wrote
On 23 May 07, at 12:19 AM 23 May 07, Brett Porter wrote:
On 23/05/2007, at 2:16 PM, Jason van Zyl wrote:
I think there is a lot missing from wikis and CMS tools to
actually help with this sort of evolution of information. I'm
interesting in figuring out how best to do this. If Confluence
On 23 May 07, at 12:19 AM 23 May 07, Brett Porter wrote:
On 23/05/2007, at 2:16 PM, Jason van Zyl wrote:
I think there is a lot missing from wikis and CMS tools to
actually help with this sort of evolution of information. I'm
interesting in figuring out how best to do this. If Confluence
On 23/05/2007, at 2:16 PM, Jason van Zyl wrote:
I think there is a lot missing from wikis and CMS tools to actually
help with this sort of evolution of information. I'm interesting in
figuring out how best to do this. If Confluence had some simple
tagging that would be very nice. Tell me i
On 22 May 07, at 10:24 PM 22 May 07, John Casey wrote:
I tend to think that it would be helpful if we could setup the wiki
spaces
for Maven (the tool, not the over-arching umbrella project) in the
following
ways:
1. separate content areas for 2.0.x, 2.1.x, 2.2.x, etc.
2. each content area
On 22 May 07, at 11:25 PM 22 May 07, John Casey wrote:
For the cases where we're going to wind up with multiple concurrent
branches
of development, I think it would be valuable to provide versioned
sub-spaces
in the developer documentation. This way, developers working on
2.0.x can
read up
On 22 May 07, at 10:37 PM 22 May 07, Brett Porter wrote:
Thanks for starting this - I downloaded the spaces while I was
offline and starting thinking about ways to do it also.
On 23/05/2007, at 8:28 AM, Jason van Zyl wrote:
Hi,
I started trying to reference artifact pages in the spec I've
For the cases where we're going to wind up with multiple concurrent branches
of development, I think it would be valuable to provide versioned sub-spaces
in the developer documentation. This way, developers working on 2.0.x can
read up on the architecture and design decisions that apply to 2.0.x,
Thanks for starting this - I downloaded the spaces while I was
offline and starting thinking about ways to do it also.
On 23/05/2007, at 8:28 AM, Jason van Zyl wrote:
Hi,
I started trying to reference artifact pages in the spec I've
written up for the artifact resolution and I found it imp
On 23/05/2007, at 12:24 PM, John Casey wrote:
3. eventually, we should setup a sync process to mirror these
developer-oriented sites to a subsection of the main Maven site
Or, use the one that already exists :)
Per my mail a couple of weeks back, I was very quickly able to set
this up:
ht
I tend to think that it would be helpful if we could setup the wiki spaces
for Maven (the tool, not the over-arching umbrella project) in the following
ways:
1. separate content areas for 2.0.x, 2.1.x, 2.2.x, etc.
2. each content area should be setup to look like a developer-oriented
website for
Ok, there seems to be some interest. I will spend some time putting
the code into a suitable packaging / licensing structure and post it
for a vote.
On 22/05/2007, at 5:46 AM, Brian E. Fox wrote:
"But more importantly, it helps identify your dependency jars as
described in the proposal. In
Just browsing around trying to sort things out there are 3 major
categories here:
1) Designs that have actually been incorporated into the project
which should be the basis for documentation and go to the site
2) Designs under discussion, or proposals, that have yet to make it
into the pro
On 22 May 07, at 8:19 PM 22 May 07, Barrie Treloar wrote:
On 5/23/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Sorry, just assume the devs knew where it was. We point at the user
space as that's what people can edit but I will try to organize the
user space in the same way as the dev space so
On 22 May 07, at 8:19 PM 22 May 07, Barrie Treloar wrote:
On 5/23/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Sorry, just assume the devs knew where it was. We point at the user
space as that's what people can edit but I will try to organize the
user space in the same way as the dev space so
Hi,
I was just taking a first pass at trying to sift out good doco from
the user space and noticed there are lots of pages by people who have
access to the official space and that the user space is a
amalgamation of all the sub projects. I would like to align the
spaces to make movement o
On 5/23/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Sorry, just assume the devs knew where it was. We point at the user
space as that's what people can edit but I will try to organize the
user space in the same way as the dev space so that we can easily
move documents between the two. But the us
On 22 May 07, at 6:49 PM 22 May 07, Stefano Bagnara wrote:
Jason van Zyl ha scritto:
I started trying to reference artifact pages in the spec I've
written up
for the artifact resolution and I found it impossible to really find
anything so I took John's initial outline for the taxonomy that
Jason van Zyl ha scritto:
> I started trying to reference artifact pages in the spec I've written up
> for the artifact resolution and I found it impossible to really find
> anything so I took John's initial outline for the taxonomy that makes up
> our subject matter and I made an attempt to align
Hi,
I started trying to reference artifact pages in the spec I've written
up for the artifact resolution and I found it impossible to really
find anything so I took John's initial outline for the taxonomy that
makes up our subject matter and I made an attempt to align the wiki
with the ca
+1
On 22 May 07, at 5:19 PM 22 May 07, Emmanuel Venisse wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch
creation and the latest Maven-SCM (1.0)
The Road Map: http://jira.codehaus.org/secure/Releas
On 22 May 07, at 5:10 PM 22 May 07, Hervé BOUTEMY wrote:
Here is a little patch for the 3 pages that have to be updated in
maven-site
and published.
The binaires are not yet in the distribution library
http://www.apache.org/dyn/closer.cgi/maven/binaries: I suppose this is
different from the
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch creation and
the latest Maven-SCM (1.0)
The Road Map:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&styleName=Html&version=13452
Staging re
On 22 May 07, at 2:29 PM 22 May 07, Jason Dillon wrote:
I think there is more than merging needed,
Not sure what you mean. This is really the first release using this
artifact id.
the website needs to be updated. And is there an uber jar or
something for this? Previously the jar for a
Here is a little patch for the 3 pages that have to be updated in maven-site
and published.
The binaires are not yet in the distribution library
http://www.apache.org/dyn/closer.cgi/maven/binaries: I suppose this is
different from the production repository.
Hervé
Le mardi 22 mai 2007, Jason D
During further use/testing of the mercurial provider (maven-scm-provider-hg)
I discovered that the "tag" command was missing. I've just fixed this.
Please see the patch attached to http://jira.codehaus.org/browse/SCM-319
Thank you,
Ryan Daum
--
Ryan Daum
[EMAIL PROTECTED]
Senior Developer, To
I think there is more than merging needed, the website needs to be
updated. And is there an uber jar or something for this? Previously
the jar for ant to include as maven-artifact-ant-2.0.4-dep.jar, now
there is just maven-ant-tasks-2.0.6.jar?
The info page should also be updated too:
Yup, the 72 hours elapsed from the last vote. So I'll merge those
into the production repository.
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/
maven/maven-ant-tasks/
All deployed.
On 22 May 07, at 6:48 AM 22 May 07, Jason Dillon wrote:
What ever happened to this?
On 5/22/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
Since Maven 2.0.6 is out, I think it should be useful to redeploy this
Maven site:
http://maven.apache.org/ref/current/
WDYT?
That 'current' directory is a symlink which points to 2.0.4 right now.
The 2.0.6 docs need to be deployed to /ref
Hi,
Since Maven 2.0.6 is out, I think it should be useful to redeploy this
Maven site:
http://maven.apache.org/ref/current/
WDYT?
Cheers,
Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EM
Hi Patrick,
Oh my goodness, you're a genius!
Your suggestions finally did the trick for me and
mvn clean test-compile
works as it should.
Sincere thanks to you my friend, you saved my day ;)
Best regards,
Severin
-Ursprüngliche Nachricht-
Von: Patrick Schneider [mailto:[EMAIL PROTECTE
What ever happened to this? Can we please get this released and
update the docs to explain to folks how to use it?
--jason
On 5/16/07, Brett Porter <[EMAIL PROTECTED]> wrote:
+1 - tested successfully.
On 15/05/2007, at 6:15 PM, Jason van Zyl wrote:
> Hi,
>
> Repost of the vote after fixing
Well.. I must say I am not sure I understood the questions fully, but I
give it a try...
Hi,
Its regarding identifiyng the plugin name.
We are using Maven in my project. i have small doubt.
I need to identify the "aspectj-maven-plugin" if we are using in our project.
if it is foun
The vote passed with 4 binding (Jason, Stephane, Arnaud, myself) and one
non-binding (Jeff) +1.
Vote thread:
http://www.nabble.com/-vote---m1--release-artifact-plugin-1.9.1-and-test-plugin-1.8.2-tf3779381s177.html
Thanks,
-Lukas
Lukas Theussl wrote:
We discovered two rather severe issues in
This change is needed because the pom writer generate files with unix line
ending. Tested on OSX and windows.
Emmanuel
Brett Porter a écrit :
Why is that needed? Will it still work on Windows?
On 22/05/2007, at 12:56 AM, [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Mon May 21 07:55:57 20
44 matches
Mail list logo
