Okay, then I may have been doing something wrong.
I think I needed to clean the project before rebuilding the site.
It seems to be working now. Thanks!
I'll take a look at the proposal.
-K
On Aug 9, 2008, at 12:40 PM, Hervé BOUTEMY wrote:
Hi,
This parameter works on my projects.
What
I vote (a). Use UTF-8.
I'd actually prefer an option under the reporting element to set the
encoding to a desired value and
have it default to UTF-8, but I can live with a procrustean solution.
-K
Hervé BOUTEMY wrote:
Dear community,
The Maven team is currently discussing a proposal
Hello,
I have recently upgraded my macbook pro from the standard version of maven
(2.0.6) to 2.0.9, and am getting the following error on 'mvn install':
Embedded error: Error while executing the external compiler.
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/../bin/javac:
not
This question is really just highlighting my ignorance of how maven
works but I've been unable to find this documented anywhere. The problem
I'm having is mavens use of repositories, I know maven by default uses
the central repo at http://repo1.maven.org/maven2 when locating
artifacts, I also
The home looks ok - I'm not sure why it's looking in ../bin instead of
$JAVA_HOME/bin - have you configured the compiler plugin in some way?
You might be interested in this script for changing versions of Maven:
http://jira.codehaus.org/browse/MNG-2730
Cheers,
Brett
2008/8/11 darnokA [EMAIL
On Sun, Aug 10, 2008 at 3:37 PM, Matt Milliss [EMAIL PROTECTED] wrote:
As far as I understand these are
the only repositories my installation should be using but what I find is
there are others that I haven't defined that are being used
...
Where do these repositories
come from if I haven't
These can sometimes be introduced by dependencies (though some of
these strangely seem to come from plugins that shouldn't be
introduced).
Using Archiva will help - you can have your Maven install locked to
using that no matter what repositories are encountered, and then use
the proxying combined
Hey all
The issue I'm having is wondering what the best way to set up our maven
internal repo. Should we use the repo to hold production builds or developer
builds or should we have a two repos or ?.
Atm we use the repo to store production build artifacts. But this is not the
best solution for
2008/8/11 rmahnovetsky [EMAIL PROTECTED]:
Hey all
The issue I'm having is wondering what the best way to set up our maven
internal repo. Should we use the repo to hold production builds or developer
builds or should we have a two repos or ?.
I think it's a good idea to separate them. I
Thanks Brett for your inputs.
You are right the both TC webserver and Build Agent were configured by
default to run as local system account.
I changed them to run with my user and also removed the localRepository
tag from maven installation/conf/settings.xml. After the restart
everything works
wow what service, super fast reply ;)
That is a good point with minimizing the difference between config for the
artifacts. Which we can do in the majority of the situations. Really the
only time we can't is when we have to split up a web app into core and a web
components, so core will then
Hi guys,
My SVN is set up with pre-commit hooks to verify, 1. if there's comment,
2. if a ticket number is mentioned.
I couldn't find a way to specify comment (the scmCommentPrefix option
doesn't seem to help either), so whenever I run the `mvn
release:prepare` command, Maven will with this
When you say the scmCommentPrefix doesn't help - does the option not
work, or is it not letting you change the comment to the extent you'd
like? Currently, I don't think there is any other way to configure it.
Of course, the values are consistent, so you might be able to change
your pre-commit
13 matches
Mail list logo
