[jira] Created: (CONTINUUM-619) shell command line not preserved
shell command line not preserved Key: CONTINUUM-619 URL: http://jira.codehaus.org/browse/CONTINUUM-619 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.2 Reporter: Lee Meador Priority: Minor I have a shell project. The executable is 'mvn.bat' and the argument is the long string: -f 00Build/pom.xml --settings C:\Program Files\Apache Software Foundation\continuum-1.0.2\bin\win32\conf\settings.xml clean install This argument shows up on the info tab for the project correctly. There is only one build for that project. When I click edit to change the argument, the whole argument (as shown above) does not appear in the text box on that web page. It's not that it doesn't fit in the box and I would have to get it to scroll left and right to see the text. It just ends where the first double quote is. I see the first part of the argument and the last word shown is '--settings'. I can work around it by copying the argument on the info tab to my clipboard and then pasting it after I click the 'edit' link. -- 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: (MNGECLIPSE-8) Jar from remote repo not loaded and causes error in POM
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=comments#action_55452 ] Lee Meador commented on MNGECLIPSE-8: - Let me describe the process a bit better. 1. You select Maven2 add dependency from the context menu on a project entry in the package explorer view. 2. You pick a jar file that isn't in the local repository but is, instead, in the remote repository where the searcher window is searching. 3. The entry is added to the POM by the plugin. 4. Some part of the plugin is supposed to update the Maven classpath with that newly added jar. It doesn't do that. 5. A red X appears in the POM beside that jar file's name and the error says the jar file cannot be found. I hope this has been more informative. Jar from remote repo not loaded and causes error in POM --- Key: MNGECLIPSE-8 URL: http://jira.codehaus.org/browse/MNGECLIPSE-8 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3 Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all. -- 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-1926) maven 2 jxr plugin puts wrong javadoc link
maven 2 jxr plugin puts wrong javadoc link
--
Key: MNG-1926
URL: http://jira.codehaus.org/browse/MNG-1926
Project: Maven 2
Type: Bug
Components: Plugins and Lifecycle
Versions: 2.0.1
Reporter: Lee Meador
Priority: Minor
There are too many '../'s in the link to the javadocs that is generated at the
top of each page of java class source code. I have moved the javadocs to
${project.build.directory}/site/javadoc/ (which is given to the javadoc plugin
and then told the jxr plugin that they were at
${project.build.directory}/site/javadoc/apidocs/ which takes into account how
the javadocs are built. The link has way too many .. parts to the path and
backs up all the way to the top of my web site instead of just to the folder
equivalent to site
The xml is:
reporting
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjxr-maven-plugin/artifactId
configuration
javadocDir${project.build.directory}/site/javadoc/apidocs//javadocDir
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
destDir${project.build.directory}/site/javadoc//destDir
/configuration
/plugin
...
Sorry to put this issue here. It needs moving but there is no MNGJXR and MPJXR
seemed to be the maven1 jxr plugin. I assume it will be moved to the right
place. (and thanks)
--
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: (MNGECLIPSE-17) Can't Attach Source to Maven Dependencies
Can't Attach Source to Maven Dependencies - Key: MNGECLIPSE-17 URL: http://jira.codehaus.org/browse/MNGECLIPSE-17 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Reporter: Lee Meador There does not seem to be any way to attach source to any of the classpath entries that the maven2 plugin adds. When you are tracing around (or using ctrl-F3) and it pops up a class that for which it doesn't know the source there is usually a button you can click to add source. If the class is among the Maven Dependencies, there is no button. The instructions that it does give don't really seem to apply. You can't bring up the project properties build classpath and add source. -- 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: (MNGECLIPSE-18) Eclipse JUnit runner doesn't seem to get all the dependencies on its classpath
Eclipse JUnit runner doesn't seem to get all the dependencies on its classpath -- Key: MNGECLIPSE-18 URL: http://jira.codehaus.org/browse/MNGECLIPSE-18 Project: Maven 2.x Plug-in for Eclipse Type: Bug Reporter: Lee Meador This has happened several times. If I add the dependency into the eclipse part of the classpath by pointing to a copy that's not in the m2 repo, it will run the JUnit test(s). Latest time it can't find ApplicationContext from Spring even though its in the POM, it can be found when tests are run directly in maven2, it appears in the package explorer, and it appears in the project properties classpath. -- 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: (MNGECLIPSE-19) version can not be supplied in parent pom
version can not be supplied in parent pom - Key: MNGECLIPSE-19 URL: http://jira.codehaus.org/browse/MNGECLIPSE-19 Project: Maven 2.x Plug-in for Eclipse Type: Bug Reporter: Lee Meador If I don't have a version tag in the POM, I get an eclipse error with its little red spot on the top line of the POM. The maven dependencies all disappear (and, of course, most everything won't compile any more). The version should be gotten from the parent POM but doesn't seem to be. Interestingly enough, the first dependency with no version (jmock) seems to be ok. The message on the red spot on the pom does not mention jmock. It does mention all three of the spring dependencies that follow 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNGECLIPSE-6) Search in repository fails for log4j
Search in repository fails for log4j Key: MNGECLIPSE-6 URL: http://jira.codehaus.org/browse/MNGECLIPSE-6 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Windows XP, Eclipse 3.1, MyEclipse Reporter: Lee Meador Assigned to: Eugene Kuleshov Priority: Minor The repository search doesn't seem to see all the things in my repository. It couldn't find anything when I typed 'log4j' or 'log4' but found things for 'log' -- 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: (MNGECLIPSE-7) Search repository: Versions in local repo not seen
Search repository: Versions in local repo not seen -- Key: MNGECLIPSE-7 URL: http://jira.codehaus.org/browse/MNGECLIPSE-7 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Window XP, Eclipse 3.1, MyEclipse, local repo, no mirror, central=IBiblio Reporter: Lee Meador Assigned to: Eugene Kuleshov Priority: Minor I searched for 'mail' and it seemed to find version 1.3.2. The only version in my repository is 1.3.3_01 which it didn't show. Not noticing the difference I picked the 1.3.2 version and, though it was added to the POM, the red X at the top of the POM showed an error saying it couldn't find the jar. I edited the POM by hand and put in the 1.3.3_01 version and all was well. -- 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: (MNGECLIPSE-7) Search repository: Versions in local repo not seen
[ http://jira.codehaus.org/browse/MNGECLIPSE-7?page=comments#action_52322 ] Lee Meador commented on MNGECLIPSE-7: - Similar issue (most likely) : I have jaf-1.0.2 in my repository in the folder jaf/jaf/1.0.2/jaf-1.0.2.jar and an empty .pom. IBiblio has the POM only in jaf/activation/1.0.2/jaf-1.0.2.pom. Only the version in IBiblio showed up and when I picked it it put the dependency in the POM as jaf:activation:1.0.2 which couldn't find anything, again, in my repository. Search repository: Versions in local repo not seen -- Key: MNGECLIPSE-7 URL: http://jira.codehaus.org/browse/MNGECLIPSE-7 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Window XP, Eclipse 3.1, MyEclipse, local repo, no mirror, central=IBiblio Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor I searched for 'mail' and it seemed to find version 1.3.2. The only version in my repository is 1.3.3_01 which it didn't show. Not noticing the difference I picked the 1.3.2 version and, though it was added to the POM, the red X at the top of the POM showed an error saying it couldn't find the jar. I edited the POM by hand and put in the 1.3.3_01 version and all was well. -- 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: (MNGECLIPSE-8) Jar from remote repo not loaded and causes error in POM
Jar from remote repo not loaded and causes error in POM --- Key: MNGECLIPSE-8 URL: http://jira.codehaus.org/browse/MNGECLIPSE-8 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3 Reporter: Lee Meador Assigned to: Eugene Kuleshov Priority: Minor It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all. -- 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: (MNGECLIPSE-9) Classpath entries based on M2_REPO interfere with plugin classpath entries
Classpath entries based on M2_REPO interfere with plugin classpath entries -- Key: MNGECLIPSE-9 URL: http://jira.codehaus.org/browse/MNGECLIPSE-9 Project: Maven 2.x Plug-in for Eclipse Type: Wish Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, IBiblio is central repo, plugin version 0.0.3 Reporter: Lee Meador Assigned to: Eugene Kuleshov Priority: Minor My projects had originally been set up using mvn eclipse:eclipse so there were a bunch of M2_REPO based items in the classpath. When I added the maven2Nature with the menu selection, it added the maven based dependencies which, of course, duplicated the M2_REPO ones and caused an error. Perhaps there could be some way to remove the M2_REPO ones that are duplicates of the ones from the POM. I don't imagine everyone is so meticulous as to keep the two in sync when doing it by hand. -- 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: (MNGECLIPSE-6) Search in repository fails for log4j
[ http://jira.codehaus.org/browse/MNGECLIPSE-6?page=comments#action_52325 ] Lee Meador commented on MNGECLIPSE-6: - More environment infor: local repo, no mirrors, IBiblio is central repo, plugin version 0.0.3 Search in repository fails for log4j Key: MNGECLIPSE-6 URL: http://jira.codehaus.org/browse/MNGECLIPSE-6 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Windows XP, Eclipse 3.1, MyEclipse Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor The repository search doesn't seem to see all the things in my repository. It couldn't find anything when I typed 'log4j' or 'log4' but found things for 'log' -- 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: (MNGECLIPSE-7) Search repository: Versions in local repo not seen
[ http://jira.codehaus.org/browse/MNGECLIPSE-7?page=comments#action_52326 ] Lee Meador commented on MNGECLIPSE-7: - More environment infor: plugin version 0.0.3 Search repository: Versions in local repo not seen -- Key: MNGECLIPSE-7 URL: http://jira.codehaus.org/browse/MNGECLIPSE-7 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Window XP, Eclipse 3.1, MyEclipse, local repo, no mirror, central=IBiblio Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor I searched for 'mail' and it seemed to find version 1.3.2. The only version in my repository is 1.3.3_01 which it didn't show. Not noticing the difference I picked the 1.3.2 version and, though it was added to the POM, the red X at the top of the POM showed an error saying it couldn't find the jar. I edited the POM by hand and put in the 1.3.3_01 version and all was well. -- 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: (MNGECLIPSE-9) Classpath entries based on M2_REPO interfere with plugin classpath entries
[ http://jira.codehaus.org/browse/MNGECLIPSE-9?page=comments#action_52360 ] Lee Meador commented on MNGECLIPSE-9: - Blowing it away completely seems somewhat draconian. Perhaps just removing the ones in M2_REPO that are duplicated in the maven dependencies classpath. Then you could at least look at them and transfer them to the POM if you had some in the classpath when you enabled Maven2 on the project. As they were added to the POM the one with M2_REPO would get removed. Classpath entries based on M2_REPO interfere with plugin classpath entries -- Key: MNGECLIPSE-9 URL: http://jira.codehaus.org/browse/MNGECLIPSE-9 Project: Maven 2.x Plug-in for Eclipse Type: Wish Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, IBiblio is central repo, plugin version 0.0.3 Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor My projects had originally been set up using mvn eclipse:eclipse so there were a bunch of M2_REPO based items in the classpath. When I added the maven2Nature with the menu selection, it added the maven based dependencies which, of course, duplicated the M2_REPO ones and caused an error. Perhaps there could be some way to remove the M2_REPO ones that are duplicates of the ones from the POM. I don't imagine everyone is so meticulous as to keep the two in sync when doing it by hand. -- 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: (MNGECLIPSE-6) Search in repository fails for log4j
[ http://jira.codehaus.org/browse/MNGECLIPSE-6?page=comments#action_52361 ] Lee Meador commented on MNGECLIPSE-6: - BTW the thing it found for log was a taglib that I didn't recognize. Search in repository fails for log4j Key: MNGECLIPSE-6 URL: http://jira.codehaus.org/browse/MNGECLIPSE-6 Project: Maven 2.x Plug-in for Eclipse Type: Bug Environment: Windows XP, Eclipse 3.1, MyEclipse Reporter: Lee Meador Assignee: Eugene Kuleshov Priority: Minor The repository search doesn't seem to see all the things in my repository. It couldn't find anything when I typed 'log4j' or 'log4' but found things for 'log' -- 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-1660) Import the antrun plugin docs to explain sourceRoot and testSourceRoot
Import the antrun plugin docs to explain sourceRoot and testSourceRoot -- Key: MNG-1660 URL: http://jira.codehaus.org/browse/MNG-1660 Project: Maven 2 Type: Improvement Components: maven-antrun-plugin, documentation - guides Versions: 2.0 Reporter: Lee Meador Priority: Minor Attachments: MNG-XXX-maven-antrun-plugin.patch The documentation does not explain that the sourceRoot or testSourceRoot properties can be used with the antrun plugin to cause a path to be added to the list of things that gets compiled in a later lifecycle phase. The attached patch file will make the docs better by changing the descriptions for the attributes over in the plugin docs and adds another example to the introductory document. -- 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-1660) Import the antrun plugin docs to explain sourceRoot and testSourceRoot
[ http://jira.codehaus.org/browse/MNG-1660?page=comments#action_51672 ] Lee Meador commented on MNG-1660: - Oh yes, the patch file doesn't have a number because you don't get an issue number until you create the issue and I attached it to the issue while creating it. Please forgive. Import the antrun plugin docs to explain sourceRoot and testSourceRoot -- Key: MNG-1660 URL: http://jira.codehaus.org/browse/MNG-1660 Project: Maven 2 Type: Improvement Components: maven-antrun-plugin, documentation - guides Versions: 2.0 Reporter: Lee Meador Priority: Minor Attachments: MNG-XXX-maven-antrun-plugin.patch The documentation does not explain that the sourceRoot or testSourceRoot properties can be used with the antrun plugin to cause a path to be added to the list of things that gets compiled in a later lifecycle phase. The attached patch file will make the docs better by changing the descriptions for the attributes over in the plugin docs and adds another example to the introductory document. -- 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]
