date:20120606

[jira] (MNG-5237) Cannot download maven dependencies through proxy

2012-06-06 Thread cforce (JIRA)


[ 
https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300503#comment-300503
 ] 

cforce commented on MNG-5237:
-

Yes, actually we use NTLM proxy!

Please fix this!

> Cannot download maven dependencies through proxy
> 
>
> Key: MNG-5237
> URL: https://jira.codehaus.org/browse/MNG-5237
> Project: Maven 2 & 3
>  Issue Type: Bug
>  Components: Dependencies
>Affects Versions: 3.0.4
> Environment: windows xp64 using cygwin
>Reporter: Niels Mordt-Ostergaard
>Assignee: Jason van Zyl
>
> Using proxy in settings.xml, I was able to download maven dependencies in 
> 3.0.3, but this seems to be broken with 3.0.4:
> Proxy definition in settings.xml (hidden ip adress below, but correct proxy 
> ip on my system):
>   
>
>   optional
>   true
>   http
>   
>   
>   xxx.xx.xx.xx
>   8080
>   localhost|127.0.0.1
> 
>   
> Output from 3.0.3:
> $ mvn -V clean
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: C:\Program Files\apache-maven-3.0.3
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: no_NO, platform encoding: Cp1252
> OS name: "windows xp", version: "5.2", arch: "amd64", family: "windows"
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building 
> [INFO] 
> 
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
> Downloaded: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
>  (5 KB at 4.9 KB/sec)
> . and so on...
> Output from 3.0.4:
> $ mvn -V clean
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: C:\Program Files\apache-maven-3.0.4
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: no_NO, platform encoding: Cp1252
> OS name: "windows xp", version: "5.2", arch: "amd64", family: "windows"
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building 
> [INFO] 
> 
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.390s
> [INFO] Finished at: Fri Feb 03 13:14:35 CET 2012
> [INFO] Final Memory: 5M/490M
> [INFO] 
> 
> [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of 
> its dependencies could not be resolved: Failed to read artifact descriptor 
> for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer 
> artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to 
> central (http://repo.maven.apache.org/maven2): Access denied to: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom,
>  ReasonPhrase:Forbidden. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MEAR-146) Expose parameter to not write library-directory element in application.xml

2012-06-06 Thread Alex Halovanic (JIRA)


[ 
https://jira.codehaus.org/browse/MEAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300502#comment-300502
 ] 

Alex Halovanic commented on MEAR-146:
-

I have the response back from Oracle:

{quote}
You can either use AppFileOverrides directory (and let the container do the 
classloading discovery), or you can use  and you decide 
where you want the files to come from. You should not use both.

By default, library-directory will be loaded from APP-INF/lib of the EAR 
anyways, rendering the explicit  inside the application.xml 
is redundant.

When no , you're delegating the classloading to the 
container (ie. WLS), and the documented behavior below will suffix :

http://docs.oracle.com/cd/E12839_01/web./e13702/config.htm#i1066493

However, if you explicitly define  in application.xml, this 
would take precedence, and since you specify the following -
...
APP-INF/lib
...
.
in which you have the following file in APP-INF/lib in 
classloader-ear-libdir.ear -
.
classloader-jse-1.0-SNAPSHOT.ear
.
In such case, you're essentially overriding the AppFileOverrides directory.

So you can either use  or AppFileOverrides, but not both. If 
both are specified,  will take precedence.
{quote}

So in their opinion, this is not a bug, but intended behavior and always 
defining  to the default EAR lib folder has side-effects.  
However, unless there's another product that has special classloading overrides 
like this, it's almost certainly still WebLogic-specific.

> Expose parameter to not write library-directory element in application.xml
> --
>
> Key: MEAR-146
> URL: https://jira.codehaus.org/browse/MEAR-146
> Project: Maven 2.x Ear Plugin
>  Issue Type: Improvement
>Affects Versions: 2.8
> Environment: Oracle WebLogic
>Reporter: Alex Halovanic
>Priority: Minor
> Attachments: ear-remove-librarydirectory-IT.patch, 
> ear-remove-librarydirectory.patch
>
>
> The current handling of defaultLibBundleDir leads to some issues on Oracle 
> Weblogic 10+.  The Ear plugin currently sets library-directory to the value 
> of defaultLibBundleDir in the application.xml for EARs v5+.  Some of Oracle's 
> classloading features break (specifically "Generic File Loading") when this 
> element is set.  defaultLibBundleDir has to be set to APP-INF/lib since this 
> is the magic library folder for WebLogic.
> The patch adds a parameter to prevent setting library-directory for cases 
> like this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-5294:
---

Description: 
Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the app 
fuse-maven-plugin:full-source goal:

http://issues.appfuse.org/browse/APF-1220

Here is the specific block of code used in the Appfuse Plugin:

{code}

private MavenProject createProjectFromPom(File pom) {
MavenEmbedder maven = new MavenEmbedder();
maven.setOffline(true);
maven.setClassLoader(Thread.currentThread().getContextClassLoader());
maven.setLogger(new MavenEmbedderConsoleLogger());

MavenProject p = null;

try {
maven.setAlignWithUserInstallation(true);
maven.start();
p = maven.readProjectWithDependencies(pom);
maven.stop();
} catch (Exception e) {
e.printStackTrace();
}

return p;
}

{code}

  was:
Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the app 
fuse-maven-plugin:full-source goal:

http://issues.appfuse.org/browse/APF-1220

Here is the specific block of code used in the Appfuse Plugin:

{code}
private MavenProject createProjectFromPom(File pom) {
MavenEmbedder maven = new MavenEmbedder();
maven.setOffline(true);
maven.setClassLoader(Thread.currentThread().getContextClassLoader());
maven.setLogger(new MavenEmbedderConsoleLogger());

MavenProject p = null;

try {
maven.setAlignWithUserInstallation(true);
maven.start();
p = maven.readProjectWithDependencies(pom);
maven.stop();
} catch (Exception e) {
e.printStackTrace();
}

return p;
}
{code}


> Attempt to restore backward compatibility for the MavenEmbedder
> ---
>
> Key: MNG-5294
> URL: https://jira.codehaus.org/browse/MNG-5294
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the 
> app fuse-maven-plugin:full-source goal:
> http://issues.appfuse.org/browse/APF-1220
> Here is the specific block of code used in the Appfuse Plugin:
> {code}
> private MavenProject createProjectFromPom(File pom) {
> MavenEmbedder maven = new MavenEmbedder();
> maven.setOffline(true);
> maven.setClassLoader(Thread.currentThread().getContextClassLoader());
> maven.setLogger(new MavenEmbedderConsoleLogger());
> MavenProject p = null;
> try {
> maven.setAlignWithUserInstallation(true);
> maven.start();
> p = maven.readProjectWithDependencies(pom);
> maven.stop();
> } catch (Exception e) {
> e.printStackTrace();
> }
> return p;
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-5294:
---

Description: 
Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the app 
fuse-maven-plugin:full-source goal:

http://issues.appfuse.org/browse/APF-1220

Here is the specific block of code used in the Appfuse Plugin:

{code}
private MavenProject createProjectFromPom(File pom) {
MavenEmbedder maven = new MavenEmbedder();
maven.setOffline(true);
maven.setClassLoader(Thread.currentThread().getContextClassLoader());
maven.setLogger(new MavenEmbedderConsoleLogger());

MavenProject p = null;

try {
maven.setAlignWithUserInstallation(true);
maven.start();
p = maven.readProjectWithDependencies(pom);
maven.stop();
} catch (Exception e) {
e.printStackTrace();
}

return p;
}
{code}

  was:
Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the app 
fuse-maven-plugin:full-source goal:

http://issues.appfuse.org/browse/APF-1220


> Attempt to restore backward compatibility for the MavenEmbedder
> ---
>
> Key: MNG-5294
> URL: https://jira.codehaus.org/browse/MNG-5294
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the 
> app fuse-maven-plugin:full-source goal:
> http://issues.appfuse.org/browse/APF-1220
> Here is the specific block of code used in the Appfuse Plugin:
> {code}
> private MavenProject createProjectFromPom(File pom) {
> MavenEmbedder maven = new MavenEmbedder();
> maven.setOffline(true);
> maven.setClassLoader(Thread.currentThread().getContextClassLoader());
> maven.setLogger(new MavenEmbedderConsoleLogger());
> MavenProject p = null;
> try {
> maven.setAlignWithUserInstallation(true);
> maven.start();
> p = maven.readProjectWithDependencies(pom);
> maven.stop();
> } catch (Exception e) {
> e.printStackTrace();
> }
> return p;
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5295) Review compatibility of default transport in Maven

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-5295:
---

Description: 
I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
with the new transport. I think we might have been too hasty in quickly 
flipping over to a new transport which is so fundamental to Maven. That it 
might make sense to roll back to the light weight transport in the short/medium 
term.

MNG-5237
MNG-5293

  was:
I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
with the new transport. I think we might have been too hasty in quickly 
flipping over to a new transport which is so fundamental to Maven. That it 
might make sense to roll back to the light weight transport in the short/medium 
term.

MNG-5293


> Review compatibility of default transport in Maven
> --
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
> with the new transport. I think we might have been too hasty in quickly 
> flipping over to a new transport which is so fundamental to Maven. That it 
> might make sense to roll back to the light weight transport in the 
> short/medium term.
> MNG-5237
> MNG-5293

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5237) Cannot download maven dependencies through proxy

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reassigned MNG-5237:
--

Assignee: Jason van Zyl

> Cannot download maven dependencies through proxy
> 
>
> Key: MNG-5237
> URL: https://jira.codehaus.org/browse/MNG-5237
> Project: Maven 2 & 3
>  Issue Type: Bug
>  Components: Dependencies
>Affects Versions: 3.0.4
> Environment: windows xp64 using cygwin
>Reporter: Niels Mordt-Ostergaard
>Assignee: Jason van Zyl
>
> Using proxy in settings.xml, I was able to download maven dependencies in 
> 3.0.3, but this seems to be broken with 3.0.4:
> Proxy definition in settings.xml (hidden ip adress below, but correct proxy 
> ip on my system):
>   
>
>   optional
>   true
>   http
>   
>   
>   xxx.xx.xx.xx
>   8080
>   localhost|127.0.0.1
> 
>   
> Output from 3.0.3:
> $ mvn -V clean
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: C:\Program Files\apache-maven-3.0.3
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: no_NO, platform encoding: Cp1252
> OS name: "windows xp", version: "5.2", arch: "amd64", family: "windows"
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building 
> [INFO] 
> 
> Downloading: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
> Downloaded: 
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
>  (5 KB at 4.9 KB/sec)
> . and so on...
> Output from 3.0.4:
> $ mvn -V clean
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: C:\Program Files\apache-maven-3.0.4
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: no_NO, platform encoding: Cp1252
> OS name: "windows xp", version: "5.2", arch: "amd64", family: "windows"
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building 
> [INFO] 
> 
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.390s
> [INFO] Finished at: Fri Feb 03 13:14:35 CET 2012
> [INFO] Final Memory: 5M/490M
> [INFO] 
> 
> [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of 
> its dependencies could not be resolved: Failed to read artifact descriptor 
> for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer 
> artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to 
> central (http://repo.maven.apache.org/maven2): Access denied to: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom,
>  ReasonPhrase:Forbidden. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

2012-06-06 Thread Jason van Zyl (JIRA)


[ 
https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300488#comment-300488
 ] 

Jason van Zyl commented on MNG-5293:


Does this work with Maven 3.0.3?

> Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.
> --
>
> Key: MNG-5293
> URL: https://jira.codehaus.org/browse/MNG-5293
> Project: Maven 2 & 3
>  Issue Type: Bug
>  Components: Bootstrap & Build
>Affects Versions: 3.0.4
> Environment: openSUSE 12.1 x64
> -=-=-
> denixx@denixxwork:~> java -version
> java version "1.6.0_32"
> Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)
> -=-=-
> additionnaly: NetBeans 7.1.2 uses this flag by default (this flag can be 
> erased in options).
>Reporter: denixx baykin
> Attachments: hs_err_pid9618.log, hs_err_pid9918.log
>
>
> I have localized the issue: it's a Maven issue.
> Maven, started with flag "-Djava.net.useSystemProxies=true" crashes because 
> it somehow use libdbus in openSUSE 12.1 x64 in wrong way.
> Here is a console output:
> denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
>  /home/denixx/soft/apache-maven-3.0.4/bin/mvn 
> -Djava.net.useSystemProxies=true clean install
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.pb:finmonitor:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.systemPath' for 
> com.enterprisedt:edtftp:jar should not point at files within the project 
> directory, ${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be 
> unresolvable by dependent projects @ line 53, column 25
> [WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
> point at files within the project directory, 
> ${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
> dependent projects @ line 61, column 25
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building FinMonitor 0.0.1-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ finmonitor ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
> finmonitor ---
> Downloading: 
> http://repo.maven.apache.org/maven2/commons-cli/commons-cli/1.0/commons-cli-1.0.jar
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.jar
> Downloading: 
> http://repo.maven.apache.org/maven2/junit/junit/3.8.1/junit-3.8.1.jar
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f2d14766727, pid=9618, tid=139831727105792
> #
> # JRE version: 6.0_32-b05
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.7-b02 mixed mode linux-amd64 
> compressed oops)
> # Problematic frame:
> # C  [libdbus-1.so.3+0x8727]  double+0x67
> #
> (process:9618): GConf-WARNING **: Client failed to connect to the D-BUS 
> daemon:
> Failed to connect to socket abstract: Connection refused
> GConf Error: No D-BUS daemon running
> # An error report file with more information is saved as:
> # 
> /home/denixx/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier/hs_err_pid9618.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> ÐÐ²Ð°ÑÐ¸Ð¹Ð½ÑÐ¹ Ð¾ÑÑÐ°Ð½Ð¾Ð² (crash)
> -=-=-
> Another one:
> denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
>  /home/denixx/soft/apache-maven-3.0.4/bin/mvn 
> -Djava.net.useSystemProxies=true clean install
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.pb:finmonitor:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.systemPath' for 
> com.enterprisedt:edtftp:jar should not point at files within the project 
> directory, ${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be 
> unresolvable by dependent projects @ line 53, column 25
> [WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
> point at files within the project directory, 
> ${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
> dependent projects @ line 61, column 25
> [WARN

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reassigned MNG-5293:
--

Assignee: Jason van Zyl

> Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.
> --
>
> Key: MNG-5293
> URL: https://jira.codehaus.org/browse/MNG-5293
> Project: Maven 2 & 3
>  Issue Type: Bug
>  Components: Bootstrap & Build
>Affects Versions: 3.0.4
> Environment: openSUSE 12.1 x64
> -=-=-
> denixx@denixxwork:~> java -version
> java version "1.6.0_32"
> Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)
> -=-=-
> additionnaly: NetBeans 7.1.2 uses this flag by default (this flag can be 
> erased in options).
>Reporter: denixx baykin
>Assignee: Jason van Zyl
> Attachments: hs_err_pid9618.log, hs_err_pid9918.log
>
>
> I have localized the issue: it's a Maven issue.
> Maven, started with flag "-Djava.net.useSystemProxies=true" crashes because 
> it somehow use libdbus in openSUSE 12.1 x64 in wrong way.
> Here is a console output:
> denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
>  /home/denixx/soft/apache-maven-3.0.4/bin/mvn 
> -Djava.net.useSystemProxies=true clean install
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.pb:finmonitor:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.systemPath' for 
> com.enterprisedt:edtftp:jar should not point at files within the project 
> directory, ${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be 
> unresolvable by dependent projects @ line 53, column 25
> [WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
> point at files within the project directory, 
> ${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
> dependent projects @ line 61, column 25
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building FinMonitor 0.0.1-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ finmonitor ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
> finmonitor ---
> Downloading: 
> http://repo.maven.apache.org/maven2/commons-cli/commons-cli/1.0/commons-cli-1.0.jar
> Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.jar
> Downloading: 
> http://repo.maven.apache.org/maven2/junit/junit/3.8.1/junit-3.8.1.jar
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f2d14766727, pid=9618, tid=139831727105792
> #
> # JRE version: 6.0_32-b05
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.7-b02 mixed mode linux-amd64 
> compressed oops)
> # Problematic frame:
> # C  [libdbus-1.so.3+0x8727]  double+0x67
> #
> (process:9618): GConf-WARNING **: Client failed to connect to the D-BUS 
> daemon:
> Failed to connect to socket abstract: Connection refused
> GConf Error: No D-BUS daemon running
> # An error report file with more information is saved as:
> # 
> /home/denixx/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier/hs_err_pid9618.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> ÐÐ²Ð°ÑÐ¸Ð¹Ð½ÑÐ¹ Ð¾ÑÑÐ°Ð½Ð¾Ð² (crash)
> -=-=-
> Another one:
> denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
>  /home/denixx/soft/apache-maven-3.0.4/bin/mvn 
> -Djava.net.useSystemProxies=true clean install
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.pb:finmonitor:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.systemPath' for 
> com.enterprisedt:edtftp:jar should not point at files within the project 
> directory, ${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be 
> unresolvable by dependent projects @ line 53, column 25
> [WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
> point at files within the project directory, 
> ${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
> dependent projects @ line 61, column 25
> [WARNING] 
> [WARNING] It is hig

[jira] (MNG-5295) Review compatibility of default transport in Maven

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-5295:
---

Description: 
I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
with the new transport. I think we might have been too hasty in quickly 
flipping over to a new transport which is so fundamental to Maven. That it 
might make sense to roll back to the light weight transport in the short/medium 
term.

MNG-5293

  was:I've seen issues reported with pre-emptive auth, client side certs, and 
NTLM with the new transport. I think we might have been too hasty in quickly 
flipping over to a new transport which is so fundamental to Maven. That it 
might make sense to roll back to the light weight transport in the short/medium 
term.


> Review compatibility of default transport in Maven
> --
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
> with the new transport. I think we might have been too hasty in quickly 
> flipping over to a new transport which is so fundamental to Maven. That it 
> might make sense to roll back to the light weight transport in the 
> short/medium term.
> MNG-5293

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5295) Review compatibility of default transport in Maven

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reassigned MNG-5295:
--

Assignee: Jason van Zyl

> Review compatibility of default transport in Maven
> --
>
> Key: MNG-5295
> URL: https://jira.codehaus.org/browse/MNG-5295
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
> with the new transport. I think we might have been too hasty in quickly 
> flipping over to a new transport which is so fundamental to Maven. That it 
> might make sense to roll back to the light weight transport in the 
> short/medium term.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5295) Review compatibility of default transport in Maven

2012-06-06 Thread Jason van Zyl (JIRA)

Jason van Zyl created MNG-5295:
--

 Summary: Review compatibility of default transport in Maven
 Key: MNG-5295
 URL: https://jira.codehaus.org/browse/MNG-5295
 Project: Maven 2 & 3
  Issue Type: Task
Reporter: Jason van Zyl


I've seen issues reported with pre-emptive auth, client side certs, and NTLM 
with the new transport. I think we might have been too hasty in quickly 
flipping over to a new transport which is so fundamental to Maven. That it 
might make sense to roll back to the light weight transport in the short/medium 
term.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

2012-06-06 Thread Jason van Zyl (JIRA)


 [ 
https://jira.codehaus.org/browse/MNG-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reassigned MNG-5294:
--

Assignee: Jason van Zyl

> Attempt to restore backward compatibility for the MavenEmbedder
> ---
>
> Key: MNG-5294
> URL: https://jira.codehaus.org/browse/MNG-5294
> Project: Maven 2 & 3
>  Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the 
> app fuse-maven-plugin:full-source goal:
> http://issues.appfuse.org/browse/APF-1220

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

2012-06-06 Thread Jason van Zyl (JIRA)

Jason van Zyl created MNG-5294:
--

 Summary: Attempt to restore backward compatibility for the 
MavenEmbedder
 Key: MNG-5294
 URL: https://jira.codehaus.org/browse/MNG-5294
 Project: Maven 2 & 3
  Issue Type: Task
Reporter: Jason van Zyl


Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the app 
fuse-maven-plugin:full-source goal:

http://issues.appfuse.org/browse/APF-1220

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

2012-06-06 Thread Michal Kalisz (JIRA)

Michal Kalisz created SUREFIRE-875:
--

 Summary: testng-results contains only last suite execute in 
forkmode = always
 Key: SUREFIRE-875
 URL: https://jira.codehaus.org/browse/SUREFIRE-875
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Failsafe Plugin
Affects Versions: 2.12
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
OS name: "linux", version: "3.0.0-20-generic", arch: "amd64", family: "unix"

Reporter: Michal Kalisz
 Attachments: misiu.test-0.0.1-SNAPSHOT-test-sources.jar, pom.xml

Every fork creates new testng-results.xml by replacing previous one. 
If there are two tests class - to suite will be created and only last one will 
be visible in testng-results.xml.

In attached project:
Two test classes: 
SimpleIT, CopyOfCopyOfSimpleIT

running: mvn verify
Generates two sites:

Running pl.misiu.CopyOfCopyOfSimpleIT
Configuring TestNG with: 
org.apache.maven.surefire.testng.conf.TestNGMapConfigurator@771c8a71
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.362 sec
Running pl.misiu.SimpleIT
Configuring TestNG with: 
org.apache.maven.surefire.testng.conf.TestNGMapConfigurator@72c53dce
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.326 sec

In target/failsafe-reports/testng-results.xml

there is only one test SimpleIT (the last execute site)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

2012-06-06 Thread denixx baykin (JIRA)

denixx baykin created MNG-5293:
--

 Summary: Maven 3.0.4 crashes when 
"-Djava.net.useSystemProxies=true" added.
 Key: MNG-5293
 URL: https://jira.codehaus.org/browse/MNG-5293
 Project: Maven 2 & 3
  Issue Type: Bug
  Components: Bootstrap & Build
Affects Versions: 3.0.4
 Environment: openSUSE 12.1 x64
-=-=-
denixx@denixxwork:~> java -version
java version "1.6.0_32"
Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)
-=-=-
additionnaly: NetBeans 7.1.2 uses this flag by default (this flag can be erased 
in options).
Reporter: denixx baykin
 Attachments: hs_err_pid9618.log, hs_err_pid9918.log

I have localized the issue: it's a Maven issue.
Maven, started with flag "-Djava.net.useSystemProxies=true" crashes because it 
somehow use libdbus in openSUSE 12.1 x64 in wrong way.

Here is a console output:
denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
 /home/denixx/soft/apache-maven-3.0.4/bin/mvn -Djava.net.useSystemProxies=true 
clean install
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
com.pb:finmonitor:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for com.enterprisedt:edtftp:jar 
should not point at files within the project directory, 
${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be unresolvable by 
dependent projects @ line 53, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
point at files within the project directory, 
${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
dependent projects @ line 61, column 25
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] 
[INFO] Building FinMonitor 0.0.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ finmonitor ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
finmonitor ---
Downloading: 
http://repo.maven.apache.org/maven2/commons-cli/commons-cli/1.0/commons-cli-1.0.jar
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.jar
Downloading: 
http://repo.maven.apache.org/maven2/junit/junit/3.8.1/junit-3.8.1.jar
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7f2d14766727, pid=9618, tid=139831727105792
#
# JRE version: 6.0_32-b05
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.7-b02 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libdbus-1.so.3+0x8727]  double+0x67
#

(process:9618): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket abstract: Connection refused
GConf Error: No D-BUS daemon running

# An error report file with more information is saved as:
# 
/home/denixx/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier/hs_err_pid9618.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
ÐÐ²Ð°ÑÐ¸Ð¹Ð½ÑÐ¹ Ð¾ÑÑÐ°Ð½Ð¾Ð² (crash)

-=-=-
Another one:
denixx@denixxwork:~/NetBeansProjects/FinMonitor_server_boevoy_20120517_Qualifier>
 /home/denixx/soft/apache-maven-3.0.4/bin/mvn -Djava.net.useSystemProxies=true 
clean install
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
com.pb:finmonitor:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for com.enterprisedt:edtftp:jar 
should not point at files within the project directory, 
${basedir}/src/main/webapp/WEB-INF/lib/edtftpj.jar will be unresolvable by 
dependent projects @ line 53, column 25
[WARNING] 'dependencies.dependency.systemPath' for com.sun:jna:jar should not 
point at files within the project directory, 
${basedir}/src/main/webapp/WEB-INF/lib/jna.jar will be unresolvable by 
dependent projects @ line 61, column 25
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] 
[INFO] Building FinMonitor 0.0.1-SNAPSHOT
[INFO] ---

[jira] (MNG-5237) Cannot download maven dependencies through proxy

[jira] (MEAR-146) Expose parameter to not write library-directory element in application.xml

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

[jira] (MNG-5295) Review compatibility of default transport in Maven

[jira] (MNG-5237) Cannot download maven dependencies through proxy

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

[jira] (MNG-5295) Review compatibility of default transport in Maven

[jira] (MNG-5295) Review compatibility of default transport in Maven

[jira] (MNG-5295) Review compatibility of default transport in Maven

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder

[jira] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

[jira] (MNG-5293) Maven 3.0.4 crashes when "-Djava.net.useSystemProxies=true" added.

15 matches

Site Navigation

Mail list logo

Footer information