date:20170910

Jenkins build is back to stable : Rampart » Rampart - Samples #2482

2017-09-10 Thread Apache Jenkins Server

See 



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2017-09-10 Thread Martin Gainty

MG>see below

From: Thorsten Schöning 
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,4152279java.exe16280   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: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
Webpräsenz AM-SoFT IT-Systeme GmbH - Startseite
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: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5866) Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5866.

Resolution: Incomplete

> Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds
> -
>
> Key: AXIS2-5866
> URL: https://issues.apache.org/jira/browse/AXIS2-5866
> Project: Axis2
>  Issue Type: Bug
>  Components: client-api, transports
>Affects Versions: 1.7.4
> Environment: Java 8, Tomcat
>Reporter: Mykhailo Hodovaniuk
>Priority: Minor
>
> According to documentation 
> https://axis.apache.org/axis2/java/core/docs/http-transport.html the timeouts 
> can be defined:
> {code:java}
> For runtime configuration, it can be set as follows within the client stub:
> ...
> Options options = new Options();
> options.setProperty(HTTPConstants.SO_TIMEOUT, new 
> Integer(timeOutInMilliSeconds));
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT, new 
> Integer(timeOutInMilliSeconds));
> // or
> options.setTimeOutInMilliSeconds(timeOutInMilliSeconds);
> ...
> {code}
> But instead, Axis ignores this property because: 
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ has code 
> {code:java}
> // set the property values only if they are not set by the user explicitly
> if (msgContext.getProperty(HTTPConstants.SO_TIMEOUT) == null) {
> msgContext.setProperty(HTTPConstants.SO_TIMEOUT, soTimeout);
> }
> if (msgContext.getProperty(HTTPConstants.CONNECTION_TIMEOUT) == 
> null) {
> msgContext.setProperty(HTTPConstants.CONNECTION_TIMEOUT, 
> connectionTimeout);
> }
> {code}
>  where _connectionTimeout_ and _soTimeout_ are always non null.
> At the same time 
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_ 
> tries to define these values if they are null with timeOutInMilliSeconds.
> The problem is that 
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ is higher 
> in call hirarchy so the 
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_ 
> does not work as expected. The _SO_TIMEOUT_ and _CONNECTION_TIMEOUT_ 
> parameters are always defined inside 
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_.
> The workaround is to define timeouts in axis2.xml.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build became unstable: Rampart #2481

2017-09-10 Thread Apache Jenkins Server

See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build became unstable: Rampart » Rampart - Samples #2481

2017-09-10 Thread Apache Jenkins Server

See 



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5884) Change parameter "Description" to lower-case for service.xml.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5884.

   Resolution: Fixed
Fix Version/s: 1.8.0

> Change parameter "Description" to lower-case for service.xml.
> -
>
> Key: AXIS2-5884
> URL: https://issues.apache.org/jira/browse/AXIS2-5884
> Project: Axis2
>  Issue Type: Improvement
>  Components: deployment
>Affects Versions: 1.7.6
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.8.0
>
>
> Because of AXIS2-5881 I had a look at my own Axis2 services and recognized 
> that their description is wrong and is the service name instead of what is 
> defined in the service.xml file. The problem was simply using "description" 
> instead of "Description" and the latter is documented, so I must have simply 
> overlooked the different spelling.
> http://axis.apache.org/axis2/java/core/docs/axis2config.html#Service_Configuration
> So why not change this configuration to lower case to be in-line with all 
> other configs in this file and with most other configs as well?
> Searching through the Axis2 codebase reveals that "description" is hard coded 
> at some places already and I even found service.xml files in tests where 
> "description" is used, so are wrong in theory. The only environment where 
> "Description" seems to make sense is module.xml, which uses "InFlow", 
> "OutFlow" etc. as well.
> So we can change the value of TAG_DESCRIPTION to be lower case and hard-code 
> something for modules or keep TAG_DESCRIPTION as it is and hard code a lower 
> case variant for service.xml or simply use "description" for all, which 
> wouldn't like that right in module.xml anymore...
> What do you prefer?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5884) Change parameter "Description" to lower-case for service.xml.

2017-09-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160490#comment-16160490
 ] 

Hudson commented on AXIS2-5884:
---

SUCCESS: Integrated in Jenkins build Axis2 #3829 (See 
[https://builds.apache.org/job/Axis2/3829/])
AXIS2-5884: Allow both 'description' and 'Description' in service.xml and 
module.xml files. (veithen: rev 1807970)
* (edit) 
axis2/modules/kernel/src/org/apache/axis2/deployment/DeploymentConstants.java
* (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleBuilder.java
* (edit) 
axis2/modules/kernel/src/org/apache/axis2/deployment/ServiceBuilder.java
* (edit) axis2/modules/samples/json/src/META-INF/services.xml
* (edit) axis2/src/site/xdoc/docs/axis2config.xml
* (edit) 
axis2/systests/webapp-tests/src/test/java/org/apache/axis2/webapp/AxisAdminServletITCase.java
* (edit) 
axis2/systests/webapp-tests/src/test/java/org/apache/axis2/webapp/AxisServletITCase.java


> Change parameter "Description" to lower-case for service.xml.
> -
>
> Key: AXIS2-5884
> URL: https://issues.apache.org/jira/browse/AXIS2-5884
> Project: Axis2
>  Issue Type: Improvement
>  Components: deployment
>Affects Versions: 1.7.6
>Reporter: Thorsten Schöning
>Priority: Minor
>
> Because of AXIS2-5881 I had a look at my own Axis2 services and recognized 
> that their description is wrong and is the service name instead of what is 
> defined in the service.xml file. The problem was simply using "description" 
> instead of "Description" and the latter is documented, so I must have simply 
> overlooked the different spelling.
> http://axis.apache.org/axis2/java/core/docs/axis2config.html#Service_Configuration
> So why not change this configuration to lower case to be in-line with all 
> other configs in this file and with most other configs as well?
> Searching through the Axis2 codebase reveals that "description" is hard coded 
> at some places already and I even found service.xml files in tests where 
> "description" is used, so are wrong in theory. The only environment where 
> "Description" seems to make sense is module.xml, which uses "InFlow", 
> "OutFlow" etc. as well.
> So we can change the value of TAG_DESCRIPTION to be lower case and hard-code 
> something for modules or keep TAG_DESCRIPTION as it is and hard code a lower 
> case variant for service.xml or simply use "description" for all, which 
> wouldn't like that right in module.xml anymore...
> What do you prefer?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5882) Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5882.

Resolution: Invalid

> Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream
> ---
>
> Key: AXIS2-5882
> URL: https://issues.apache.org/jira/browse/AXIS2-5882
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
>  Labels: security
>
> Attackers can control the filesystem path argument to File() at 
> PreProcessorInputStream.java line 218, which allows them to access or modify 
> otherwise protected files.
> Explanation:
> Path manipulation errors occur when the following two conditions are met:
> 1. An attacker can specify a path used in an operation on the filesystem.
> 2. By specifying the resource, the attacker gains a capability that would not 
> otherwise be permitted.
> For example, the program may give the attacker the ability to overwrite the 
> specified file or run with a configuration controlled by the attacker.
> In this case, the attacker can specify the value that enters the program at 
> readLine() in PreProcessorInputStream.java at line 86, and this value is used 
> to access a filesystem resource at File() in PreProcessorInputStream.java at 
> line 218, 230, 232, 250, 253, 278.
> Possible solution: Make sure the absolute filename is validated against 
> known/configured valid base path.
> Also: 
> Attackers can control the filesystem path argument to File() at 
> WSDL20ToAxisServiceBuilder.java line 153, which allows them to access or 
> modify otherwise protected files. In this case, the attacker can specify the 
> value that enters the program at getHeaderField() in 
> CodeGenerationEngine.java at line 101, and this value is used to access a 
> filesystem resource at File() in WSDL20ToAxisServiceBuilder.java at line 153 
> and 1281.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5882) Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160467#comment-16160467
 ] 

Andreas Veithen commented on AXIS2-5882:


AFAICS {{PreProcessorInputStream}} is used by the IDL processor to process 
{{#include}} statements. This is a legitimate use of path manipulation. I don't 
see how this would satisfy any of the two conditions you mentioned.

Please note that naive implementations of static code analyzers designed to 
detect security issues will produce a lot of false positives like this. Please 
don't create bugs unless you have confirmed that the reported "issues" are 
actual security problems.

> Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream
> ---
>
> Key: AXIS2-5882
> URL: https://issues.apache.org/jira/browse/AXIS2-5882
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
>  Labels: security
>
> Attackers can control the filesystem path argument to File() at 
> PreProcessorInputStream.java line 218, which allows them to access or modify 
> otherwise protected files.
> Explanation:
> Path manipulation errors occur when the following two conditions are met:
> 1. An attacker can specify a path used in an operation on the filesystem.
> 2. By specifying the resource, the attacker gains a capability that would not 
> otherwise be permitted.
> For example, the program may give the attacker the ability to overwrite the 
> specified file or run with a configuration controlled by the attacker.
> In this case, the attacker can specify the value that enters the program at 
> readLine() in PreProcessorInputStream.java at line 86, and this value is used 
> to access a filesystem resource at File() in PreProcessorInputStream.java at 
> line 218, 230, 232, 250, 253, 278.
> Possible solution: Make sure the absolute filename is validated against 
> known/configured valid base path.
> Also: 
> Attackers can control the filesystem path argument to File() at 
> WSDL20ToAxisServiceBuilder.java line 153, which allows them to access or 
> modify otherwise protected files. In this case, the attacker can specify the 
> value that enters the program at getHeaderField() in 
> CodeGenerationEngine.java at line 101, and this value is used to access a 
> filesystem resource at File() in WSDL20ToAxisServiceBuilder.java at line 153 
> and 1281.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5884) Change parameter "Description" to lower-case for service.xml.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5884:
---
Affects Version/s: (was: 1.8.0)
   1.7.6

> Change parameter "Description" to lower-case for service.xml.
> -
>
> Key: AXIS2-5884
> URL: https://issues.apache.org/jira/browse/AXIS2-5884
> Project: Axis2
>  Issue Type: Improvement
>  Components: deployment
>Affects Versions: 1.7.6
>Reporter: Thorsten Schöning
>Priority: Minor
>
> Because of AXIS2-5881 I had a look at my own Axis2 services and recognized 
> that their description is wrong and is the service name instead of what is 
> defined in the service.xml file. The problem was simply using "description" 
> instead of "Description" and the latter is documented, so I must have simply 
> overlooked the different spelling.
> http://axis.apache.org/axis2/java/core/docs/axis2config.html#Service_Configuration
> So why not change this configuration to lower case to be in-line with all 
> other configs in this file and with most other configs as well?
> Searching through the Axis2 codebase reveals that "description" is hard coded 
> at some places already and I even found service.xml files in tests where 
> "description" is used, so are wrong in theory. The only environment where 
> "Description" seems to make sense is module.xml, which uses "InFlow", 
> "OutFlow" etc. as well.
> So we can change the value of TAG_DESCRIPTION to be lower case and hard-code 
> something for modules or keep TAG_DESCRIPTION as it is and hard code a lower 
> case variant for service.xml or simply use "description" for all, which 
> wouldn't like that right in module.xml anymore...
> What do you prefer?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5883.

   Resolution: Fixed
Fix Version/s: 1.7.7

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build became unstable: rampart-1.7 » Rampart - Samples #94

2017-09-10 Thread Apache Jenkins Server

See 



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build became unstable: rampart-1.7 #94

2017-09-10 Thread Apache Jenkins Server

See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160401#comment-16160401
 ] 

Hudson commented on AXIS2-5883:
---

SUCCESS: Integrated in Jenkins build axis2-1.7 #143 (See 
[https://builds.apache.org/job/axis2-1.7/143/])
AXIS2-5883: Merge r1807941 and r1807943 to the 1.7 branch. (veithen: rev 
1807954)
* (edit) axis2
* (edit) axis2/apidocs/pom.xml
* (edit) axis2/pom.xml


> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2017-09-10 Thread Thorsten Schöning

Guten Tag Martin Gainty,
am Sonntag, 10. September 2017 um 03:40 schrieben Sie:

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?

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

> 17:24:02,4152279java.exe16280   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

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.

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.

Such things are really annoying. :-)

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
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: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160355#comment-16160355
 ] 

Hudson commented on AXIS2-5883:
---

SUCCESS: Integrated in Jenkins build Axis2 #3826 (See 
[https://builds.apache.org/job/Axis2/3826/])
AXIS2-5883: Add change missing in r1807941. (veithen: rev 1807943)
* (edit) axis2/pom.xml
AXIS2-5883: Fix site generation failure on Windows. Patch provided by Thorsten 
Schöning. (veithen: rev 1807941)
* (edit) axis2/apidocs/pom.xml


> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5885) Generating apidocs fails with Java 8.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5885.

   Resolution: Fixed
Fix Version/s: 1.7.7

> Generating apidocs fails with Java 8.
> -
>
> Key: AXIS2-5885
> URL: https://issues.apache.org/jira/browse/AXIS2-5885
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
>
>
> The project "apidocs" can not be build by default using Java 8 because of a 
> lot of errors in the Javadocs and the new "javadoc" errors on those problems 
> instead of warning/ignoring them. A workaround is to add 
> "false" to the configuration, in that case the 
> errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs 
> to fix what and where "javadoc" says. But some errors are related to missing 
> packages and might be a hint to classpath issues or some problems with 
> available packages in the build?
> https://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\Logger.java:4:
>  error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\ADBDataSource.java:44:
>  warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {CODE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5885) Generating apidocs fails with Java 8.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5885:
---
Affects Version/s: (was: 1.8.0)
   1.7.6

> Generating apidocs fails with Java 8.
> -
>
> Key: AXIS2-5885
> URL: https://issues.apache.org/jira/browse/AXIS2-5885
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
>
>
> The project "apidocs" can not be build by default using Java 8 because of a 
> lot of errors in the Javadocs and the new "javadoc" errors on those problems 
> instead of warning/ignoring them. A workaround is to add 
> "false" to the configuration, in that case the 
> errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs 
> to fix what and where "javadoc" says. But some errors are related to missing 
> packages and might be a hint to classpath issues or some problems with 
> available packages in the build?
> https://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\Logger.java:4:
>  error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\ADBDataSource.java:44:
>  warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {CODE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5885) Generating apidocs fails with Java 8.

2017-09-10 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160334#comment-16160334
 ] 

Hudson commented on AXIS2-5885:
---

SUCCESS: Integrated in Jenkins build axis2-1.7 #142 (See 
[https://builds.apache.org/job/axis2-1.7/142/])
AXIS2-5885: Merge r1807837 to the 1.7 branch. (veithen: rev 1807942)
* (edit) axis2
* (edit) axis2/apidocs/pom.xml
* (edit) axis2/pom.xml


> Generating apidocs fails with Java 8.
> -
>
> Key: AXIS2-5885
> URL: https://issues.apache.org/jira/browse/AXIS2-5885
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.8.0
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
>
>
> The project "apidocs" can not be build by default using Java 8 because of a 
> lot of errors in the Javadocs and the new "javadoc" errors on those problems 
> instead of warning/ignoring them. A workaround is to add 
> "false" to the configuration, in that case the 
> errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs 
> to fix what and where "javadoc" says. But some errors are related to missing 
> packages and might be a hint to classpath issues or some problems with 
> available packages in the build?
> https://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\Logger.java:4:
>  error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java 
> Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\ADBDataSource.java:44:
>  warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {CODE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5877) XML External Entity Injections

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160313#comment-16160313
 ] 

