Wendy Smoak-3 wrote:
It could go on
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
.
Can you open a JIRA issue if there isn't one, and possibly suggest a
patch?
Done, cf. http://jira.codehaus.org/browse/MNGSITE-86
-- Thorsten
--
View this message in
Hello,
I just found a---to my best knowledge---undocumented feature and though I
should share it with the community in the hope that it will made its way
into the Maven documentation.
The feature is that you can use the negation symbol ! within a profile
activation specifification not only to
-1
Background: According to http://jira.codehaus.org/browse/MFINDBUGS-66, the
plugin integrates Findbugs version 1.3.6. Meanwhile, version 1.3.8 was
released. I suggest to catch up with that release before releasing the
plugin.
-- Thorsten
Garvin LeClaire-2 wrote:
The Maven Findbugs
Hello,
I'm facing some behavior regarding activation of multiple profiles within a
pom.xml, which is contrary to what I was expecting. Maybe someone can help.
I have a pom consisting of three profiles:
profiles
profile!-- Set tools.jar for most SUN JDKs. --
iddefault/id
I can confirm your observation, i.e., it doesn't work for me either (using
Maven 2.0.9 and site plugin 2.0-beta-7). But I havn't checked if there is
already an issue about that in JIRA.
-- Thorsten
Czollli wrote:
Hello,
according to the APT format a text like this:
Some text
Hello,
I'm creating a project Web site using the Maven site plugin. The project is
currently in a SNAPSHOT state, that is, the assembly that I create (and
artifacts) have a timestamp suffix attached to their file name when the get
deployed to some Maven repository.
Assuming that the build
Hello,
we face a rather advanced requirement regarding creation of various
assemblies in a multimodule project. What we are trying to achieve is as
follows.
Assume there is a root project P consisting of multiple module projects M1,
..., Mn (hierarchy depth max. 1). From the root POM we create
Sorry, the subject of this posting is false. I used Nabble to post that
message and for some strange reason it used a subject from an earlier
posting. I re-posted this message with the correct subject.
-- Thorsten
TM wrote:
Hello,
we face a rather advanced requirement regarding
This was eagerly awaited. Thanks for the good work!
However, I've found one minor difference that caused a change in my assembly
descriptors when upgrading from 2.2-beta-1 to 2.2-beta-3. So far, it was
possible to exclude an entire directory from a fileset just by listening its
name, as in the
Multi-module project fails with NPE on assembly:assembly (assembly plugin
used 2.2-beta-1; command used was mvn clean install assembly:assembly
eclipse:eclipse). Same configuration works with Maven 2.0.9. Below you will
find relevant excerpt from the build trace.
Best regards,
Thorsten
[INFO]
Hello,
today I tried to upgrade the Maven assembly plugin from 2.2-beta-1 to
2.2-beta-2. However, I noticed that for my project which consists of
multiple modules the resulting binary assembly now contains dependency JAR
files multiple times. The assembly descriptor contains the following
nicolas de loof-3 wrote:
For 1), you should use exclusions to block transitive dependencies.
For 2), any code generation plugin that runs before generate-resource
phase
will get executed by mvn eclipse:eclipse and the generated source folder
added to the .classpath. If you don't get
Hello,
I'm facing two issues regarding the Maven Eclipse plugin for which I havn't
found a soulution yet.
1.) Consider the simple scenario: project A depends on project B, B depends
on JAR xyz. If I run mvn eclipse:eclipse for A it will add xyz to the
classpath; so far so good. What if I want
Yes, when mvn eclipse:eclipse is run for a multi module project, the
dependencies between the modules will be project dependencies.
I see. After I started it from the root project it did work as wanted.
Thanks.
Still remains the (minor) question to me why does the plugin behaves
different
Hello,
my question is about whether it is possible to let the Maven Eclipse plugin
create the .classpath file in a way that it will directly reference
dependency projects instead of referencing the JAR artifact from the local
repository. The following example .classpath file for a project named
15 matches
Mail list logo
