I have maven-checkstyle-plugin(v2.5) and maven-eclipse-plugin(v2.8)
configured.
Everything worked as expected but as soon as I introduced,
*AND/OR* to my checkstyle-config.xml, I started to
have problems building the project.
Here is what I get:
[ERROR] BUILD ERROR
1> [INFO]
---
Thanks for your response.
I was actually missing the from the and
all of my errors were actually warnings.
I set it to warning and it worked.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-build-does-not-fail-due-to-checkstyle-errors-tp5801275p5801305.html
Sent fro
You either have to execute it manually with
mvn checkstyle:check
or if you want it to run as part of a normal build you have to bind it to a
lifecycle phase in the config
process-sources
I configured Maven to use the checkstyle plugin.
Here is what I have in pom.xml's build section :
org.apache.maven.plugins
maven-checkstyle-plugin
2.5
check
There is no bug here. I was mistaken. I inadvertently neglected to
convert one of the MQ jars to system scope and so it still appeared in
the manifest. System scope jars are NOT included in the manifest which
is the correct behavior.
Sorry for the confusion.
On 07/28/2014 09:43 AM, Steve C
I am interested on the query capability. However, I ended up to use
maven-dependency-tree and maven-compat to resolve artifacts. Take a look at
maven-dependency-plugin, maven-report-info-plugin, license-maven-plugin for
various sample code. However, those are not directly deal with aether
-D
O
I have a fairly large Maven build where I often get build errors relating
to failures to either create something on the local disk or delete
something. The module that fails varies but here is an example.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.5.1:unpack
I don't think so. The path that must be provided with system scope is a
feature I very much want. I chose system over provided for this reason.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requ
I'm now being told by IBM that they provide OSGI-compliant jars which
may make all this moot.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requirements, I think scope system is exactly what
I nee
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requirements, I think scope system is exactly what
I need and your blanket statement that I shouldn't use this seems too
rigid.
To review, these are my requirements.
1) Project already built w
Actually, given my requirements, I think scope system is exactly what I
need and your blanket statement that I shouldn't use this seems too rigid.
To review, these are my requirements.
1) Project already built with Maven and don't want to change that. We
want to continue using Maven both with
system is for JAR files that are supposed to be put in the
JVM's ext directory or equivalent.
You do not want to use system
On 28 July 2014 15:43, Steve Cohen wrote:
> Sadly, my hopes were not completely fulfilled.
>
> In spite of specifying the MQ jars as system dependencies with their own
>
Hi Steve,
You could amend your classpath manually to include the necessary jars as I
suggested in my previous mail, using a maven-jar-plugin configuration
block. Then "java -jar" might still work. Although I have never used that
feature with nonrelative paths... are you sure it would work?
-Curti
Sadly, my hopes were not completely fulfilled.
In spite of specifying the MQ jars as system dependencies with their own
paths, the maven manifest generator ignored these paths. This means
that I must no longer run my application with java -jar, relying on the
classpath manifest, but must spec
I think the most painless and maven-like way to proceed given the
non-maven requirements of IBM here is to install the IBM Websphere MQ
client package on each development or production machine that needs it
and alter pom xml to make these system-scope dependencies, which lets me
specify the non
I still do not see the release in Maven Central. Thoughts?
Gary
On Fri, Jul 25, 2014 at 3:31 PM, Gary Gregory
wrote:
> Could you only announce after the plugins surface on MC? Right now I only
> see 2.5.4.
>
> Gary
>
>
> On Fri, Jul 25, 2014 at 11:34 AM, Garvin LeClaire <
> garvin.lecla...@gma
On 07/22/2014 06:51 PM, Preston, Dale wrote:
I was just wondering why this group uses an email list rather than a forum. It
seems forum software is more searchable and filterable than email lists.
I'd rather Mailing-List.
-
Hi,
I am developing a plugin that needs to query the repositories. I'm using the
Aether API because I thought that's the Maven 3 way to do it (cf.
http://blog.sonatype.com/2011/01/how-to-use-aether-in-maven-plugins/) and
because many of the Maven 2 methods are marked as deprecated. With Maven
18 matches
Mail list logo
