Re: [AXIS2] Some project builds fail if goal "clean" is not used

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty





From: Thorsten Schöning <[hidden email]>
Sent: Tuesday, September 5, 2017 5:12 AM
To: [hidden email]
Subject: [AXIS2] Some project builds fail if goal "clean" is not used
 
Hi all,

I'm facing the problem that when I execute goals like "install" or
"test" without "clean" the build of some projects fail, the problem
seems to be with an existing or not "target" dir and it looks like
that because of that the build of some projects "thinks" it doesn't
need to compile classes etc. Which would be fine if it wouldn't delete
the formerly created classes itself without re-creating them! :-)

One example is with axis-metadata, were the following command fails
after a former successful build:

> mvn test --projects :axis2-metadata

While the following one succeeds:

> mvn clean test --projects :axis2-metadata

"clean" deletes the whole "target" dir, so a fresh new build is
executed. Without "clean", pre-compiled classes in
"target/test-classes" are deleted, but not re-created for some reason,
resulting in error messages like the following:

> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:testCompile (default-testCompile) on project axis2-metadata: Compilation failure: Compilation failure:
> [ERROR] /C:/Users/tschoening/Documents/Eclipse/Java Axis2/axis2/modules/metadata/test/org/apache/axis2/jaxws/description/DocLitWrappedImplWithSEI.java:[23,36] package org.test.proxy.doclitwrapped does not exist

Classes of "org.test.proxy.doclitwrapped" were available in the last
successful build and have been deleted, but no re-created. the
interesting thing as well is that really only the Java classes
themselfs have been deleted, the corresponding parent dir already
exists:

> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\modules\metadata\target\test-classes\org\test\proxy\doclitwrapped

I have that problem with various projects and it was driving me crazy,
because things like "Debug as/Maven test" etc. per project directly
from Eclipse were not working and such. I really need to always
execute "clean" in addition to the other goals to be sure a build
works.

Is that intended or some kind of build issue? Shouldn't "mvn install"
not only delete pre-compiled test classes, but also be able to create
them again?
MG>the built-in maven-compiler-plugin (the default of compile phase) compile *default* is not full but incremental compile
MG>of special note is the lastModGranularityMs parameter which you can set in maven-compiler-plugin configuration
/**
     * Sets the granularity in milliseconds of the last modification
     * date for testing whether a source needs recompilation.
     */
    @Parameter( property = "lastModGranularityMs", defaultValue = "0" )
    private int staleMillis;

MG>to avoid that heartache when implementing maven-compiler-plugin i always set useIncrementalCompilation = false e.g.

MG><groupId>org.apache.maven.plugins</groupId>
MG><artifactId>maven-compiler-plugin</artifactId>
          <configuration>
                 <useIncrementalCompilation>false</useIncrementalCompilation>

Mit freundlichen Grüßen,
Thorsten Schöning

MG>gruss
MG>Martin

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty







From: Thorsten Schöning <[hidden email]>
Sent: Saturday, September 9, 2017 6:25 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Samstag, 9. September 2017 um 02:28 schrieben Sie:

> the built-in maven-compiler-plugin (the default of compile phase) compile *default* is not full but incremental compile
> of special note is the lastModGranularityMs parameter which you can set in maven-compiler-plugin configuration

But there need to be something then which deletes already existing
compiled Java classes for no reason. Is that maven as well? Doesn't
make sense if it's afterwards not compiling what has been deleted
before. Sounds to me the deletion comes from somewhere else.

MG>maven-compiler-plugin (with incremental) overwrites most recent changed classes inside target\classes and target\test-classes
MG>maven-compiler-plugin (full compile) compiles and overwrites ALL classes (changed or not)

MG>as you have already discovered default behaviour for mvn clean is to delete ALL classes in target\classes and target\test-classes

MG>if you want mvn clean to delete specific filesets then you would configure maven-clean-plugin excludeDefaultDirectories=true 
http://maven.apache.org/plugins/maven-clean-plugin/clean-mojo.html
MG>unless you have aspectj -> java or some other conversion in place OR
MG> have specified an ant deletion there should be no "automatic deletion" of directories in mvn
MG>https://ant.apache.org/manual/Tasks/delete.html

MG>jenkins of course has its own delete plugin but i didnt hear you are using that so we will leave that for another day..

Mit freundlichen Grüßen,

Thorsten Schöning

MG>gruss
MG>martin

Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty





From: Thorsten Schöning <[hidden email]>
Sent: Saturday, September 9, 2017 9:27 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Samstag, 9. September 2017 um 13:36 schrieben Sie:

MG>>maven-compiler-plugin (with incremental) overwrites most recent changed classes inside target\classes and target\test-classes
MG>>maven-compiler-plugin (full compile) compiles and overwrites ALL classes (changed or not)

MG>>as  you have already discovered default behaviour for mvn clean  is to delete ALL classes in target\classes and target\test-classes

You are getting it wrong: The problem is e.g. "mvn test" without(!)
"clean". In that case there is something which deletes totally
unchanged, formerly successfully compiled classes and only the class
files itself, not the parent directory or any other directory. And
that is bad because some builds depend on formerly
compiled/packaged/whatever results and those are not available anymore
sometimes, because they has been deleted.

MG>which version surefire are you implementing?

MG>what is your surefire tempDir parameter set to?
MG>if you are setting tempDir to either target\classes or target\test-classes then surefire will surely eliminate that directory
MG>what is reportsDirectory set to
MG>if you are setting reportsDirectory to either target\classes or target\tests-classes then surefire will overwrite those contents at will
MG>what is testSourceDirectory set to?
MG>what is classesDirectory set to ?
 
MG>also surefire assumes $maven.project.base.directory/cwd_1 belongs to surefire and will delete that directory at will

MG>we need to stop spott talk and narrow down your surefire TestCase implementors which is one of 
  • TestNG
  • JUnit (3.8 or 4.x)
  • POJO
MG>an excellent surefire debugging tool is the directive
MG>redirectTestOutputToFile 

MG>what i would do 
MG>mvn compile
MG>set read-only attribute to the folder(s) you want to keep and run your test again e.g.
MG>mvn test --projects :axis2-metadata
MG>observe exception thrown by maven-surefire-plugin...what does it say?


Adding "clean" fixes that, because a complete rebuild is issued, but
that shouldn't be needed if I don't change things. Let me quote
myself:

> One example is with axis-metadata, were the following command fails
> after a former successful build:
>
> > mvn test --projects :axis2-metadata
>
> While the following one succeeds:
>
> > mvn clean test --projects :axis2-metadata

From my understanding, "mvn test ..." only shouldn't fail after a
successful former build, but it does. Instead it should simply execute
tests again, which it is doing, but it fails for some tests because
some of those depend on compiled Java classes which are not available
anymore.

So the question only is if "mvn test ..." should have deleted those
files or not.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
In reply to this post by Martin Gainty
This appears to be a bug in jaxb2-maven-plugin. If clean is not
executed, then that plugin skips code generation (which is correct),
but then it also skips the following line of code:

https://github.com/mojohaus/jaxb2-maven-plugin/blob/jaxb2-maven-plugin-2.3.1/src/main/java/org/codehaus/mojo/jaxb2/javageneration/AbstractJavaGeneratorMojo.java#L434

That means that the output directory is not added to the list of test
sources, resulting in compilation failures.

Andreas


On Tue, Sep 5, 2017 at 10:12 AM, Thorsten Schöning
<[hidden email]> wrote:

> Hi all,
>
> I'm facing the problem that when I execute goals like "install" or
> "test" without "clean" the build of some projects fail, the problem
> seems to be with an existing or not "target" dir and it looks like
> that because of that the build of some projects "thinks" it doesn't
> need to compile classes etc. Which would be fine if it wouldn't delete
> the formerly created classes itself without re-creating them! :-)
>
> One example is with axis-metadata, were the following command fails
> after a former successful build:
>
>> mvn test --projects :axis2-metadata
>
> While the following one succeeds:
>
>> mvn clean test --projects :axis2-metadata
>
> "clean" deletes the whole "target" dir, so a fresh new build is
> executed. Without "clean", pre-compiled classes in
> "target/test-classes" are deleted, but not re-created for some reason,
> resulting in error messages like the following:
>
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:testCompile (default-testCompile) on project axis2-metadata: Compilation failure: Compilation failure:
>> [ERROR] /C:/Users/tschoening/Documents/Eclipse/Java Axis2/axis2/modules/metadata/test/org/apache/axis2/jaxws/description/DocLitWrappedImplWithSEI.java:[23,36] package org.test.proxy.doclitwrapped does not exist
>
> Classes of "org.test.proxy.doclitwrapped" were available in the last
> successful build and have been deleted, but no re-created. the
> interesting thing as well is that really only the Java classes
> themselfs have been deleted, the corresponding parent dir already
> exists:
>
>> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\modules\metadata\target\test-classes\org\test\proxy\doclitwrapped
>
> I have that problem with various projects and it was driving me crazy,
> because things like "Debug as/Maven test" etc. per project directly
> from Eclipse were not working and such. I really need to always
> execute "clean" in addition to the other goals to be sure a build
> works.
>
> Is that intended or some kind of build issue? Shouldn't "mvn install"
> not only delete pre-compiled test classes, but also be able to create
> them again?
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: [hidden email]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
In reply to this post by Martin Gainty
Stop talking nonsense, Martin.

On Sun, Sep 10, 2017 at 2:40 AM, Martin Gainty <[hidden email]> wrote:





From: Thorsten Schöning <[hidden email]>
Sent: Saturday, September 9, 2017 9:27 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Samstag, 9. September 2017 um 13:36 schrieben Sie:

MG>>maven-compiler-plugin (with incremental) overwrites most recent changed classes inside target\classes and target\test-classes
MG>>maven-compiler-plugin (full compile) compiles and overwrites ALL classes (changed or not)

MG>>as  you have already discovered default behaviour for mvn clean  is to delete ALL classes in target\classes and target\test-classes

You are getting it wrong: The problem is e.g. "mvn test" without(!)
"clean". In that case there is something which deletes totally
unchanged, formerly successfully compiled classes and only the class
files itself, not the parent directory or any other directory. And
that is bad because some builds depend on formerly
compiled/packaged/whatever results and those are not available anymore
sometimes, because they has been deleted.

MG>which version surefire are you implementing?

MG>what is your surefire tempDir parameter set to?
MG>if you are setting tempDir to either target\classes or target\test-classes then surefire will surely eliminate that directory
MG>what is reportsDirectory set to
MG>if you are setting reportsDirectory to either target\classes or target\tests-classes then surefire will overwrite those contents at will
MG>what is testSourceDirectory set to?
MG>what is classesDirectory set to ?
 
MG>also surefire assumes $maven.project.base.directory/cwd_1 belongs to surefire and will delete that directory at will

MG>we need to stop spott talk and narrow down your surefire TestCase implementors which is one of 
  • TestNG
  • JUnit (3.8 or 4.x)
  • POJO
MG>an excellent surefire debugging tool is the directive
MG>redirectTestOutputToFile 

MG>what i would do 
MG>mvn compile
MG>set read-only attribute to the folder(s) you want to keep and run your test again e.g.
MG>mvn test --projects :axis2-metadata
MG>observe exception thrown by maven-surefire-plugin...what does it say?


Adding "clean" fixes that, because a complete rebuild is issued, but
that shouldn't be needed if I don't change things. Let me quote
myself:

> One example is with axis-metadata, were the following command fails
> after a former successful build:
>
> > mvn test --projects :axis2-metadata
>
> While the following one succeeds:
>
> > mvn clean test --projects :axis2-metadata

From my understanding, "mvn test ..." only shouldn't fail after a
successful former build, but it does. Instead it should simply execute
tests again, which it is doing, but it fails for some tests because
some of those depend on compiled Java classes which are not available
anymore.

So the question only is if "mvn test ..." should have deleted those
files or not.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
AM-SoFT IT-Systeme „Neue Wege entstehen, indem wir sie gehen!“ AM-SoFT GmbH IT-Systeme, 1989 in Hameln gegründet, ist EDV-Systemhaus, Internet-Service-Provider ...



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty
In reply to this post by Martin Gainty


MG>see below




From: Thorsten Schöning <[hidden email]>
Sent: Sunday, September 10, 2017 12:11 PM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Sonntag, 10. September 2017 um 03:40 schrieben Sie:

There are no exceptions, even though using Process Monitor I can see
that someone tries to delete the files:

> 17:24:02,4152279        java.exe        16280   CreateFile      C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\modules\metadata\target\test-classes\org\test\proxy\doclitwrapped\FinOpResponse.class    ACCESS DENIED   Desired Access: Delete, Disposition: Open, Options: Non-Directory File, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

MG>maven-surefire-plugin should *never* delete testcases, maven-surefire-plugin should only *execute* testcases

MG>which version java?
MG>which version mvn ?
MG>which version maven-surefire-plugin?
MG>which version axis?
MG>can you place small sample on github and allow me to fork?


As you can see on "ACCESS DENIED", deletion is forbidden, tests
succeed, nothing is logged using "-X" param for Maven.

But the best is yet to come: If I remove "read-only" and am running
the test only again directly afterwards, it still succeeds and Process
Monitor doesn't log any attempt to delete files like the one above.
Even after 10 minutes have passed.
MG>this is a one-time anomaly..much harder to track (probably the reason this potential bug *slipped* thru the cracks)

If I "mvn clean test ..." and "mvn test ..." right afterwards, this
time without setting "read-only" in between, Process Monitor logs file
deletions again and things fail again.
MG>yes it seems the first time thru manifests the aberrant deletion

Such things are really annoying. :-)
MG>the testing phase for software is the only validation that a software release produces expected results that r reproducible and reliable
MG>you would be surprised how many professional programmers let a bug or 2 slip thru in a release
MG>fortunately Kristian, Tibor and Mirko are very responsive to cleaning up bugs and will work with you or i to make sure this bug 
MG>is identified AND fixed

Mit freundlichen Grüßen,

Thorsten Schöning

MG>Vielen Danke Thorsten!

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
On Mon, Sep 11, 2017 at 9:34 AM, Thorsten Schöning
<[hidden email]> wrote:

> Guten Tag Martin Gainty,
> am Montag, 11. September 2017 um 01:15 schrieben Sie:
>
> MG>>which version java?
> MG>>which version mvn ?
>
>> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2>mvn --version
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
>> Maven home: C:\Program Files\Apache Software Foundation\Maven\bin\..
>> Java version: 1.8.0_144, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.8\jre
>> Default locale: de_DE, platform encoding: Cp1252
>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>
> MG>>which version maven-surefire-plugin?
>
>>                <plugin>
>>                    <artifactId>maven-surefire-plugin</artifactId>
>>                    <version>2.20</version>
>>                </plugin>
>
> MG>>which version axis?
> MG>>can you place small sample on github and allow me to fork?
>
> I'm basically using current trunk with some small, unrelated
> modifications, like e.g. Eclipse project files, launch configurations
> etc. A "small example" is not that easy, because I would need to
> create a new pom.xml and such because of the project structure of axis2.

As I said earlier, this is a bug in jaxb2-maven-plugin. It should be
easy to reproduce on any project that uses the testXjc goal of that
plugin.

> I'm pretty sure it's best to do the same I'm doing, getting the whole
> trunk in either original or my version and executing command for
> individual projects like axis2-metadata. Just take the same commands
> from my former mails and see if it happens for you as well. I hope
> so... :-)
>
> https://github.com/apache/axis2-java
> https://github.com/tschoening/axis2-java
> https://github.com/tschoening/axis2-java/tree/libs_java_3rd_usage_trunk
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: [hidden email]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty
In reply to this post by Martin Gainty

axis2-kernel-1.8.0 has dependency org.apache.ws.xmlschema:xmlschema-core:jar:2.2.3-20170506.104137-3.jar


any suggestions to locate this jar?

______________________________________________




From: Thorsten Schöning <[hidden email]>
Sent: Monday, September 11, 2017 4:34 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Montag, 11. September 2017 um 01:15 schrieben Sie:

MG>>which version java?
MG>>which version mvn ?

> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2>mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Program Files\Apache Software Foundation\Maven\bin\..
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"

MG>>which version maven-surefire-plugin?

>                <plugin>
>                    <artifactId>maven-surefire-plugin</artifactId>
>                    <version>2.20</version>
>                </plugin>

MG>>which version axis?
MG>>can you place small sample on github and allow me to fork?

I'm basically using current trunk with some small, unrelated
modifications, like e.g. Eclipse project files, launch configurations
etc. A "small example" is not that easy, because I would need to
create a new pom.xml and such because of the project structure of axis2.

I'm pretty sure it's best to do the same I'm doing, getting the whole
trunk in either original or my version and executing command for
individual projects like axis2-metadata. Just take the same commands
from my former mails and see if it happens for you as well. I hope
so... :-)

https://github.com/apache/axis2-java


https://github.com/tschoening/axis2-java


https://github.com/tschoening/axis2-java/tree/libs_java_3rd_usage_trunk



Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty

great the d/l of xmlschema-core worked!

in modules/metadata/pom.xml i had to add target/GENERA~2/jaxb folder so mvn test-compile now compiles all tests


<!-- MG 09/11 add build-helper-maven-plugin to add target/GENERA~2/jaxb source folder -->
<plugin>
       <groupId>org.codehaus.mojo</groupId>
       <artifactId>build-helper-maven-plugin</artifactId>
       <executions>
         <execution>
           <id>add-test-source</id>
           <phase>generate-test-sources</phase>
               <goals>
             <goal>add-test-source</goal>
               </goals>
               <configuration>
              <sources>
               <source>target/GENERA~2/jaxb</source>
              </sources>
           </configuration>
                  </execution>
               </executions>
      </plugin>
<!-- end MG 09/11 add build-helper-maven-plugin -->      

so now have all test classes (generated and provided) compiled to target/test-classes by mvn test-compile
Thanks Thorsten


From: Thorsten Schöning <[hidden email]>
Sent: Monday, September 11, 2017 8:46 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Montag, 11. September 2017 um 14:00 schrieben Sie:

> axis2-kernel-1.8.0 has dependency
> org.apache.ws.xmlschema:xmlschema-core:jar:2.2.3-20170506.104137-3.jar

> any suggestions to locate this jar?

It's a dependency of the project and therefore was downloaded by Maven
for me:

>            <dependency>
>                <groupId>org.apache.ws.xmlschema</groupId>
>                <artifactId>xmlschema-core</artifactId>
>                <version>${xmlschema.version}</version>
>            </dependency>

> C:\Users\tschoening\.m2\repository\org\apache\ws\xmlschema\xmlschema-core\2.2.3-SNAPSHOT\xmlschema-core-2.2.3-20170506.104137-3.jar

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty

MG>i am experiencing difficultly reproducing that error with command

MG>mvn -e -X test -projects :axis2-metadata 


MG>this is my console display when i run the above command

[INFO]  T E S T S
[INFO] -------------------------------------------------------
[DEBUG] boot classpath:  %USERPROFILE%\.m2\repository\org\apache\maven\surefire\surefire-booter\2.20\surefire-booter-2.20.jar  %USERPROFILE%\.m2\repository\org\apache\maven\surefire\surefire-api\2.20\surefire-api-2.20.jar  %USERPROFILE%\.m2\repository\org\apache\maven\surefire\surefire-logger-api\2.20\surefire-logger-api-2.20.jar  C:\Axis\Thorsten\axis2-java-trunk\modules\metadata\target\test-classes  C:\Axis\Thorsten\axis2-java-trunk\modules\metadata\target\classes  %USERPROFILE%\.m2\repository\org\apache\maven\maven-project\3.3.3\maven-project-3.3.3.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-settings\2.2.1\maven-settings-2.2.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-profile\2.2.1\maven-profile-2.2.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-model\2.2.1\maven-model-2.2.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-artifact-manager\2.2.1\maven-artifact-manager-2.2.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-repository-metadata\2.2.1\maven-repository-metadata-2.2.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\wagon\wagon-provider-api\1.0-beta-6\wagon-provider-api-1.0-beta-6.jar  %USERPROFILE%\.m2\repository\backport-util-concurrent\backport-util-concurrent\3.1\backport-util-concurrent-3.1.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-plugin-registry\2.2.1\maven-plugin-registry-2.2.1.jar  %USERPROFILE%\.m2\repository\org\codehaus\plexus\plexus-interpolation\1.11\plexus-interpolation-1.11.jar  %USERPROFILE%\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.9\plexus-utils-1.4.9.jar  %USERPROFILE%\.m2\repository\org\apache\maven\maven-artifact\3.3.9\maven-artifact-3.3.9.jar  %USERPROFILE%\.m2\repository\org\apache\commons\commons-lang3\3.4\commons-lang3-3.4.jar  %USERPROFILE%\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-9-stable-1\plexus-container-default-1.0-alpha-9-stable-1.jar  %USERPROFILE%\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar  %USERPROFILE%\.m2\repository\org\apache\axis2\axis2-kernel\1.8.0-SNAPSHOT\axis2-kernel-1.8.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.3.0-SNAPSHOT\axiom-api-1.3.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\jaxen\jaxen\1.1.6\jaxen-1.1.6.jar  %USERPROFILE%\.m2\repository\org\apache\james\apache-mime4j-core\0.8.0\apache-mime4j-core-0.8.0.jar  %USERPROFILE%\.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.3.0-SNAPSHOT\axiom-impl-1.3.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\codehaus\woodstox\woodstox-core-asl\4.2.0\woodstox-core-asl-4.2.0.jar  %USERPROFILE%\.m2\repository\org\codehaus\woodstox\stax2-api\3.1.1\stax2-api-3.1.1.jar  %USERPROFILE%\.m2\repository\org\apache\geronimo\specs\geronimo-ws-metadata_2.0_spec\1.1.2\geronimo-ws-metadata_2.0_spec-1.1.2.jar  %USERPROFILE%\.m2\repository\org\apache\geronimo\specs\geronimo-jta_1.1_spec\1.1\geronimo-jta_1.1_spec-1.1.jar  %USERPROFILE%\.m2\repository\javax\servlet\servlet-api\2.3\servlet-api-2.3.jar  %USERPROFILE%\.m2\repository\commons-fileupload\commons-fileupload\1.3.3\commons-fileupload-1.3.3.jar  %USERPROFILE%\.m2\repository\wsdl4j\wsdl4j\1.6.2\wsdl4j-1.6.2.jar  %USERPROFILE%\.m2\repository\org\apache\ws\xmlschema\xmlschema-core\2.2.3-SNAPSHOT\xmlschema-core-2.2.3-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\neethi\neethi\3.0.4-SNAPSHOT\neethi-3.0.4-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\woden\woden-core\1.0M11-SNAPSHOT\woden-core-1.0M11-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar  %USERPROFILE%\.m2\repository\javax\ws\rs\jsr311-api\1.1.1\jsr311-api-1.1.1.jar  %USERPROFILE%\.m2\repository\commons-io\commons-io\2.1\commons-io-2.1.jar  %USERPROFILE%\.m2\repository\org\apache\axis2\axis2-adb\1.8.0-SNAPSHOT\axis2-adb-1.8.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.3.0-SNAPSHOT\axiom-dom-1.3.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\geronimo\specs\geronimo-jaxws_2.2_spec\1.0\geronimo-jaxws_2.2_spec-1.0.jar  %USERPROFILE%\.m2\repository\org\apache\axis2\axis2-saaj\1.8.0-SNAPSHOT\axis2-saaj-1.8.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\xml-resolver\xml-resolver\1.2\xml-resolver-1.2.jar  %USERPROFILE%\.m2\repository\com\sun\xml\bind\jaxb-impl\2.2.6\jaxb-impl-2.2.6.jar  %USERPROFILE%\.m2\repository\junit\junit\4.12\junit-4.12.jar  %USERPROFILE%\.m2\repository\org\hamcrest\hamcrest-core\1.3\hamcrest-core-1.3.jar  %USERPROFILE%\.m2\repository\log4j\log4j\1.2.15\log4j-1.2.15.jar  %USERPROFILE%\.m2\repository\javax\xml\bind\jaxb-api\2.2.6\jaxb-api-2.2.6.jar  %USERPROFILE%\.m2\repository\com\sun\xml\ws\jaxws-tools\2.1.3\jaxws-tools-2.1.3.jar  %USERPROFILE%\.m2\repository\org\apache\axis2\axis2-transport-http\1.8.0-SNAPSHOT\axis2-transport-http-1.8.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\httpcomponents\httpclient\4.5.3\httpclient-4.5.3.jar  %USERPROFILE%\.m2\repository\org\apache\httpcomponents\httpcore\4.4.6\httpcore-4.4.6.jar  %USERPROFILE%\.m2\repository\commons-codec\commons-codec\1.9\commons-codec-1.9.jar  %USERPROFILE%\.m2\repository\org\apache\axis2\axis2-transport-local\1.8.0-SNAPSHOT\axis2-transport-local-1.8.0-SNAPSHOT.jar  %USERPROFILE%\.m2\repository\org\apache\maven\surefire\surefire-junit4\2.20\surefire-junit4-2.20.jar
[DEBUG] boot(compact) classpath:  surefire-booter-2.20.jar  surefire-api-2.20.jar  surefire-logger-api-2.20.jar  test-classes  classes  maven-project-3.3.3.jar  maven-settings-2.2.1.jar  maven-profile-2.2.1.jar  maven-model-2.2.1.jar  maven-artifact-manager-2.2.1.jar  maven-repository-metadata-2.2.1.jar  wagon-provider-api-1.0-beta-6.jar  backport-util-concurrent-3.1.jar  maven-plugin-registry-2.2.1.jar  plexus-interpolation-1.11.jar  plexus-utils-1.4.9.jar  maven-artifact-3.3.9.jar  commons-lang3-3.4.jar  plexus-container-default-1.0-alpha-9-stable-1.jar  classworlds-1.1-alpha-2.jar  axis2-kernel-1.8.0-SNAPSHOT.jar  axiom-api-1.3.0-SNAPSHOT.jar  jaxen-1.1.6.jar  apache-mime4j-core-0.8.0.jar  axiom-impl-1.3.0-SNAPSHOT.jar  woodstox-core-asl-4.2.0.jar  stax2-api-3.1.1.jar  geronimo-ws-metadata_2.0_spec-1.1.2.jar  geronimo-jta_1.1_spec-1.1.jar  servlet-api-2.3.jar  commons-fileupload-1.3.3.jar  wsdl4j-1.6.2.jar  xmlschema-core-2.2.3-SNAPSHOT.jar  neethi-3.0.4-SNAPSHOT.jar  woden-core-1.0M11-SNAPSHOT.jar  commons-logging-1.1.1.jar  jsr311-api-1.1.1.jar  commons-io-2.1.jar  axis2-adb-1.8.0-SNAPSHOT.jar  axiom-dom-1.3.0-SNAPSHOT.jar  geronimo-jaxws_2.2_spec-1.0.jar  axis2-saaj-1.8.0-SNAPSHOT.jar  xml-resolver-1.2.jar  jaxb-impl-2.2.6.jar  junit-4.12.jar  hamcrest-core-1.3.jar  log4j-1.2.15.jar  jaxb-api-2.2.6.jar  jaxws-tools-2.1.3.jar  axis2-transport-http-1.8.0-SNAPSHOT.jar  httpclient-4.5.3.jar  httpcore-4.4.6.jar  commons-codec-1.9.jar  axis2-transport-local-1.8.0-SNAPSHOT.jar  surefire-junit4-2.20.jar
[DEBUG] Forking command line: 

