Brett,
We are in the progress of moving to Maven 2 and at the moment we just use a
local drive (c:) or a shared drive as a repository.
We are trying to come up with a standard for the whole organisation and for all
projects executed internally. So what we need is 1 central company wide
2.1 is the latest version of maven-idea-plugin for Maven 2. Please read
the documentation for this version here:
http://maven.apache.org/plugins/maven-idea-plugin/
You referenced properties in your first mail. Those only work in the
IDEA plugin for Maven 1. The Maven 2 plugin is configured
Zeltner Martin wrote:
I can't find any doc how to declare the doxia-module-twiki in my pom
that mvn site will render my twiki files in src/site/twiki to
target/site.
If anyone else is interested, I think something has changed here. I just
tried it this morning and it worked (yesterday
Dave Syer wrote:
It doesn't work with site:run as far as I can tell...
That's wrong, it does work. Awesome.
The only issue I can see is that there are some inconsistencies between the
way that the HTML is rendered from twiki and the other doxia formats - e.g.
it uses div class=section
Dave Syer wrote:
The only issue I can see is that there are some inconsistencies between
the way that the HTML is rendered from twiki and the other doxia formats -
e.g. it uses div class=section instead of h2 - so you need a
different css.
http://jira.codehaus.org/browse/DOXIA-125
--
I have found this to be fixed with 2.0.7 - give it a shot.
Andy
On 25 Apr 2007, at 21:54, Mykel Alvis wrote:
Once upon a time, in the distant past (Maven 2.0.5 and before), the
instructions found on the Maven User Wiki (at
http://docs.codehaus.org/display/MAVENUSER/Deploying+3rd+Party+Jars
Hello All,
I'm trying to integrating Maven in my project.
I was quite comfortable using maven 1.0.
But with Maven 2.0 I have one problem to define dependency of a jar file.
I wants to define dependency without having a version number. how can I do
that ??
Please suggest me
Best Regards
Ah, now I see what you mean. This does indeed look strange, especially
the wording of the message. On the other hand, it is just an INFO and
not a WARNING like the other problems found by the dependency:analyze
goal. I don't know if this behavior is intended. The message may be
even
useful,
Hi all,
I would like to customize the site.xml and add couple of logos as
compensation for
free licenses I got for my open source project with the powered by style
logo.
The problem is that site.xml poweredBy tag ignores the following HTML
parameters:
width height, border e.g.:
logo
On 6/30/07, Giovanni Azua [EMAIL PROTECTED] wrote:
I would like to customize the site.xml and add couple of logos as
compensation for
free licenses I got for my open source project with the powered by style
logo.
You might want to create a custom skin for your project instead of
using the
Thank you, that is a good idea. Is there a method which I could call
which would tell me what repositories are used by the various plugins?
Otherwise, would you suggest that I open the various POM's and obtain
the information from these? Thanks.
This message (including any attachments)
On 6/29/07, Morgovsky, Alexander (US - Glen Mills)
[EMAIL PROTECTED] wrote:
My Maven process runs in a controlled environment where I do not have
connectivity to the internet. For this reason, I placed all the Maven
dependencies from repositories like repo1 and codehaus onto our company
Hi V,
You may want to try http://www.jfrog.org/sites/dep-analyzer/latest/
dependency analyzer - it is a tool for viewing and analyzing maven
dependencies. It can help you if you have a pom with all your modules as
dependencies (some kind of parent pom).
Regards,
Dror Bereznitsky
Vanja
Hi all,
I'd like to test Maven2's ability to build eclipse plugin projects.
Therefore I built a little sample project as described on the home page of
the pde-maven-plugin (see here:
http://mojo.codehaus.org/pde-maven-plugin/examples/simple_plugin.html).
But unfortunately every attempt to build
It isn't the proxy. I've removed the proxy completely from the picture
and it hasn't helped. In fact, I've completely deleted the
org/apache/maven/plugins from my local repo, and for some reason it is
trying to pull the 2.0-alpha-1 version of the maven-dependency-plugin.
Additionally, this
You should specify a version for the plugin in your pom. That is the
only way to know for sure which version will be used.
Brad O'Hearne wrote:
It isn't the proxy. I've removed the proxy completely from the picture
and it hasn't helped. In fact, I've completely deleted the
Thanks to a friend, who hopefully will post a description of the problem
later this weekend to the list, the problem was identified and a
workaround found. The problem is maven, and lack of class-loading
isolation for plugins in child modules of a parent project. In a
nutshell, the first
I have seen this occur as well. First project to use a plugin picks the
version for everyone else in the reactor.
-Original Message-
From: Brad O'Hearne [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 30, 2007 2:14 PM
To: Maven Users List
Subject: Re: repeated problems with
On 6/30/07, Brian E. Fox [EMAIL PROTECTED] wrote:
Ah, now I see what you mean. This does indeed look strange, especially
the wording of the message. On the other hand, it is just an INFO and
not a WARNING like the other problems found by the dependency:analyze
goal. I don't know if this behavior
Try: @phase pre-site
In any case, you can for binding to pre-site with
executions
execution
phasepre-site/phase
goals
goalinit-project/goal
/goals
/execution
/executions
On 6/24/07, Libor Kramoliš [EMAIL PROTECTED] wrote:
This is not a bug - if you want to specify a specific JVM to run, try using
the executable element to specify a path. You can even use the ${
env.JAVA_HOME} variable, like ${env.JAVA_HOME}/bin/javac
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html
http://mojo.codehaus.org/webstart-maven-plugin-parent/webstart-maven-plugin/howto.html
Eric
On 6/27/07, Billy Bacon [EMAIL PROTECTED] wrote:
I'm looking to use Maven 2 to manage a Java Web Start application. Would I
just package the entire contents within a .war file with the .jnlp file in
One idea:
Create a profile that configures the compiler plugin with
debugfalse/debug.
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
Then in the profile, configure the jar plugin to have a classifier -
something like non-debug.
Then, when you want to install w/ debug
Sure there's a way:
http://sourceforge.net/projects/pdfdoclet/
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html
When you work out the kinks - please post your results... :)
Thanks;
Eric
On 6/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi,
is it
I followed the link you provided. Please correct me if I am wrong, but
the capability in Maven 1 IDEA plugin to turn off exclusion of the
target directory tree is missing. So is the mechanism to mark the
xmlbeans generated source directory as an IDEA source directory. Unless
the
25 matches
Mail list logo
