Dennis Lundberg-2 wrote:
Hang on a second, Subversion is telling us that your directory
workspace is not under version control here. And that is a correct
observation, since your parent is in the FireDragon directory.
I wonder who is telling svn to perform svn operations on that
Hello,
Roadmap for maven-javadoc-plugin 2.5 seems to be ok.
http://jira.codehaus.org/browse/MJAVADOC?report=com.atlassian.jira.plugin.system.project:roadmap-panel
Is it possible to release it ?
Thanks
Damien
-
To unsubscribe,
Hi Damien,
I can take the lead.
Let me have a look at it today and if it's good I'll launch the release
process.
Arnaud
On Thu, Jul 17, 2008 at 5:05 PM, Damien Lecan [EMAIL PROTECTED] wrote:
Hello,
Roadmap for maven-javadoc-plugin 2.5 seems to be ok.
ok thanks a lot.
I think we are numerous to wait for this release ;-)
Arnaud
On Fri, Jul 18, 2008 at 12:52 AM, Brian E. Fox [EMAIL PROTECTED]
wrote:
I worked on it last night, I am able to reproduce it, but I haven't
finished the code yet. I will work on it some more tonight.
-Original
Done.
http://jira.codehaus.org/browse/MOJO-1178
if anyone wants to take a bite...
On Thu, Jul 17, 2008 at 3:15 PM, Stephen Connolly
[EMAIL PROTECTED] wrote:
OK, so... i'll give that a shot once I reformat it to the Maven code style!
On Thu, Jul 17, 2008 at 3:04 PM, Brian E. Fox [EMAIL
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my module is
depending on the other one using this syntax:
dependency
groupIdnet.sourceforge.jwebunit/groupId
I will be out of the office starting 12.07.2008 and will not return until
28.07.2008.
I will respond to your message when I return. In urgent cases please refer
to Elena Tonoyan ([EMAIL PROTECTED]) or Daria Ignatieva
([EMAIL PROTECTED])
2008/7/16 Daniel Kulp [EMAIL PROTECTED]:
I just verified with CXF that if I use maven 2.0.7, the reduced pom has many
extra excludes. I've gone ahead and added some code to the ShadeMojo to
double check if it's an irrelevant exclude and not bother. This isn't
needed with 2.0.9, but it is
Hi,
-0 due to minor documentation errors:
- project url is specified to http://maven.apache.org/maven-artifact
in Project Summary and the deploy seems to be
http://maven.apache.org/ref/maven-artifact-3.0-alpha-1/ so we need to
clarify it. I guess http://maven.apache.org/artifact will be fine.
-
Hi Damien,
Yes I saw that yesterday when I fixed MJAVADOC-198... I plan to cut it
next week. I have some minor things to do before.
Cheers,
Vincent
2008/7/17, Damien Lecan [EMAIL PROTECTED]:
Hello,
Roadmap for maven-javadoc-plugin 2.5 seems to be ok.
One more vote please!
Vincent
2008/7/15, Vincent Siveton [EMAIL PROTECTED]:
Hi,
We solved around 65 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142styleName=Htmlversion=12621
There are still a couple of issues left in JIRA:
ok, I let you the lead.
good luck :-)
Arnaud
On Fri, Jul 18, 2008 at 2:03 PM, Vincent Siveton [EMAIL PROTECTED]
wrote:
Hi Damien,
Yes I saw that yesterday when I fixed MJAVADOC-198... I plan to cut it
next week. I have some minor things to do before.
Cheers,
Vincent
2008/7/17, Damien
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you
do there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceable at any time in
On 17-Jul-08, at 11:12 PM, Wendy Smoak wrote:
I gather this is the reason that the commits (r677787 to r677789) for
the Maven Artifact release that Oleg just called a vote on look like
they were done by Jason?
I'm really not comfortable with svn credentials being shared like
that.
They
I think as strict set of requires for a final release I would even say
a -1 from you would be valid. But as we move toward a final release I
think we can address this. I know you've been working to setup
consistent reporting and that can be used as a gauge for the final
release. For this
Hi,
Agree, and it is why I did not want to put a veto for this alpha.
+1 to release this as alpha and let s fix MARTIFACT-30 for 3.0
Cheers,
Vincent
2008/7/18, Jason van Zyl [EMAIL PROTECTED]:
I think as strict set of requires for a final release I would even say a -1
from you would be
On Fri, Jul 18, 2008 at 3:00 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
On 17-Jul-08, at 11:12 PM, Wendy Smoak wrote:
I gather this is the reason that the commits (r677787 to r677789) for
the Maven Artifact release that Oleg just called a vote on look like
they were done by Jason?
I'm
I'm not saying there is only one developer, the core group just
represents the group doing the majority of the work in a time period.
That graph was the last few months in your new location.
It's just the natural evolution of projects.
I am actually trying to work with a developer who knows
ok, I prefer when it is explain like that.
It's a good thing to try to reuse existing librairies and plugins
Emmanuel
On Fri, Jul 18, 2008 at 3:54 PM, Jason van Zyl [EMAIL PROTECTED] wrote:
I'm not saying there is only one developer, the core group just represents
the group doing the
Jason van Zyl wrote:
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you do
there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
I'll give it a try today and see if I can reproduce the problem. Then,
we should file a JIRA ticket so it shows up on the release notes, and
I'll fix it.
Thanks for testing!
-john
Julien HENRY wrote:
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my module is
On 18-Jul-08, at 10:30 AM, Ralph Goers wrote:
Jason van Zyl wrote:
On 17-Jul-08, at 8:08 PM, Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you
do there is no need to rewrite anything it just works...
My builds never use
Hi,
Important note: this release changes the groupId for the artifacts:
http://maven.markmail.org/message/s6l35jjjyz242lfa?q=plugin+testing+reorganization+from:%22Vincent+Siveton%22page=1
We solved several issues:
Okay, I've duplicated the problem, and generated a simple test case to
replicate it separately from the JWebUnit project, so we can create an
integration test. The JIRA issue is:
http://jira.codehaus.org/browse/MNG-3671
I have a fix for this issue (I believe), but still need to formalize the
Ok, I have a new portable bundle. I replaced all the scripting with
Velocity templating for all the jobs that are created. Brian tested it
on Windows and it all seems to be working fine.
http://people.apache.org/~jvanzyl/hudson.zip
I'm next getting Hudson to pull the POMs directly to create
Jason van Zyl wrote:
Ok, I have a new portable bundle.
Maybe you find this Windows batch file a useful addition:
@echo off
set dir=%~dp0
if %dir:~-1% == \ set dir=%dir:~0,-1%
set HUDSON_HOME=%dir%\runtime
if not exist %HUDSON_HOME% (
java -jar
-1
I'm having trouble getting the dependencies report working. So far I've
tested on Maven Site Plugin and Maven One Plugin, both fail but with
different results.
Maven Site Plugin
[INFO] Generating Dependencies report.
[INFO]
You and Brian can fight it out over the windows stuff.
On 18-Jul-08, at 12:12 PM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
Ok, I have a new portable bundle.
Maybe you find this Windows batch file a useful addition:
@echo off
set dir=%~dp0
if
Jason van Zyl wrote:
I replaced all the scripting with Velocity templating for all the jobs that are
created.
Another suggestion: In ExodusCli.java:45 replace
hudsonHome = System.getProperty(user.dir);
with
hudsonHome = new File(System.getProperty(user.dir),
runtime).getPath();
This
Can you try again with the code on trunk? Just committed some more
changes.
Dan
On Jul 18, 2008, at 6:45 AM, Mark Hobson wrote:
2008/7/16 Daniel Kulp [EMAIL PROTECTED]:
I just verified with CXF that if I use maven 2.0.7, the reduced pom
has many
extra excludes. I've gone ahead and
Jason van Zyl wrote:
I replaced all the scripting with Velocity templating
ExodusCli.java:70
w = new FileWriter(job);
Using
w = WriterFactory.newXmlWriter(job);
from plexus-utils instead would ensure proper output encoding for the
config.xml and improve platform independence of the
Jason van Zyl wrote:
Ok, I have a new portable bundle.
To get rid of the requirement on cygwin: You could use the Os class from
plexus-utils to detect Windows and set a flag in the Velocity context
for the templates. Using this flag, the templates could be tweaked to
use batch files
Here are a bunch of other comments:
1. Clirr reports 2 errors. Are they something we need to handle?
2. Checkstyle, CPD and PMD reports show a couple of issues, but nothing
that prevent a release.
3. L10n Status doesn't look as good as it should. We currently don't
have a localization
What dependency on cygwin? I fired it up on a naked windows vm without
cygwin. That batch script seems overly complicated, what's it doing that
the other .bat isn't?
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Friday, July 18, 2008 1:08 PM
To: Maven
I've committed most of the stuff I had in mind, although there are still
a few TODOs in the site documents. Would you mind having a look at those
Hervé?
We also need to decide the URL for the site. If we don't configure
anything it will end up at http://maven.apache.org/maven-ant-tasks/
Is
Brian E. Fox wrote:
What dependency on cygwin?
I am referring to this error while trying to build maven-2.1.x-IT-support:
[workspace] $ sh -xe snip\Temp\hudson39040.sh
The system cannot find the file specified
FATAL: Command execution failed
java.io.IOException: Cannot run program sh (in
You've got the wrong bundle it appears. The new one:
-rw-r--r-- 1 jvanzyl jvanzyl 2441718 17 Jul 14:19 haven-1.0.jar
-rw-r--r--@ 1 jvanzyl jvanzyl 19810714 17 Jul 13:55 hudson.war
-rw-r--r-- 1 jvanzyl jvanzyl 119 17 Jul 15:37 start.bat
-rwxr-xr-x@ 1 jvanzyl jvanzyl 142 17
Jason van Zyl wrote:
You've got the wrong bundle it appears. The new one:
-rw-r--r-- 1 jvanzyl jvanzyl 2441718 17 Jul 14:19 haven-1.0.jar
-rw-r--r--@ 1 jvanzyl jvanzyl 19810714 17 Jul 13:55 hudson.war
-rw-r--r-- 1 jvanzyl jvanzyl 119 17 Jul 15:37 start.bat
-rwxr-xr-x@ 1 jvanzyl
I just downloaded and unpacked the new bundle, and I've got
-rw-rw-rw- 1 dlg01 0 440 2008-07-11 15:55 create.sh
-rw-rw-rw- 1 dlg01 0 2441718 2008-07-17 14:19 haven-1.0.jar
-rw-rw-rw- 1 dlg01 0 19810714 2008-07-17 13:55 hudson.war
-rw-rw-rw- 1 dlg01 0 142 2008-07-17 14:13 start.sh
On Jul 17, 2008, at 4:26 PM, Jesse McConnell wrote:
hey all,
I have been working on the jetty-client in the jetty project over in
codehaus which is the library mercury uses that is doing the
asynchronous retrieval and deployment of artifacts. Greg Wilkins and
I have recently been increasing
djencks,
I am not sure what the client side of a jaspi api would look like, can
you give an example of what it would be doing?
from my perspective what we need to wire up in mercury right now is
some generic security api that something like maven can inject with
the goop in setting.xml meshed
For 4.2 I think that Frenchies pased here (Mega/Giga-Octets instead of
Mega/Giga-Bytes)
Arnaud
On Fri, Jul 18, 2008 at 7:17 PM, Dennis Lundberg [EMAIL PROTECTED] wrote:
Here are a bunch of other comments:
1. Clirr reports 2 errors. Are they something we need to handle?
2. Checkstyle, CPD
Thanks John. I will try next RC and comment in Jira issue if there is still a
problem.
- Message d'origine
De : John Casey [EMAIL PROTECTED]
À : Maven Developers List dev@maven.apache.org
Envoyé le : Vendredi, 18 Juillet 2008, 17h18mn 53s
Objet : Re: Re : [PLEASE TEST] Maven
Hi Dennis,
I confirm JDK 5 error for maven one but I didn't got any exception for
maven-site (Maven 2.0.9 Java 1.4.2_13) What was your command line?
Cheers,
Vincent
2008/7/18 Dennis Lundberg [EMAIL PROTECTED]:
-1
I'm having trouble getting the dependencies report working. So far I've
Thanks Dennis for your comments! See inline.
2008/7/18 Dennis Lundberg [EMAIL PROTECTED]:
Here are a bunch of other comments:
1. Clirr reports 2 errors. Are they something we need to handle?
Not specially. It is internal changes.
2. Checkstyle, CPD and PMD reports show a couple of issues,
There's a new bundle up there now.
On 18-Jul-08, at 3:02 PM, Dennis Lundberg wrote:
I just downloaded and unpacked the new bundle, and I've got
-rw-rw-rw- 1 dlg01 0 440 2008-07-11 15:55 create.sh
-rw-rw-rw- 1 dlg01 0 2441718 2008-07-17 14:19 haven-1.0.jar
-rw-rw-rw- 1 dlg01 0
Hi,
Following the recent Dennis's comments on MPIR and Antrun, I asked
myself how to improve our QA review and specially how to handle Maven
reports in the release process.
Does release manager need to justify failing reports for a given
release? If so, how.
How to improve the Maven report conf
Jason van Zyl wrote:
There's a new bundle up there now.
OK, now I get:
440 create.sh
2.441.718 haven-1.0.jar
119 hudson.bat
142 hudson.sh
19.810.714 hudson.war
142 start.sh
DIR templates
Also, the
Hi,
2008/7/18, Dennis Lundberg [EMAIL PROTECTED]:
I've committed most of the stuff I had in mind, although there are still a
few TODOs in the site documents. Would you mind having a look at those
Hervé?
We also need to decide the URL for the site. If we don't configure anything
it will end
Hi,
2008/7/18, Vincent Siveton [EMAIL PROTECTED]:
Hi,
-0 due to minor documentation errors:
- project url is specified to http://maven.apache.org/maven-artifact
in Project Summary and the deploy seems to be
http://maven.apache.org/ref/maven-artifact-3.0-alpha-1/ so we need to
clarify
Vincent Siveton wrote:
Hi Dennis,
I confirm JDK 5 error for maven one but I didn't got any exception for
maven-site (Maven 2.0.9 Java 1.4.2_13) What was your command line?
mvn clean site -Pvsiveton-staging,reporting
As you can see I've created a local profile with your staging-repo
Vincent Siveton wrote:
Thanks Dennis for your comments! See inline.
2008/7/18 Dennis Lundberg [EMAIL PROTECTED]:
Here are a bunch of other comments:
1. Clirr reports 2 errors. Are they something we need to handle?
Not specially. It is internal changes.
2. Checkstyle, CPD and PMD reports
Whatever we choose we should try to be consistent with the paths we
use in SVN. So we have ant-tasks in SVN, so it probably makes sense
to try and keep the same pattern for the site URL.
On 18-Jul-08, at 5:50 PM, Vincent Siveton wrote:
Hi,
2008/7/18, Dennis Lundberg [EMAIL PROTECTED]:
Brian and Dennis were both running under Windows and Brian didn't have
Cygwin installed. Not sure what Dennis had on his machine.
On 18-Jul-08, at 2:47 PM, Benjamin Bentmann wrote:
Brian E. Fox wrote:
What dependency on cygwin?
I am referring to this error while trying to build
Vincent Siveton wrote:
Hi,
2008/7/18, Vincent Siveton [EMAIL PROTECTED]:
Hi,
-0 due to minor documentation errors:
- project url is specified to http://maven.apache.org/maven-artifact
in Project Summary and the deploy seems to be
55 matches
Mail list logo