cmd.exe /X /C "%JAVA_HOME%\jre\bin\java -Xbootclasspath/p:%USERPROFILE%\.m2\repository\org\apache\geronimo\specs\geronimo-jaxws_2.2_spec\1.0\geronimo-jaxws_2.2_spec-1.0.jar -jar C:\Axis\Thorsten\axis2-java-trunk\modules\metadata\target\surefire\surefirebooter5601085136083788745.jar C:\Axis\Thorsten\axis2-java-trunk\modules\metadata\target\surefire 2017-09-12T08-22-34_929-jvmRun1 surefire477378821769487523tmp surefire_0884734975243770122tmp"

[INFO] Running org.apache.axis2.jaxws.description.addressing.ActionTests...
<snip>
[INFO] Results:
[INFO] 
[INFO] Tests run: 191, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

MG>I suggest posting this bug to maven-surefire-plugin JIRA....be aware 2.2* is a bit old but still maintained

MG>to file a bug (which you should do) i would suggest to use herves surefire bug report to tibor as a template
https://issues.apache.org/jira/browse/SUREFIRE-1254

MG>*danke Thorsten*
MG>martin



From: Martin Gainty <[hidden email]>
Sent: Monday, September 11, 2017 11:25 AM
To: [hidden email]
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 

great the d/l of xmlschema-core worked!