Andreas Veithen commented on AXIS2-5877:


{{XSLTTemplateProcessor}} is not security sensitive because it's only used 
during code generation. Can you provide a test case or exploit that shows how 
the code in {{ConvertUtils}} would be used to carry out an attack 
([CVE-2010-1632|https://svn.apache.org/repos/asf/axis/axis2/java/core/security/CVE-2010-1632.pdf]
 provides an example)?

> XML External Entity Injections
> --
>
> Key: AXIS2-5877
> URL: https://issues.apache.org/jira/browse/AXIS2-5877
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
>  Labels: security
> Attachments: xxe1.png, xxe2.png
>
>
> XML parser configured in ConvertUtils.java:225 does not prevent nor limit 
> external entities resolution. This can expose the parser to an XML External 
> Entities attack.
> Proposed fix: Enable where TransformerFactory is used always the secure 
> processing feature:
> {code:java}
>   public static TransformerFactory createTransformerFactory() {
>   TransformerFactory factory = TransformerFactory.newInstance();
>   try {
>   
> factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
>   }
>   catch (TransformerConfigurationException e) {
>   throw new IllegalStateException(e);
>   }
>   return factory;
>   }
> {code}
> Also in XSLTTemplateProcessor.java:147 (XSLT Injection) and other locations 
> where this and DocumentBuilderFactory is handled wrong. See attached 
> screenshots.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160293#comment-16160293
 ] 

Andreas Veithen commented on AXIS2-5875:


bq. Additionally, no error messages are shown when I import the modules using 
m2e instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is 
not created in that case. So might it be a solution to remove the following 
line in the pom.xml instead of dealing with the imports?

bq. {CODE}
org.eclipse.pde.ManifestBuilder
{CODE}

The PDE builders are necessary to test these plugins in Eclipse.

> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
>  Issue Type: Bug
>  Components: ide plugins
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the 
> following error messages about unresolved imported packages in 
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a 
> look at the associated pom.xml, it seems that a lot of libs are already 
> excluded from the import. Therefore I ask myself if the ones of the error 
> messages simply need to be excluded as well? If not, shouldn't the imports be 
> resolved using what my Eclipse provides and the project itself? I see a lot 
> of Jars in the lib folder of those projects, but none of the ones with error 
> messages.
> Additionally, no error messages are shown when I import the modules using m2e 
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is 
> not created in that case. So might it be a solution to remove the following 
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but 
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in 
> Problem
> No available bundle exports package 'javax.jms'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation' 
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 113Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.internal'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No

[jira] [Updated] (AXIS2-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5875:
---
Affects Version/s: (was: 1.8.0)
   1.7.6

> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
>  Issue Type: Bug
>  Components: ide plugins
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the 
> following error messages about unresolved imported packages in 
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a 
> look at the associated pom.xml, it seems that a lot of libs are already 
> excluded from the import. Therefore I ask myself if the ones of the error 
> messages simply need to be excluded as well? If not, shouldn't the imports be 
> resolved using what my Eclipse provides and the project itself? I see a lot 
> of Jars in the lib folder of those projects, but none of the ones with error 
> messages.
> Additionally, no error messages are shown when I import the modules using m2e 
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is 
> not created in that case. So might it be a solution to remove the following 
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but 
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in 
> Problem
> No available bundle exports package 'javax.jms'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation' 
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 113Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.internal'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'   
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF  line 61 Plug-in 
> Problem
> No available bundle exports package 'org.aspectj.lang.annotation' 
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF  line 72 Plug-in 
> Problem
> No available bundle exports package 'org.aspectj.lang'

[jira] [Commented] (AXIS2-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160291#comment-16160291
 ] 

Andreas Veithen commented on AXIS2-5875:


These errors are only present on the trunk. They are related to r1800555.

On the 1.7 there is a different error:

bq. Unsatisfied constraint: 'Import-Package: javax.xml.stream; version="1.0.0"'


> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
>  Issue Type: Bug
>  Components: ide plugins
>Affects Versions: 1.8.0
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the 
> following error messages about unresolved imported packages in 
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a 
> look at the associated pom.xml, it seems that a lot of libs are already 
> excluded from the import. Therefore I ask myself if the ones of the error 
> messages simply need to be excluded as well? If not, shouldn't the imports be 
> resolved using what my Eclipse provides and the project itself? I see a lot 
> of Jars in the lib folder of those projects, but none of the ones with error 
> messages.
> Additionally, no error messages are shown when I import the modules using m2e 
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is 
> not created in that case. So might it be a solution to remove the following 
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but 
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in 
> Problem
> No available bundle exports package 'javax.jms'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation' 
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 111Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 113Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 
> 'org.openjdk.tools.internal.jline.internal'   MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'   
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF  line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation'  MANIFEST.MF 
> /axis2.eclipse.codegen.plugin/META-INF  line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'   
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF  line 61 Plug-in 
> Problem
> No available bundle exports package

[jira] [Commented] (AXIS2-5874) Memory leak when trying to getInputStream() from an External Repository data through AXIS

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160281#comment-16160281
 ] 

