[jira] Commented: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories

2006-01-26 Thread Christian Mouttet (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-488?page=comments#action_56987 
] 

Christian Mouttet commented on CONTINUUM-488:
-

I did so and got following line in the log

14686 [Thread-1] DEBUG org.apache.maven.settings.MavenSettingsBuilder  - 
Building Maven global-level settings from: 
'/opt/continuum-1.0.2/bin/linux/$M2_HOME/conf/settings.xml'

this can't work.

Removing wrapper.java.additional.6 again it reads

jvm 1| 2006-01-26 10:57:06,614 [Thread-1] DEBUG MavenSettingsBuilder
   - Building Maven global-level settings from: 
'/opt/continuum-1.0.2/bin/linux/conf/settings.xml'

In this directory we already tried to place settings.xml at 25. Jan.

There are Windows-like environment entries in linux/wrapper.conf e. g. 
wrapper.java.command=%JAVA_HOME%/bin/java. Is that intended?

 Continuum will not use mirrors or alternate repositories
 

  Key: CONTINUUM-488
  URL: http://jira.codehaus.org/browse/CONTINUUM-488
  Project: Continuum
 Type: Bug

   Components: Core system
 Versions: 1.0.1
 Reporter: David Hawkins



 I can't get Continuum to use a repository other than repo1.maven.org.  
 Running mvn manually for my user works fine and fetches the dependencies from 
 the mirror specified in settings.xml.  However, when I start continuum and it 
 attempts the build, it always tries to get dependencies from repo1.maven.org. 
  I have tried specifying a mirror and also specified my server in a 
 profile/repositories/repository in settings.xml. Neither worked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories

2006-01-26 Thread Christian Mouttet (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-488?page=comments#action_57027 
] 

Christian Mouttet commented on CONTINUUM-488:
-

log looks better

jvm 1| 2006-01-26 17:38:41,682 [Thread-1] DEBUG MavenSettingsBuilder
   - Building Maven global-level settings from: 
'/opt/maven-2.0.1/conf/settings.xml'

but the settings still aren't used :-(

Where is the difference between starting mvn from command line and from 
continuum. Continuum passes the globalSettingsPath and userSettingsPath 
with -D system parameters, right?

Unfortunately I'm not able to check out from ASF-SVN (maybe because of your 
company's proxy settings). I'm getting invalid request ... REPORT 
http://svn.apache.org:80/repos/asf/!svn/vcc/default;. So I'm not able to do 
some debugging.

 Continuum will not use mirrors or alternate repositories
 

  Key: CONTINUUM-488
  URL: http://jira.codehaus.org/browse/CONTINUUM-488
  Project: Continuum
 Type: Bug

   Components: Core system
 Versions: 1.0.1
 Reporter: David Hawkins



 I can't get Continuum to use a repository other than repo1.maven.org.  
 Running mvn manually for my user works fine and fetches the dependencies from 
 the mirror specified in settings.xml.  However, when I start continuum and it 
 attempts the build, it always tries to get dependencies from repo1.maven.org. 
  I have tried specifying a mirror and also specified my server in a 
 profile/repositories/repository in settings.xml. Neither worked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories

2006-01-25 Thread Christian Mouttet (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-488?page=comments#action_56900 
] 

Christian Mouttet commented on CONTINUUM-488:
-

Ok, thanks.
Both maven-2.0 and 2.0.1 work perfectly if I run mvn manually from a console.

 Continuum will not use mirrors or alternate repositories
 

  Key: CONTINUUM-488
  URL: http://jira.codehaus.org/browse/CONTINUUM-488
  Project: Continuum
 Type: Bug

   Components: Core system
 Versions: 1.0.1
 Reporter: David Hawkins



 I can't get Continuum to use a repository other than repo1.maven.org.  
 Running mvn manually for my user works fine and fetches the dependencies from 
 the mirror specified in settings.xml.  However, when I start continuum and it 
 attempts the build, it always tries to get dependencies from repo1.maven.org. 
  I have tried specifying a mirror and also specified my server in a 
 profile/repositories/repository in settings.xml. Neither worked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories

2006-01-25 Thread Christian Mouttet (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-488?page=comments#action_56879 
] 

Christian Mouttet commented on CONTINUUM-488:
-

Hi Emmanuel,

I followed your suggestion but it doesn't work for me. What a pity. 
Dependencies of the project can't be downloaded because of the missing proxy 
setting.

 Continuum will not use mirrors or alternate repositories
 

  Key: CONTINUUM-488
  URL: http://jira.codehaus.org/browse/CONTINUUM-488
  Project: Continuum
 Type: Bug

   Components: Core system
 Versions: 1.0.1
 Reporter: David Hawkins



 I can't get Continuum to use a repository other than repo1.maven.org.  
 Running mvn manually for my user works fine and fetches the dependencies from 
 the mirror specified in settings.xml.  However, when I start continuum and it 
 attempts the build, it always tries to get dependencies from repo1.maven.org. 
  I have tried specifying a mirror and also specified my server in a 
 profile/repositories/repository in settings.xml. Neither worked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (MNG-1178) weird junit classloader issue

2005-11-14 Thread Christian Mouttet (JIRA)
[ http://jira.codehaus.org/browse/MNG-1178?page=comments#action_50889 ] 

Christian Mouttet commented on MNG-1178:


Brett,

to reproduce the bug you can write a simple TestCase like this (initializing 
Log4J):

public class SimpleTest extends TestCase {
static {
URL url = AbstractTestCase.class.getResource(/test-log4j.xml);
DOMConfigurator.configure(url);
}

// any tests you like to do ...

}


I have maven-2.0 with surefire-1.4 and junit-3.8.1.

 weird junit classloader issue
 -

  Key: MNG-1178
  URL: http://jira.codehaus.org/browse/MNG-1178
  Project: Maven 2
 Type: Bug
  Environment: java 1.5, linux
 Reporter: Matthew Pocock
 Assignee: Brett Porter
  Attachments: mng-1178-1.tar.gz


 In some cases (that I've not narrowed down), I get this exception when doing 
 m2 install. The affected projects have no test cases and no dependencies taht 
 use JUnit in any way. i can get rid of this exceptino if Junit is added as a 
 test scope dependency. It smells like a class loader issue where something 
 funkey is going on to make the no-args constructor of UnitTest unavailable 
 for chaining from BatteryAssert. Beats me.
 org.apache.maven.plugin.MojoExecutionException: Error executing surefire
 at 
 org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:294)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:419)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:599)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:326)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:152)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:237)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:251)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.surefire.SurefireBooter.run(SurefireBooter.java:104)
 at 
 org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:289)
 ... 16 more
 Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)
 at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at 
 org.codehaus.surefire.Surefire.instantiateBatteries(Surefire.java:274)
 at org.codehaus.surefire.Surefire.run(Surefire.java:82)
 at org.codehaus.surefire.Surefire.run(Surefire.java:76)
 ... 22 more
 Caused by: java.lang.IllegalAccessError: tried to access method 
 junit.framework.TestCase.init()V from class 
 org.codehaus.surefire.battery.assertion.BatteryAssert
 at 
 org.codehaus.surefire.battery.assertion.BatteryAssert.init(BatteryAssert.java:23)
 at 
 org.codehaus.surefire.battery.AbstractBattery.init(AbstractBattery.java:31)
 at 
 org.codehaus.surefire.battery.DirectoryBattery.init(DirectoryBattery.java:39)
 ... 29 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: