Hi,
I'm pleased to announce the release of the gwt-maven-plugin version 2.5.0-rc2.
http://mojo.codehaus.org/gwt-maven-plugin/
To get this update, simply specify the version in your project's
plugin configuration:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdgwt-maven
Hi Stephen,
Stephen Coy wrote:
Are you using Surefire 2.6? I believe that has a memory leak. See
http://jira.codehaus.org/browse/SUREFIRE-647.
Well, most use Surefire 2.5, only the latest projects use already 2.6. I ran
the build with -DskipTests so that this memory leak should not
Did you try running the build with JMX? Watching for memorycpu consumption?
And doing a thread dump to know where the build is actually stuck could be
interesting.
Cheers
2010/9/24 Jörg Schaible joerg.schai...@gmx.de
Hi Stephen,
Stephen Coy wrote:
Are you using Surefire 2.6? I believe
drive can
get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
Before reporting any issues found during testing, please be sure to have a
close look at the compatibility notes for Maven 3.x:
https
kristian wrote:
any hints are welcome to do the better.
/** @parameter default-value=${repositorySystemSession}
* @readonly
*/
private RepositorySystemSession repoSession;
...
request.setRepositorySession( repoSesssion );
Benjamin
cool ;-) thanx.
On Thu, Sep 23, 2010 at 2:27 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
kristian wrote:
any hints are welcome to do the better.
/** @parameter default-value=${repositorySystemSession}
* @readonly
*/
private RepositorySystemSession repoSession;
...
from this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
Before reporting any issues found during testing, please be sure to have
a close look at the compatibility notes for Maven 3.x:
https://cwiki.apache.org/confluence/display
this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-
maven/3.0-RC2/
Before reporting any issues found during testing, please be sure to have
a close look at the compatibility notes for Maven 3.x:
https://cwiki.apache.org/confluence/display/MAVEN/Maven
Works fine with my most important builds, including site.
Jochen
--
I Am What I Am And That's All What I Yam (Popeye)
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
a preview of the upcoming release for a test drive can
get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
Before reporting any issues found during testing, please be sure to have a
close look
Den 23.09.2010 11:31, skrev Jörg Schaible:
Is it possible that the new code for parallel processing unintentionally
swallows the OOME? Does someone else observe the same behavior?
Are you running with the -T option active ?
Kristian
Hi Kristian,
Kristian Rosenvold wrote:
Den 23.09.2010 11:31, skrev Jörg Schaible:
Is it possible that the new code for parallel processing unintentionally
swallows the OOME? Does someone else observe the same behavior?
Are you running with the -T option active ?
No.
- Jörg
Hi
Our build which consists of 57 projects fails with the following on
3.0-RC2 (Ok on 2.2.1)
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.3.1:install
(default-install) on project
site-resources: Execution default-install of goal
org.apache.maven.plugins:maven
to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive
can get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-
maven/3.0-RC2/
Before reporting
://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
Before reporting any issues found during testing, please be sure to have
a close look at the compatibility notes for Maven 3.x:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
If you
Great!
On Wed, Sep 22, 2010 at 2:44 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
I just performed a 30-something multi-module release (prepare, perform
[deploy, site-deploy]) and I
is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive can
get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
Before
/2.2.1-RC2
Please file JIRA issues for anything you come across that still seems
broken. The list of issues we've resolved so far for this release is
here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328
Thanks!
-john
---
John Casey
Developer and PMC
/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues for anything you come across that still seems
broken. The list of issues we've resolved so far for this release is
here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName
of testing out RC1, I think we're in better shape to
attempt a release again.
Before we do, I'd like to get as many eyes as possible on this latest
release candidate:
https://repository.apache.org/content/repositories/maven-staging-008/org/ap
ache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues
to attempt a
release again.
Before we do, I'd like to get as many eyes as possible on this latest
release candidate:
https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues for anything you come across that still
on this latest
release candidate:
https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues for anything you come across that still seems
broken. The list of issues we've resolved so far for this release is here
to attempt a
release again.
Before we do, I'd like to get as many eyes as possible on this latest
release candidate:
https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues for anything you come across
as possible on this latest
release candidate:
https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
Please file JIRA issues for anything you come across that still seems
broken. The list of issues we've resolved so far for this release
/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the issue! :-)
Thanks for testing!
-john
-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the issue! :-)
Thanks for testing!
-john
I just grepped the uberjar file listing in RC2 for 'ightweight' and came
up with nothing. Are you sure the lightweight wagon is present in the
copy you have?
Arnaud HERITIER wrote:
I thought the wagon-lightweight was always here.It's with the 2.2.0-RC you
delivered.
Arnaud
On Mon, May 18
No I'm not sure. I just supposed it was it.Sorry
Arnaud
On Mon, May 18, 2009 at 10:13 PM, John Casey jdca...@commonjava.org wrote:
I just grepped the uberjar file listing in RC2 for 'ightweight' and came up
with nothing. Are you sure the lightweight wagon is present in the copy you
have
/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the issue! :-)
Thanks for testing!
-john
at generifying the codebase, we've respun a new release
candidate.
If you have time, please give it a whirl:
https://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org
://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the issue! :-)
Looks good. I
.
If you have time, please give it a whirl:
https://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply
/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to: http://jira.codehaus.org/browse/MNG
with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the
issue! :-)
I've just noticed this whilst doing
.
If you have time, please give it a whirl:
https://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
Hey,
I had no issue building my projects.
release:prepare is working but release:perform is not (see the trace below).
I switched to 2.1.0 right after that and the release:perform went well.
I'm using the javasvn scm provider here but I get the same error using the
native one.
/Paul
+1. Just noticed the same problem while mvn releasing a multimodule project.
The rest is fine (mvn clean deploy is ok).
Cheers.
2009/5/5 Paul MERLIN p...@nosphere.org
Hey,
I had no issue building my projects.
release:prepare is working but release:perform is not (see the trace
below).
I
/maven/apache-maven/2.2.0-RC2/
Remember, if you have any problems, report them to:
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0
...then, please reply to this thread to let me know about the issue! :-)
Thanks for testing!
-john
Hi all,
Proximity RC2 is here!
Proximity RC2 has moved forward in time, due to an important BUG about
handling aggregated repositories and Maven2 metadata.
If using non-snapshot and snapshot repositories together that contains
same paths (NOT with the default config), RC1 and former releases
Hey all
I'm a bit new at maven, so bear with me. I'm trying to build geronimo
1.0source and I'm having problems with maven
1.0-rc2 (I would update but the place I'm at runs on maven 1.0.2 and won't
be upgrading). When I build, I keep on getting dependency errors :
Attempting to download commons
On 2/25/06, Johnny l [EMAIL PROTECTED] wrote:
Hey all
I'm a bit new at maven, so bear with me. I'm trying to build geronimo
1.0source and I'm having problems with maven
1.0-rc2 (I would update but the place I'm at runs on maven 1.0.2 and won't
be upgrading). When I build, I keep on getting
: [.war plugin] maven.war.final.name changed
in 1.0
(from 1.0-rc2)?
Hello.
Just wondering if anything changed with the .war
plugin since 1.0-rc2? In my maven.xml file, I
define
the following:
preGoal name=java:prepare-filesystem
tstamp
format property=timestamp
Hello.
Just wondering if anything changed with the .war
plugin since 1.0-rc2? In my maven.xml file, I define
the following:
preGoal name=java:prepare-filesystem
tstamp
format property=timestamp
pattern=MMdd-HHmm/
/tstamp
property name=maven.war.final.name
value=${prj.war.name
Objet : [.war plugin] maven.war.final.name changed in 1.0
(from 1.0-rc2)?
Hello.
Just wondering if anything changed with the .war
plugin since 1.0-rc2? In my maven.xml file, I define
the following:
preGoal name=java:prepare-filesystem
tstamp
format property=timestamp
pattern
After fetching RC2 I've noticed that a number of the plugins have diffs
between the one shipped with RC1 versus the one shipped with RC2.
I'm curious about the diffs in the case when the version identifiers are the
same for the jars in question.
For example, in RC1, the plugin 'maven-java-plugin
This won't happen again. In RC1, plugins were built with the release. With
RC2 and beyond, they were built in advance and released as is.
However, many that didn't change were rebuilt for RC2. Its likely the
difference is a new manifest and Apache license.
It isn't something to be concerned
Hi,
I have found an issue in RC2 in maven.bat on line 56:
if exist %JAVA_HOME%\nul goto chkMHome
As there is no quotes around it, it fails when there is spaces in the
JAVA_HOME value e.g. program files.
I got it to work by changing the line to the following:
if exist %JAVA_HOME% goto
Fixed in CVS.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 12 May 2004 9:23 AM
To: [EMAIL PROTECTED]
Subject: RC2 Windows - Maven.bat does not allow spaces in JAVA_HOME
Hi,
I have found an issue in RC2 in maven.bat on line 56
[EMAIL PROTECTED] wrote on 12/05/2004 11:24:31:
Fixed in CVS.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 12 May 2004 9:23 AM
To: [EMAIL PROTECTED]
Subject: RC2 Windows - Maven.bat does not allow spaces in JAVA_HOME
Hi,
I have
You're right. The fix was for JAVA_HOME.
Can you submit a tested patch for JAVA_HOME?
- Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 12 May 2004 9:37 AM
To: Maven Users List
Subject: RE: RC2 Windows - Maven.bat does not allow spaces
Subject: RE: RC2 Windows - Maven.bat does not allow spaces in
JAVA_HOME
Brett,
I am a newbie at this, but I checked the Web Access CVS
before I posted. I
navigated to maven/src/bin/maven.bat and the latest revision was 1.40
which still had the fault. If it is already fixed
Subject: RE: RC2 Windows - Maven.bat does not allow spaces in
JAVA_HOME
Brett,
I do not have CVS access because of our firewall (will be
sorted out next
week). I have just copy and pasted revision 1.40 from Web
Access CVS into
WebSphere Studio done the change and created a unified
May 2004 1:14 PM
To: Maven Users List
Subject: RE: RC2 Windows - Maven.bat does not allow spaces in
JAVA_HOME
Brett,
I do not have CVS access because of our firewall (will be
sorted out next
week). I have just copy and pasted revision 1.40 from Web
Access CVS into
WebSphere
PROTECTED]
Sent: Wednesday, 12 May 2004 1:46 PM
To: Maven Users List
Subject: RE: RC2 Windows - Maven.bat does not allow spaces in
JAVA_HOME
Unfortunately the \nul and the quotes appear to be mutually
exclusive (at
least on Win2000).
I have tried:
if exist %JAVA_HOME%\nul goto
installation
with spaces?
Thanks,
Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 12 May 2004 1:46 PM
To: Maven Users List
Subject: RE: RC2 Windows - Maven.bat does not allow spaces in
JAVA_HOME
Unfortunately the \nul
I just recently upgraded from an RC1-SNAPSHOT to RC2 but when I ran the site
goal maven gives me a NoSuchGoalException for maven-license-plugin:register
in the xdoc plugin. Any ideas what might be causing this?
Yoway Buorn
Software Engineer
Imagery Systems Engineering
GENERAL DYNAMICS
Advanced
Clear your plugin cache and try again (rm -rf ~/.maven/plugins on unix)
RC3 fixes the problem
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 11 May 2004 7:36 AM
To: [EMAIL PROTECTED]
Subject: Upgrade to RC2 and then NoSuchGoalException
I
=no
j:include uri=${stylesheet.toString()}/
/j:file
Is this right? Any idea why it can't parse?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 10, 2004 4:08 PM
To: 'Maven Users List'
Subject: RE: Upgrade to RC2
May 2004 9:21 AM
To: [EMAIL PROTECTED]
Subject: RE: Upgrade to RC2 and then NoSuchGoalException
I tried clearing the plugin cache and I ran the site goal
once more, but now maven is complaining about this,
BUILD FAILED
File..
file:/export/home/cruise/.maven/plugins/maven-xdoc
I'll take the option with the smiley next to it.
Thanks.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 10, 2004 4:25 PM
To: 'Maven Users List'
Subject: RE: Upgrade to RC2 and then NoSuchGoalException
Ah, this is a bug in xdoc-1.6 which was fixed
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
I finally got it working. And well. Does all the things I
had ever dreamed an aspectj-plugin would do. :)
I will update the documentation files over the next two or
three days.
After that
what should I do with everything
]
Sent: 28 April 2004 02:00
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I finally got it working. And well. Does all the things I had ever
dreamed an aspectj-plugin would do. :)
I will update the documentation files over the next two or three days.
After that
what
aspectj.weave and aspectj.weaveWith but,
what do you think?
-Mensaje original-
De: Vincent Massol [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 18:22
Para: 'Maven Users List'
CC: [EMAIL PROTECTED]
Asunto: RE: aspectj plugin maven 1.0 rc2
Hi Charles / Carlos,
Carlos
Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
Ok, one more question. :)
The current maven goal has jar:jar as a preGoal. So,
projectC.jar is created and then aspects are created on that
jar. With inpath we don't have to create the jar first and
then weave into it. We can weave
/dev
guide/antTasks-iajc.html because injars has been deprecated.
Thanks
-Mensaje original-
De: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 23 de abril de 2004 2:33
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
I should be able to get
guide/antTasks-iajc.html because injars has been deprecated.
Thanks
-Mensaje original-
De: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 23 de abril de 2004 2:33
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
I should be able to get to this next
I'd say we should go for 1.2. We can version the plugin as version 3.0.
Thanks
-Vincent
-Original Message-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: 23 April 2004 17:00
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
Correct. When you
PROTECTED]
Asunto: RE: aspectj plugin maven 1.0 rc2
I'd say we should go for 1.2. We can version the plugin as
version 3.0.
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
de 2004 17:13
Para: 'Maven Users List'; [EMAIL PROTECTED]
Asunto: RE: aspectj plugin maven 1.0 rc2
I'd say we should go for 1.2. We can version the plugin as
version 3.0.
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL
That line is mandatory
-Mensaje original-
De: Daniel Henrique Alves Lima [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 0:11
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the error
seems
To: Maven Users List
Subject: Re: aspectj plugin maven 1.0 rc2
I've added the following line in my project.xml and the error seems to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my
if you post the patch in JIRA and document
it.
-Mensaje original-
De: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 22 de abril de 2004 18:11
Para: Maven Users List
Asunto: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file
Users List
Subject: Re: aspectj plugin maven 1.0 rc2
A while back I inserted injars into my plugin.jelly file for the
aspecj
plugin and its been going great. It gives me the ability to weave an
aspect into a pre-compiled jar. This feature is available when using
iajc
so it is not something I
rc2
Hi Charles / Carlos,
Carlos has sent a big patch a few days back. I'm still
fighting to find some time to read it, analyze it and decide
whether we should apply it as is or with some tweaks (I think
we agree to remove the autoweave feature for example). There
are several parameters
]
Asunto: RE: aspectj plugin maven 1.0 rc2
Hi Charles / Carlos,
Carlos has sent a big patch a few days back. I'm still
fighting to find some time to read it, analyze it and decide
whether we should apply it as is or with some tweaks (I think
we agree to remove the autoweave feature for example
in the Problem with RC2's site goal thread. I'm running it on Unix as
well.
Anyway, here's the additional output to the third problem :
- BEGIN SNIPPET ---
[echo] Generating /home/user/ft/target/docs/linkcheck.html from
/home/user/ft/target/linkcheck/docs/linkcheck.xml
BUILD FAILED
anyone been able to confirm my first problem? Should I install the
JAVANSS plugin differently?
I've raised MAVEN-1242 in JIRA for the second problem
(clover/JDK131/XML) as you suggested.
As for the third problem it looks like it's similar to the issue
discussed in the Problem with RC2's site
.
-Mensaje original-
De: Daniel Henrique Alves Lima [mailto:[EMAIL PROTECTED]
Enviado el: miércoles, 21 de abril de 2004 22:12
Para: Maven Users List
Asunto: aspectj plugin maven 1.0 rc2
Hi, everybody !
I'm trying to use aspectj plugin with maven 1.0rc2 but
i'm getting
-Vincent
-Original Message-
From: Daniel Henrique Alves Lima [mailto:[EMAIL PROTECTED]
Sent: 21 April 2004 22:12
To: Maven Users List
Subject: aspectj plugin maven 1.0 rc2
Hi, everybody !
I'm trying to use aspectj plugin with maven 1.0rc2 but i'm getting
the following
]
Sent: 21 April 2004 22:12
To: Maven Users List
Subject: aspectj plugin maven 1.0 rc2
Hi, everybody !
I'm trying to use aspectj plugin with maven 1.0rc2 but i'm getting
the following error:
aspectj:weave-internal:
[move] Moving 1 files to /projects/new_project/target
copyInjars not required
I've added the following line in my project.xml and the error seems to
stop :
aspectSourceDirectorysrc/java/aspectSourceDirectory
Daniel Henrique Alves Lima wrote:
Now i'm getting this already defined message for all my classes...
Can be a configuration problem ? I don't have any
[mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 April 2004 2:17 AM
To: Maven Users List
Subject: Re: 3 issues found while upgrading to rc2
Hi
I'm new on this list, but I also experienced this issue.
I made a quick heck as follows:
Edit .maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly
add
Hi All,
First, thanks for a terrific product. Now to my concerns. I have found some
issues while upgrading from rc1 to rc2 that I thought you might be
interrested in.
Here's what I did when upgrading:
1) Completely removed the rc1 (including ~/.maven directory)
2) Installed the rc2
Hello,
This failed build cited below is driving me crazy. After migrating from RC1 to RC2 the
site goal doesn't succeed any longer. The position on which the build process halts is
the
line marked with the arrow:
j:file name=${outFile} encoding=${outputencoding
Just in case: the XDoc-Plugin in Version 1.6
-Ursprüngliche Nachricht-
Von: Christian Nill [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 19. April 2004 18:38
An: Maven Users List
Betreff: Problem with RC2's site goal
Hello,
This failed build cited below is driving me crazy. After
in case: the XDoc-Plugin in Version 1.6
-Ursprüngliche Nachricht-
Von: Christian Nill [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 19. April 2004 18:38
An: Maven Users List
Betreff: Problem with RC2's site goal
Hello,
This failed build cited below is driving me crazy. After migrating from RC1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into what I think was the same problem about a month ago
(it's hard to tell because the original post in this thread did not
include the error messages or line number). I guess there is something
in RC2 that works in Windows does
1) JAVANCSS fails
classloader 'maven.root' not found. Adding dependencies to
the project
classloader instead
Maven.root never existed, but I think these can be ignored as they are
putting it where it expected to be put.
javancss:do-html:
[java]
[java] (Location of error
: having troubles with maven RC2
It is probably a problem in the maven cactus plugin.
To solve it you can add the next dependance to the
~/.maven/plugins/cactus-maven-1.6dev-20040226/project.xml
dependency
groupIdcommons-jelly/groupId
artifactIdcommons-jelly-tags-xml
Would be required if you use any jelly:xml in cactus.
- Brett
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Sunday, 18 April 2004 12:23 AM
To: 'Cactus Users List'; 'Maven Users List'
Subject: RE: having troubles with maven RC2
Hi Nicolas,
Not sure
Hi,
I am having a problem since the rc2 where invoking the goal
appserver:install does not create the tomcat instance directory under
maven.appserver.dir (defined in the plugin.properties of the appserver
plugin). After investigating the problem I realized that the goal calls
the goal
Fixed this morning in CVS. Will all work as of RC3.
- Brett
-Original Message-
From: Guillaume Lasnier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 14 April 2004 3:25 AM
To: Maven Users List
Subject: Pb with appserver plugin since rc2
Hi,
I am having a problem since
respond toSubject: Re: HELP! - rc2 - resource
exception on download
users
-Original Message-
From: Dan Washusen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 11:54 PM
To: Maven Users List
Subject: Re: HELP! - rc2 - resource exception on download
I found that upgrading to RC2 also caused me some issues. I just
deleted (moved away) my
Hi Max, just want to let you know that you are not alone on your planet,
I have the exact same problem : With RC2, I must install manually many
jars in my local repository, even when the correct version is present in
the remote repo and the project.properties file is correctly configured
(at least
]
|
| cc:
|
| Subject: RE: HELP! - rc2 - resource exception on download
, April 08, 2004 10:20 AM
To: [EMAIL PROTECTED]
Subject: RE: HELP! - rc2 - resource exception on download
Thanx Martin - here's my environment spec, to possibly identify
similarities:
os: Sun Solaris 2.6
jdk: tried both 1.3.1, 1.4.1
locale: en
also, I have to go through a proxy for downloads
Ever since upgrading to rc2, I cannot run any maven goals that require
fetches from the remote repo... maven crashes out w/ the following message:
BUILD FAILED
File..
file:/export/java/maven/currentversion/plugins/unpacked/maven-xdoc-plugin-1.6/plugin.jelly
Element... attainGoal
Line
[EMAIL PROTECTED] wrote:
Ever since upgrading to rc2, I cannot run any maven goals that require
fetches from the remote repo... maven crashes out w/ the following message:
BUILD FAILED
File..
file:/export/java/maven/currentversion/plugins/unpacked/maven-xdoc-plugin-1.6/plugin.jelly
Element
Ok, I need to revisit the FAQ and change it to match.
Can you build a small app that replicates this on a clean RC2 install and
post to JIRA? I can't replicate it.
Thanks,
Brett
-Original Message-
From: Darren Hartford [mailto:[EMAIL PROTECTED]
Sent: Friday, 2 April 2004 11:55 PM
Ah, I missed that in the FAQ. Unfortunately the FAQ does conflicts with the
project.xml file from CVS, and the commons-jelly jars in the maven-1.0-rc2 binary
distribution where both are 20030902.160215 opposed to FAQ's 20030211. This
specifically is occuring when calling 'multiproject
1 - 100 of 165 matches
Mail list logo