Andreas Veithen commented on AXIS2-5874:


* The contract of {{DataHandler}} allows multiple calls to 
{{getInputStream()}}. That means that requesting the stream and closing it will 
not free the memory held by the {{DataHandler}}.
* The fact that you get an {{OutOfMemoryError}} in the code that reads the MIME 
part does not mean that the (presumed) leak occurs there. You will need to look 
at a heap dump to determine where references to the objects involved in the 
leak are held. There is no a priori reason to believe that it's Axis2's fault; 
it may be a problem in your code.
* 1.6.2 is an old release that is no longer supported. You would need to 
provide steps to reproduce the problem on a more recent release.

> Memory leak when trying to getInputStream() from an External Repository data 
> through AXIS
> -
>
> Key: AXIS2-5874
> URL: https://issues.apache.org/jira/browse/AXIS2-5874
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws, wsdl
>Affects Versions: 1.6.2
> Environment: Windows 2008
>Reporter: Nidhin Lazar
>Priority: Blocker
>
> We are using AXIS WS to connect and download files from an external 
> repository .We are using SOAP based webservice calls download an object. The 
> API returns a DataHandler object, from where we are getting the input stream. 
> We have tried closing the inputstream object but even after the close call we 
> can see that the memory is still holding the stream, and eventually the 
> client machine is running out of memory.Any help on this would be highly 
> appreciated.
> Our client code is as shown below
> URL url = new URL("http://"+host+"/ws/CntSrvc.svc?wsdl;);
> CntSrvc_Svc cService = new CntSrvc_Svc(url);
> CntSrvc cntSrvcClient = cService.getBasicHttpBindingCntSrvc(new 
> MTOMFeature());
> InputStream in = null ;
> in = cntSrvcClient.download(contextIDString).getInputStream();
> // write in to a file.
> //closing the input stream
> if (in != null){
>  in.close(); 
> }
> [Note;] Our client code runs under tomcat container, and this acts as a 
> server to other services.
> [Note:]We have created a sample client without using AXIS, where our client 
> connecting to external repository and download content.Here we donot see any 
> memory leak.Our investigation proves that its when we use AXIS and 
> getinputstream() the memory is leaking, input stream is not closing.Our 
> current framework demands AXIS hence we would like to get a solution or 
> workaround for this issue



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thorsten Schöning updated AXIS2-5883:
-
Attachment: MJAVADOC-469.patch

Good catch, have forgotten to change that.

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thorsten Schöning updated AXIS2-5883:
-
Attachment: (was: MJAVADOC-469.patch)

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5874) Memory leak when trying to getInputStream() from an External Repository data through AXIS

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5874:
---
Fix Version/s: (was: 1.6.2)

