Could it be that it declared in one of your dependencies? Just a guess as I
don't know if Maven warns for that or not.
What are the console output just before and after these two warnings?
/Anders
On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström pop.qvarnst...@gmail.com
wrote:
Hi,
I've
If maven warns for dependencies I'm good, did - for no good reason - not
think that was the case. Thanks.
Slightly edited console output before, including and after warnings:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for
Hi,
I've searched the best I can, but have not been able to find a solution.
When running maven 3 to build an older project I get what seems like
self-explanatory warnings:
[WARNING] The expression ${artifactId} is deprecated. Please use
${project.artifactId} instead. and
[WARNING] The
It could be interesting to know if that is the reason. Try removing the
dependencies and see if Maven still complains.
/Anders
On Wed, Feb 25, 2015 at 2:34 PM, Pop Qvarnström pop.qvarnst...@gmail.com
wrote:
If maven warns for dependencies I'm good, did - for no good reason - not
think that
Tried without dependencies, to no avail. However, when that made no
difference, I started searching the local repo and found a grandparent pom
using these expressions. Searching in files based on extensions (*.xml)
made me miss that one during the first round, since it is named .pom.
Effective
OT: It is! (Noticed the sig as soon as I hit send, i.e. as soon as it was
to late to remove.) Thanks again!
Cheers,
Pop
2015-02-25 15:46 GMT+01:00 Anders Hammar and...@hammar.net:
Tried without dependencies, to no avail. However, when that made no
difference, I started searching the local
Tried without dependencies, to no avail. However, when that made no
difference, I started searching the local repo and found a grandparent pom
using these expressions.
Ok, great that you found the issue. Thinking harder I don't think Maven
would warn about this type of issues in dependencies.
Hi,
It is necessary to concentrate the maven plugin integration tests in its
own takari-jar project ?
I'm asking because I have test poms inside src/test/projects being
duplicated on both Plugin and Plugin IT projects.
Maybe I could put both UT and IT in the same plugin project ?
thanks,
I have a number of algorithms that output complicated data structures and I
have tests verifying the output.
Often, I’ll make one small change, which will then cascade and invalidate
all the tests causing them to fail. The NEW output is correct but now I
need to go through and update all my
Hi,
AFAIK this Takari project is not hosted neither maintained here at Apache
by Apache Maven developers.
So for any questions please ask directly maintainers or find a user group
related to it (maybe it's documented on their website).
Cheers
Olivier
On 26 February 2015 at 03:52, Cristiano
10 matches
Mail list logo
