[jira] Created: (MRM-304) Reference to derby.jar but the artifact isn't in the folder specified
Reference to derby.jar but the artifact isn't in the folder specified - Key: MRM-304 URL: http://jira.codehaus.org/browse/MRM-304 Project: Archiva Issue Type: Bug Components: documentation Reporter: John Tolentino Priority: Minor Need to update the docs to point to either ~/.m2/org/apache/derby or to the remote 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
[jira] Created: (MRM-305) Web application to add new artifacts to the repository
Web application to add new artifacts to the repository -- Key: MRM-305 URL: http://jira.codehaus.org/browse/MRM-305 Project: Archiva Issue Type: New Feature Components: web application Reporter: John Tolentino Priority: Minor A web application to add new artifacts to the repository might be a good feature. If an organization have existing non-Maven 2 builds and would like to migrate, it would be easier for them to use a form to do so instead of a command line deploy. -- 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: (MRM-304) Reference to derby.jar but the artifact isn't in the folder specified
[ http://jira.codehaus.org/browse/MRM-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Tolentino closed MRM-304. -- Resolution: Fixed Fix Version/s: 1.0 Reference to derby.jar but the artifact isn't in the folder specified - Key: MRM-304 URL: http://jira.codehaus.org/browse/MRM-304 Project: Archiva Issue Type: Bug Components: documentation Reporter: John Tolentino Assigned To: John Tolentino Priority: Minor Fix For: 1.0 Need to update the docs to point to either ~/.m2/org/apache/derby or to the remote 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
[jira] Closed: (MRM-305) Web application to add new artifacts to the repository
[ http://jira.codehaus.org/browse/MRM-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Tolentino closed MRM-305. -- Resolution: Duplicate A duplicate of MRM-216. Web application to add new artifacts to the repository -- Key: MRM-305 URL: http://jira.codehaus.org/browse/MRM-305 Project: Archiva Issue Type: New Feature Components: web application Reporter: John Tolentino Assigned To: John Tolentino Priority: Minor A web application to add new artifacts to the repository might be a good feature. If an organization have existing non-Maven 2 builds and would like to migrate, it would be easier for them to use a form to do so instead of a command line deploy. -- 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: (MWAR-85) FAQ documentation
[ http://jira.codehaus.org/browse/MWAR-85?page=all ] John Tolentino closed MWAR-85. -- Resolution: Fixed Fix Version/s: 2.0.2 Created FAQ page FAQ documentation - Key: MWAR-85 URL: http://jira.codehaus.org/browse/MWAR-85 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.0.2 Reporter: John Tolentino Assigned To: John Tolentino Priority: Minor Fix For: 2.0.2 Plugin fails docck because of a missing FAQ.fml. There's also a considerable number of frequently asked questions for this plugin like filtering and exclusions. -- 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: (MWAR-85) FAQ documentation
FAQ documentation - Key: MWAR-85 URL: http://jira.codehaus.org/browse/MWAR-85 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.0.2 Reporter: John Tolentino Priority: Minor Plugin fails docck because of a missing FAQ.fml. There's also a considerable number of frequently asked questions for this plugin like filtering and exclusions. -- 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: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=all ] John Tolentino closed MWAR-58. -- Resolution: Fixed Test cases done. Elliot Metsger, you can still submit your test cases if you want. consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58-new.patch, MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79342 ] John Tolentino commented on MWAR-58: Yes. Please provide test cases if you can. Would greatly demonstrate the use case for the functionality you want added. This is for a portlet right? consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=all ] John Tolentino closed MWAR-59. -- Resolution: Fixed Patch applied--although have to manually insert then test them because they got stale. Thanks for providing tests. artifact extension set incorrectly in a multi-module build -- Key: MWAR-59 URL: http://jira.codehaus.org/browse/MWAR-59 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0, 2.0.1 Reporter: Brett Porter Assigned To: John Tolentino Fix For: 2.0.2 Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt from the list... unfortunately [MWAR-38] is not fully fixed - It still does not work in a multi-module build. We do have here the following structure: root jarmodule ejb webapp Running a mvn package inside the webapp module, the EJB-Client jar from the ejb module is resolved correctly and copied to WEB-INF/lib with the correct .jar ending. Running the mvn package from the root module, the ejb-client jar from the ejb module is resolved but copied with a .ejb-client ending, and not with .jar. You can test this by using the daytrader example from the Maven book. -- 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: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=all ] John Tolentino updated MWAR-58: --- Attachment: MWAR-58-new.patch Merged with current svn code (mostly affected by MWAR-59). consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58-new.patch, MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79352 ] John Tolentino commented on MWAR-58: Elliot Metsger: Please use the patch I've attached here in creating your test cases. I've already merged it with MWAR-59 (which is already committed to svn). I'll do some tests as well. More tests the better. consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58-new.patch, MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=comments#action_79359 ] John Tolentino commented on MWAR-59: Changed code to use getClassifier() instead of getType(). artifact extension set incorrectly in a multi-module build -- Key: MWAR-59 URL: http://jira.codehaus.org/browse/MWAR-59 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0, 2.0.1 Reporter: Brett Porter Assigned To: John Tolentino Fix For: 2.0.2 Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt from the list... unfortunately [MWAR-38] is not fully fixed - It still does not work in a multi-module build. We do have here the following structure: root jarmodule ejb webapp Running a mvn package inside the webapp module, the EJB-Client jar from the ejb module is resolved correctly and copied to WEB-INF/lib with the correct .jar ending. Running the mvn package from the root module, the ejb-client jar from the ejb module is resolved but copied with a .ejb-client ending, and not with .jar. You can test this by using the daytrader example from the Maven book. -- 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: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79360 ] John Tolentino commented on MWAR-58: This got resolved with the fix to MWAR-59. They both use getClassifier() in resolving the default final name. Need some test case though to prove this works for this scenario (duplicate artifacts). consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58-new.patch, MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=comments#action_79083 ] John Tolentino commented on MWAR-48: Just wondering why this was reopened? Was there any problem with the current documentation or is this just waiting for the plugin documentation to be released? review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.0 Reporter: Marvin King Fix For: 2.0.2 Attachments: MWAR-48-maven-war-plugin[draft4-1-1].patch, MWAR-48-maven-war-plugin[draft4-1].patch, MWAR-48-maven-war-plugin[draft4].patch Time Spent: 1 day, 13 hours, 30 minutes Remaining Estimate: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79084 ] John Tolentino commented on MWAR-58: I assume this haven't been applied yet. I'll look into this and write some test cases if it doesn't have any. Same goes with MWAR-59. consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=comments#action_79085 ] John Tolentino commented on MWAR-59: Checking. I assume that this haven't been applied as well. artifact extension set incorrectly in a multi-module build -- Key: MWAR-59 URL: http://jira.codehaus.org/browse/MWAR-59 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0, 2.0.1 Reporter: Brett Porter Assigned To: John Tolentino Fix For: 2.0.2 Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt from the list... unfortunately [MWAR-38] is not fully fixed - It still does not work in a multi-module build. We do have here the following structure: root jarmodule ejb webapp Running a mvn package inside the webapp module, the EJB-Client jar from the ejb module is resolved correctly and copied to WEB-INF/lib with the correct .jar ending. Running the mvn package from the root module, the ejb-client jar from the ejb module is resolved but copied with a .ejb-client ending, and not with .jar. You can test this by using the daytrader example from the Maven book. -- 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-233) maven-scm-api bug in test cases
maven-scm-api bug in test cases --- Key: SCM-233 URL: http://jira.codehaus.org/browse/SCM-233 Project: Maven SCM Issue Type: Bug Components: maven-scm-api Affects Versions: 1.0 Reporter: John Tolentino Doing a release of an application using maven-scm will create an error when executing the tests for the maven-scm-api When it did the checkout the source was placed into the foo/target/foo-1.0/maven-scm-api directory and the test cases where executed...this resulted in an error in the ScmFileSetTest which appeared to come from the test case using */target/* in an execludes and a file not being removed or something... perhaps because of the directory path looking like /home/user/src/foo-trunk/target/foo-1.0/maven-scm-api/target/foo we need to make sure that */target/* is treated right when there are two target tokens in the path -- 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: (SCM-233) maven-scm-api bug in test cases
[ http://jira.codehaus.org/browse/SCM-233?page=all ] John Tolentino updated SCM-233: --- Attachment: SCM-233-maven-scm-api.diff This patch excludes the basedir from the filtered paths checked in the tests. maven-scm-api bug in test cases --- Key: SCM-233 URL: http://jira.codehaus.org/browse/SCM-233 Project: Maven SCM Issue Type: Bug Components: maven-scm-api Affects Versions: 1.0 Reporter: John Tolentino Assigned To: John Tolentino Attachments: SCM-233-maven-scm-api.diff Doing a release of an application using maven-scm will create an error when executing the tests for the maven-scm-api When it did the checkout the source was placed into the foo/target/foo-1.0/maven-scm-api directory and the test cases where executed...this resulted in an error in the ScmFileSetTest which appeared to come from the test case using */target/* in an execludes and a file not being removed or something... perhaps because of the directory path looking like /home/user/src/foo-trunk/target/foo-1.0/maven-scm-api/target/foo we need to make sure that */target/* is treated right when there are two target tokens in the path -- 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: (MRELEASE-141) Review Plugin Documentation
[ http://jira.codehaus.org/browse/MRELEASE-141?page=all ] John Tolentino closed MRELEASE-141. --- Resolution: Fixed Fix Version/s: 2.0 Done Review Plugin Documentation --- Key: MRELEASE-141 URL: http://jira.codehaus.org/browse/MRELEASE-141 Project: Maven 2.x Release Plugin Issue Type: Task Affects Versions: 2.0 Reporter: John Tolentino Assigned To: John Tolentino Fix For: 2.0 Original Estimate: 1 day, 7 hours Time Spent: 1 day, 8 hours Remaining Estimate: 0 minutes Add examples and FAQs, pass docck, fix navigation and home page to conform with plugin documentation standards. -- 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: (MRM-66) Repository configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] John Tolentino updated MRM-66: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Repository configuration Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: John Tolentino Fix For: 1.0-beta-1 Original Estimate: 16 hours Remaining: 16 hours A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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: (MRESOURCES-16) test resources plugin using plugin testing harness
[ http://jira.codehaus.org/browse/MRESOURCES-16?page=all ] John Tolentino closed MRESOURCES-16: Resolution: Fixed Fix Version: 2.2 Patch applied. test resources plugin using plugin testing harness -- Key: MRESOURCES-16 URL: http://jira.codehaus.org/browse/MRESOURCES-16 Project: Maven 2.x Resources Plugin Type: Test Reporter: John Tolentino Assignee: John Tolentino Fix For: 2.2 Attachments: MRESOURCES-16-maven-resource-plugin.patch -- 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: (MEJB-9) test ejb plugin using plugin testing harness
test ejb plugin using plugin testing harness Key: MEJB-9 URL: http://jira.codehaus.org/browse/MEJB-9 Project: Maven 2.x Ejb Plugin Type: Test Reporter: John Tolentino Assigned to: John Tolentino -- 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: (MWAR-12) Add resource filtering to war plugin
[ http://jira.codehaus.org/browse/MWAR-12?page=all ] John Tolentino updated MWAR-12: --- Attachment: MWAR-12-maven-war-plugin.patch Add resource filtering to war plugin Key: MWAR-12 URL: http://jira.codehaus.org/browse/MWAR-12 Project: Maven 2.x War Plugin Type: Improvement Reporter: Mark Hobson Assignee: John Tolentino Fix For: 2.0 Attachments: AbstractWarMojo.patch, MWAR-12-maven-war-plugin.patch, MWAR-12.patch, ResourcesMojo.patch, test.zip Original Estimate: 15 minutes Remaining: 15 minutes I'd like to patch the war plugin to perform resource filtering as per the resources plugin. This is a trivial patch but would duplicate the following code from the resources plugin: PropertyUtils ReflectionProperties ResourcesMojo.copyFile(File, File) These look like handy util methods that could be incorporated into plexus-utils - what do the developers think? Also not sure how resource filtering will be affected by MNG-788. -- 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: (MWAR-27) It should be possible to exclude the META-INF/maven directory from produced WARs
[ http://jira.codehaus.org/browse/MWAR-27?page=all ] John Tolentino closed MWAR-27: -- Resolution: Cannot Reproduce This is already addressed by the current version (2.0.1) of MavenArchiver, which is shared throughout Maven JAR, EAR, and WAR Plugins. Use archiveaddMavenDescriptorfalse/addMavenDescriptor/archive to exclude META-INF/maven. See http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html and org.apache.maven.archiver.MavenArchiver.createArchive() for more details. It should be possible to exclude the META-INF/maven directory from produced WARs Key: MWAR-27 URL: http://jira.codehaus.org/browse/MWAR-27 Project: Maven 2.x War Plugin Type: Improvement Reporter: Mang Lau Assignee: John Tolentino Priority: Minor Fix For: 2.0 Just like the maven-ear-plugin and the maven-jar-plugin, the maven-war-plugin should allow users to exclude the META-INF/maven directory from the produced WARs. -- 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: (MRELEASE-4) release plugin should ignore pom.xml from status check
[ http://jira.codehaus.org/browse/MRELEASE-4?page=all ] John Tolentino updated MRELEASE-4: -- Attachment: MRELEASE-4-maven-release-plugin.patch release plugin should ignore pom.xml from status check -- Key: MRELEASE-4 URL: http://jira.codehaus.org/browse/MRELEASE-4 Project: Maven 2.x Release Plugin Type: Bug Reporter: Brett Porter Assignee: John Tolentino Priority: Trivial Fix For: 2.0-beta-5 Attachments: MNG-1104-maven-release-plugin.patch, MRELEASE-4-maven-release-plugin.patch -- 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: (MWAR-21) Need a way to include limited set of webapp's dependencies
[ http://jira.codehaus.org/browse/MWAR-21?page=all ] John Tolentino closed MWAR-21: -- Resolution: Fixed Need a way to include limited set of webapp's dependencies -- Key: MWAR-21 URL: http://jira.codehaus.org/browse/MWAR-21 Project: Maven 2.x War Plugin Type: Improvement Environment: M2.0.1 Reporter: Dirk Olmes Assignee: John Tolentino Priority: Blocker Fix For: 2.0 Attachments: AbstractWarMojo.diff Time Spent: 6 hours Remaining: 0 minutes I need a way to pack a war that includes only a limited set of the webapp's dependencies. We're deploying in mainly two different environments: for testing, the webapp runs standalone and thus needs to include all its dependencies in the war. For production we deploy the webapp into a JBoss server that has all the dependencies already installed. I've modified AbstractWarMojo in the following way: 1) allow to specify dependencyIncludes an dependencyExcludes (as lists) 2) upon building the war, each dependency is checked against the excludes and the includes and will be added to the war accordingly. While this patch may not be the best way to to it, it clearly shows my requirements. -- 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: (MRAR-5) Move the description of the mojo from @description to the top of the class's comment block
[ http://jira.codehaus.org/browse/MRAR-5?page=all ] John Tolentino closed MRAR-5: - Resolution: Fixed Move the description of the mojo from @description to the top of the class's comment block -- Key: MRAR-5 URL: http://jira.codehaus.org/browse/MRAR-5 Project: Maven 2.x Rar Plugin Type: Improvement Reporter: John Tolentino Assignee: John Tolentino Attachments: maven-rar-plugin.patch Time Spent: 15 minutes Remaining: 0 minutes Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSUREFIRE-82) Move the description of the mojo from @description to the top of the class's comment block
[ http://jira.codehaus.org/browse/MSUREFIRE-82?page=all ] John Tolentino closed MSUREFIRE-82: --- Resolution: Fixed Move the description of the mojo from @description to the top of the class's comment block -- Key: MSUREFIRE-82 URL: http://jira.codehaus.org/browse/MSUREFIRE-82 Project: Maven 2.x Surefire Plugin Type: Improvement Reporter: John Tolentino Assignee: John Tolentino Attachments: maven-surefire-plugin.patch Original Estimate: 15 minutes Time Spent: 15 minutes Remaining: 0 minutes Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEAR-23) Move the description of the mojo from @description to the top of the class's comment block
[ http://jira.codehaus.org/browse/MEAR-23?page=all ] John Tolentino updated MEAR-23: --- Fix Version: 2.2 Move the description of the mojo from @description to the top of the class's comment block -- Key: MEAR-23 URL: http://jira.codehaus.org/browse/MEAR-23 Project: Maven 2.x Ear Plugin Type: Improvement Reporter: John Tolentino Assignee: John Tolentino Fix For: 2.2 Attachments: maven-ear-plugin.patch Original Estimate: 15 minutes Time Spent: 15 minutes Remaining: 0 minutes Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRESOURCES-14) Move the description of the mojo from @description to the top of the class's comment block
[ http://jira.codehaus.org/browse/MRESOURCES-14?page=all ] John Tolentino updated MRESOURCES-14: - Fix Version: 2.2 Move the description of the mojo from @description to the top of the class's comment block -- Key: MRESOURCES-14 URL: http://jira.codehaus.org/browse/MRESOURCES-14 Project: Maven 2.x Resources Plugin Type: Improvement Reporter: John Tolentino Assignee: John Tolentino Fix For: 2.2 Attachments: maven-resources-plugin.patch Original Estimate: 15 minutes Time Spent: 15 minutes Remaining: 0 minutes Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTRUN-46) Move the description of the mojo from @description to the top of the class's comment block
Move the description of the mojo from @description to the top of the class's comment block -- Key: MANTRUN-46 URL: http://jira.codehaus.org/browse/MANTRUN-46 Project: Maven 2.x Antrun Plugin Type: Improvement Reporter: John Tolentino Assigned to: John Tolentino Attachments: maven-antrun-plugin.patch Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEJB-8) Move the description of the mojo from @description to the top of the class's comment block
Move the description of the mojo from @description to the top of the class's comment block -- Key: MEJB-8 URL: http://jira.codehaus.org/browse/MEJB-8 Project: Maven 2.x Ejb Plugin Type: Improvement Reporter: John Tolentino Assigned to: John Tolentino Attachments: maven-ejb-plugin.patch Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRAR-5) Move the description of the mojo from @description to the top of the class's comment block
Move the description of the mojo from @description to the top of the class's comment block -- Key: MRAR-5 URL: http://jira.codehaus.org/browse/MRAR-5 Project: Maven 2.x Rar Plugin Type: Improvement Reporter: John Tolentino Assigned to: John Tolentino Attachments: maven-rar-plugin.patch Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSUREFIRE-82) Move the description of the mojo from @description to the top of the class's comment block
Move the description of the mojo from @description to the top of the class's comment block -- Key: MSUREFIRE-82 URL: http://jira.codehaus.org/browse/MSUREFIRE-82 Project: Maven 2.x Surefire Plugin Type: Improvement Reporter: John Tolentino Assigned to: John Tolentino Attachments: maven-surefire-plugin.patch Maven gets the description of the mojo from the comment block of the class instead of the @description javadoc tag. The site generated therefore either has No description. or an incomplete description of the mojo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-26) Do not overwrite target unless source is modified
[ http://jira.codehaus.org/browse/MWAR-26?page=comments#action_61556 ] John Tolentino commented on MWAR-26: Maven 2.0.3 was already voted on for release. That email was sent by John Casey to maven developers list, subject is [vote] Release Maven 2.0.3 (third RC). So the libraries used in that 2.0.3 won't have any more changes. There will still be a patch for maven-war-plugin in time for its 2.0 release though. Instead of having the code in plexus-utils, it will be in the war plugin. We'll just have to apply the first patch when maven changes the plexus-utils version that it uses to 1.2. Do not overwrite target unless source is modified - Key: MWAR-26 URL: http://jira.codehaus.org/browse/MWAR-26 Project: Maven 2.x War Plugin Type: Bug Reporter: Andres March Assignee: John Tolentino Fix For: 2.0 Attachments: MWAR-26-maven-war-plugin-2.diff, MWAR-26-maven-war-plugin.diff Time Spent: 3 hours, 40 minutes Remaining: 0 minutes I thought MWAR-8 had fixed my issue but it seems to still exist. Correct me if I'm wrong but doing incremental builds with this war plugin is not possible. All the web app sources get overwritten regardless if they have been modified or not. Incremental build were possible in Maven 1 because it was ANT based. This version uses plexus FileUtils which overwrites without regard to if the target file exists or older than the source. Besides the time issue, overwriting the web.xml each time makes my context reload since the context runs on tomcat from the target location. I think this is a reasonable configuration but if there is a better way, let me know. Building inplace wars is not an option as it dirties the source. If we are in agreement, I may be able to provide a patch. -- 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: (MWAR-26) Do not overwrite target unless source is modified
[ http://jira.codehaus.org/browse/MWAR-26?page=all ] John Tolentino updated MWAR-26: --- Attachment: MWAR-26-maven-war-plugin-2.diff Do not overwrite target unless source is modified - Key: MWAR-26 URL: http://jira.codehaus.org/browse/MWAR-26 Project: Maven 2.x War Plugin Type: Bug Reporter: Andres March Assignee: John Tolentino Fix For: 2.0 Attachments: MWAR-26-maven-war-plugin-2.diff, MWAR-26-maven-war-plugin.diff Time Spent: 3 hours, 40 minutes Remaining: 0 minutes I thought MWAR-8 had fixed my issue but it seems to still exist. Correct me if I'm wrong but doing incremental builds with this war plugin is not possible. All the web app sources get overwritten regardless if they have been modified or not. Incremental build were possible in Maven 1 because it was ANT based. This version uses plexus FileUtils which overwrites without regard to if the target file exists or older than the source. Besides the time issue, overwriting the web.xml each time makes my context reload since the context runs on tomcat from the target location. I think this is a reasonable configuration but if there is a better way, let me know. Building inplace wars is not an option as it dirties the source. If we are in agreement, I may be able to provide a patch. -- 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: (MWAR-26) Do not overwrite target unless source is modified
[ http://jira.codehaus.org/browse/MWAR-26?page=all ] John Tolentino updated MWAR-26: --- Attachment: MWAR-26-maven-war-plugin.diff Do not overwrite target unless source is modified - Key: MWAR-26 URL: http://jira.codehaus.org/browse/MWAR-26 Project: Maven 2.x War Plugin Type: Bug Reporter: Andres March Assignee: John Tolentino Fix For: 2.0 Attachments: MWAR-26-maven-war-plugin.diff Time Spent: 1 hour, 40 minutes Remaining: 0 minutes I thought MWAR-8 had fixed my issue but it seems to still exist. Correct me if I'm wrong but doing incremental builds with this war plugin is not possible. All the web app sources get overwritten regardless if they have been modified or not. Incremental build were possible in Maven 1 because it was ANT based. This version uses plexus FileUtils which overwrites without regard to if the target file exists or older than the source. Besides the time issue, overwriting the web.xml each time makes my context reload since the context runs on tomcat from the target location. I think this is a reasonable configuration but if there is a better way, let me know. Building inplace wars is not an option as it dirties the source. If we are in agreement, I may be able to provide a patch. -- 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: (MWAR-26) Do not overwrite target unless source is modified
[ http://jira.codehaus.org/browse/MWAR-26?page=comments#action_61081 ] John Tolentino commented on MWAR-26: Almost done but still doing unit tests. Will definitely have a patch ready by tomorrow. Do not overwrite target unless source is modified - Key: MWAR-26 URL: http://jira.codehaus.org/browse/MWAR-26 Project: Maven 2.x War Plugin Type: Bug Reporter: Andres March Assignee: John Tolentino Fix For: 2.0 I thought MWAR-8 had fixed my issue but it seems to still exist. Correct me if I'm wrong but doing incremental builds with this war plugin is not possible. All the web app sources get overwritten regardless if they have been modified or not. Incremental build were possible in Maven 1 because it was ANT based. This version uses plexus FileUtils which overwrites without regard to if the target file exists or older than the source. Besides the time issue, overwriting the web.xml each time makes my context reload since the context runs on tomcat from the target location. I think this is a reasonable configuration but if there is a better way, let me know. Building inplace wars is not an option as it dirties the source. If we are in agreement, I may be able to provide a patch. -- 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: (MWAR-24) [PATCH] Add ability to specify context.xml file in plugin configuration
[ http://jira.codehaus.org/browse/MWAR-24?page=comments#action_60986 ] John Tolentino commented on MWAR-24: I agree. But since the full path with filename is specified, we can substitute other container config's path to the context.xml path right? So a non-container-specific solution would be calling the parameter as containerConfig (or something similar) instead. [PATCH] Add ability to specify context.xml file in plugin configuration --- Key: MWAR-24 URL: http://jira.codehaus.org/browse/MWAR-24 Project: Maven 2.x War Plugin Type: New Feature Versions: 2.0 Reporter: Kris Nuttycombe Assignee: John Tolentino Fix For: 2.0 Attachments: contextXml.patch Time Spent: 2 hours, 30 minutes Remaining: 0 minutes The context.xml file for a web application may require configuration specific to the deployment environment of the webapp, and consequently should be able to be treated like the web.xml file in allowing the location of the context.xml file to be used in the webapp to be specified by a plugin configuration parameter. This patch basically duplicates the replacement functionality provided for the web.xml file for META-INF/context.xml. This patch also provides a minor bugfix to ensure that values of the webXml and contextXml parameters do not accept whitespace as valid values. -- 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: (MWAR-24) [PATCH] Add ability to specify context.xml file in plugin configuration
[ http://jira.codehaus.org/browse/MWAR-24?page=all ] John Tolentino reopened MWAR-24: Rename parameter to a non-container specific identifier. [PATCH] Add ability to specify context.xml file in plugin configuration --- Key: MWAR-24 URL: http://jira.codehaus.org/browse/MWAR-24 Project: Maven 2.x War Plugin Type: New Feature Versions: 2.0 Reporter: Kris Nuttycombe Assignee: John Tolentino Fix For: 2.0 Attachments: contextXml.patch Time Spent: 2 hours, 30 minutes Remaining: 0 minutes The context.xml file for a web application may require configuration specific to the deployment environment of the webapp, and consequently should be able to be treated like the web.xml file in allowing the location of the context.xml file to be used in the webapp to be specified by a plugin configuration parameter. This patch basically duplicates the replacement functionality provided for the web.xml file for META-INF/context.xml. This patch also provides a minor bugfix to ensure that values of the webXml and contextXml parameters do not accept whitespace as valid values. -- 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: (MWAR-24) [PATCH] Add ability to specify context.xml file in plugin configuration
[ http://jira.codehaus.org/browse/MWAR-24?page=all ] John Tolentino updated MWAR-24: --- Attachment: MWAR-24-maven-war-plugin.diff [PATCH] Add ability to specify context.xml file in plugin configuration --- Key: MWAR-24 URL: http://jira.codehaus.org/browse/MWAR-24 Project: Maven 2.x War Plugin Type: New Feature Versions: 2.0 Reporter: Kris Nuttycombe Assignee: John Tolentino Fix For: 2.0 Attachments: MWAR-24-maven-war-plugin.diff, contextXml.patch Time Spent: 2 hours, 30 minutes Remaining: 0 minutes The context.xml file for a web application may require configuration specific to the deployment environment of the webapp, and consequently should be able to be treated like the web.xml file in allowing the location of the context.xml file to be used in the webapp to be specified by a plugin configuration parameter. This patch basically duplicates the replacement functionality provided for the web.xml file for META-INF/context.xml. This patch also provides a minor bugfix to ensure that values of the webXml and contextXml parameters do not accept whitespace as valid values. -- 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
