[jira] Commented: (MAVENUPLOAD-1874) Winstone 0.9.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118977 ] Grzegorz Slowikowski commented on MAVENUPLOAD-1874: --- Hi Carlos I don't understand what's the problem. This artifact is not build by Maven so I created bundles as described here: http://maven.apache.org/guides/mini/guide-central-repository-upload.html "If you are not using maven as your build system but want something uploaded to the Central Repository then you just need to make a JAR (using the jar executable, not zip , pkzip or equivalent) with the following content: pom.xml foo-1.0.jar (or whatever artifact is referred to in the pom.xml) foo-1.0-sources.jar (optional, jar containing java sources) foo-1.0-javadoc.jar (optional, jar containing javadocs)" What have I done wrong? I'm not a developer of this project so don't want to add full pom.xml to build it and upload my build jars (binary and sources) instead of the oryginal one. > Winstone 0.9.9 > -- > > Key: MAVENUPLOAD-1874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1874 > Project: maven-upload-requests > Issue Type: Task >Reporter: Grzegorz Slowikowski > Attachments: winstone-099-bundle.jar, winstone-lite-099-bundle.jar > > > Upload bundle based on 0.9.6 version > (http://jira.codehaus.org/browse/MAVENUPLOAD-1432) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1874) Winstone 0.9.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118979 ] Carlos Sanchez commented on MAVENUPLOAD-1874: - if you open the attached files, you'll see there's no jars inside > Winstone 0.9.9 > -- > > Key: MAVENUPLOAD-1874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1874 > Project: maven-upload-requests > Issue Type: Task >Reporter: Grzegorz Slowikowski > Attachments: winstone-099-bundle.jar, winstone-lite-099-bundle.jar > > > Upload bundle based on 0.9.6 version > (http://jira.codehaus.org/browse/MAVENUPLOAD-1432) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1849) Add SwiXML 1.6.151
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118980 ] Carlos Sanchez commented on MAVENUPLOAD-1849: - anybody can request an upload if the original project does not want to > Add SwiXML 1.6.151 > -- > > Key: MAVENUPLOAD-1849 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1849 > Project: maven-upload-requests > Issue Type: Task >Reporter: Steve Taylor >Assignee: Carlos Sanchez > > The file in "Bundle URL" isn't a maven bundle per se, but the jar file can be > found in the /build directory of the project and the pom is in the root > directory. The jar just needs to be renamed according to convention. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1874) Winstone 0.9.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118981 ] Grzegorz Slowikowski commented on MAVENUPLOAD-1874: --- I download and open them and there are jars inside. I'm on Windows > Winstone 0.9.9 > -- > > Key: MAVENUPLOAD-1874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1874 > Project: maven-upload-requests > Issue Type: Task >Reporter: Grzegorz Slowikowski > Attachments: winstone-099-bundle.jar, winstone-lite-099-bundle.jar > > > Upload bundle based on 0.9.6 version > (http://jira.codehaus.org/browse/MAVENUPLOAD-1432) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-103) Can't deploy to a file: repository
[ http://jira.codehaus.org/browse/MANTTASKS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118982 ] Olov Andersson commented on MANTTASKS-103: -- Running 'mvn deploy' with a distributionManagement section works, although that's not really the same scenario since I only had an existing jar to deploy. I've tested 'mvn deploy:deploy-file' also which is more similar. That works as well. It's only when running the ant task I run into this problem. Here's the stack trace: C:\Temp\maven-ant-tasks-jiratestcase\build.xml:5: Error deploying artifact 'org.dummy:dummy:jar': Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata at org.apache.maven.artifact.ant.DeployTask.doExecute(DeployTask.java:132) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:658) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) at org.apache.tools.ant.Project.executeTarget(Project.java:1298) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1181) at org.apache.tools.ant.Main.runBuild(Main.java:698) at org.apache.tools.ant.Main.startAnt(Main.java:199) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102) at org.apache.maven.artifact.ant.DeployTask.doExecute(DeployTask.java:111) ... 18 more Caused by: org.apache.maven.artifact.repository.metadata.RepositoryMetadataDeploymentException: Error installing metadata: Error updating group repository metadata at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:432) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) ... 19 more Caused by: org.apache.maven.artifact.repository.metadata.RepositoryMetadataStoreException: Error updating group repository metadata at org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:72) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:428) ... 20 more Caused by: java.io.FileNotFoundException: C:\Documents and Settings\oland\.m2\repository\org\dummy\dummy\maven-metadata-file:C:\.xml (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:131) at hidden.org.codehaus.plexus.util.xml.XmlStreamWriter.(XmlStreamWriter.java:61) at hidden.org.codehaus.plexus.util.WriterFactory.newXmlWriter(WriterFactory.java:112) at org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.updateRepositoryMetadata(AbstractRepositoryMetadata.java:134) at org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:68) ... 21 more --- Nested Exception --- org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102) at org.apache.maven.artifact.ant.DeployTask.doExecute(DeployTask.java:111) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:658) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorIm
[jira] Commented: (MJAR-82) Class-Path manifest entry should support maven repository layout
[ http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118978 ] Olivier Lamy commented on MJAR-82: -- have a look at the it MJAR-82 in the jar plugin (the directory of the jar is used). > Class-Path manifest entry should support maven repository layout > > > Key: MJAR-82 > URL: http://jira.codehaus.org/browse/MJAR-82 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Geoffrey De Smet >Assignee: Olivier Lamy > Fix For: 2.2 > > > The assembly plugin supports outputting all dependencies in a repository > layout. > The jar plugin should support adding the classpath manifest entry based on > the repository layout. > The combination of the two makes it easy to write a script to run the app: > "java -jar org/domain/project/projectApp.jar" at the base of the repository > layout. > Example of a Class-Path entry: > ClassPath: > org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar > Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in > " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1846) please upload YUIcompressor to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118985 ] nicolas de loof commented on MAVENUPLOAD-1846: -- The bundle has been updated with "com.yahoo.platform.yui" as groupId. I've contacted Jerome Lacoste (yuicompressor developer) but he doesn't seem to have lot's of interest for maven, so I've created a synched repo at people.apache.org/x1/home/nicolas/rsync-to-central Here is the required script : #!/bin/sh CONTACTS="Nicolas De Loof <[EMAIL PROTECTED]>" MODE=rsync_ssh [EMAIL PROTECTED]:/x1/home/nicolas/rsync-to-central GROUP_DIR=com/yahoo/platform/yui/ > please upload YUIcompressor to central > -- > > Key: MAVENUPLOAD-1846 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1846 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof > > Yahoo UI Javascript compressor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3118) Test-classes should come before classes in the classpath
[ http://jira.codehaus.org/browse/MNG-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118993 ] Ceki Gulcu commented on MNG-3118: - In my 20 months experience with Maven, the test-classes always came before "classes". This is a feature that I heavily rely on. Could you please kindly document this behavior as part of the Maven/Surefire contract, so that the re-ordering problem does not reoccur? Many thanks in advance, > Test-classes should come before classes in the classpath > > > Key: MNG-3118 > URL: http://jira.codehaus.org/browse/MNG-3118 > Project: Maven 2 > Issue Type: Improvement > Components: General >Affects Versions: 2.0.7 >Reporter: Paul Gier > Fix For: 2.0.8, 2.1-alpha-1 > > Attachments: MNG-3118-maven-project-r558713.patch > > > Currently maven-project creates the test classpath in the order: classes, > tests-classes, dependencies. > It would be better if test-classes came first because sometimes it is useful > for a test class to replace a main class during testing. The opposite case > is not normally true (i.e. one would not want to override a test class with > one of the main classes). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2220) ${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer recognized
[ http://jira.codehaus.org/browse/MNG-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118999 ] Venelin Mitov commented on MNG-2220: Hello All, I used the attached buglet.zip project to reproduce the problem on versions 2.0.5, 2.0.7 and 2.0.8 of maven. Here is the output I got when executing mvn clean test. $ /cygdrive/c/maven/maven-2.0.8/bin/mvn clean test [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - maven:buglet:jar:01.01-SNAPSHOT [INFO]task-segment: [clean, test] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from internal [INFO] [clean:clean] [INFO] Deleting directory c:\adhoc\buglet\target [INFO] Deleting directory c:\adhoc\buglet\target\classes [INFO] Deleting directory c:\adhoc\buglet\target\test-classes [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for updates from internal [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from internal [INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for updates from internal [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 1 source file to c:\adhoc\buglet\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: c:\adhoc\buglet\target\surefire-reports --- T E S T S --- Running BugletTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.187 sec <<< FAILURE! Results : Tests in error: testOne(BugletTest) Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Mon Jan 07 11:43:01 CET 2008 [INFO] Final Memory: 6M/13M [INFO] And this is the test error: [EMAIL PROTECTED] /cygdrive/c/adhoc/buglet $ less target/surefire-reports/*.txt --- Test set: BugletTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.109 sec <<< FAILURE! testOne(BugletTest) Time elapsed: 0 sec <<< ERROR! java.lang.NullPointerException at java.io.Reader.(Reader.java:74) at java.io.InputStreamReader.(InputStreamReader.java:118) at java.util.Properties.load(Properties.java:298) at BugletTest.testOne(BugletTest.java:10) at BugletTest.testOne(BugletTest.java:10) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) 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:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138
[jira] Closed: (MNG-2925) NullPointerException in PluginDescriptor.getMojo() if there's no mojo in pom.xml
[
http://jira.codehaus.org/browse/MNG-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-2925.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.9
Applied in r609576
For the next time, please provide us a patch.
http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch
> NullPointerException in PluginDescriptor.getMojo() if there's no mojo in
> pom.xml
>
>
> Key: MNG-2925
> URL: http://jira.codehaus.org/browse/MNG-2925
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 2.0.5
>Reporter: Kohsuke Kawaguchi
>Assignee: Vincent Siveton
> Fix For: 2.0.9, 2.1-alpha-1
>
>
> The getMojo method fails with NPE because getMojos() method returns null.
> This happens when there's no mojo in the plugin.
> The code should be modified to check for this situation, like this:
> {code}
> public MojoDescriptor getMojo( String goal )
> {
> List mojos = getMojos();
> if(mojos==null) return null; // no mojo in this POM
> MojoDescriptor mojoDescriptor = null;
> for ( Iterator i = mojos.iterator(); i.hasNext() && mojoDescriptor ==
> null; )
> {
> MojoDescriptor desc = (MojoDescriptor) i.next();
> if ( goal.equals( desc.getGoal() ) )
> {
> mojoDescriptor = desc;
> }
> }
> return mojoDescriptor;
> }
> {/code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3145) StringIndexOutOfBoundsException in AbstractMavenReportRenderer
[
http://jira.codehaus.org/browse/MNG-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNG-3145.
Assignee: Vincent Siveton
Resolution: Fixed
Fixed in r609579
For the next time, please provide us a patch.
http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch
> StringIndexOutOfBoundsException in AbstractMavenReportRenderer
> --
>
> Key: MNG-3145
> URL: http://jira.codehaus.org/browse/MNG-3145
> Project: Maven 2
> Issue Type: Bug
> Components: Sites & Reporting
>Affects Versions: 2.0.6
>Reporter: Thomas Krammer
>Assignee: Vincent Siveton
> Fix For: Shared Components
>
>
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.applyPattern(AbstractMavenReportRenderer.java:598)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.linkPatternedText(AbstractMavenReportRenderer.java:353)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:213)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:193)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.tableRow(AbstractMavenReportRenderer.java:225)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderDependenciesForScope(DependenciesReport.java:318)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:228)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:97)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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)
> When you look at the code it seems like a copy/paste error:
> String subString = text.substring(
> lastOffset, i );
> lastOffset = i + 1;
> int lastComma = subString.lastIndexOf( "," );
> if ( lastComma != -1 )
> {
> segments.put( subString.substring( 0,
> lastComma ).trim(),
> subString.substring(
> lastComma + 1 ).trim() );
> }
> else
> {
> segments.put( subString.substring( 0,
> lastComma ).trim(), null );
> }
> I guess the last
[jira] Closed: (MJAR-58) Update Jar Plugin Documentation (more examples for manifest customization)
[ http://jira.codehaus.org/browse/MJAR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MJAR-58. Assignee: Olivier Lamy Resolution: Fixed A link to the improved Maven Archiver documentation has been added in the home page. svn rev 609580. > Update Jar Plugin Documentation (more examples for manifest customization) > -- > > Key: MJAR-58 > URL: http://jira.codehaus.org/browse/MJAR-58 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Franz Allan Valencia See >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.2 > > > The current jarplugin documentations has an example on how to customize the > manifest to be generated. Furthermore, it provides a link to the javadoc of > MavenArchiveConfiguration, which implies under configurations aside from the > one shown there (manifest entries). > IMHO, we can remove the link to the javadoc and replace that with actual > examples of those configurations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3135) Enable skipping clean:clean goal in verifier
[ http://jira.codehaus.org/browse/MNG-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3135. Assignee: Vincent Siveton Resolution: Fixed applied with the Maven code style (609582) > Enable skipping clean:clean goal in verifier > > > Key: MNG-3135 > URL: http://jira.codehaus.org/browse/MNG-3135 > Project: Maven 2 > Issue Type: Improvement > Components: integration tests >Affects Versions: Shared Components >Reporter: Arnaud Bailly >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Shared Components > > Attachments: autoclean.patch > > > WHen using maven-verifier, clean:clean goal is automatically added at the > start of the execution of the plugin. The attached patch simply adds an > autoclean property to the verifier that is 'true' by default but may be unset. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSITE-286) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-2910 to MSITE-286: Affects Version/s: (was: 2.0.4) 2.0-beta-5 Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0-beta-6 Component/s: (was: Errors) Key: MSITE-286 (was: MNG-2910) Project: Maven 2.x Site Plugin (was: Maven 2) > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-286 > URL: http://jira.codehaus.org/browse/MSITE-286 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: christian-Luc Houze >Priority: Minor > Fix For: 2.0-beta-6 > > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affectr my builds or sites generation > is this normal/abnormal. > what should i do so that i get rid of this, and that my manager does not feel > bad about a product that throws errors even if final result seems ok :-) > thanks, > Christian-Luc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-286) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MSITE-286. - Assignee: Vincent Siveton Resolution: Duplicate Duplicate MSITE-170 Fixed in maven-site-plugin:2.0-beta-6 > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-286 > URL: http://jira.codehaus.org/browse/MSITE-286 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: christian-Luc Houze >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.0-beta-6 > > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affectr my builds or sites generation > is this normal/abnormal. > what should i do so that i get rid of this, and that my manager does not feel > bad about a product that throws errors even if final result seems ok :-) > thanks, > Christian-Luc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2849) nonProxyHosts element's value separator
[ http://jira.codehaus.org/browse/MNG-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-2849. Assignee: Vincent Siveton Resolution: Cannot Reproduce Already fixed by r426263 and r426268 http://maven.apache.org/ref/current/maven-settings/settings.html#class_proxy > nonProxyHosts element's value separator > > > Key: MNG-2849 > URL: http://jira.codehaus.org/browse/MNG-2849 > Project: Maven 2 > Issue Type: Wish > Components: Sites & Reporting >Affects Versions: 2.0.5 >Reporter: Sang-Jea Shin >Assignee: Vincent Siveton >Priority: Trivial > Fix For: Reviewed Pending Version Assignment > > > According to this article proxy separator is "|". > http://maven.apache.org/guides/mini/guide-proxies.html > But according to this article, separator is ",". > http://maven.apache.org/ref/2.0.4/maven-settings/settings.html > Which one is correct? > Or both works? > I wish to correct these description. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3349) reactor build order doesn't consider plugins modules in build order
reactor build order doesn't consider plugins modules in build order --- Key: MNG-3349 URL: http://jira.codehaus.org/browse/MNG-3349 Project: Maven 2 Issue Type: Bug Components: Reactor and workspace Affects Versions: 2.0.8 Reporter: nicolas de loof Priority: Minor When a project has maven plugins as modules, and some modules use the plugin, the reactor SHOULD build the plugins before the modules that use it. A workaround is to declare plugins modules FIRST in parent POM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-1876) blazeds-common
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Heaton reopened MAVENUPLOAD-1876: -- Doh! There was a typo in the blazeds-remoting pom. Please re-upload the blazeds-remoting bundle. Sorry! > blazeds-common > -- > > Key: MAVENUPLOAD-1876 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1876 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ryan Heaton >Assignee: Carlos Sanchez > > BlazeDS is the server-based Java remoting and web messaging technology that > enables developers to easily connect to back-end distributed data and push > data in real-time to Adobe Flex and Adobe AIR applications for more > responsive rich Internet application (RIA) experiences. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAR-95) Documentation: "Guide to using attached tests" specifies wrong classifier
Documentation: "Guide to using attached tests" specifies wrong classifier - Key: MJAR-95 URL: http://jira.codehaus.org/browse/MJAR-95 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Maven 2.0.8 Reporter: Jim Cushing Priority: Minor http://maven.apache.org/guides/mini/guide-attached-tests.html test-jar Should be: tests With this change, test JAR dependencies will correctly be found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release
[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119031 ] Jim Cushing commented on MRELEASE-285: -- I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MJAR-95 ( http://jira.codehaus.org/browse/MJAR-95 ), which might be related. > Unresolved test-jar dependency during release > - > > Key: MRELEASE-285 > URL: http://jira.codehaus.org/browse/MRELEASE-285 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: Maven version: 2.0.7 > Java version: 1.5.0_07 > OS name: "mac os x" version: "10.4.10" arch: "i386" >Reporter: Rod Coffin > Attachments: example.jar > > > I have a multi-module project where one project produces a normal jar and a > test-jar > (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). > Another submodule has a test scoped dependency on the test-jar from the first > submodule. For example, this is the structure and produced artifacts for a > small sample (attached) I built to reproduce this behavior: > release-test-jar (parent project) > project-with-test-jar (submodule) > => project-with-test-jar-1.0.jar > => project-with-test-jar-1.0-tests.jar > project-using-test-jar (submodule) > => project-user-test-jar-1.0.jar > When I run a 'clean install' the build succeeds. However, when I run a > 'release:prepare' the build fails with the following error: > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > 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: > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: > Missing: > -- > 1) com.rfc:project-with-test-jar:test-jar:tests:1.1 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) com.rfc:project-using-test-jar:jar:1.1 > 2) com.rfc:project-with-test-jar:test-jar:tests:1.1 > -- > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) > at > org.apache.maven.plugin.DefaultPluginMan
[jira] Updated: (MJAR-95) Documentation: "Guide to using attached tests" specifies wrong classifier
[ http://jira.codehaus.org/browse/MJAR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MJAR-95: - Assignee: Olivier Lamy > Documentation: "Guide to using attached tests" specifies wrong classifier > - > > Key: MJAR-95 > URL: http://jira.codehaus.org/browse/MJAR-95 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Maven 2.0.8 >Reporter: Jim Cushing >Assignee: Olivier Lamy >Priority: Minor > > http://maven.apache.org/guides/mini/guide-attached-tests.html > test-jar > Should be: > tests > With this change, test JAR dependencies will correctly be found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNG-3350) Documentation: "Guide to using attached tests" specifies wrong classifier
[ http://jira.codehaus.org/browse/MNG-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MJAR-95 to MNG-3350: --- Affects Version/s: (was: 2.1) Documentation Deficit Key: MNG-3350 (was: MJAR-95) Project: Maven 2 (was: Maven 2.x Jar Plugin) > Documentation: "Guide to using attached tests" specifies wrong classifier > - > > Key: MNG-3350 > URL: http://jira.codehaus.org/browse/MNG-3350 > Project: Maven 2 > Issue Type: Bug >Affects Versions: Documentation Deficit > Environment: Maven 2.0.8 >Reporter: Jim Cushing >Assignee: Olivier Lamy >Priority: Minor > > http://maven.apache.org/guides/mini/guide-attached-tests.html > test-jar > Should be: > tests > With this change, test JAR dependencies will correctly be found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3350) Documentation: "Guide to using attached tests" specifies wrong classifier
[ http://jira.codehaus.org/browse/MNG-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-3350. - Resolution: Fixed fix in rev 609646. Thanks. > Documentation: "Guide to using attached tests" specifies wrong classifier > - > > Key: MNG-3350 > URL: http://jira.codehaus.org/browse/MNG-3350 > Project: Maven 2 > Issue Type: Bug >Affects Versions: Documentation Deficit > Environment: Maven 2.0.8 >Reporter: Jim Cushing >Assignee: Olivier Lamy >Priority: Minor > > http://maven.apache.org/guides/mini/guide-attached-tests.html > test-jar > Should be: > tests > With this change, test JAR dependencies will correctly be found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPPDF-56) Some HTML in the .xml file do not translate to the PDF
[ http://jira.codehaus.org/browse/MPPDF-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPPDF-56. -- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 2.5.2 I have added and support, style attributes are hopeless IMO. > Some HTML in the .xml file do not translate to the PDF > -- > > Key: MPPDF-56 > URL: http://jira.codehaus.org/browse/MPPDF-56 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Maven 1.0.2; Java 1.5 >Reporter: Jamie Bisotti >Assignee: Lukas Theussl > Fix For: 2.5.2 > > > Our documentation makes use of tags like the following: color='red'>Foo; however, in the PDF the text is not appearing in red. > Also, the tag seems to be ignored as well. Finally, the 'style' > attribute seems to be ignored altogether. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPPDF-61) PDF Generates content for
[ http://jira.codehaus.org/browse/MPPDF-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPPDF-61. -- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 2.5.2 I have committed it to svn and deployed a snapshot (2.5.2-SNAPSHOT, which also includes MPPDF-56). I just don't know if there will ever be an m1 release again... > PDF Generates content for
[jira] Commented: (MNG-3289) unable to resolve profile properties from a parent pom
[
http://jira.codehaus.org/browse/MNG-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119058
]
Ken in nashua commented on MNG-3289:
Yeah I'm getting WHACKED by the same thing too...
[DEBUG] Trying repository central
[DEBUG] Unable to get resource 'oracle.jdbc.driver:oracle-jdbc:pom:9.0.2.0'
from repository central (http://repo1.maven.org/maven2) Unable to locate
resource in repository
[DEBUG] Trying repository central
[DEBUG] Unable to get resource 'oracle.jdbc.driver:oracle-jdbc:pom:9.0.2.0'
from repository central (http://repo1.maven.org/maven2) Unable to locate
resource in repository
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] java.lang.UnsupportedOperationException
java.lang.UnsupportedOperationException
at java.util.AbstractCollection.add(Unknown Source)
at
org.apache.maven.compat.plugin.Maven20xCompatAspect.checkPlexusUtils(Maven20xCompatAspect.aj:309)
at
org.apache.maven.compat.plugin.Maven20xCompatAspect.ajc$privMethod$org_apache_maven_compat_plugin_Maven20xCompatAspect$org_apache_maven_compat_plugin_Maven20xCompatAspect$checkPlexusUtils(Maven20xCompatAspect.aj:1)
at
org.apache.maven.extension.DefaultExtensionManager.getArtifacts_aroundBody1$advice(DefaultExtensionManager.java:237)
at
org.apache.maven.extension.DefaultExtensionManager.addExtension(DefaultExtensionManager.java:323)
at
org.apache.maven.extension.DefaultExtensionManager.addExtension(DefaultExtensionManager.java:147)
at
org.apache.maven.extension.DefaultBuildExtensionScanner.checkModelBuildForExtensions(DefaultBuildExtensionScanner.java:309)
at
org.apache.maven.extension.DefaultBuildExtensionScanner.scanInternal(DefaultBuildExtensionScanner.java:153)
at
org.apache.maven.extension.DefaultBuildExtensionScanner.scanForBuildExtensions(DefaultBuildExtensionScanner.java:81)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:282)
at
org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:109)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:813)
at
org.maven.ide.eclipse.embedder.Maven2Executor.main(Maven2Executor.java:85)
[INFO]
[INFO] Total time: 5 second
[INFO] Finished at: Mon Jan 07 14:31:04 EST 2008
[INFO] Memory 1M/6M
[INFO]
> unable to resolve profile properties from a parent pom
> --
>
> Key: MNG-3289
> URL: http://jira.codehaus.org/browse/MNG-3289
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.7
>Reporter: Rot Ulet
>
> I defined some properties in the default profile in the settings.xml :
>
>
>
> profile01
>
> true
>
>
> scm:svn:svn://linux-dev/source
> http://linux-dev/bugzilla
>
>
>
>
> I have defined a parent pom file named BaseProject (for default
> configuration, report, etc.) used in all project I use. I can compile and
> install this pom to my local repository. I reference this pom as the parent
> for my other projects.
> * For a project with parent defined to my BaseProject-pom and without
> dependencies to other project, there is no problem : I can compile and
> install without any warning.
> * But for a project with parent defined to my BaseProject-pom and with some
> dependencies to other project (previously compiled and installed), I have
> this warning :
> [WARNING] POM for 'net.dummy:FW-Interfaces:pom:1.0-SNAPSHOT:compile' is
> invalid. It will be ignored for artifact resolution. Reason: The POM
> expression: ${pom.scm.connection} could not be evaluated. Reason: Expression
> value '${pom.scm.connection}/FW/FW-Interfaces' references itself in
> 'net.dummy:FW-Interfaces:jar:1.0-SNAPSHOT'. for project
> net.dummy:FW-Interfaces at Artifact
> [net.dummy:FW-Interfaces:pom:1.0-SNAPSHOT:compile]
> But ${pom.scm.connection} (or ${scm.connection}) is defined in the default
> profile of the settings.xml.
> But It is just a warning and can go through all the compilation steps.
> * And for an helper project (called 'all_project.pom') without parent and
> dependencies but with all the project in need to compile in the 'modules'
> section. I got this :
> [WARNING] POM for 'net.dummy:BaseProject-Conf:pom:1.0-SNAPSHOT:runtime' is
> invalid. It will be ignored for artifact resolution. Reason: The POM
> expression: ${pom.scm.connection} could not be evaluated. Reas
[jira] Closed: (MJAR-91) release maven-archiver
[ http://jira.codehaus.org/browse/MJAR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MJAR-91. Resolution: Fixed maven-archiver 2.3 released. dependency version updated rev 609765. > release maven-archiver > -- > > Key: MJAR-91 > URL: http://jira.codehaus.org/browse/MJAR-91 > Project: Maven 2.x Jar Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.2 > > > fix of MJAR-74 introduce a dependency to a new version of maven-archiver -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-364) NPE in StarteamChangeLogCommand
NPE in StarteamChangeLogCommand --- Key: SCM-364 URL: http://jira.codehaus.org/browse/SCM-364 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-starteam Affects Versions: 1.0 Reporter: Olivier Lamy look CONTINUUM-1521 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-364) NPE in StarteamChangeLogCommand
[ http://jira.codehaus.org/browse/SCM-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-364. Assignee: Dan Tran Resolution: Fixed Fix Version/s: 1.x fixed in rev 607771. > NPE in StarteamChangeLogCommand > --- > > Key: SCM-364 > URL: http://jira.codehaus.org/browse/SCM-364 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-starteam >Affects Versions: 1.0 >Reporter: Olivier Lamy >Assignee: Dan Tran > Fix For: 1.x > > > look CONTINUUM-1521 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1885) Uploading BlueCove 2.0.2 to repository
Uploading BlueCove 2.0.2 to repository -- Key: MAVENUPLOAD-1885 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1885 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy New in version 2.0.2 * Support for Mac OSX -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-70) Move hard-coded strings to resource bundle
Move hard-coded strings to resource bundle -- Key: MPMD-70 URL: http://jira.codehaus.org/browse/MPMD-70 Project: Maven 2.x PMD Plugin Issue Type: Bug Components: CPD, PMD Reporter: Benjamin Bentmann Priority: Trivial Attachments: i18n-no-problems.patch Both reports output something like " found no problems in your source code" in case no violations were found. These strings are hard-coded in the Java code but should come from the resource bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-71) Add german translation
Add german translation -- Key: MPMD-71 URL: http://jira.codehaus.org/browse/MPMD-71 Project: Maven 2.x PMD Plugin Issue Type: Improvement Components: CPD, PMD Reporter: Benjamin Bentmann Priority: Trivial Attachments: i18n-de.patch Well, it's all said, isn't it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPMD-61) When running build using "-f /pom.xml" the site is stored in working directory instead of project directory
[
http://jira.codehaus.org/browse/MPMD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MPMD-61:
--
Attachment: output-directory.patch
Actually, the issue is caused by the plugin's incorrect handling of relative
paths. Relatives paths are resolved against the current working directory by
java.io.File but we expect them to be resolved against the project's base
directory.
In plain words, somebody must explicitly resolve the path against the intended
directory since java.io.File will not do the job. Fortunately, Maven can do
this for the plugin IF it declares its path parameters to be of type
java.io.File instead of java.lang.String (see also MNG-3273).
Compare the value of "outputDirectory" in these debug logs. Before the path:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-pmd-plugin:2.4-SNAPSHOT:pmd' -->
[DEBUG] (f) aggregate = false
[DEBUG] (f) compileSourceRoots = [M:\maven\z\javacc\src\main\java]
[DEBUG] (f) format = xml
[DEBUG] (f) includeTests = false
[DEBUG] (f) linkXRef = true
[DEBUG] (f) minimumPriority = 5
[DEBUG] (f) outputDirectory = target/site
[DEBUG] (f) project = MavenProject: de.test:javacc:1.0 @
M:\maven\z\javacc\pom.xml
[DEBUG] (f) reactorProjects = [MavenProject: de.test:javacc:1.0 @
M:\maven\z\javacc\pom.xml]
[DEBUG] (f) skip = false
[DEBUG] (f) targetDirectory = M:\maven\z\javacc\target
[DEBUG] (f) testSourceRoots = [M:\maven\z\javacc\src\test\java]
[DEBUG] (f) xrefLocation = M:\maven\z\javacc\target\site\xref
[DEBUG] (f) xrefTestLocation = M:\maven\z\javacc\target\site\xref-test
[DEBUG] -- end configuration --
{noformat}
and after the patch:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-pmd-plugin:2.4-SNAPSHOT:pmd' -->
[DEBUG] (f) aggregate = false
[DEBUG] (f) compileSourceRoots = [M:\maven\z\javacc\src\main\java]
[DEBUG] (f) format = xml
[DEBUG] (f) includeTests = false
[DEBUG] (f) linkXRef = true
[DEBUG] (f) minimumPriority = 5
[DEBUG] (f) outputDirectory = M:\maven\z\javacc\target\site
[DEBUG] (f) project = MavenProject: de.test:javacc:1.0 @
M:\maven\z\javacc\pom.xml
[DEBUG] (f) reactorProjects = [MavenProject: de.test:javacc:1.0 @
M:\maven\z\javacc\pom.xml]
[DEBUG] (f) skip = false
[DEBUG] (f) targetDirectory = M:\maven\z\javacc\target
[DEBUG] (f) testSourceRoots = [M:\maven\z\javacc\src\test\java]
[DEBUG] (f) xrefLocation = M:\maven\z\javacc\target\site\xref
[DEBUG] (f) xrefTestLocation = M:\maven\z\javacc\target\site\xref-test
[DEBUG] -- end configuration --
{noformat}
> When running build using "-f /pom.xml" the site is stored in
> working directory instead of project directory
>
>
> Key: MPMD-61
> URL: http://jira.codehaus.org/browse/MPMD-61
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 2.2
> Environment: Windows XP, Java 1.5, Maven 2.0.7
>Reporter: Peter Hayes
> Attachments: output-directory.patch, pmd-multi-module.zip
>
>
> I setup a multi-module build and included the pmd check goal to run during
> the verify phase. When I execute a build from the top level directory
> specifying -f /pom.xml, the plugin creates a target/site/... directory
> in the current working directory. This directory should be in the project
> directory and now fails to clean.
> I have attached a sample project. To reproduce :
> cd pmd-multi-module
> mvn -f ./root/pom.xml install
> Note that after the build there is a target directory in the current working
> directory with the pmd.html and other files within it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-285) Unresolved test-jar dependency during release
[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119031 ] jimothy edited comment on MRELEASE-285 at 1/7/08 4:02 PM: -- I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MNG-3350 ( http://jira.codehaus.org/browse/MNG-3350 ), which might be related. was (Author: jimothy): I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MJAR-95 ( http://jira.codehaus.org/browse/MJAR-95 ), which might be related. > Unresolved test-jar dependency during release > - > > Key: MRELEASE-285 > URL: http://jira.codehaus.org/browse/MRELEASE-285 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: Maven version: 2.0.7 > Java version: 1.5.0_07 > OS name: "mac os x" version: "10.4.10" arch: "i386" >Reporter: Rod Coffin > Attachments: example.jar > > > I have a multi-module project where one project produces a normal jar and a > test-jar > (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). > Another submodule has a test scoped dependency on the test-jar from the first > submodule. For example, this is the structure and produced artifacts for a > small sample (attached) I built to reproduce this behavior: > release-test-jar (parent project) > project-with-test-jar (submodule) > => project-with-test-jar-1.0.jar > => project-with-test-jar-1.0-tests.jar > project-using-test-jar (submodule) > => project-user-test-jar-1.0.jar > When I run a 'clean install' the build succeeds. However, when I run a > 'release:prepare' the build fails with the following error: > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > 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: > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: > Missing: > -- > 1) com.rfc:project-with-test-jar:test-jar:tests:1.1 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file there: > mvn deploy:deploy-file -DgroupId=com.rfc > -DartifactId=project-with-test-jar \ > -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar > -Dfile=/path/to/file \ >-Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) com.rfc:project-using-test-jar:jar:1.1 > 2) com.rfc:project-with-test-jar:test-jar:tests:1.1 > -- > 1 required artifact is missing. > for artifact: > com.rfc:project-using-test-jar:jar:1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) >
[jira] Created: (MDEP-131) Complete i18n support for new analyze-report
Complete i18n support for new analyze-report Key: MDEP-131 URL: http://jira.codehaus.org/browse/MDEP-131 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: analyze Affects Versions: 2.0-alpha-5 Reporter: Benjamin Bentmann Assignee: Brian Fox Priority: Trivial Attachments: i18n.patch The patch applied from MDEP-104 missed some hard-coded strings that should be moved into the resource bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-132) Add german translation for analyze-report mojo
Add german translation for analyze-report mojo -- Key: MDEP-132 URL: http://jira.codehaus.org/browse/MDEP-132 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: analyze Affects Versions: 2.0-alpha-5 Reporter: Benjamin Bentmann Assignee: Brian Fox Priority: Trivial Attachments: i18n-de.patch Teaching the report another language. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-287) Clarify/fix documentation about encoding for translated resource bundles.
Clarify/fix documentation about encoding for translated resource bundles. - Key: MSITE-287 URL: http://jira.codehaus.org/browse/MSITE-287 Project: Maven 2.x Site Plugin Issue Type: Improvement Affects Versions: 2.0-beta-6 Reporter: Benjamin Bentmann Priority: Minor According to http://maven.apache.org/plugins/maven-site-plugin/i18n.html translators are expected to provide their properties files in UTF-8 encoding. However, the JRE reads properties files using ISO-8859-1 encoding (see [class javadoc for PropertyResourceBundle|http://java.sun.com/javase/6/docs/api/java/util/PropertyResourceBundle.html]). Either the documentation should be fixed to state ISO-8859-1 or it should be made clear why Maven requires another encoding than usual. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-80) Add german translation
Add german translation -- Key: MCHECKSTYLE-80 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-80 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Benjamin Bentmann Priority: Trivial Attachments: i18n-de.patch Teaching the report another language. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-131) Attach source and javadoc to dependencies in pde projects
[ http://jira.codehaus.org/browse/MECLIPSE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119102 ] luke w patterson commented on MECLIPSE-131: --- Hi, When I set the pde parameter to 'true' in my pom, I only get source attachments (.classpath entries) for non-bundle artifacts. Does the fix attach source code for bundle artifacts as well? Is there a way to manually attach source code besides creating a bundle which contains an extension point of type "org.eclipse.pde.core.source"? I use version 2.5-SNAPSHOT. Thanks, Luke > Attach source and javadoc to dependencies in pde projects > - > > Key: MECLIPSE-131 > URL: http://jira.codehaus.org/browse/MECLIPSE-131 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: PDE support >Affects Versions: 2.3 > Environment: windows xp, eclipse3.2.0, jdk 1.5, maven 2.0.4 >Reporter: stephane bouchet >Assignee: fabrizio giustina > Fix For: 2.3 > > > when using plugin for pde projects, source and javadoc are not attached for > dependencies even if they are available in repo. > this feature exists already for java project, it could be nice to have the > same for pde projects. > Thanks, > Stéphane . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-92) JIRA Report Improvements
JIRA Report Improvements Key: MCHANGES-92 URL: http://jira.codehaus.org/browse/MCHANGES-92 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: jira-report Affects Versions: 2.0-beta-3 Reporter: Niall Pemberton Attachments: maven-changes-jira-report-improvements.patch OK heres my wish-list to improve the JIRA report: - Be able to configure which columns are shown on the report - Make the following additional columns available on the report: Reporter, Type, Priority, Version, Fix Version and Component - Be able to configure the "Fix Version" to show on the report (rather than all versions) - Be able to configure which "types" are shown on the report (rather than all types) - Currently the configurable Status, Resolution and Priority values are ignored (because of bugs in the url parameters used) I realize the Fix Version and Types can be configured using the existing "filter" - but thats not a very user friendly feature. Attaching a patch which does all of the above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRRESOURCES-31) Add an "alternative" apache-jar-resource-bundle
Add an "alternative" apache-jar-resource-bundle --- Key: MRRESOURCES-31 URL: http://jira.codehaus.org/browse/MRRESOURCES-31 Project: Maven 2.x Remote Resources Plugin Issue Type: Improvement Reporter: Niall Pemberton I propose adding an "alternative" apache-jar-resource-bundle (perhaps called "apache-jar-resource-bundle-alt"?) which is a copy of the existing apache-jar-resource-bundle[1] except that the LICENSE.vm is renamed to LICENSE.txt.vm NOTICE.vm is renamed to NOTICE.txt.vm This will create files named LICENSE.txt and NOTICE.txt rather than LICENSE and NOTICE. The ASF policy[2] on the naming of these files says: - Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt? - This is permitted. However the preference is that the files be called LICENSE and NOTICE. Many projects use ".txt" extensions as its more friendly to windows users and since the policy says its permitted then IMO it would be good to support projects which chose to use that naming convention with a standard resource bundle. This has come out of a discussion at Apache Commons [3] and a bundle such as this would allow that project (with 34 diffferent components, each with a copy of NOTICE.txt and LICENSE.txt) to be able to easily migrate to using the remote-resources-plugin with minimal effort. Currently, configuring the remote-resources-plugin in Commons's parent pom causes duplicate Notice and License files (i.e. versions with and without the .txt extension). Apologies if this is filed in the wrong place - but theres no issue tracking link in the pom for apache-jar-resource-bundle to indicate where issues should be filed. [1] http://svn.apache.org/repos/asf/maven/resources/trunk/apache-jar-resource-bundle/ [2] http://apache.org/dev/apply-license.html#license-file-name [3] http://issues.apache.org/jira/browse/COMMONSSITE-21 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRRESOURCES-31) Add an "alternative" apache-jar-resource-bundle
[ http://jira.codehaus.org/browse/MRRESOURCES-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton updated MRRESOURCES-31: --- Attachment: NOTICE.txt.vm LICENSE.txt.vm pom.xml Sorry, the svn client I use (TortoiseSVN) doesn't create patches properly when new directories are added - so I'm just attaching the three files. Directory structure is the same as apache-jar-resource-bundle. > Add an "alternative" apache-jar-resource-bundle > --- > > Key: MRRESOURCES-31 > URL: http://jira.codehaus.org/browse/MRRESOURCES-31 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Reporter: Niall Pemberton > Attachments: LICENSE.txt.vm, NOTICE.txt.vm, pom.xml > > > I propose adding an "alternative" apache-jar-resource-bundle (perhaps called > "apache-jar-resource-bundle-alt"?) which is a copy of the existing > apache-jar-resource-bundle[1] except that the >LICENSE.vm is renamed to LICENSE.txt.vm >NOTICE.vm is renamed to NOTICE.txt.vm > This will create files named LICENSE.txt and NOTICE.txt rather than LICENSE > and NOTICE. > The ASF policy[2] on the naming of these files says: > - Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt? > - This is permitted. However the preference is that the files be called > LICENSE and NOTICE. > Many projects use ".txt" extensions as its more friendly to windows users and > since the policy says its permitted then IMO it would be good to support > projects which chose to use that naming convention with a standard resource > bundle. > This has come out of a discussion at Apache Commons [3] and a bundle such as > this would allow that project (with 34 diffferent components, each with a > copy of NOTICE.txt and LICENSE.txt) to be able to easily migrate to using the > remote-resources-plugin with minimal effort. Currently, configuring the > remote-resources-plugin in Commons's parent pom causes duplicate Notice and > License files (i.e. versions with and without the .txt extension). > Apologies if this is filed in the wrong place - but theres no issue tracking > link in the pom for apache-jar-resource-bundle to indicate where issues > should be filed. > [1] > http://svn.apache.org/repos/asf/maven/resources/trunk/apache-jar-resource-bundle/ > [2] http://apache.org/dev/apply-license.html#license-file-name > [3] http://issues.apache.org/jira/browse/COMMONSSITE-21 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3351) Release plugin throws NullPointerException when using version range for dependency
Release plugin throws NullPointerException when using version range for dependency -- Key: MNG-3351 URL: http://jira.codehaus.org/browse/MNG-3351 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.8 Reporter: David Hoffer Priority: Blocker After upgrading to 2.0.8 I find that the release plugin throws NPE if any dependency uses version range. I have one dependency with version range [1.0,2.0) the rest are test scope with fixed version. Here is the crash stack trace: java.lang.NullPointerException: version was null for com.xrite:xrite-colorlib-api [13:42:05]: at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) [13:42:05]: at org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:557) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkArtifact(CheckDependencySnapshotsPhase.java:252) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:138) [13:42:05]: at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:106) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) [13:42:05]: at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) [13:42:05]: at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) [13:42:05]: at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:228) [13:42:05]: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) [13:42:05]: at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) [13:42:05]: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [13:42:05]: at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) [13:42:05]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [13:42:05]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [13:42:05]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [13:42:05]: at java.lang.reflect.Method.invoke(Method.java:597) [13:42:05]: at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [13:42:05]: at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [13:42:05]: at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [13:42:05]: at org.codehaus.classworlds.Launcher.main(Launcher.java:375) It seems the reason version is null is that the call to selectVersionFromNewRangeIfAvailable() assumes that versionRange.getRecommendedVersion() will always return non-null, else it sets the version to null! However during the release:prepare phase this is not true, see the output: [13:42:04]: [INFO] [release:prepare] [13:42:04]: [INFO] Verifying that there are no local modifications... [13:42:04]: [INFO] Executing: svn --non-interactive status [13:42:04]: [INFO] Working directory: C:\BuildAgent\work\23044d751bcc9843 [13:42:05]: [INFO] Checking dependencies and plugins for snapshots ... [13:42:05]: TEST!!! version=null [13:42:05]: TEST!!! versionRange=[1.0,2.0) [13:42:05]: TEST!!! getRecommendedVersion=null TEST!!! Lines are my test code so I could see what is going on here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3351) Release plugin throws NullPointerException when using version range for dependency
[ http://jira.codehaus.org/browse/MNG-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119110 ] David Hoffer commented on MNG-3351: --- I was using release plugin version 2.0-beta-6. > Release plugin throws NullPointerException when using version range for > dependency > -- > > Key: MNG-3351 > URL: http://jira.codehaus.org/browse/MNG-3351 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.8 >Reporter: David Hoffer >Priority: Blocker > > After upgrading to 2.0.8 I find that the release plugin throws NPE if any > dependency uses version range. > I have one dependency with version range [1.0,2.0) the > rest are test scope with fixed version. > Here is the crash stack trace: > java.lang.NullPointerException: version was null for > com.xrite:xrite-colorlib-api > [13:42:05]: at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > [13:42:05]: at > org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:557) > [13:42:05]: at > org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkArtifact(CheckDependencySnapshotsPhase.java:252) > [13:42:05]: at > org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:138) > [13:42:05]: at > org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:106) > [13:42:05]: at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) > [13:42:05]: at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) > [13:42:05]: at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) > [13:42:05]: at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) > [13:42:05]: at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:228) > [13:42:05]: at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > [13:42:05]: at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > [13:42:05]: at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > [13:42:05]: at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > [13:42:05]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [13:42:05]: at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [13:42:05]: at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [13:42:05]: at java.lang.reflect.Method.invoke(Method.java:597) > [13:42:05]: at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [13:42:05]: at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > [13:42:05]: at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > [13:42:05]: at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > It seems the reason version is null is that the call to > selectVersionFromNewRangeIfAvailable() assumes that > versionRange.getRecommendedVersion() will always return non-null, else it > sets the version to null! However during the release:prepare phase this is > not true, see the output: > [13:42:04]: [INFO] [release:prepare] > [13:42:04]: [INFO] Verifying that there are no local modifications... > [13:42:04]: [INFO] Executing: svn --non-interactive status > [13:42:04]: [INFO] Working directory: C:\BuildAgent\work\23044d751bcc9843 > [13:42:05]: [INFO] Checking dependencies and plugins for snapshots ... > [13:42:05]: TEST!!! version=null > [13:42:05]: TEST!!! versionRange=[1.0,2.0) > [13:42:05]: TEST!!! getRecommendedVersion=null > TEST!!! Lines are my test code so I could see what is going on here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119114 ] Lee Bieber commented on MNG-2551: - I have the same problem as described above, when ever I deploy a jar file into my repository, the pom file is truncated at 4096 bytes. This is using maven 2.0.8, with Java 1.5.0_12 on CentOS. This happens when I do NOT use SNAPSHOT in my version string and run "mvn deploy" > pom metadata file gets truncated during install into local repository > - > > Key: MNG-2551 > URL: http://jira.codehaus.org/browse/MNG-2551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Fix For: Reviewed Pending Version Assignment > > Attachments: pom.xml, shared-1.9.0.pom > > > When I attempt to install my project artifact to my local repository it seems > that sometimes an incomplete/truncated ".pom" is deployed to my local > repository. It's kind of weird because sometimes it happens and sometimes it > doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and > the truncated pom meta data artifact deployed to my local repository. One > thing I found that's odd is that the size of the truncated pom generated is > consistently 4096 bytes. > p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3337) Downloading plugins for an inhouse repository problem
[ http://jira.codehaus.org/browse/MNG-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119116 ] sedatcorbaci commented on MNG-3337: --- I stated that this bug occurs for an inhouse-internal-a network not connected to internet repository. So there is no possibility to use central repo. I also tried to override the central repo to internal repo but nothing changed. > Downloading plugins for an inhouse repository problem > - > > Key: MNG-3337 > URL: http://jira.codehaus.org/browse/MNG-3337 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Reporter: sedatcorbaci >Priority: Blocker > > For an inhouse maven repository we can't find a way to download the plugins > to local repo. > When we try to execute an initial archetype:create command encountered maven > couldn't find the archetype plugin error. To deal with this we just copies > org.apache folder to local repo and then everything fine. But again if i need > any plugin that is not in copied to local repo manually maven couldn't > download it from internal repository. -- 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
