Hi there,
I have the following maven project setup:
master
| module1
| class ClassA (has annotation @Annotation)
| module2
| class ClassB (also has annotation @Annotation)
and I'm building it with maven, and I use an AbstractProcessor during
compilation
There are a number of issues within JIRA that are the result of Resource
access issues.
They way I see it, we have 4 different resource access issues when
dealing with plugins/reports.
1) resources from dependency in parent pom.
2) resources from transitive dependency.
3) resources from
Sounds like a great idea! They should all go in maven-core-it (possibly
as multiple projects). This is really the integration testing of the
Maven distribution, not just the maven-core library.
- Brett
Joakim Erdfelt wrote:
There are a number of issues within JIRA that are the result of
From: Brett Porter [EMAIL PROTECTED]
What forking are you using in m1/ant?
None. Or rather, whatever the default is-- I have nothing in
project.properties that says otherwise.
Likewise, nothing special in the surefire configuration in pom.xml, so I'm
using the defaults there, too.
I've
(resending from the right address...)
From: Brett Porter [EMAIL PROTECTED]
What forking are you using in m1/ant?
None. Or rather, whatever the default is-- I have nothing in
project.properties that says otherwise.
Likewise, nothing special in the surefire configuration in pom.xml, so I'm
ok. I'm not sure whether recreating the classloader for each test is
really necessary though, but we can look into it.
Is this something you can correct by some appropriate commands in
tearDown() ? It seems that would be more robust across test runners (I'm
not sure how IDEs handle your
From: Brett Porter [EMAIL PROTECTED]
ok. I'm not sure whether recreating the classloader for each test is
really necessary though, but we can look into it.
I'm not sure it's necessary either-- but it is different from the way it
worked in m1, so it's worth noting.
Is this something you can
