I notice the "Maven Dependencies" container resolves "runtime" scope
dependencies for compilation which allows one to use them
erroneously while writing code in Eclipse. This will reveal the
error later, when building from the command-line. Is it possible
the "Maven Dependencies" container re
Sun, 16 Oct 2011 21:54:54 +0300, /Stanimir Stamenkov/:
I would also like to see an option to resolve only declared
dependencies for compilation and not their transitive dependencies,
e.g. using the dependency:analyze goal one could get warnings like
"Used undeclared dependencies found" - it woul
Sun, 16 Oct 2011 23:21:13 +0300, /Stanimir Stamenkov/:
Would it be possible to automatically classify APIs from
transitively resolved dependencies as forbidden or discouraged
(probably depending on an m2e setting) and then the Java Compiler
settings for marking access to those as errors/warnings
Sun, 16 Oct 2011 23:25:16 +0300, /Stanimir Stamenkov/:
I've now realized if the above is possible, it could be used to
restrict the usage of "runtime" dependencies for compilation, also
(marking their APIs as forbidden, but still placing them on the
classpath for run configurations).
It appear
This is a limitation of JDT. Eclipse Java project will use single
classpath and single set of compiler preferences for all project
sources, which in m2e case means both main and test sources. Because of
this, m2e needs to use dependencies of all scopes (test scope includes
all other scopes) both f
Sun, 16 Oct 2011 17:41:42 -0400, /Igor Fedorenko/:
This is a limitation of JDT. Eclipse Java project will use single
classpath and single set of compiler preferences for all project
sources, which in m2e case means both main and test sources. Because of
this, m2e needs to use dependencies of all
Mon, 17 Oct 2011 01:18:09 +0300, /Stanimir Stamenkov/:
... and then (optionally)
transitive "compile/provided" scope dependencies are restricted as
"discouraged"...
To clarify - _transitive_ "compile/provided" dependencies, unless
declared as explicit project dependencies.
--
Stanimir
_
Sun, 16 Oct 2011 17:41:42 -0400, /Igor Fedorenko/:
This is a limitation of JDT. Eclipse Java project will use single
classpath and single set of compiler preferences for all project
sources, which in m2e case means both main and test sources. Because of
this, m2e needs to use dependencies of all
I have a Maven war project which includes the following for including some
resources
../../sql
WEB-INF/sql
**/*.sql
../../reports
WEB-INF/reports
**/*.jasper
**/*.xslt
This has always worked fine in Maven (2 & 3) as well as the old m2eclipse.
The new m2e complains with "A
Can you try using ${basedir}/../../sql, this scenario
is tested in m2e-wtp :
https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp.tests/projects/WebResourceFiltering/top/mid/web/pom.xml
Regards,
Fred Bricon
2011/10/17 Collin Peters
> I have a Maven war project which
10 matches
Mail list logo
