[maven2 build - FAILED - update] Wed Oct 12 06:15:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.061502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 06:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.06.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 05:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.054500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1182) update plexus-utils code for stream handling
update plexus-utils code for stream handling Key: MNG-1182 URL: http://jira.codehaus.org/browse/MNG-1182 Project: Maven 2 Type: Improvement Reporter: Brett Porter Fix For: 2.0.1 we are still using plexus-utils with old versions of FileUtils that don't properly close files on exception - this could be an issue when we get to embedding. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 05:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.053000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 05:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.051500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-3) MavenProject / pom listener
[ http://jira.codehaus.org/browse/MNG-3?page=comments#action_48395 ] Eugene Kuleshov commented on MNG-3: --- I still not sure how useful it would be considering that it doesn't really make much sense to keep projects or models in memory since there are a good chance that they would be changed externally, so you would need to scratch it. The only case it could be useful if you are implementing your own model editor, but there you may use your own model or something instead... > MavenProject / pom listener > --- > > Key: MNG-3 > URL: http://jira.codehaus.org/browse/MNG-3 > Project: Maven 2 > Type: Improvement > Components: maven-embedder, maven-project > Reporter: gilles dodinet > > > ide integration needs a listener mechanism so that when project/model is > changed interested parties are notified and can eventually reflect those > changes (f.i. refresh a view). we've implemented that in mevenide, please see > : > http://cvs.mevenide.codehaus.org/cvsweb.cgi/mevenide-core/src/java/org/mevenide/project/ -- 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: [EMAIL PROTECTED]
[jira] Updated: (MNG-963) add "toplinks" configuration for FAQs
[ http://jira.codehaus.org/browse/MNG-963?page=all ] Johnny R. Ruiz III updated MNG-963: --- Assign To: (was: Johnny R. Ruiz III) > add "toplinks" configuration for FAQs > - > > Key: MNG-963 > URL: http://jira.codehaus.org/browse/MNG-963 > Project: Maven 2 > Type: Improvement > Components: maven-site-plugin > Reporter: Brett Porter > Fix For: 2.0-beta-4 > > > need to be able to tell the FAQ whether to generate the top links. > There are probably a few options for configuring the sinks: > - put it in the fml file as metadata > - add that configuration to the site mojo as various subsections that can be > passed as beans to doxia > - add to site.xml -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 05:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.05.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1181) MavenEmbedder.execute() doesn't run reactor modules
MavenEmbedder.execute() doesn't run reactor modules --- Key: MNG-1181 URL: http://jira.codehaus.org/browse/MNG-1181 Project: Maven 2 Type: Bug Components: maven-embedder Reporter: Eugene Kuleshov Priority: Blocker MavenEmbedder.execute() doesn't run reactor modules. I've been trying to run it with "generate-sources" goal, but it only build the root project. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 04:45:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.044501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1132) Dependency outputdirectory ignored when unpack is specified
[ http://jira.codehaus.org/browse/MNG-1132?page=all ]
Brett Porter closed MNG-1132:
-
Assign To: Brett Porter (was: John Casey)
Resolution: Fixed
applied
> Dependency outputdirectory ignored when unpack is specified
> ---
>
> Key: MNG-1132
> URL: http://jira.codehaus.org/browse/MNG-1132
> Project: Maven 2
> Type: Bug
> Components: maven-assembly-plugin
> Versions: 2.0-beta-3
> Reporter: Jerome Lacoste
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0-beta-4
> Attachments: support_output_dir_with_unpack.diff,
> support_output_dir_with_unpack.diff
>
>
> [I hope this can be looked into before official 2.0 otherwise that could
> create issues with regard to breaking existing code. Making critical for this
> reason]
> I am attempting to unpack in a particular place below the working directory.
> Let's say I do something like
>
> tomcat/webapp/
>
> org.cb.project:webapp
>
> true
> runtime
>
> The code in
> maven-plugins/maven-assembly-plugin/src/main/java/org/apache/maven/plugin/assembly/AssemblyMojo.java
> if ( dependencySet.isUnpack() )
> {
> // TODO: something like zipfileset in plexus-archiver
> //archiver.addJar( )
> File tempLocation = new File( workDirectory,
> name.substring( 0, name.length() - 4 ) );
> boolean process = false;
> if ( !tempLocation.exists() )
> {
> tempLocation.mkdirs();
> process = true;
> }
> else if ( artifact.getFile().lastModified() >
> tempLocation.lastModified() )
> {
> process = true;
> }
> if ( process )
> {
> try
> {
> unpack( artifact.getFile(), tempLocation );
> }
> catch ( NoSuchArchiverException e )
> {
> throw new MojoExecutionException(
> "Unable to obtain unarchiver for file '"
> + artifact.getFile() + "'" );
> }
> }
> archiver.addDirectory( tempLocation, null,
>(String[])
> getDefaultExcludes().toArray( EMPTY_STRING_ARRAY ) );
> }
> else
> {
> archiver.addFile( artifact.getFile(), output +
> evaluateFileNameMapping(
> dependencySet.getOutputFileNameMapping(), artifact ) );
> }
> This treats files to unpack and pack differently.
> I believe
> File tempLocation = new File( workDirectory,
> name.substring( 0, name.length() - 4 ) );
> should be replaced by something like:
> File tempOutputLocation = new File( workDirectory,
> output);
> File tempLocation = new File( tempOutputLocation,
> name.substring( 0, name.length() - 4 ) );
> That way both code paths will end up treating the files similarly. If I
> change from unpack to pack, my file end up in the same place. That sounds
> logical to me.
> Someone can still use / if he doesn't want
> the files to be some levels below the work directory.
--
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: [EMAIL PROTECTED]
[jira] Commented: (MNG-1161) Assembly doesn't work with provided scope
[ http://jira.codehaus.org/browse/MNG-1161?page=comments#action_48393 ] Brett Porter commented on MNG-1161: --- ok, we should look into the best way to work this out then. A workaround is probably to have a dependency set where the artifacts are explicity declared for inclusion. > Assembly doesn't work with provided scope > - > > Key: MNG-1161 > URL: http://jira.codehaus.org/browse/MNG-1161 > Project: Maven 2 > Type: Bug > Components: maven-assembly-plugin > Versions: 2.0-beta-3 > Environment: WinXP > Reporter: Brian Fox > > > I have a project with all dependancies in the provided scope. I'd like to > create an assembly that contains all these jars. If I set the scope to > provided in the assembly descriptor xml file, it ignores all these > dependancies. If I change it to test, it grabs them, but also my test > dependancies as expected. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 04:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.043000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1169) Support profiles in pom type
[ http://jira.codehaus.org/browse/MNG-1169?page=all ] Brett Porter updated MNG-1169: -- Assign To: Brett Porter Fix Version: 2.0-beta-4 Component: (was: maven-ant-plugin) maven-artifact-ant > Support profiles in pom type > > > Key: MNG-1169 > URL: http://jira.codehaus.org/browse/MNG-1169 > Project: Maven 2 > Type: Improvement > Components: maven-artifact-ant > Versions: 2.0-beta-4 > Reporter: Mark Hobson > Assignee: Brett Porter > Fix For: 2.0-beta-4 > > > Need to be able to pass in a list of profiles to activate in pom type - > there's currently a TODO in Pom.java for this. -- 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: [EMAIL PROTECTED]
[jira] Created: (MNG-1180) improve integration of the site into the assembly
improve integration of the site into the assembly - Key: MNG-1180 URL: http://jira.codehaus.org/browse/MNG-1180 Project: Maven 2 Type: Bug Reporter: Brett Porter it would be good to be able to automate the calling of site:site via a lifecycle binding, but not sure how to make this optional depending on arguments in the mojo. -- 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: [EMAIL PROTECTED]
[jira] Closed: (MNG-958) ability to optionally include site in binary distribution
[ http://jira.codehaus.org/browse/MNG-958?page=all ] Brett Porter closed MNG-958: Resolution: Fixed > ability to optionally include site in binary distribution > - > > Key: MNG-958 > URL: http://jira.codehaus.org/browse/MNG-958 > Project: Maven 2 > Type: New Feature > Components: maven-assembly-plugin > Versions: 2.0-beta-4 > Reporter: Brett Porter > Assignee: Johnny R. Ruiz III > Fix For: 2.0-beta-4 > Attachments: MNG-958-maven-assembly-plugin.patch > > Original Estimate: 4 hours >Time Spent: 4 hours > Remaining: 0 minutes > -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 04:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.041500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 04:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.04.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1171) I wish there was a recommended way of naming plugins
[ http://jira.codehaus.org/browse/MNG-1171?page=all ] Brett Porter updated MNG-1171: -- Component: documentation > I wish there was a recommended way of naming plugins > > > Key: MNG-1171 > URL: http://jira.codehaus.org/browse/MNG-1171 > Project: Maven 2 > Type: Wish > Components: documentation > Reporter: Brian Bonner > Priority: Minor > > > What *is* the preferred article id naming for Maven Plugins? > I've seen it as -maven-plugin and maven--plugin > It would help me (and other users) avoid silly mistakes if there was a > recommended pattern. > I ran into this with the xmlbeans plugin. The example had it named as > maven-xmlbeans-plugin. After looking at other plugins, it looks like this is > the "standard". > It seems like the name should either go at the beginning or end (i.e. > xmlbeans-maven-plugin, or maven-plugin-xmlbeans). > I'm wondering if there is really a rhyme or reason to this. It would make it > easier to write poms if there was some sort of recommended standard. -- 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: [EMAIL PROTECTED]
[jira] Closed: (MNG-1172) class loading / xerces
[ http://jira.codehaus.org/browse/MNG-1172?page=all ] Brett Porter closed MNG-1172: - Assign To: Brett Porter Resolution: Cannot Reproduce Maven doesn't use Xerces - so the property must be set somewhere in your own code. Do you have xerces listed as a dependency? That should be able to be removed if you are compiling with JDK 1.5. > class loading / xerces > -- > > Key: MNG-1172 > URL: http://jira.codehaus.org/browse/MNG-1172 > Project: Maven 2 > Type: Bug > Components: maven-surefire-plugin > Versions: 2.0-beta-3 > Environment: maven-2-beta-3, jdk 5.0.0_4, winXP SP2 > Reporter: Dirk Sturzebecher > Assignee: Brett Porter > > > I have two tests in one test class. Both read a csv file and check for > certain attributes. Both tests run ok outside maven. In maven the first test > fails, the second (ordered by execution sequence) is ok. That is, if I do > understand the output correctly. The output in surefire-reports is: > --- > Battery: de.dst.money.stock.StockPluginTest > --- > testDoImport01(de.dst.money.stock.StockPluginTest) > [ stdout ] --- > [ stderr ] --- > [ stacktrace ] --- > javax.xml.parsers.FactoryConfigurationError: Provider > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:145) > at > de.dst.money.framework.model.persistence.xml.XMLUtil.loadDocument(XMLUtil.java:64) > at > de.dst.money.framework.model.persistence.xml.XMLPersistenceManager.loadDocument(XMLPersistenceManager.java:82) > at de.dst.money.stock.StockPlugin.load(StockPlugin.java:97) > at de.dst.money.stock.StockPlugin.getModel(StockPlugin.java:87) > at > de.dst.money.stock.StockPluginTest.testDoImport01(StockPluginTest.java:35) > 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 junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > 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.battery.JUnitBattery.executeJUnit(JUnitBattery.java:246) > at > org.codehaus.surefire.battery.JUnitBattery.execute(JUnitBattery.java:220) > at org.codehaus.surefire.Surefire.executeBattery(Surefire.java:203) > at org.codehaus.surefire.Surefire.run(Surefire.java:152) > at org.codehaus.surefire.Surefire.run(Surefire.java:76) > 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:229) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:508) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:494) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:2
[jira] Updated: (MNG-1173) transitive dependencies with system scope are treated as normal scope
[ http://jira.codehaus.org/browse/MNG-1173?page=all ] Brett Porter updated MNG-1173: -- Assign To: John Casey Fix Version: 2.0-beta-4 I think John has fixed this? > transitive dependencies with system scope are treated as normal scope > - > > Key: MNG-1173 > URL: http://jira.codehaus.org/browse/MNG-1173 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-4 > Environment: linux, sun jdk 1.5 > Reporter: Matthew Pocock > Assignee: John Casey > Fix For: 2.0-beta-4 > > > Module A has a system dependency on tools.jar - this works out fine. The > module is built and artifact(s) deployed. > Module B has A as a dependency. During transitive dependency resolution, > tools.jar must be resolved. However, it appears that m2 is attempting to > resolve it as a non-system dependency. -- 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: [EMAIL PROTECTED]
[jira] Commented: (MNG-1174) New Mojos for compiler and jar plugins to allow alternate jars
[ http://jira.codehaus.org/browse/MNG-1174?page=comments#action_48386 ] Brett Porter commented on MNG-1174: --- I think these should possibly be a separate plugin, but am not sure. If its ok, I'm holding off reviewing this until after we have 2.0 out next week. > New Mojos for compiler and jar plugins to allow alternate jars > -- > > Key: MNG-1174 > URL: http://jira.codehaus.org/browse/MNG-1174 > Project: Maven 2 > Type: Improvement > Versions: 2.0-beta-3 > Environment: Linux using JDK 1.5.0_01 > Reporter: Bob Allison > Fix For: 2.0-beta-4 > Attachments: AltCompilerMojo.java, AltJarMojo.java, pom.xml > > > Add mojos so that mock objects and other affiliated source roots can be > compiled and packaged in the same project -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 03:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.034500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1178) weird junit classloader issue
[ http://jira.codehaus.org/browse/MNG-1178?page=comments#action_48385 ] Brett Porter commented on MNG-1178: --- what version of m2 / surefire were you getting this with? > 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 > > > 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.()V from class > org.codehaus.surefire.battery.assertion.BatteryAssert > at > org.codehaus.surefire.battery.assertion.BatteryAssert.(BatteryAssert.java:23) > at > org.codehaus.surefire.battery.AbstractBattery.(AbstractBattery.java:31) > at > org.codehaus.surefire.battery.DirectoryBattery.(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: [EMAIL PROTECTED]
[jira] Closed: (MNG-1179) allow user to specify the settings.xml file location to the MBoot class
[ http://jira.codehaus.org/browse/MNG-1179?page=all ] Brett Porter closed MNG-1179: - Assign To: Brett Porter Resolution: Fixed Fix Version: 2.0-beta-4 > allow user to specify the settings.xml file location to the MBoot class > --- > > Key: MNG-1179 > URL: http://jira.codehaus.org/browse/MNG-1179 > Project: Maven 2 > Type: New Feature > Versions: 2.0-beta-3 > Reporter: Jerome Lacoste > Assignee: Brett Porter > Priority: Trivial > Fix For: 2.0-beta-4 > Attachments: maven-mboot2-support-setting-settings-file.diff > > > I don't use ~/.m2/settings.xml not ~/.m2/repository and I don't want m2 to > install there. Patch attached. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 03:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.031501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 03:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.03.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 02:45:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.024501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 02:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.021500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 02:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.02.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-108) Springframework: Add Optional Flag to Implementation Specific Dependencies
Springframework: Add Optional Flag to Implementation Specific Dependencies -- Key: MEV-108 URL: http://jira.codehaus.org/browse/MEV-108 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Stephen Duncan Jr Many dependencies of the springframework should have the optional flag set (true). For spring-orm: spring-webmvc, toplink-api, jdo, ibatis (probably others) For spring-jdbc: c3p0, commons-dbcp, xapool For spring-hibernate: hibernate3, hibernate-annotations, hibernate2 Assumably there are many others that Spring developers would know, but these are ones I know are optional. The use case is here is that I want to use spring-hibernate with hibernate 2 only. Therefore of the listed optional dependencies, only hibernate 2 (net.sf.hibernate:hibernate) should be required. I currently receive the others transitively, but they are not desired, and frequently will not be desired. Therefore it's better to set them to be flagged as optional, instead of forcing users to set exclusions. Optional flag added: http://jira.codehaus.org/browse/MNG-947 -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 01:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.014500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1179) allow user to specify the settings.xml file location to the MBoot class
allow user to specify the settings.xml file location to the MBoot class --- Key: MNG-1179 URL: http://jira.codehaus.org/browse/MNG-1179 Project: Maven 2 Type: New Feature Versions: 2.0-beta-3 Reporter: Jerome Lacoste Priority: Trivial Attachments: maven-mboot2-support-setting-settings-file.diff I don't use ~/.m2/settings.xml not ~/.m2/repository and I don't want m2 to install there. Patch attached. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 01:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.013000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 01:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.011501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 12 01:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-969) FAQ entries with in the question aren't properly formatted
[ http://jira.codehaus.org/browse/MNG-969?page=all ] Johnny R. Ruiz III closed MNG-969: -- Resolution: Fixed plexus-site-renderer dependency to doxia-core must be updated to the patched version 1.0-alpha-5-SNAPSHOT. > FAQ entries with in the question aren't properly formatted > - > > Key: MNG-969 > URL: http://jira.codehaus.org/browse/MNG-969 > Project: Maven 2 > Type: Bug > Components: maven-site-plugin > Versions: 2.0-beta-1 > Reporter: Trygve Laugstol > Assignee: Johnny R. Ruiz III > Fix For: 2.0-beta-4 > > Original Estimate: 3 hours > Remaining: 3 hours > > The 5th element here contains in verbatim: > http://maven.apache.org/maven2/maven1.html -- 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: [EMAIL PROTECTED]
[jira] Updated: (MNG-968) linkoffline tag is not parsed properly
[ http://jira.codehaus.org/browse/MNG-968?page=all ] Lester Ecarma updated MNG-968: -- Attachment: MNG-968.patch Attached file should fix this issue, as well as provide support for multiple link and linkoffline options declarations. For example, it should be able to handle declarations in the pom such as, org.apache.maven.plugins maven-javadoc-plugin 2.0-beta-4 http://java.sun.com/j2se/1.4.2/docs/api/, C:\local dir\docs\api\ http://java.sun.com/j2se/1.4.2/docs/api/#C:\local dir\docs\api\, http://ant.apache.org/manual/api/#C:\local dir\apache-ant-1.6.1\docs\manual\api , C:\local-dir-for-offlinelinks-in-offline-mode\docs\api 1.4 where comma is used to separate argument sets, and # to separate arguments in linkoffline. > linkoffline tag is not parsed properly > -- > > Key: MNG-968 > URL: http://jira.codehaus.org/browse/MNG-968 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0-beta-1 > Reporter: David DIDIER > Assignee: Lester Ecarma > Fix For: 2.0-beta-4 > Attachments: MNG-968.patch > > Original Estimate: 4 hours > Remaining: 4 hours > > When using the javadoc plugin with linkoffline, my pom contains : > > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.0-beta-1 > > http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/ > 1.4 > > > ... > > > but the generated command is then : > javadoc.exe ... -linkoffline "http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/" ... > according to the javadoc documentation, it seems that the syntax should be : > javadoc.exe ... -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/ ... > (without ") > Here is the interesting part of the trace : > [INFO] [javadoc:javadoc] > [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package-source > 1.4 -sourcePath D:\projets\ndd\root\..\ndd14-base\src\main\java -classpath > D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\commons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar > -author -bottom "Copyright null DD. All Rights Reserved." -charset > ISO-8859-1 -d D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle > "NDD Base project 0.20-SNAPSHOT API" -linkoffline > "http://java.sun.com/j2se/1.4.2/docs/api/ ../root/src/javadoc/j2sdk-1.4.2/" > -stylesheetfile > D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use > -version -windowtitle "NDD Base project 0.20-SNAPSHOT API" @files > javadoc: Illegal package name: > "D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css" -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - checkout] Wed Oct 12 00:47:48 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.004748.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=all ] Brett Porter closed MNG-678: Resolution: Fixed Fix Version: (was: 2.0.1) 2.0-beta-4 yes, the new version passed all the tests. great! > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0-beta-4 > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Oct 12 00:00:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051012.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051012.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_48376 ] Brett Porter commented on MNG-678: -- yes, I saw this this morning. Thanks for saving me the reading :) I'll test it out. > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0.1 > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 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: [EMAIL PROTECTED]
[maven2 build - SKIPPED - checkout] Wed Oct 12 00:15:00 GMT 2005
ci.sh already running... exiting maven 9127 8938 0 00:02:36 ? 0:00 /bin/sh /export/home/maven/ci.sh update maven 8938 8907 0 00:00:01 ? 0:00 /bin/sh /export/home/maven/ci.sh update maven 8907 8900 0 00:00:01 ? 0:00 /bin/sh /export/home/maven/ci.sh update - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-968) linkoffline tag is not parsed properly
[ http://jira.codehaus.org/browse/MNG-968?page=all ] Lester Ecarma updated MNG-968: -- Remaining Estimate: 4 hours Original Estimate: 14400 > linkoffline tag is not parsed properly > -- > > Key: MNG-968 > URL: http://jira.codehaus.org/browse/MNG-968 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0-beta-1 > Reporter: David DIDIER > Assignee: Lester Ecarma > Fix For: 2.0-beta-4 > > Original Estimate: 4 hours > Remaining: 4 hours > > When using the javadoc plugin with linkoffline, my pom contains : > > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.0-beta-1 > > http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/ > 1.4 > > > ... > > > but the generated command is then : > javadoc.exe ... -linkoffline "http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/" ... > according to the javadoc documentation, it seems that the syntax should be : > javadoc.exe ... -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ > path/to/package-list/ ... > (without ") > Here is the interesting part of the trace : > [INFO] [javadoc:javadoc] > [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package-source > 1.4 -sourcePath D:\projets\ndd\root\..\ndd14-base\src\main\java -classpath > D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\commons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar > -author -bottom "Copyright null DD. All Rights Reserved." -charset > ISO-8859-1 -d D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle > "NDD Base project 0.20-SNAPSHOT API" -linkoffline > "http://java.sun.com/j2se/1.4.2/docs/api/ ../root/src/javadoc/j2sdk-1.4.2/" > -stylesheetfile > D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use > -version -windowtitle "NDD Base project 0.20-SNAPSHOT API" @files > javadoc: Illegal package name: > "D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css" -- 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: [EMAIL PROTECTED]
[jira] Closed: (MNG-1096) Error handling needs improvement
[ http://jira.codehaus.org/browse/MNG-1096?page=all ] John Casey closed MNG-1096: --- Resolution: Fixed added error diagnoser for MojoExecutionException instances. > Error handling needs improvement > > > Key: MNG-1096 > URL: http://jira.codehaus.org/browse/MNG-1096 > Project: Maven 2 > Type: Improvement > Components: maven-site-plugin > Versions: 2.0-beta-2 > Reporter: David Jackman > Assignee: John Casey > Fix For: 2.0-beta-4 > > Original Estimate: 1 hour >Time Spent: 30 minutes > Remaining: 0 minutes > > I'm actually not sure if this is specific for the site plugin or something > more general for Maven 2 error reporting. > Here was the situation that brought this about: I was trying to build the > site for the maven-site project. At the time, there were two files checked > into src/site/resources/images that had the same name (h3.gif and h3.jpg). > (Note: this problem has since been cleared up.) When executing the site:site > goal, I got the following back: > ... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Diagnosis: Error during report generation > [INFO] > > After adding the -X option, I get this exception information: > [DEBUG] Trace: > org.apache.maven.plugin.MojoExecutionException: Error during report generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:422) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:517) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:247) > 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:324) > 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: org.apache.maven.reporting.MavenReportException: Some files are > duplicates in the site directory or in the generated-site directory. > Review the following files for the "English" version: > images\h3 > resources\images\h3.gif > resources\images\h3.jpg > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:312) > ... 16 more > It seems like something is throwing an exception with a helpful message, but > it's caught by DoxiaMojo, which then throws a MojoExecutionException that > chains the original exception. Maven is just reporting the > MojoExecutionException message, which doesn't contain the helpful information. > So, to fix this problem, either the DoxiaMojo code should be fixed so the > message in the MojoExecutionException includes the message from the exception > it caught, or the core Maven error reporting code should be fixed so it > includes messages from exceptions chained with the MojoExecutionException. -- 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: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-546) upload cewolf 0.12.0
upload cewolf 0.12.0 Key: MAVENUPLOAD-546 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-546 Project: maven-upload-requests Type: Bug Reporter: Brian Fox http://sourceforge.net/projects/cewolf/ http://sourceforge.net/project/memberlist.php?group_id=57282 Cewolf is a tag library using jfreechart to generate charts. I recently discovered that cewolf already existed under /maven/cewolf and /maven2/cewolf so I modified the project.xml -- 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: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-544) upload cewolf 0.12.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-544?page=all ] Brian Fox closed MAVENUPLOAD-544: - Resolution: Duplicate > upload cewolf 0.12.0 > > > Key: MAVENUPLOAD-544 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-544 > Project: maven-upload-requests > Type: Task > Reporter: Brian Fox > > > http://sourceforge.net/projects/cewolf/ > http://sourceforge.net/project/memberlist.php?group_id=57282 > Cewolf is a tag library using jfreechart to generate charts. -- 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: [EMAIL PROTECTED]
[jira] Created: (MNG-1178) weird junit classloader issue
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 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.()V from class org.codehaus.surefire.battery.assertion.BatteryAssert at org.codehaus.surefire.battery.assertion.BatteryAssert.(BatteryAssert.java:23) at org.codehaus.surefire.battery.AbstractBattery.(AbstractBattery.java:31) at org.codehaus.surefire.battery.DirectoryBattery.(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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 21:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.214500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.214500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1177) Project descriptor reference does not explain the syntax for the element.
Project descriptor reference does not explain the syntax for the element. -- Key: MNG-1177 URL: http://jira.codehaus.org/browse/MNG-1177 Project: Maven 2 Type: Bug Components: documentation Reporter: David Jackman The Project Descriptor reference page (maven-model/maven.html) should contain information about the properties element under project. Specifically, the format for setting properties, what I can use for values (string literals only, or can I use the values of other properties) and what property types I can create (Strings only, or ints, dates, floats, booleans, etc.) -- 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: [EMAIL PROTECTED]
[jira] Created: (MNG-1176) Add ejb bundle feature like in maven 1
Add ejb bundle feature like in maven 1 -- Key: MNG-1176 URL: http://jira.codehaus.org/browse/MNG-1176 Project: Maven 2 Type: New Feature Components: maven-ejb-plugin Versions: 2.0-beta-3 Environment: windows Reporter: Alexandre Vivien Fix For: 2.0-beta-4 It could be nice if we could include dependencies in the ejb jar produce by the ejb plugin. In fact, I think an ejb bundle feature like in Maven 1 will be useful. We could use the dependencies scope or whatever. (Perhaps it can be handy to add a new scope name "bundle" that could be use with ejb, war and ear plugin ) Thanks. Alexandre Vivien -- 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: [EMAIL PROTECTED]
[jira] Created: (MNG-1175) Investigate if MavenEmbedderLogger can be replaced by ...plugin.logging.Log
Investigate if MavenEmbedderLogger can be replaced by ...plugin.logging.Log --- Key: MNG-1175 URL: http://jira.codehaus.org/browse/MNG-1175 Project: Maven 2 Type: Task Components: maven-embedder Reporter: Eugene Kuleshov Priority: Critical Maven plugins are using its own logging framework ...plugin.logging.Log which is quite the same as MavenEmbedderLogger exposed by embedder. Please investigate if plugin logger should be used directly. That could be helpful if some of IDE plugins would use maven plugins directly (e.g. some utility classes from maven-eclipse-plugin) -- 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 21:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.211502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.211502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: optional dependencies was: [m2] POM inheritance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Joerg Hohwiller wrote: > Hello Brett, > > Brett Porter wrote: > >>>We've so far opted not to do this (basically an optional dependency) as >>>it can encourage poorly specified poms to stay that way. Basically by >>>saying this you are saying to those depending on you "you may need tis >>>jar at some point, but I can't tell you when". That's going to manifest >>>in a class cast exception. It really is a dependency, and instead we >>>allow the dependee to exclude the ones it knows it doesn't need. >>> >>>This is more tedious though, and I'm not currently certain whether it is >>>better to allow optinoal dependencies to aid in this. > > Well if we make the example (commons-logging) more abstract we can think > of a project providing a facade to some functionalitiy provided by > various exisiting implementations (e.g. could also be a facade for GUI > toolkits that allows Swing and SWT as backend). > In that case you would have a more abstract dependency where one can > choose. If that would be expressed in the POM as "dependency group" > there could also be a default choice if not explicitly choosen by the > aggregating project. > But actually the more I think about, it may be the best and simplest > approach to have a project just for the API and general code and a > subproject for each backend implementation defining the dependencies to > the real implementation. In the aggregating project you have a > dependency on the API and choose the implementation by another dependency. > So all I am saying is: you're right and maven(2) enforces structuring > your projects, which is good :) Actually I got totally lost in jarkarta-commons and othe projects before getting into maven. But now from the commons-logging point of view I want to raise this issue again: If JCL would have the API as top-level project and a sub-project for each bridge-implementation (log4j1.2, log4j1.3, jdk1.4-logger, logkit, avalon, etc.) this would cause: 1. ugly maintainence of the project 2. a jar for each bridge-implementation I think one could live with 1. Especially there is a general problem because of the dependency on log4j in two different version - this forces to splitt off in sub-projects if maven is used at all for the build. But for 2. there should be a way to build a jar in the top-level project that includes all code-output compiled in the sub-projects. Is that making sense for you or is this already targeted by m2? Do you see a better solution? BTW. I have seen this issue for aggregated javadocs in maven1 discussions a long time ago. Is that solved in m2? > [cut] Thanks Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDTDDXmPuec2Dcv/8RAhvNAJ9rHaZuCa+pduDOfZ5eE9sgG/mMIgCghJ5u BWBIw970xrSMXMnetOQmJFg= =EFwJ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 21:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.21.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 20:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.204500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1174) New Mojos for compiler and jar plugins to allow alternate jars
[ http://jira.codehaus.org/browse/MNG-1174?page=all ] Bob Allison updated MNG-1174: - Attachment: pom.xml The build section from a POM which shows how to use the new mojos > New Mojos for compiler and jar plugins to allow alternate jars > -- > > Key: MNG-1174 > URL: http://jira.codehaus.org/browse/MNG-1174 > Project: Maven 2 > Type: Improvement > Versions: 2.0-beta-3 > Environment: Linux using JDK 1.5.0_01 > Reporter: Bob Allison > Fix For: 2.0-beta-4 > Attachments: AltCompilerMojo.java, AltJarMojo.java, pom.xml > > > Add mojos so that mock objects and other affiliated source roots can be > compiled and packaged in the same project -- 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: [EMAIL PROTECTED]
[jira] Updated: (MNG-1174) New Mojos for compiler and jar plugins to allow alternate jars
[ http://jira.codehaus.org/browse/MNG-1174?page=all ] Bob Allison updated MNG-1174: - Attachment: AltJarMojo.java AltJarMojo is identical to JarMojo except: -- Goal changed to "altjar" -- Parameter "outputDirectory" renamed to "sourceDirectory" , made editable, and given no default > New Mojos for compiler and jar plugins to allow alternate jars > -- > > Key: MNG-1174 > URL: http://jira.codehaus.org/browse/MNG-1174 > Project: Maven 2 > Type: Improvement > Versions: 2.0-beta-3 > Environment: Linux using JDK 1.5.0_01 > Reporter: Bob Allison > Fix For: 2.0-beta-4 > Attachments: AltCompilerMojo.java, AltJarMojo.java > > > Add mojos so that mock objects and other affiliated source roots can be > compiled and packaged in the same project -- 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: [EMAIL PROTECTED]
[jira] Updated: (MNG-1174) New Mojos for compiler and jar plugins to allow alternate jars
[ http://jira.codehaus.org/browse/MNG-1174?page=all ] Bob Allison updated MNG-1174: - Attachment: AltCompilerMojo.java The AltCompilerMojo is identical to CompilerMojo except: -- Goal changed to "altcompile" -- A parameter "suffix" added to allow an easy definition of the file endings to compile -- Parameter "compileSourceRoots" renamed to "sources" and made editable -- Parameter "outputDirectory" made editable > New Mojos for compiler and jar plugins to allow alternate jars > -- > > Key: MNG-1174 > URL: http://jira.codehaus.org/browse/MNG-1174 > Project: Maven 2 > Type: Improvement > Versions: 2.0-beta-3 > Environment: Linux using JDK 1.5.0_01 > Reporter: Bob Allison > Fix For: 2.0-beta-4 > Attachments: AltCompilerMojo.java > > > Add mojos so that mock objects and other affiliated source roots can be > compiled and packaged in the same project -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 20:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.201500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1174) New Mojos for compiler and jar plugins to allow alternate jars
New Mojos for compiler and jar plugins to allow alternate jars -- Key: MNG-1174 URL: http://jira.codehaus.org/browse/MNG-1174 Project: Maven 2 Type: Improvement Versions: 2.0-beta-3 Environment: Linux using JDK 1.5.0_01 Reporter: Bob Allison Fix For: 2.0-beta-4 Add mojos so that mock objects and other affiliated source roots can be compiled and packaged in the same project -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 20:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.20.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-77) Hibernate 2.1.8 pom dependency is empty
[ http://jira.codehaus.org/browse/MEV-77?page=all ] Carlos Sanchez closed MEV-77: - Assign To: Carlos Sanchez Resolution: Incomplete The pom needs to be provided. We don't have time or resources to create it. > Hibernate 2.1.8 pom dependency is empty > --- > > Key: MEV-77 > URL: http://jira.codehaus.org/browse/MEV-77 > Project: Maven Evangelism > Type: Bug > Reporter: Edward Yakop > Assignee: Carlos Sanchez > > > Hibernate 2.1.8 contains no dependency: > > 4.0.0 > hibernate > hibernate > 2.1.8 > -- 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 19:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.194500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.194500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1173) transitive dependencies with system scope are treated as normal scope
transitive dependencies with system scope are treated as normal scope - Key: MNG-1173 URL: http://jira.codehaus.org/browse/MNG-1173 Project: Maven 2 Type: Bug Versions: 2.0-beta-4 Environment: linux, sun jdk 1.5 Reporter: Matthew Pocock Module A has a system dependency on tools.jar - this works out fine. The module is built and artifact(s) deployed. Module B has A as a dependency. During transitive dependency resolution, tools.jar must be resolved. However, it appears that m2 is attempting to resolve it as a non-system dependency. -- 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: [EMAIL PROTECTED]
[jira] Commented: (MNG-806) tools.jar needs to be supported as a normal dependency
[ http://jira.codehaus.org/browse/MNG-806?page=comments#action_48361 ] Matthew Pocock commented on MNG-806: This is great. Adding dependencies to the profiles section would work arround the issue with osx, and possibly be generally useful, particularly if there was a library of profiles & dependencies for different platforms. > tools.jar needs to be supported as a normal dependency > -- > > Key: MNG-806 > URL: http://jira.codehaus.org/browse/MNG-806 > Project: Maven 2 > Type: Improvement > Environment: sun sdk > Reporter: Matthew Pocock > Assignee: John Casey > Fix For: 2.0-beta-1 > > > Sun SDKs have a tools.jar that provides API for extending the Sun java tools. > This includes APT and Javadoc. There is no mechanism in maven for loading in > tools.jar as a dependency. It can be added to the classpath before maven is > launched, or manually loaded into the local repository. However, neither of > these solutions are very satisfactory. > Could we have some smarts in the dependency loading that understands a > magical jdk groupId that resolves to the current JDK being used for > compilation? This would let JDK-dependent stuff be linked in. In the case of > tools.jar, the dependency snippet would look something like this: > > sun.jdk > tools > jar > provided > -- 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: [EMAIL PROTECTED]
[jira] Commented: (MPCHANGELOG-69) Changelog returning 0 entries on Windows with CVS (not CVSNT)
[ http://jira.codehaus.org/browse/MPCHANGELOG-69?page=comments#action_48359 ] Laird Nelson commented on MPCHANGELOG-69: - Actually, the more I look at this bug the more weird it is. This has nothing to do with CVSNT as far as I can tell. The CvsChangeLogGenerator.java file simply quotes arguments to cvs log -d if you're on the Windows platform. But recall that ostensibly the Maven CVS infrastructure (at least on Maven 1.1b2) is all Netbeans-Java-based, so the type of client you would otherwise run is wholly irrelevant. > Changelog returning 0 entries on Windows with CVS (not CVSNT) > - > > Key: MPCHANGELOG-69 > URL: http://jira.codehaus.org/browse/MPCHANGELOG-69 > Project: maven-changelog-plugin > Type: Bug > Versions: 1.8.2 > Environment: Windows XP > maven 1.0.2 > GNU cvs for DOS > Cygwin cvs > Reporter: Daniel Beland > Priority: Critical > Fix For: 1.9 > > > A change as been made for users using CVSNT to add quotes aroud dates on > windows. (MPCHANGELOG-47) > However this add a bug for all other users using either cygwin's CVS or GNU > cvs for DOS since it looks at the os.name value we cannot work around it. > I think it should be added as a plugin property to set if they are using > CVSNT to get quotes around the dates. -- 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: [EMAIL PROTECTED]
[jira] Commented: (MPCHANGELOG-69) Changelog returning 0 entries on Windows with CVS (not CVSNT)
[ http://jira.codehaus.org/browse/MPCHANGELOG-69?page=comments#action_48357
]
Laird Nelson commented on MPCHANGELOG-69:
-
I found a hideous, hideous workaround for this, which, like everything
involving Jelly, relies on some black magic that I don't understand.
Put this or something similar in your maven.xml if you have an environment like
the original poster (boy, I hope this is formatted right by JIRA):
${systemScope.setProperty('oldOSName', oldName)}
${systemScope.setProperty('os.name', 'bogus')}
${systemScope.setProperty('os.name', oldName)}
> Changelog returning 0 entries on Windows with CVS (not CVSNT)
> -
>
> Key: MPCHANGELOG-69
> URL: http://jira.codehaus.org/browse/MPCHANGELOG-69
> Project: maven-changelog-plugin
> Type: Bug
> Versions: 1.8.2
> Environment: Windows XP
> maven 1.0.2
> GNU cvs for DOS
> Cygwin cvs
> Reporter: Daniel Beland
> Priority: Critical
> Fix For: 1.9
>
>
> A change as been made for users using CVSNT to add quotes aroud dates on
> windows. (MPCHANGELOG-47)
> However this add a bug for all other users using either cygwin's CVS or GNU
> cvs for DOS since it looks at the os.name value we cannot work around it.
> I think it should be added as a plugin property to set if they are using
> CVSNT to get quotes around the dates.
--
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: [EMAIL PROTECTED]
[jira] Created: (MNG-1172) class loading / xerces
class loading / xerces -- Key: MNG-1172 URL: http://jira.codehaus.org/browse/MNG-1172 Project: Maven 2 Type: Bug Components: maven-surefire-plugin Versions: 2.0-beta-3 Environment: maven-2-beta-3, jdk 5.0.0_4, winXP SP2 Reporter: Dirk Sturzebecher I have two tests in one test class. Both read a csv file and check for certain attributes. Both tests run ok outside maven. In maven the first test fails, the second (ordered by execution sequence) is ok. That is, if I do understand the output correctly. The output in surefire-reports is: --- Battery: de.dst.money.stock.StockPluginTest --- testDoImport01(de.dst.money.stock.StockPluginTest) [ stdout ] --- [ stderr ] --- [ stacktrace ] --- javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:145) at de.dst.money.framework.model.persistence.xml.XMLUtil.loadDocument(XMLUtil.java:64) at de.dst.money.framework.model.persistence.xml.XMLPersistenceManager.loadDocument(XMLPersistenceManager.java:82) at de.dst.money.stock.StockPlugin.load(StockPlugin.java:97) at de.dst.money.stock.StockPlugin.getModel(StockPlugin.java:87) at de.dst.money.stock.StockPluginTest.testDoImport01(StockPluginTest.java:35) 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 junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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.battery.JUnitBattery.executeJUnit(JUnitBattery.java:246) at org.codehaus.surefire.battery.JUnitBattery.execute(JUnitBattery.java:220) at org.codehaus.surefire.Surefire.executeBattery(Surefire.java:203) at org.codehaus.surefire.Surefire.run(Surefire.java:152) at org.codehaus.surefire.Surefire.run(Surefire.java:76) 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:229) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:508) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:494) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) at org.apache.maven.cli.MavenCli.main(MavenCli.java:247) 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.c
[jira] Updated: (MNG-1096) Error handling needs improvement
[ http://jira.codehaus.org/browse/MNG-1096?page=all ] John Casey updated MNG-1096: Remaining Estimate: 1 hour Original Estimate: 3600 add error diagnoser for report exceptions, and see where we stand > Error handling needs improvement > > > Key: MNG-1096 > URL: http://jira.codehaus.org/browse/MNG-1096 > Project: Maven 2 > Type: Improvement > Components: maven-site-plugin > Versions: 2.0-beta-2 > Reporter: David Jackman > Assignee: John Casey > Fix For: 2.0-beta-4 > > Original Estimate: 1 hour > Remaining: 1 hour > > I'm actually not sure if this is specific for the site plugin or something > more general for Maven 2 error reporting. > Here was the situation that brought this about: I was trying to build the > site for the maven-site project. At the time, there were two files checked > into src/site/resources/images that had the same name (h3.gif and h3.jpg). > (Note: this problem has since been cleared up.) When executing the site:site > goal, I got the following back: > ... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Diagnosis: Error during report generation > [INFO] > > After adding the -X option, I get this exception information: > [DEBUG] Trace: > org.apache.maven.plugin.MojoExecutionException: Error during report generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:422) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:517) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:247) > 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:324) > 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: org.apache.maven.reporting.MavenReportException: Some files are > duplicates in the site directory or in the generated-site directory. > Review the following files for the "English" version: > images\h3 > resources\images\h3.gif > resources\images\h3.jpg > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:312) > ... 16 more > It seems like something is throwing an exception with a helpful message, but > it's caught by DoxiaMojo, which then throws a MojoExecutionException that > chains the original exception. Maven is just reporting the > MojoExecutionException message, which doesn't contain the helpful information. > So, to fix this problem, either the DoxiaMojo code should be fixed so the > message in the MojoExecutionException includes the message from the exception > it caught, or the core Maven error reporting code should be fixed so it > includes messages from exceptions chained with the MojoExecutionException. -- 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: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Tue Oct 11 18:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051011.18.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051011.18.txt
[jira] Commented: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_48348 ] Ørjan Austvold commented on MNG-678: A new version of jsch has just been released (0.1.23). Changes since version 0.1.22: - bugfix: there is a freeze problem at fails on key-exchanging. FIXED. - bugfix: race-condition forcefully disconnects session in closing channels. FIXED. Could the "freeze" bugfix be releated to the scp knowhosts tests failing? Here's what was reported on sch-mailinglist: Hi, +-From: Michal Belicek <[EMAIL PROTECTED]> -- |_Date: Fri, 07 Oct 2005 14:24:11 +0200 __ | |I have found one bug in jsch-0.1.22. The thing is that, when calling |session.connect() and the call checkHost(host, kex) inside of the |connect(...) method in Session.java throws JSchException, then the |program will freeze on line 432: write(packet) because of infinite loop. |The fix is following: |diff Session.java Session_.java |426a427 |>> in_kex = false; > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0.1 > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 17:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.174500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.174500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1171) I wish there was a recommended way of naming plugins
I wish there was a recommended way of naming plugins Key: MNG-1171 URL: http://jira.codehaus.org/browse/MNG-1171 Project: Maven 2 Type: Wish Reporter: Brian Bonner Priority: Minor What *is* the preferred article id naming for Maven Plugins? I've seen it as -maven-plugin and maven--plugin It would help me (and other users) avoid silly mistakes if there was a recommended pattern. I ran into this with the xmlbeans plugin. The example had it named as maven-xmlbeans-plugin. After looking at other plugins, it looks like this is the "standard". It seems like the name should either go at the beginning or end (i.e. xmlbeans-maven-plugin, or maven-plugin-xmlbeans). I'm wondering if there is really a rhyme or reason to this. It would make it easier to write poms if there was some sort of recommended standard. -- 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 17:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.173000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.173000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1167) fail at end skips the wrong projects
[ http://jira.codehaus.org/browse/MNG-1167?page=all ] Brett Porter closed MNG-1167: - Assign To: Brett Porter Resolution: Fixed > fail at end skips the wrong projects > > > Key: MNG-1167 > URL: http://jira.codehaus.org/browse/MNG-1167 > Project: Maven 2 > Type: Bug > Components: maven-core > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0-beta-4 > > > eg: m-projecthelp-p is failing > it skips the parent (due to modules, I presume), and then skips > m-plugin-plugin (presumably because the parent depends on that). That seems > the wrong way around. -- 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: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-269) MyFaces JSF-API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-269?page=comments#action_48341 ] Carlos Sanchez commented on MAVENUPLOAD-269: It's the responsability of the apache project to put jars there when making a release. If you are an apache committer you can contact with me to get more help (with your apache email). > MyFaces JSF-API > --- > > Key: MAVENUPLOAD-269 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-269 > Project: maven-upload-requests > Type: Task > Reporter: Matthias Weßendorf > Assignee: Carlos Sanchez > > > incubator.apache.org/myfaces/ > http://incubator.apache.org/myfaces/community/contributors.html > MyFaces is an open source Impl of JavaServer Faces Spec. (JSR #127). > Since some projects depend on JSF-API, I guess there is interesst > in hosting MyFaces' JSF-API Impl on ibiblio > Please upload! DO IT NOW! > ;-) -- 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: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Tue Oct 11 17:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051011.17.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.17.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Tue Oct 11 17:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051011.17.txt
Re: [Maven Wiki] Update of "MavenDiscussionEclipseIntegration" by JeanMichelGarnier
the page is intended to be in spanish or it should be in english? If it should
be in spanish i can fix some typos.
On Tuesday 11 October 2005 13:12, Apache Wiki wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Maven Wiki" for
> change notification.
>
> The following page has been changed by JeanMichelGarnier:
> http://wiki.apache.org/maven/MavenDiscussionEclipseIntegration
>
> New page:
> La pesadilla del classpath de Java ...
>
> Por defecto, eclipse añade los jars del
> target/{pom.artefactId}/WEB-INF/lib an el build path ...
>
> === SNAPSHOT ===
>
> Sin snapshot:
>
> Hay un articulo en la web de Eclipse sobre la integration de WST con maven:
> http://www.eclipse.org/webtools/jst/components/j2ee/scenarios/MavenEclipseI
>ntegration.html
>
> Debug
>
> Fragmento de http://maven.apache.org/reference/plugins/eclipse/:
> Artifact Sources:
> Frequently you will want to include for compiled jars the source .java
> files to help with debugging. The plugin will check if the file specified
> is located in MAVEN_REPO/${groupId}/src/ directory and ending in
> maven.eclipse.src.extension exists and will add it as a source attachment.
> Using default values the dependency
> MAVEN_REPO/eclipse/jars/eclipse-ui-3.0.0.jar will be mapped to
> MAVEN_REPO/eclipse/src/eclipse-ui-3.0.0.zip
>
> PodrÃamos subir los zips de codigo fuente en nuestro
> http://www.opentrends.net/repository/
>
> Para los servicios de openFrame, podrÃamos la propiedad
> http://maven.apache.org/reference/plugins/eclipse/
> y añadir una propriedad Eclipse a cada dependency
>
> group
> artifact
> version
>
> true
>
>
>
> --> generar .wtpmodules
> **
> Supongo q habÃas "hacked" el classpath.jelly del maven eclipse plugin para
> tu fichero /openFrame-samples-Petstore/templates/classpath.jelly. Para mi,
> Jelly no un language, es otro frankensteinXML ;-) pero entiendo bastante
> para genera el .wtpmodules
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Buenos Aires, Argentina 22°C with winds at 22 km/h NNE
pgpJfjeiJrvPQ.pgp
Description: PGP signature
[jira] Closed: (MNG-1170) Reports should be alphabetized
[ http://jira.codehaus.org/browse/MNG-1170?page=all ]
Brett Porter closed MNG-1170:
-
Assign To: Brett Porter
Resolution: Fixed
Fix Version: 2.0-beta-4
nicely timed, I just implemented it
> Reports should be alphabetized
> --
>
> Key: MNG-1170
> URL: http://jira.codehaus.org/browse/MNG-1170
> Project: Maven 2
> Type: Improvement
> Components: maven-site-plugin
> Versions: 2.0-beta-3
> Reporter: Matthew Beermann
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-4
>
>
> The ${reports} section of a site ought to have its reports alphabetized, at
> least by a configuration parameter and probably by default. The same goes for
> links to super- and sub-projects, if that ever happens.
--
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: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-269) MyFaces JSF-API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-269?page=comments#action_48339 ] Dave Brondsema commented on MAVENUPLOAD-269: So who should we contact to do so? MyFaces and other projects (e.g. geronimo has a javax.transaction api) might not know how to deploy to that repository. > MyFaces JSF-API > --- > > Key: MAVENUPLOAD-269 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-269 > Project: maven-upload-requests > Type: Task > Reporter: Matthias Weßendorf > Assignee: Carlos Sanchez > > > incubator.apache.org/myfaces/ > http://incubator.apache.org/myfaces/community/contributors.html > MyFaces is an open source Impl of JavaServer Faces Spec. (JSR #127). > Since some projects depend on JSF-API, I guess there is interesst > in hosting MyFaces' JSF-API Impl on ibiblio > Please upload! DO IT NOW! > ;-) -- 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: [EMAIL PROTECTED]
[jira] Created: (MNG-1170) Reports should be alphabetized
Reports should be alphabetized
--
Key: MNG-1170
URL: http://jira.codehaus.org/browse/MNG-1170
Project: Maven 2
Type: Improvement
Components: maven-site-plugin
Versions: 2.0-beta-3
Reporter: Matthew Beermann
Priority: Minor
The ${reports} section of a site ought to have its reports alphabetized, at
least by a configuration parameter and probably by default. The same goes for
links to super- and sub-projects, if that ever happens.
--
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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 16:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.164500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.163000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Tue Oct 11 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051011.163000.txt
[jira] Updated: (MNG-1132) Dependency outputdirectory ignored when unpack is specified
[ http://jira.codehaus.org/browse/MNG-1132?page=all ]
Jerome Lacoste updated MNG-1132:
Attachment: support_output_dir_with_unpack.diff
Patch had rotted. Impressive for a one liner :)
> Dependency outputdirectory ignored when unpack is specified
> ---
>
> Key: MNG-1132
> URL: http://jira.codehaus.org/browse/MNG-1132
> Project: Maven 2
> Type: Bug
> Components: maven-assembly-plugin
> Versions: 2.0-beta-3
> Reporter: Jerome Lacoste
> Priority: Critical
> Fix For: 2.0-beta-4
> Attachments: support_output_dir_with_unpack.diff,
> support_output_dir_with_unpack.diff
>
>
> [I hope this can be looked into before official 2.0 otherwise that could
> create issues with regard to breaking existing code. Making critical for this
> reason]
> I am attempting to unpack in a particular place below the working directory.
> Let's say I do something like
>
> tomcat/webapp/
>
> org.cb.project:webapp
>
> true
> runtime
>
> The code in
> maven-plugins/maven-assembly-plugin/src/main/java/org/apache/maven/plugin/assembly/AssemblyMojo.java
> if ( dependencySet.isUnpack() )
> {
> // TODO: something like zipfileset in plexus-archiver
> //archiver.addJar( )
> File tempLocation = new File( workDirectory,
> name.substring( 0, name.length() - 4 ) );
> boolean process = false;
> if ( !tempLocation.exists() )
> {
> tempLocation.mkdirs();
> process = true;
> }
> else if ( artifact.getFile().lastModified() >
> tempLocation.lastModified() )
> {
> process = true;
> }
> if ( process )
> {
> try
> {
> unpack( artifact.getFile(), tempLocation );
> }
> catch ( NoSuchArchiverException e )
> {
> throw new MojoExecutionException(
> "Unable to obtain unarchiver for file '"
> + artifact.getFile() + "'" );
> }
> }
> archiver.addDirectory( tempLocation, null,
>(String[])
> getDefaultExcludes().toArray( EMPTY_STRING_ARRAY ) );
> }
> else
> {
> archiver.addFile( artifact.getFile(), output +
> evaluateFileNameMapping(
> dependencySet.getOutputFileNameMapping(), artifact ) );
> }
> This treats files to unpack and pack differently.
> I believe
> File tempLocation = new File( workDirectory,
> name.substring( 0, name.length() - 4 ) );
> should be replaced by something like:
> File tempOutputLocation = new File( workDirectory,
> output);
> File tempLocation = new File( tempOutputLocation,
> name.substring( 0, name.length() - 4 ) );
> That way both code paths will end up treating the files similarly. If I
> change from unpack to pack, my file end up in the same place. That sounds
> logical to me.
> Someone can still use / if he doesn't want
> the files to be some levels below the work directory.
--
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: [EMAIL PROTECTED]
[jira] Commented: (MNG-441) surefire plugin needs to be able to fork tests
[ http://jira.codehaus.org/browse/MNG-441?page=comments#action_48335 ] Andy Glick commented on MNG-441: Dave - If you take a look at Brett's remarks of Sep 22, 2005, you'll notice that he mentions jvmargs as a required addition to the supported surefire argument list. In a complete surefire/surefire plugin implementation you would add any "ea" arguments to the jvmargs and you wouldn't have to use MAVEN_OPTS. I actually do sympathize with your desire to see this completed, as it was my desire to see it completed that lead me to attempt to add the forking behavior. :-) There is still some unfinished business WRT forking, but we are going to get to jvmargs, please bear with us. > surefire plugin needs to be able to fork tests > -- > > Key: MNG-441 > URL: http://jira.codehaus.org/browse/MNG-441 > Project: Maven 2 > Type: Improvement > Components: maven-surefire-plugin > Reporter: Brett Porter > Fix For: 2.0-beta-4 > Attachments: SurefirePlugin.java, pom.xml > > > they can leak memory, so a "fork once for all" option would be good. -- 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: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 16:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.161500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt
[ http://jira.codehaus.org/browse/MPCHANGELOG-38?page=comments#action_48334 ] Laird Nelson commented on MPCHANGELOG-38: - I am seeing this issue on a proper checkout, having done all my homework. I am running Maven 1.1b2. The cvs server in this case is cvsnt; the client is obviously the embedded netbeans client. Running a regular cvs log command from the commandline works fine. Is there any further information on this closed-but-not-solved bug (the resolution remains "incomplete")? > changelog does not work with cvsnt > -- > > Key: MPCHANGELOG-38 > URL: http://jira.codehaus.org/browse/MPCHANGELOG-38 > Project: maven-changelog-plugin > Type: Bug > Versions: 1.5 > Environment: CVSNT 2.0.26 > Reporter: Archimedes Trajano > Attachments: output > > > C:\Projects\pensions>maven maven-changelog-plugin:report > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT > build:start: > maven-changelog-plugin:report: > [echo] Generating the changelog report > Server is not supporting gzip-file-contents request > ChangeLog found: 0 entries > BUILD SUCCESSFUL > Total time: 5 seconds > Finished at: Tue May 04 19:27:12 CEST 2004 -- 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: [EMAIL PROTECTED]
[Maven Wiki] Update of "MavenDiscussionEclipseIntegration" by JeanMichelGarnier
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Maven Wiki" for change
notification.
The following page has been changed by JeanMichelGarnier:
http://wiki.apache.org/maven/MavenDiscussionEclipseIntegration
New page:
La pesadilla del classpath de Java ...
Por defecto, eclipse añade los jars del target/{pom.artefactId}/WEB-INF/lib an
el build path ...
=== SNAPSHOT ===
Sin snapshot:
Hay un articulo en la web de Eclipse sobre la integration de WST con maven:
http://www.eclipse.org/webtools/jst/components/j2ee/scenarios/MavenEclipseIntegration.html
Debug
Fragmento de http://maven.apache.org/reference/plugins/eclipse/:
Artifact Sources:
Frequently you will want to include for compiled jars the source .java files to
help with debugging.
The plugin will check if the file specified is located in
MAVEN_REPO/${groupId}/src/ directory and ending in maven.eclipse.src.extension
exists and will add it as a source attachment. Using default values the
dependency MAVEN_REPO/eclipse/jars/eclipse-ui-3.0.0.jar will be mapped to
MAVEN_REPO/eclipse/src/eclipse-ui-3.0.0.zip
PodrÃamos subir los zips de codigo fuente en nuestro
http://www.opentrends.net/repository/
Para los servicios de openFrame, podrÃamos la propiedad
http://maven.apache.org/reference/plugins/eclipse/
y añadir una propriedad Eclipse a cada dependency
group
artifact
version
true
--> generar .wtpmodules
**
Supongo q habÃas "hacked" el classpath.jelly del maven eclipse plugin para tu
fichero /openFrame-samples-Petstore/templates/classpath.jelly.
Para mi, Jelly no un language, es otro frankensteinXML ;-) pero entiendo
bastante para genera el .wtpmodules
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Tue Oct 11 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.16.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Tue Oct 11 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051011.16.txt
[maven2 build - FAILED - update] Tue Oct 11 15:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.154501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-945) Handle project that contains no source
[ http://jira.codehaus.org/browse/MNG-945?page=all ] Brett Porter closed MNG-945: Assign To: Brett Porter Resolution: Fixed > Handle project that contains no source > -- > > Key: MNG-945 > URL: http://jira.codehaus.org/browse/MNG-945 > Project: Maven 2 > Type: Bug > Components: maven-core, maven-site-plugin > Versions: 2.0-beta-1 > Environment: trunk (290857) > Reporter: Vincent Siveton > Assignee: Brett Porter > Fix For: 2.0-beta-4 > > > In a specific case, site plugin throws IllegalArgumentException if no source > was defined. > My project is a *main* parent project with the following structure: > +- test/ >+- pom.xml > In this case, the following exception is thrown when site:site is call. > java.lang.IllegalStateException: basedir C:\temp\test\src\main\java does not > exist > at > org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:539) > at > org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1343) > at > org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1309) > at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1281) > at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1275) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.getFilesToProcess(CheckstyleReport.java:387) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:244) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at > org.apache.maven.doxia.DoxiaMojo.generateReportsPages(DoxiaMojo.java:813) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:332) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:367) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:502) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:465) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:136) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) > 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:324) > 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) > In my opinion, if no source was defined, I don't need a report. > The proposed that the patch applies this rule but the generated site has > project report link in the nav bar (so checkstyle.html is empty and > apidocs\index.html doesnt exist) > Thoughts? -- 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: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-353) scheduded build is skipped with starteam provider
scheduded build is skipped with starteam provider -- Key: CONTINUUM-353 URL: http://jira.codehaus.org/browse/CONTINUUM-353 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0-beta-1 Environment: xp Reporter: Dan Tran Fix For: 1.0-beta-2 Even with changes in starteam, scheduled build does not recognize changes and skip the build. It could be starteam provider is problem, but command line testing looks ok. Btw, how come i dont see any log coming from starteam provider? continuum seeems to swallow them -- 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
[continuum build - FAILED - update] Tue Oct 11 15:30:02 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051011.153002.txt
[maven2 build - FAILED - update] Tue Oct 11 15:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051011.151500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-945) Handle project that contains no source
[ http://jira.codehaus.org/browse/MNG-945?page=comments#action_48332 ] Brett Porter commented on MNG-945: -- I liked Edwin's idea, however on implementing it I realised that each is done individually with the reports list pre-rendered - so when a report fails, it is already linked on previously successful reports. I will instead investigate adding: boolean canGenerateReport(); to MavenReport > Handle project that contains no source > -- > > Key: MNG-945 > URL: http://jira.codehaus.org/browse/MNG-945 > Project: Maven 2 > Type: Bug > Components: maven-core, maven-site-plugin > Versions: 2.0-beta-1 > Environment: trunk (290857) > Reporter: Vincent Siveton > Fix For: 2.0-beta-4 > > > In a specific case, site plugin throws IllegalArgumentException if no source > was defined. > My project is a *main* parent project with the following structure: > +- test/ >+- pom.xml > In this case, the following exception is thrown when site:site is call. > java.lang.IllegalStateException: basedir C:\temp\test\src\main\java does not > exist > at > org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:539) > at > org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1343) > at > org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1309) > at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1281) > at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1275) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.getFilesToProcess(CheckstyleReport.java:387) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:244) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at > org.apache.maven.doxia.DoxiaMojo.generateReportsPages(DoxiaMojo.java:813) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:332) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:367) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:502) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:465) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:136) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) > 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:324) > 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) > In my opinion, if no source was defined, I don't need a report. > The proposed that the patch applies this rule but the generated site has > project report link in the nav bar (so checkstyle.html is empty and > apidocs\index.html doesnt exist) > Thoughts? -- 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: [EMAIL PROTECTED]
