This plugin needs two more binding votes before being released. Anyone
that missed this first go round care to vote?
Brett Porter wrote:
Please revise this to: 2.0.1-20060329.093329-3 (r389725). I noticed a
regression and a bug in the test-jar. I'm done now.
Please test this version before vot
Please send your question to [EMAIL PROTECTED]
- Brett
mathapfahl wrote:
Hi friends,
I want to install a jar in my local repo.
mvn install -f pom_components.xml
The problem: In the pom_components.xml I have a dependency with a variable
${maven.build.parent}
Now I thought I can write follow
Hi friends,
I want to install a jar in my local repo.
mvn install -f pom_components.xml
The problem: In the pom_components.xml I have a dependency with a variable
${maven.build.parent}
Now I thought I can write following:
mvn install -f pom_components.xml -Dmaven.build.parent=sys
But it does
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Maven Wiki" for change
notification.
The following page has been changed by FernandoR:
http://wiki.apache.org/maven/FrontPage
--
[http://www.j
Issue Subscription
Filter: Design & Best Practices (34 issues)
Subscriber: mavendevlist
Key Summary
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-1508Need a process-test-classes phase
http://jira.codehaus.org/b
I'll reply on the user list.
LaCasse, John wrote:
Why is it that properties don't get expanded when used inside of a
version tag? This seems like a bug to me and is making it impossible to
incorporate maven into our build environment because we can't get maven
to use a version property from outs
Why is it that properties don't get expanded when used inside of a
version tag? This seems like a bug to me and is making it impossible to
incorporate maven into our build environment because we can't get maven
to use a version property from outside, i.e. via an environment variable
or something of
You are right, this is by design. I prefer to have a build fail by
default, even if the error is minor, because otherwise I tend to
overlook things.
The problem with sourceforge is that remote users don't have the right
to change the permission for the root site directory (htdocs), so the
There is a bug in the plugin caching mechanism in m1.0. Sometimes just
running the same goal a second time resolves the problem (or running a
fake goal, as Stephane suggests), but the best thing to do is just
clearing your cache.
However, I don't know exactly under which circumstances this hap
Fixed. Thanks for spotting this!
-Lukas
Dennis Lundberg wrote:
Hi Lukas
First off, thanks for pushing out new versions of all the Maven 1 plugins!
Reading through the changes report for the site plugin I couldn't quite
understand one thing. There seems to be an error in the changes report
+1
Emmanuel
Brett Porter a écrit :
It seems to be common to hit XML problems with surefire because it is
using child first classloading (like a webapp) to ensure you get what
you ask for which often causes xml problems because the apis are not in
the same place as the implementation.
I'd li
It's me again...
After getting the project site built correctly, I then tried to sshdeploy it to SourceForge using the new site-plugin. It didn't go all that well. Having switched back and
forth between 1.6.1 and 1.7-SNAPSHOT I have found one thing that's different in 1.7. This might be by desig
On 3 May 06, at 11:38 PM 3 May 06, Brett Porter wrote:
It seems to be common to hit XML problems with surefire because it
is using child first classloading (like a webapp) to ensure you get
what you ask for which often causes xml problems because the apis
are not in the same place as the i
When you have changed a plugin it's always better to call a fake goal (such
as cleanr or something) to make sure the cache is up-to-date. Some plugins
have a weird behavior in this case (such as the site/xdoc plugins)
Cheers,
Stéphane
On 5/4/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hello
Brett Porter wrote on Thursday, May 04, 2006 5:39 AM:
> It seems to be common to hit XML problems with surefire because it is
> using child first classloading (like a webapp) to ensure you get what
> you ask for which often causes xml problems because the apis
> are not in
> the same place as the
On May 3, 2006, at 11:38 PM, Brett Porter wrote:
It seems to be common to hit XML problems with surefire because it
is using child first classloading (like a webapp) to ensure you get
what you ask for which often causes xml problems because the apis
are not in the same place as the implemen
Hello
It seems that there was a glitch during the upgrade. I tried a couple of other projects and they all ran fine. So I went back and tried my project again, and it worked.
Then I looked back to the beginning of the session and found this snippet right at the start:
plugin maven-site-plugin-
+1
Vincent
2006/5/1, Brett Porter <[EMAIL PROTECTED]>:
Please test this as much as you can first, given that the classloader
has change somewhat.
Vote open for 72 hours, based on:
maven-surefire-plugin 2.2-20060501.172356-2 and 2.0-20060501.172351-2
(r398639)
[ ] +1
[ ] +0
[ ] -1
http://jira
Hi Dennis,
Can you try to clean your plugins cache ?
The new site plugin doesn't need a newer release of the xdoc plugin.
It seems that maven lost your xdoc plugin 1.9.2.
Arnaud
On 5/4/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Lukas,
I tried the site plugin on a SourceForge project I
Lukas,
I tried the site plugin on a SourceForge project I work on, but the site
generation fails. Here's what I did:
- maven clean
- maven site (all is well)
- maven clean
- upgrade from maven-site-plugin-1.6.1 to maven-site-plugin-1.7-SNAPSHOT
- maven site (ERROR see below)
...
xdoc:generate
Thx, Dennis,
You're right, it's an error in my comment. I can't commit it actually, if
Lukas can do it..
Otherwise, +1 for all.
Arnaud
On 5/4/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi Lukas
First off, thanks for pushing out new versions of all the Maven 1 plugins!
Reading through
Hi Lukas
First off, thanks for pushing out new versions of all the Maven 1 plugins!
Reading through the changes report for the site plugin I couldn't quite
understand one thing. There seems to be an error in the changes report
[1] for maven-site-plugin-1.7. The comments made in issue MPSITE-39
22 matches
Mail list logo