in modules/metadata/pom.xml i had to add target/GENERA~2/jaxb folder so mvn test-compile now compiles all tests


<!-- MG 09/11 add build-helper-maven-plugin to add target/GENERA~2/jaxb source folder -->
<plugin>
       <groupId>org.codehaus.mojo</groupId>
       <artifactId>build-helper-maven-plugin</artifactId>
       <executions>
         <execution>
           <id>add-test-source</id>
           <phase>generate-test-sources</phase>
               <goals>
             <goal>add-test-source</goal>
               </goals>
               <configuration>
              <sources>
               <source>target/GENERA~2/jaxb</source>
              </sources>
           </configuration>
                  </execution>
               </executions>
      </plugin>
<!-- end MG 09/11 add build-helper-maven-plugin -->      

so now have all test classes (generated and provided) compiled to target/test-classes by mvn test-compile
Thanks Thorsten


From: Thorsten Schöning <[hidden email]>
Sent: Monday, September 11, 2017 8:46 AM
To: Martin Gainty
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Montag, 11. September 2017 um 14:00 schrieben Sie:

> axis2-kernel-1.8.0 has dependency
> org.apache.ws.xmlschema:xmlschema-core:jar:2.2.3-20170506.104137-3.jar

> any suggestions to locate this jar?

It's a dependency of the project and therefore was downloaded by Maven
for me:

>            <dependency>
>                <groupId>org.apache.ws.xmlschema</groupId>
>                <artifactId>xmlschema-core</artifactId>
>                <version>${xmlschema.version}</version>
>            </dependency>

> C:\Users\tschoening\.m2\repository\org\apache\ws\xmlschema\xmlschema-core\2.2.3-SNAPSHOT\xmlschema-core-2.2.3-20170506.104137-3.jar

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
www.am-soft.de
AM-SoFT IT-Systeme „Neue Wege entstehen, indem wir sie gehen!“ AM-SoFT GmbH IT-Systeme, 1989 in Hameln gegründet, ist EDV-Systemhaus, Internet-Service-Provider ...



Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Martin Gainty

unfortunately when i run 

mvn test axis2-transport-jms  (with all tests enabled)

i see multiple errors and failures

if i disable those tests in JMSTransportTest suite method

all the previous phases and test phase for axis2-transport-jms run completely and successfully


Unfortunately when my local maven encounters errors or failures it stops the build so i havent progressed to that part yet


i am curious if you had the chance to enter your bug to JIRA ?

Martin
______________________________________________




From: Thorsten Schöning <[hidden email]>
Sent: Friday, September 15, 2017 1:17 PM
To: [hidden email]
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
 
Guten Tag Martin Gainty,
am Freitag, 15. September 2017 um 16:37 schrieben Sie:

> most of the failing tests seem to resolve around incorrectly
> configured Async callback mechanism