> Memory leak when trying to getInputStream() from an External Repository data 
> through AXIS
> -
>
> Key: AXIS2-5874
> URL: https://issues.apache.org/jira/browse/AXIS2-5874
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws, wsdl
>Affects Versions: 1.6.2
> Environment: Windows 2008
>Reporter: Nidhin Lazar
>Priority: Blocker
>
> We are using AXIS WS to connect and download files from an external 
> repository .We are using SOAP based webservice calls download an object. The 
> API returns a DataHandler object, from where we are getting the input stream. 
> We have tried closing the inputstream object but even after the close call we 
> can see that the memory is still holding the stream, and eventually the 
> client machine is running out of memory.Any help on this would be highly 
> appreciated.
> Our client code is as shown below
> URL url = new URL("http://"+host+"/ws/CntSrvc.svc?wsdl;);
> CntSrvc_Svc cService = new CntSrvc_Svc(url);
> CntSrvc cntSrvcClient = cService.getBasicHttpBindingCntSrvc(new 
> MTOMFeature());
> InputStream in = null ;
> in = cntSrvcClient.download(contextIDString).getInputStream();
> // write in to a file.
> //closing the input stream
> if (in != null){
>  in.close(); 
> }
> [Note;] Our client code runs under tomcat container, and this acts as a 
> server to other services.
> [Note:]We have created a sample client without using AXIS, where our client 
> connecting to external repository and download content.Here we donot see any 
> memory leak.Our investigation proves that its when we use AXIS and 
> getinputstream() the memory is leaking, input stream is not closing.Our 
> current framework demands AXIS hence we would like to get a solution or 
> workaround for this issue



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160277#comment-16160277
 ] 

Andreas Veithen commented on AXIS2-5883:


Note that {{failIfNoMatch}} should be {{false}} to make this work on Unix based 
systems.

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5883:
---
Affects Version/s: (was: 1.8.0)
   1.7.6

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5883:
---
Priority: Minor  (was: Major)

> Generation of apidocs fails on Windows.
> ---
>
> Key: AXIS2-5883
> URL: https://issues.apache.org/jira/browse/AXIS2-5883
> Project: Axis2
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: MJAVADOC-469.patch
>
>
> Generation of the project "apidocs" fails on Windows in case of spaces in 
> paths and because of a bug in "maven-javadoc-plugin": That plugin is writing 
> argument files for Javadoc, but is missing to escape backslashs in paths. 
> Javadoc is reading the paths from the argument file 1:1 and introduces wrong 
> characters, like a tab for "\t" in path which really is "...\tschoening". 
> This is already documented against the plugin:
> https://issues.apache.org/jira/browse/MJAVADOC-469
> The attached patch is adding quotes to the command line args and working 
> around the problem of the maven plugin by doubling backslashes on it's own so 
> that the needed amount of backslashes is available in the argument file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5880) Several Resource leaks

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5880.

Resolution: Invalid

> Several Resource leaks
> --
>
> Key: AXIS2-5880
> URL: https://issues.apache.org/jira/browse/AXIS2-5880
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
> Attachments: unreleased resources1.png, unreleased resources2.png, 
> unreleased resources3.png, unreleased resources4.png, unreleased 
> resources5.png
>
>
> Our code check tool found several resource leak issues. See attached picture. 
> Some are not real resource leaks because the objects has a finalize method, 
> but even then it is better to close the resource itself because it is not 
> defined when the GC will close them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5880) Several Resource leaks

2017-09-10 Thread Andreas Veithen (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160273#comment-16160273
 ] 

Andreas Veithen commented on AXIS2-5880:


I don't know what static code analysis tool you are using, but the results it 
produces are pretty much useless. Take the example of {{WarBasedWSDLLocator}} 
(line 68). The method returns an {{InputSource}} with an {{InputStream}}. 
Obviously that stream must be open and it is the responsibility of the caller 
to close it once it has read the data. Apparently the code analysis tool is 
based on the assumption that a stream opened in a method must be closed in the 
same method, which is only true if the reference to that stream is not passed 
back to the caller or to another method.

> Several Resource leaks
> --
>
> Key: AXIS2-5880
> URL: https://issues.apache.org/jira/browse/AXIS2-5880
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
> Attachments: unreleased resources1.png, unreleased resources2.png, 
> unreleased resources3.png, unreleased resources4.png, unreleased 
> resources5.png
>
>
> Our code check tool found several resource leak issues. See attached picture. 
> Some are not real resource leaks because the objects has a finalize method, 
> but even then it is better to close the resource itself because it is not 
> defined when the GC will close them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2017-09-10 Thread Andreas Veithen

Stop talking nonsense, Martin.

On Sun, Sep 10, 2017 at 2:40 AM, Martin Gainty  wrote:

>
>
>
> --
> *From:* Thorsten Schöning 
> *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: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
> Webpräsenz AM-SoFT IT-Systeme GmbH - Startseite 
> 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: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>

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

2017-09-10 Thread Andreas Veithen

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
 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: thorsten.schoen...@am-soft.de
> 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: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5876) axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on the Java Build Path status.tag

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5876:
---
Priority: Minor  (was: Major)

> axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was 
> not found on the Java Build Path status.tag
> 
>
> Key: AXIS2-5876
> URL: https://issues.apache.org/jira/browse/AXIS2-5876
> Project: Axis2
>  Issue Type: Bug
>  Components: modules
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> Attachments: missing jsp-api.patch
>
>
> After importing trunk into Eclipse using maven-eclipse-plugin, I got the 
> following error. This could easily be resolved by adding jsp-api to the 
> pom.xml, like in the attached patch. That way the Jar is added to the 
> classpath in Eclipse, provided by Maven and this resolves the error message.
> Please consider patching current trunk and 1.7, as the same problem seems to 
> be present in both.
> {QUOTE}
> The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on 
> the Java Build Path   status.tag  
> /axis2-webapp/src/main/webapp/WEB-INF/tags  line 1  JSP Problem
> {QUOTE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Updated] (AXIS2-5876) axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on the Java Build Path status.tag

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-5876:
---
Affects Version/s: (was: 1.8.0)

> axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was 
> not found on the Java Build Path status.tag
> 
>
> Key: AXIS2-5876
> URL: https://issues.apache.org/jira/browse/AXIS2-5876
> Project: Axis2
>  Issue Type: Bug
>  Components: modules
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
> Fix For: 1.7.7
>
> Attachments: missing jsp-api.patch
>
>
> After importing trunk into Eclipse using maven-eclipse-plugin, I got the 
> following error. This could easily be resolved by adding jsp-api to the 
> pom.xml, like in the attached patch. That way the Jar is added to the 
> classpath in Eclipse, provided by Maven and this resolves the error message.
> Please consider patching current trunk and 1.7, as the same problem seems to 
> be present in both.
> {QUOTE}
> The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on 
> the Java Build Path   status.tag  
> /axis2-webapp/src/main/webapp/WEB-INF/tags  line 1  JSP Problem
> {QUOTE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Resolved] (AXIS2-5876) axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on the Java Build Path status.tag

2017-09-10 Thread Andreas Veithen (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-5876.

   Resolution: Fixed
Fix Version/s: 1.7.7

> axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was 
> not found on the Java Build Path status.tag
> 
>
> Key: AXIS2-5876
> URL: https://issues.apache.org/jira/browse/AXIS2-5876
> Project: Axis2
>  Issue Type: Bug
>  Components: modules
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0) 
> x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> Attachments: missing jsp-api.patch
>
>
> After importing trunk into Eclipse using maven-eclipse-plugin, I got the 
> following error. This could easily be resolved by adding jsp-api to the 
> pom.xml, like in the attached patch. That way the Jar is added to the 
> classpath in Eclipse, provided by Maven and this resolves the error message.
> Please consider patching current trunk and 1.7, as the same problem seems to 
> be present in both.
> {QUOTE}
> The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on 
> the Java Build Path   status.tag  
> /axis2-webapp/src/main/webapp/WEB-INF/tags  line 1  JSP Problem
> {QUOTE}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

37 matches

Mail list logo