On 3-Mar-09, at 2:50 PM, Vincent Siveton wrote:
Hi Jason
2009/3/3 Jason van Zyl :
XWiki is not using it because it doesn't work. Vincent created a
wrapper to
We added a lot of tests in 1.1 and all seems to work with 2.0.x and
2.1.
I can't see the problems/issues that you refer. Could yo
I'll try to finish up looking at this tomorrow morning. I couldn't get
all the way through it tonight.
Vincent Siveton wrote:
Hi,
We solved more than 100 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13617&styleName=Html&projectId=10780
There are still a couple of issues le
+1
tested without any problem (with Maven 2.1.0-SNAPSHOT and maven-site-plugin
1.1-SNAPSHOT) on:
- maven site
- Modello site (reporting profile)
- Maven 2.1.x (both reporting and reporting-aggregate profiles)
I'm ready to give a try to any site: just give me a svn url.
Like in my previous mail,
Hi Jason
2009/3/3 Jason van Zyl :
> XWiki is not using it because it doesn't work. Vincent created a wrapper to
We added a lot of tests in 1.1 and all seems to work with 2.0.x and 2.1.
I can't see the problems/issues that you refer. Could you point me?
> try and help integrate it but as it seems
Hi,
We solved more than 100 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13617&styleName=Html&projectId=10780
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1
Staging repo:
Doxia
https://reposit
+1
Hervé
Le dimanche 01 mars 2009, Dennis Lundberg a écrit :
> Hi,
>
> Another step in the Doxia Release Plan:
> http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=
>Html&version=14950
>
>
On 3-Mar-09, at 9:52 AM, Vincent Siveton wrote:
Hi John,
2009/3/3 John Casey :
Is Maven the only consumer of Doxia? When you say "everything else
moving
AFAIK, Xwiki and m2eclipse are also using Doxia
XWiki is not using it because it doesn't work. Vincent created a
wrapper to try and
Are they eagerly awaiting Doxia 1.1?
What I'm wondering is, what are we standing in the way of by not putting
the latest, greatest Doxia into Maven 2.1.0?
Back in July/August of last year, we talked about pulling back from the
Doxia upgrade so it could be released and soak into the community
For the record, the famous difficulties in testing multi-threaded code
was one of the chief reasons I was hesitant to include the parallel
resolution code. If we can achieve a degree of stability through the RC
process, then fine.
But there is still a difference here between Doxia 1.1 and the
+1
Vincent
2009/3/1 Dennis Lundberg :
> Hi,
>
> Another step in the Doxia Release Plan:
> http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14950
>
> The most notable fix is
>
Hi Brian,
2009/3/3 Brian E. Fox :
> The more this thread goes on, the less optimistic I feel about this going
> into 2.1. We already know the 2.1M1 is stable and the point was to get it out
> in a release that people can use, ie non-milestone.
I hope that 2.1 is stable but I remember you that B
Hi John,
2009/3/3 John Casey :
> Is Maven the only consumer of Doxia? When you say "everything else moving
AFAIK, Xwiki and m2eclipse are also using Doxia
Cheers,
Vincent
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.
Hello,
In our release setup, we always generate the release POM for our
modules. We have a project now that fails when the
org.htmlparser:htmlparser:1.6 dependency was added. htmlparser refers
to tools.jar as a system scoped dependency. The generated release POM
contains a system scoped dependency
On 04/03/2009, at 1:59 AM, John Casey wrote:
Is Maven the only consumer of Doxia?
That would be the indication I get, but anything is possible.
When you say "everything else moving forward" do you mean Maven
plugins, or Doxia's development itself?
Plugins (eg, PDF plugin has to shade in
The more this thread goes on, the less optimistic I feel about this going into
2.1. We already know the 2.1M1 is stable and the point was to get it out in a
release that people can use, ie non-milestone. Making radical changes at the
last minute is not good for stability and not good for the use
Brett Porter wrote:
On 03/03/2009, at 6:11 AM, John Casey wrote:
What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what
to push this along?
You should first review the exact same question I asked 5 days ago :)
I had just finished reading this thread probably 30m before writing
Lukas Theussl wrote:
Hi John,
If you would have used the time it took you to write this email for
installing and testing Doxia 1.1 you probably wouldn't have to ask
anymore if it's a terrible idea. ;)
In my experience, five minutes isn't enough time to do anything when
you've got more than
On 03/03/2009, at 11:45 PM, Brian E. Fox wrote:
1.1 is NOT under development anymore, it hasn't been for at least
over a year. All
we did was small bug fixes and enhancements that came along on the
way because
there was nothing else to do.
I don't follow this logic, if it's been done for
>1.1 is NOT under development anymore, it hasn't been for at least over a year.
>All
>we did was small bug fixes and enhancements that came along on the way because
>there was nothing else to do.
I don't follow this logic, if it's been done for over a year, why has it been
discussed for the la
The vote has passed with the following result:
+1: Brett, Lukas, Benjamin, Vincent
I will promote the artifacts to the central repo.
Vincent
2009/2/28 Vincent Siveton :
> Hi,
>
> This is a maintenance release due to MPIR-146.
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.
Hi Brett,
2009/3/3 Brett Porter :
> - the directory seems wrong (there is nothing in the directory given here,
> just a subdirectory for apidocs (also in the main site) and for the site
> which should be in the original location
Fixed on p.a.o, wait for sync.
Vincent
---
Hi Benjamin,
2009/3/3 Benjamin Bentmann :
> The "Release Notes" [0] are empty. While building the plugin's tag locally I
> observed a NPE from the JIRA parser. I haven't looked further whether just
> the JIRA URL being queried is wrong or JIRA itself has changed. Anyway, it's
> just a cosmetic thi
This should be easy to replicate, I'll reopen the issue.
On 03/03/2009, at 10:07 PM, Benjamin Bentmann wrote:
Hi,
I just stumbled upon another issue with the parallel artifact
resolution in 2.1.x:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
Hi,
I just stumbled upon another issue with the parallel artifact resolution
in 2.1.x:
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven Integration Test :: Boostrap
[INFO]
Brett Porter wrote:
Yeah, it sounds right.
OK, so there seem to be no objections to the patch. As such, I will try
to apply it to 2.1.x and 3.x this day or tomorrow.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@mave
Yep.
I noticed one problem with the group though - it appears to be
offering the releases repo as well as any staged releases. This
doesn't seem right to me?
- Brett
On 03/03/2009, at 9:11 PM, Benjamin Bentmann wrote:
Hi,
regarding the contents of [0], would it be inappropriate to repla
I can add a bit of detail on the core side in addition to Vincent and
Lukas' mails.
On 03/03/2009, at 6:11 AM, John Casey wrote:
What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what
to push this along?
You should first review the exact same question I asked 5 days ago :)
1
Hi,
regarding the contents of [0], would it be inappropriate to replace to URL
http://people.apache.org/~dfabulich/stage-repo
with
https://repository.apache.org/content/groups/staging/
i.e. point at the staging group in Nexus? I assume the current examples
haven't been updated since our swit
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-4bd35808644740/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: d
Oh, right. I forgot since my testing was broken by sleep. While the
binaries and all are correct, the site doesn't appear so:
- the JIRA report is empty, as Benjamin pointed out
- the directory seems wrong (there is nothing in the directory given
here, just a subdirectory for apidocs (also in
Vincent Siveton wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-4b8f246928b178/
Tag:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-project-info-reports-plugin-2.1.1
+1
Staging site (need to sync):
http://maven.apache.org/plugins/maven-projec
+1
-Lukas
Dennis Lundberg wrote:
Hi,
Another step in the Doxia Release Plan:
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14950
The most notable fix is
http://jira.codeh
+1
-Lukas
Vincent Siveton wrote:
Hi,
This is a maintenance release due to MPIR-146.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14325&styleName=Html&projectId=11142&Create=Create
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secu
Hi John,
If you would have used the time it took you to write this email for installing and
testing Doxia 1.1 you probably wouldn't have to ask anymore if it's a terrible
idea. ;)
I also don't see a compelling reason for upgrading now. As I didn't 5 weeks ago.
Or the week before that.
Nei
34 matches
Mail list logo