The last time I ran them all tests from trunk passed for me in my
environment. Are you still focussing on my concrete example with
axis2-metadata?

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail: [hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
On Sun, Sep 17, 2017 at 1:59 PM, Thorsten Schöning
<[hidden email]> wrote:
> Guten Tag Martin Gainty,
> am Samstag, 16. September 2017 um 13:26 schrieben Sie:
>
>> i am curious if you had the chance to enter your bug to JIRA ?
>
> Not yet, I hoped that someone could first reproduce what I'm seeing
> and tell me if it's intended behavior of the Axis2 build, maybe
> even custom implemented build logic for some reason.

See my earlier messages in this thread explaining the root cause and
how one would reproduce this.

>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: [hidden email]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
On Mon, Sep 18, 2017 at 9:42 AM, Thorsten Schöning
<[hidden email]> wrote:

> Guten Tag Andreas Veithen,
> am Sonntag, 17. September 2017 um 17:43 schrieben Sie:
>
>> See my earlier messages in this thread explaining the root cause and
>> how one would reproduce this.
>
> Thanks for the hint and sorry, somehow I missed all of your answers to
> my question.
>
>> That means that the output directory is not added to the list of test
>> sources, resulting in compilation failures.
>
> But what I'm seeing is that someone actively deletes individual class
> files from the following child folders:
>
>> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\modules\metadata\target\test-classes\org
>
> All subdirs in that dir seem to be iterated and all containing Java
> class files deleted and only those class files, the following one is
> kept for example:
>
>> C:\Users\tschoening\Documents\Eclipse\Java Axis2\axis2\modules\metadata\target\test-classes\org\apache\axis2\jaxws\description\HandlerConfigFile.xml
>
> If it was only about classpath issues, shouldn't those files still be
> there?

This is exactly what I would expect from maven-compiler-plugin, namely
that for incremental builds, it removes the classes for which the
source files have been removed. Note that from the perspective of
maven-compiler-plugin, skipping the registration of the source folder
is effectively the same as removing the source files.

> Additionally, after successfully running "mvn clean test ...",
> I commented out the usage of jaxb2 in the pom.xml of metadata and that
> didn't change anything, the Java class files were still deleted.
>
> Doesn't that mean that that plugin is not the problem and that someone
> else is wrongly deleting those files for some reason?
>
> Setting "clearOutputDir" to "false" of the jaxb2 plugin didn't change
> anything as well.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: [hidden email]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [AXIS2] Some project builds fail if goal "clean" is not used

Andreas Veithen-2
I've sent a pull request with a proper fix for jaxb2-maven-plugin:

https://github.com/mojohaus/jaxb2-maven-plugin/pull/94

Andreas

On Tue, Sep 19, 2017 at 9:30 AM, Thorsten Schöning
<[hidden email]> wrote:

> Guten Tag Thorsten Schöning,
> am Montag, 18. September 2017 um 12:48 schrieben Sie:
>
>> Thanks, that was the part I was missing, because the source files are
>> actually still there. I'll file a bug in the jaxb2-maven-plugin then
>> linking to this thread.
>
> The problem has been reported before already and for some situations
> and people version 2.3 of the plugin fixes it. Not for me and the
> thing I'm seeing, but a workaround is available. I'm attaching a
> patch if you would like to integrate it.
>
> https://github.com/mojohaus/jaxb2-maven-plugin/issues/35
> https://github.com/mojohaus/jaxb2-maven-plugin/issues/44#issuecomment-272956618
>
>> Index: pom.xml
>> ===================================================================
>> --- pom.xml     (Revision 20687)
>> +++ pom.xml     (Arbeitskopie)
>> @@ -219,6 +219,24 @@
>>                  </executions>
>>              </plugin>
>>              <plugin>
>> +                <!-- https://github.com/mojohaus/jaxb2-maven-plugin/issues/35 -->
>> +                <groupId>org.codehaus.mojo</groupId>
>> +                <artifactId>build-helper-maven-plugin</artifactId>
>> +                <executions>
>> +                    <execution>
>> +                        <phase>generate-sources</phase>
>> +                        <goals>
>> +                            <goal>add-source</goal>
>> +                        </goals>
>> +                        <configuration>
>> +                            <sources>
>> +                                <source>${project.build.directory}/generated-test-sources/jaxb</source>
>> +                            </sources>
>> +                        </configuration>
>> +                    </execution>
>> +                </executions>
>> +            </plugin>
>> +            <plugin>
>>                  <groupId>org.apache.maven.plugins</groupId>
>>                  <artifactId>maven-antrun-plugin</artifactId>
>>                  <executions>
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: [hidden email]
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]