[jira] Commented: (MNG-1975) EAR project depends on WAR that doesn't exist, but it builds succesfully
[ http://jira.codehaus.org/browse/MNG-1975?page=comments#action_67910 ] Stephane Nicoll commented on MNG-1975: -- John, I don't think so. See the previous comment. > EAR project depends on WAR that doesn't exist, but it builds succesfully > > > Key: MNG-1975 > URL: http://jira.codehaus.org/browse/MNG-1975 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.2 > Environment: Debian GNU/Linux Etch (Testing), Eclipse WTP 1.0 > Reporter: Duncan Doyle > Fix For: 2.0.5 > > > While I was testing the features of Maven 2.0.1 and 2.0.2 I noticed the > following. > When specifying the correct version of my WAR project as a dependency in my > EAR pom.xml, the EAR file is generated correctly during a "mvn install" on my > SuperPom. However, when I specify a wrong WAR version number (a non-existing > one) in the dependency of my EAR Pom, the build still succeeds and an EAR > file is generated. I'm doing this just as a test. I would expect the build to > fail when the EAR project can't find the WAR file it depends on, but instead > it gives a message that it can't find the WAR file in the local repository > and remote repository and uses the generated WAR file (that is created before > the EAR file is created), which has the wrong version number, to create the > EAR package. > This my super pom.xml: > > 4.0.0 > Tour de France Service > nl.doyle.mccloud.TourDeFranceService > 0.0.1 > TourDeFranceService > pom > > ../TourDeFranceServiceEAR >../TourDeFranceServiceWeb > > > This my WAR pom.xml: > > 4.0.0 > Tour de France Service Web > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceWeb > war > 0.0.2 > > > junit > junit > 3.8.1 > test > > > > > >org.apache.maven.plugins >maven-war-plugin > > ../TourDeFranceServiceWeb/WebContent/WEB-INF/web.xml > > > >TourDeFranceServiceWeb > > > And this my EAR pom.xml with the wrong version number of the WAR project: > > 4.0.0 > Tour de France Service EAR > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceEAR > ear > 0.0.1 > > > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceWeb > war > 1.0.2 > > > > TourDeFranceServiceEAR > > > This is part of the message that "mvn install" gives me: > Downloading: > http://repo1.maven.org/maven2/nl/doyle/mccloud/TourDeFranceService/TourDeFranceServiceWeb/1.0.2/TourDeFranceServiceWeb-1.0.2.pom > [WARNING] Unable to get resource from repository central > (http://repo1.maven.org/maven2) > [INFO] [ear:generate-application-xml] > [INFO] Generating application.xml > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [ear:ear] > [INFO] Copying > artifact[war:nl.doyle.mccloud.TourDeFranceService:TourDeFranceServiceWeb:1.0.2] > to[TourDeFranceServiceWeb.war] > How can it copy an artifact that doesn't exist??? The 1.0.2 version of my WAR > file doesn't exist in my local repository and the WAR file in my Enterprise > project has a different version number!!! -- 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-33) jars with differents versions can be in WEB-INF/lib with war as dependencies
[ http://jira.codehaus.org/browse/MWAR-33?page=comments#action_67907 ] Olivier Lamy commented on MWAR-33: -- Why not using Set artifacts = project.getArtifacts(); And get dependencies of the artifacts with type war. But I think in case of war type transitive dependencies are not resolved. I don't know exactly but I think there is an issue in MNG. With all jars in WEB-INF will come from poms dependencies declaration. IMHO, it's the best and cleaner solution ? With this I'm sure to have the same classpath when I try a junit and when I build my war. -- Olivier > jars with differents versions can be in WEB-INF/lib with war as dependencies > > > Key: MWAR-33 > URL: http://jira.codehaus.org/browse/MWAR-33 > Project: Maven 2.x War Plugin > Type: Bug > Environment: all > Reporter: Olivier Lamy > Fix For: 2.1 > > Original Estimate: 15 minutes >Time Spent: 30 minutes > Remaining: 0 minutes > > My pom has the following dependencies : > - log4j:log4j:1.2.13 > - a war with log4j:log4j:1.2.11 included > Result the two jars are in WEB-INF/lib. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-708) Continuum can not correctly locate modules for multiple module maven 2 projects.
[ http://jira.codehaus.org/browse/CONTINUUM-708?page=comments#action_67905 ] Derek MacKie commented on CONTINUUM-708: I am having the same problem in a windows xp sp2, cvsnt, cvs, environment. My project structure is identical to the one described in this issue. > Continuum can not correctly locate modules for multiple module maven 2 > projects. > > > Key: CONTINUUM-708 > URL: http://jira.codehaus.org/browse/CONTINUUM-708 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.3 > Environment: Windows 2000, CVS running on windows > Reporter: Paul Grove > > > We have a Maven 2 project with mutiple modules we call this the reactor > project with the reactor POM. We have the below directory structure for > development > brokerApp > | > |POM.xml (reactor pom) > | > |-webapp1 > ||-POM.xml > | > |-coreAPI > ||-POM.xml > | > |-appEAR > ||-POM.xml > groupId = com..conceptlabs.brokerApp > In the reactor POM we have the following modules > > webapp1 > coreAPI > appEAR > > When we build and deploy from the Maven 2 reactor POM, we get the following > directory structure in our Maven 2 repository. > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/ > > Under this root we have the following > |-brokerApp > ||-1.0-SNAPSHOT > | |-brokerApp-1.0-20060523.162030-1.pom > | > |-webapp1 > ||-1.0-SNAPSHOT > | |-webapp1-1.0-20060523.162030-1.pom > | > |-coreAPI > ||-1.0-SNAPSHOT > ||-coreAPI-1.0-20060523.162030-1.pom > | > |-appEAR > ||-1.0-SNAPSHOT > ||-appEAR-1.0-20060523.162030-1.pom > Continuum can not correctly locate modules for multiple module maven 2 > projects. > This is the proper location as produced by doing a Maven 2 mvn deploy > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/webapp1/1.0-SNAPSHOT/webapp1-1.0-20060523.162030-1.pom > but Continuum for some reason looks here? > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/brokerApp/1.0-SNAPSHOT/brokerApp-1.0-20060523.1620/webapp1/pom.xml: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-38) NPE when developer section does not include an id
[ http://jira.codehaus.org/browse/MCHANGELOG-38?page=comments#action_67904 ] Baerrach bonDierne commented on MCHANGELOG-38: -- org.codehaus.mojo changelog-maven-plugin Is the plugin I am using. I hadn't committed the changes into CVS before trying on the integration server. > NPE when developer section does not include an id > - > > Key: MCHANGELOG-38 > URL: http://jira.codehaus.org/browse/MCHANGELOG-38 > Project: Maven 2.x Changelog Plugin > Type: Bug > Reporter: Baerrach bonDierne > Priority: Critical > > > [DEBUG] Trace > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:398) > at > org.apache.maven.changelog.ChangeLog.getUserList(ChangeLog.java:530) > at > org.apache.maven.changelog.ChangeLog.replaceAuthorIdWithName(ChangeLog.java:541) > at org.apache.maven.changelog.ChangeLog.doExecute(ChangeLog.java:370) > at > org.apache.maven.changelog.ChangeLogReport.getChangeLog(ChangeLogReport.java:263) > at > org.apache.maven.changelog.ChangeLogReport.generateChangeSetsFromSCM(ChangeLogReport.java:218) > at > org.apache.maven.changelog.ChangeLogReport.getChangedSets(ChangeLogReport.java:198) > at > org.apache.maven.changelog.ChangeLogReport.executeReport(ChangeLogReport.java:173) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) > This is easy to replicate, find a working "mvn site" and then remove an id > from a developer. > This is for plugin > org.apache.maven.plugins > maven-changelog-plugin > I'd like to provide version details but this plugin isn't in my repository! > So I am not sure how it is actually working. > The website does't point to a repository, and I accidentally found it at > http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-changelog-plugins > but this code doesn't match up with the error message. > I couldn't find the code base from the the old codehaus repository either. -- 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: (MCHANGELOG-38) NPE when developer section does not include an id
NPE when developer section does not include an id - Key: MCHANGELOG-38 URL: http://jira.codehaus.org/browse/MCHANGELOG-38 Project: Maven 2.x Changelog Plugin Type: Bug Reporter: Baerrach bonDierne Priority: Critical [DEBUG] Trace java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:398) at org.apache.maven.changelog.ChangeLog.getUserList(ChangeLog.java:530) at org.apache.maven.changelog.ChangeLog.replaceAuthorIdWithName(ChangeLog.java:541) at org.apache.maven.changelog.ChangeLog.doExecute(ChangeLog.java:370) at org.apache.maven.changelog.ChangeLogReport.getChangeLog(ChangeLogReport.java:263) at org.apache.maven.changelog.ChangeLogReport.generateChangeSetsFromSCM(ChangeLogReport.java:218) at org.apache.maven.changelog.ChangeLogReport.getChangedSets(ChangeLogReport.java:198) at org.apache.maven.changelog.ChangeLogReport.executeReport(ChangeLogReport.java:173) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) This is easy to replicate, find a working "mvn site" and then remove an id from a developer. This is for plugin org.apache.maven.plugins maven-changelog-plugin I'd like to provide version details but this plugin isn't in my repository! So I am not sure how it is actually working. The website does't point to a repository, and I accidentally found it at http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-changelog-plugins but this code doesn't match up with the error message. I couldn't find the code base from the the old codehaus repository either. -- 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-954) Please upload commons-jelly-tags-interaction-1.1
Please upload commons-jelly-tags-interaction-1.1 Key: MAVENUPLOAD-954 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-954 Project: maven-upload-requests Type: Task Reporter: Lukas Theussl -- 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: (SUREFIRE-31) support junit 4.0
[ http://jira.codehaus.org/browse/SUREFIRE-31?page=comments#action_67895 ] Nicole Tedesco commented on SUREFIRE-31: Is there anything I can do to make this happen? > support junit 4.0 > - > > Key: SUREFIRE-31 > URL: http://jira.codehaus.org/browse/SUREFIRE-31 > Project: surefire > Type: Improvement > Reporter: John Didion > Attachments: surefire-junit4.zip > > > I know this is a pretty sizable task. I just wanted to get it in the system > now that 4.0 has officially been released. Hopefully this will generate some > discussion about how 4.0 will be handled - mainly if it will require a > completely seperate implemenation of surefire (keeping the same API so it can > easily be used by the maven plugin), or if use of 4.0 will be made a > configurable option of the current surefire. > Here's some additional features I'd like to see: > 1. Ability to categorize tests. Unfortunately, 4.0 doesn't include an > @Category annotation, or make category a parameter of @Test. However, the > filtering mechanism provided by 4.0 is sufficent to support categories given > the presense of such an annotation. I recommend putting the @Category > annotation in a seperate module (surefire-annotations?) and build support for > it into surefire. Hopefully the junit guys could be convinced to incorporate > it in a later version. > 2. Similarly, support repeated tests via an @Repeated annotation. I'm not > sure how easy this would be to do external to junit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-547) build results cannot be accessed from xmlrpc
[ http://jira.codehaus.org/browse/CONTINUUM-547?page=comments#action_67883 ] Andrew Williams commented on CONTINUUM-547: --- the patch to DefaultContinuumXmlRpc.java on http://jira.codehaus.org/browse/CONTINUUM-732 enables the method getBuildResultsForProject which summarises all build results. I plan to add another to get the details (changes, output etc) if this one gets accepted. Hope it helps > build results cannot be accessed from xmlrpc > > > Key: CONTINUUM-547 > URL: http://jira.codehaus.org/browse/CONTINUUM-547 > Project: Continuum > Type: Bug > Components: XMLRPC Interface > Reporter: Milos Kleint > > > calls to getProjects() or getProject(id) never return any build results... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-732) Add dependencies to the python code in continuum-core-it
[ http://jira.codehaus.org/browse/CONTINUUM-732?page=comments#action_67882 ] Andrew Williams commented on CONTINUUM-732: --- OK - so I just uploaded 2 more patches (the old core-it.patch is now out of date) this adds BuildResults listing to what we previously supported > Add dependencies to the python code in continuum-core-it > > > Key: CONTINUUM-732 > URL: http://jira.codehaus.org/browse/CONTINUUM-732 > Project: Continuum > Type: Improvement > Components: XMLRPC Interface > Environment: Linux Debian, python 2.3 > Reporter: Andrew Williams > Fix For: 1.1 > Attachments: DefaultContinuumXmlRpc_java.patch, core-it.patch, core-it.patch > > > The attatched patch fixes up continuum-core-it python code to work agains the > current (as of 1.0.3) version of the XMLRPC. > It adds dependency support. > The buldResults portion is commented out as it does not work now - I will fix > that next (needs work to the XMLRPC implementation first) -- 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: (CONTINUUM-732) Add dependencies to the python code in continuum-core-it
[ http://jira.codehaus.org/browse/CONTINUUM-732?page=all ] Andrew Williams updated CONTINUUM-732: -- Attachment: DefaultContinuumXmlRpc_java.patch > Add dependencies to the python code in continuum-core-it > > > Key: CONTINUUM-732 > URL: http://jira.codehaus.org/browse/CONTINUUM-732 > Project: Continuum > Type: Improvement > Components: XMLRPC Interface > Environment: Linux Debian, python 2.3 > Reporter: Andrew Williams > Fix For: 1.1 > Attachments: DefaultContinuumXmlRpc_java.patch, core-it.patch, core-it.patch > > > The attatched patch fixes up continuum-core-it python code to work agains the > current (as of 1.0.3) version of the XMLRPC. > It adds dependency support. > The buldResults portion is commented out as it does not work now - I will fix > that next (needs work to the XMLRPC implementation first) -- 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: (CONTINUUM-732) Add dependencies to the python code in continuum-core-it
[ http://jira.codehaus.org/browse/CONTINUUM-732?page=all ] Andrew Williams updated CONTINUUM-732: -- Attachment: core-it.patch > Add dependencies to the python code in continuum-core-it > > > Key: CONTINUUM-732 > URL: http://jira.codehaus.org/browse/CONTINUUM-732 > Project: Continuum > Type: Improvement > Components: XMLRPC Interface > Environment: Linux Debian, python 2.3 > Reporter: Andrew Williams > Fix For: 1.1 > Attachments: core-it.patch, core-it.patch > > > The attatched patch fixes up continuum-core-it python code to work agains the > current (as of 1.0.3) version of the XMLRPC. > It adds dependency support. > The buldResults portion is commented out as it does not work now - I will fix > that next (needs work to the XMLRPC implementation first) -- 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: (MNG-1956) profile build without pluginManagement fails if pom build has pluginManagement
[ http://jira.codehaus.org/browse/MNG-1956?page=all ] John Casey updated MNG-1956: Fix Version: 2.0.5 > profile build without pluginManagement fails if pom build has pluginManagement > -- > > Key: MNG-1956 > URL: http://jira.codehaus.org/browse/MNG-1956 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0.1 > Reporter: Shinobu Kawai > Fix For: 2.0.5 > Attachments: pom.xml > > > If the build sections has a pluginManagement, profiles without > pluginManagement fails with the following: > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.project.injection.DefaultProfileInjector.injectPlugins(DefaultProfileInjector.java:147) > at > org.apache.maven.project.injection.DefaultProfileInjector.injectBuild(DefaultProfileInjector.java:134) > at > org.apache.maven.project.injection.DefaultProfileInjector.inject(DefaultProfileInjector.java:80) > at > org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfiles(DefaultMavenProjectBuilder.java:1037) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:838) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:594) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > 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) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Jan 11 16:29:00 PST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > > Attached is a sample pom.xml to reproduce. > Workaround is to put an empty in the profile build. -- 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: (MNG-2177) moved mojo plugins are missing web pages at http://maven.apache.org/plugins
[ http://jira.codehaus.org/browse/MNG-2177?page=all ] John Casey updated MNG-2177: Fix Version: 2.0.5 > moved mojo plugins are missing web pages at http://maven.apache.org/plugins > --- > > Key: MNG-2177 > URL: http://jira.codehaus.org/browse/MNG-2177 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Reporter: John Allen > Fix For: 2.0.5 > > > From: http://maven.apache.org/plugins > Changelog plugin link (http://mojo.codehaus.org/changelog-maven-plugin) > Redirects to http://maven.apache.org/plugins/maven-changelog-plugin > Which displays the maven 404 page > Same applies to the other moved codehaus mojo plugin links -- 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: (MNG-1998) the archetype command for creating a plugin got removed from the java plugin guide
[ http://jira.codehaus.org/browse/MNG-1998?page=all ] John Casey updated MNG-1998: Fix Version: 2.0.5 > the archetype command for creating a plugin got removed from the java plugin > guide > -- > > Key: MNG-1998 > URL: http://jira.codehaus.org/browse/MNG-1998 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: 2.0.2 > Reporter: Brian Fox > Fix For: 2.0.5 > > > I am pretty sure it used to be here, but it's gone now. This is a major first > hurdle to plugin development. -- 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: (MNG-346) Periodic cleanup of logs and builds
[ http://jira.codehaus.org/browse/MNG-346?page=all ] John Casey updated MNG-346: --- Fix Version: 2.0.5 > Periodic cleanup of logs and builds > --- > > Key: MNG-346 > URL: http://jira.codehaus.org/browse/MNG-346 > Project: Maven 2 > Type: Task > Reporter: Brett Porter > Fix For: 2.0.5 > > > the m2-build-logs and distributions from ci.sh are a bit out of control in > /home/projects/maven/public_html/ - setup a periodic purge. -- 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: (MNG-2152) pom.xml and pom.properties in JAR file causes JBOSS SARDeployer to fail.
[ http://jira.codehaus.org/browse/MNG-2152?page=all ] John Casey updated MNG-2152: Fix Version: 2.0.5 > pom.xml and pom.properties in JAR file causes JBOSS SARDeployer to fail. > > > Key: MNG-2152 > URL: http://jira.codehaus.org/browse/MNG-2152 > Project: Maven 2 > Type: Bug > Components: POM, Plugin API > Versions: 2.0.1 > Environment: Windows, JBOSS-4.0.1sp1 > Reporter: Walt Barrow > Fix For: 2.0.5 > Attachments: ESS-PD-1.1-DEV.sar > > > I am creating a JAR file which is then packaged into JBOSS MBean Service > Archives (SARs). When the JAR file is created it contains the following > files: > META-INF\maven\SJL\WorkflowManagerMBean\pom.xml > META-INF\maven\SJL\WorkflowManagerMBean\pom.properties > The JAR file is then embedded into a SAR file which is nothing more than a > JAR file with a ".sar" extension plus a special jboss-service.xml file. > When I try to deploy the SAR to JBOSS, it fails because it cannot resolve the > classloader for the classes in the JAR file. When I remove the pom.xml file > from the embedded JAR file, then the SAR file deploys properly. > Is this a known issue? Is there any way to surpress the inclusion of the > pom.xml file in the target JAR file? > Perhaps there should be a mechanism to surpress such information should the > need arise. > Thank you! -- 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: (MNG-1256) antlib + http based repository + version range errors badly
[ http://jira.codehaus.org/browse/MNG-1256?page=all ] John Casey updated MNG-1256: Fix Version: 2.0.5 > antlib + http based repository + version range errors badly > --- > > Key: MNG-1256 > URL: http://jira.codehaus.org/browse/MNG-1256 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Environment: maven 2.0 (release), antlib, ant, apache 2 webserver on windows > Reporter: spencer portee > Priority: Critical > Fix For: 2.0.5 > > > In my pom file, I have a dependency, it has no child dependencies beyond that > looks like this: > >org.sporty >xwork >[1.0.5,1.1) >runtime > > and use the following in my build script: > pathId="project.classpath.runtime"> > > layout="default" /> > > The variable I have above is being set right per tests 1-3. The last test.. > it gets strange. > I deployed xwork, as an empty jar by accident, so don't be surprised there's > nothing in the jar. But the dependency downloading from the webserver breaks > horribly. I tested 4 scenarios: > 1. If I put in my pom as my remote repository as file://c:/temp/repository > and deploy to there, the above pom works flawlessly. > 2 & 3. If I replace the range w/ a simple: 1.0.5 and set > my repository to http://sporty.org/java/repository, it downloads fine as > well. It works with the filesystem remote repository of my c:/temp... > directory. > 4. If I use the http repository AND use a range version as I originally > wanted, I get an ugly error: > C:\development\eclipse 3.0\workspace\hibernate-3\common.xml:4: Unable to > resolve > artifact: Unable to get dependency information: Unable to read local copy of > me > tadata: Cannot read metadata from 'C:\Documents and > Settings\sportee\.m2\reposit > ory\org\sporty\xwork\maven-metadata-remote.xml': end tag name must > match > start tag name from line 11 (position: START_TAG seen ... > 11-Oct-2005 17:52- \n... @11:11) > org.sporty:xwork:null:jar > from the specified remote repositories: > remote (http://sporty.org/java/repository ) > Path to dependency: > 1) org.sporty:xdoclet-xwork:jar:1.0-SNAPSHOT > -- > The contents of the ...-remote.xml file, I see a directory listing, and not > the contents of the repository file on the server. My naive guess is the > repository file to look for is getting lost, or not passed, if it's in a > hashmap, not being referenced properly... > Thanks, > -s -- 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: (MNG-1820) ant plugin cannot download uberjar artifacts from a maven 1.x repository
[ http://jira.codehaus.org/browse/MNG-1820?page=all ] John Casey updated MNG-1820: Fix Version: 2.0.5 > ant plugin cannot download uberjar artifacts from a maven 1.x repository > > > Key: MNG-1820 > URL: http://jira.codehaus.org/browse/MNG-1820 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0 > Reporter: Tim Clemons > Fix For: 2.0.5 > > > On listing an uberjar artifact as a depedency, the ant task attempts to grab > the artifact with a suffix of 'uberjar'. However, uberjars have the artifact > suffix of 'jar'. > So a depency like the following: > type="uberjar"/> > Attempts the following: > [artifact:dependencies] Downloading: foo/uberjars/bar-1.0-SNAPSHOT.uberjar > [artifact:dependencies] [WARNING] Unable to get resource from repository > remote (http://foobar.com:8080/repository) > [artifact:dependencies] An error has occurred while processing the Maven > artifact tasks. > [artifact:dependencies] Diagnosis: > [artifact:dependencies] > [artifact:dependencies] Dependency not found: Unable to download the artifact > from any repository > [artifact:dependencies] foo:bar:1.0-SNAPSHOT:uberjar -- 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: (MNG-1935) artifact:dependencies does not respect in the generated classpath the order of the dependencies
[ http://jira.codehaus.org/browse/MNG-1935?page=all ] John Casey updated MNG-1935: Fix Version: 2.0.5 > artifact:dependencies does not respect in the generated classpath the order > of the dependencies > --- > > Key: MNG-1935 > URL: http://jira.codehaus.org/browse/MNG-1935 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Environment: Windows 2005 > Ant 1.6.5 > JDK 1.4.2_10 > Reporter: Aurélien Lacenaire > Priority: Critical > Fix For: 2.0.5 > > > For example, if I put the dependencies in this order, in the generated > classpath (dependency.classpath) the order of the jars seems to be different : > filesetId="dependency.fileset" useScope="runtime"> > > > > > > the order in the generated classpath dependency.classpath is not the same as : > > > > > > And my projects have to use those jars in a specific order, otherwhise the > build fails. -- 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: (MNG-2117) Update doap file descriptor
[ http://jira.codehaus.org/browse/MNG-2117?page=all ] John Casey updated MNG-2117: Fix Version: 2.0.5 > Update doap file descriptor > --- > > Key: MNG-2117 > URL: http://jira.codehaus.org/browse/MNG-2117 > Project: Maven 2 > Type: Task > Components: Sites & Reporting > Versions: 2.0.3 > Reporter: Emmanuel Venisse > Fix For: 2.0.5 > > -- 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: (MNG-2153) Updated resource bundles for pl and en locales
[ http://jira.codehaus.org/browse/MNG-2153?page=all ] John Casey updated MNG-2153: Fix Version: 2.0.5 > Updated resource bundles for pl and en locales > -- > > Key: MNG-2153 > URL: http://jira.codehaus.org/browse/MNG-2153 > Project: Maven 2 > Type: Improvement > Reporter: Jacek Laskowski > Fix For: 2.0.5 > Attachments: messages.patch > > > Attached you can find updated resource bundles for pl and en locales that > belong to components/maven-core module. -- 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: (MNG-2352) Upgrade to plexus-container-default-alpha-10
[ http://jira.codehaus.org/browse/MNG-2352?page=all ] John Casey updated MNG-2352: Fix Version: 2.0.5 > Upgrade to plexus-container-default-alpha-10 > > > Key: MNG-2352 > URL: http://jira.codehaus.org/browse/MNG-2352 > Project: Maven 2 > Type: Improvement > Reporter: Jerome Lacoste > Priority: Blocker > Fix For: 2.0.5 > Attachments: MNG-2352.diff > > > This is required for MNG-2201 in particular. -- 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: (MASSEMBLY-120) ModuleSet/Binaries include/exclude not implemented
[ http://jira.codehaus.org/browse/MASSEMBLY-120?page=all ] John Casey closed MASSEMBLY-120: Resolution: Fixed should be fixed in svn, but I'm having some trouble deploying a new snapshot...waiting for Dan Tran to fix the permissions on the repo. > ModuleSet/Binaries include/exclude not implemented > -- > > Key: MASSEMBLY-120 > URL: http://jira.codehaus.org/browse/MASSEMBLY-120 > Project: Maven 2.x Assembly Plugin > Type: Bug > Versions: 2.1 > Environment: linux (fedora core 5) / maven 2.0.4 / java 1.5 > Reporter: Simon Goodall > Assignee: John Casey > > > The binaries section of moduleSet has an include / exclude section defined, > but it is not implemented. Currently a module can only include all or none of > its dependencies (through the includeDependencies tag). There is no selective > inclusion/exclusion of dependencies. -- 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: (MNG-2094) need comprehensive docs on the snapshot mechanism
[ http://jira.codehaus.org/browse/MNG-2094?page=all ] John Casey updated MNG-2094: Fix Version: 2.0.5 > need comprehensive docs on the snapshot mechanism > - > > Key: MNG-2094 > URL: http://jira.codehaus.org/browse/MNG-2094 > Project: Maven 2 > Type: Task > Components: Documentation: Faqs > Reporter: Brett Porter > Fix For: 2.0.5 > > > I need to document how it works, what it's limitations are. This should go > down to explaining the metadata and is aimed at the "power user". > We also need some general FAQs for people attempting common practices in > conversion - JARs in SVN and how to get them into a repository regularly, > dealing with m1 repos, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2125) [doc] when and how to define plugins in a pom
[ http://jira.codehaus.org/browse/MNG-2125?page=all ] John Casey updated MNG-2125: Fix Version: 2.0.5 > [doc] when and how to define plugins in a pom > - > > Key: MNG-2125 > URL: http://jira.codehaus.org/browse/MNG-2125 > Project: Maven 2 > Type: Improvement > Components: POM, Plugins and Lifecycle, Documentation: Faqs, Design, > Patterns & Best Practices > Reporter: Brett Porter > Fix For: 2.0.5 > > > some simple rules to document > 1) define lifecycle per packaging, according to default behaviour > 2) if a project needs to add a mojo, use + (if needed) > 3) if a project needs to remove a mojo, make mojo configurable such that > it can be skipped via POM configuration > 4) if there is a pattern in common for adjusting lifecycle for several > projects, define a new packaging -- 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: (MASSEMBLY-120) ModuleSet/Binaries include/exclude not implemented
ModuleSet/Binaries include/exclude not implemented -- Key: MASSEMBLY-120 URL: http://jira.codehaus.org/browse/MASSEMBLY-120 Project: Maven 2.x Assembly Plugin Type: Bug Versions: 2.1 Environment: linux (fedora core 5) / maven 2.0.4 / java 1.5 Reporter: Simon Goodall The binaries section of moduleSet has an include / exclude section defined, but it is not implemented. Currently a module can only include all or none of its dependencies (through the includeDependencies tag). There is no selective inclusion/exclusion of dependencies. -- 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: (MNG-1941) add an introduction to plugin configuration (patch included)
[ http://jira.codehaus.org/browse/MNG-1941?page=all ] John Casey updated MNG-1941: Fix Version: 2.0.5 > add an introduction to plugin configuration (patch included) > > > Key: MNG-1941 > URL: http://jira.codehaus.org/browse/MNG-1941 > Project: Maven 2 > Type: Improvement > Components: Plugin Creation Tools > Versions: 2.0.1 > Reporter: Hervé BOUTEMY > Fix For: 2.0.5 > Attachments: maven-plugin-tools-api_Intro.patch > > > same as http://jira.codehaus.org/browse/MPLUGIN-11, but in the "About xxx > plugin" page instead of "Plugin documentation" > by the way, having to implement 2 times the same functionality (one time with > XmlWriter API, one time with sink API) is not ideal : but that's another > question. -- 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: (MNG-1975) EAR project depends on WAR that doesn't exist, but it builds succesfully
[ http://jira.codehaus.org/browse/MNG-1975?page=all ] John Casey updated MNG-1975: Fix Version: 2.0.5 Quick question: does this issue belong in the MEAR project, since it seems to pertain to the ear plugin? > EAR project depends on WAR that doesn't exist, but it builds succesfully > > > Key: MNG-1975 > URL: http://jira.codehaus.org/browse/MNG-1975 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.2 > Environment: Debian GNU/Linux Etch (Testing), Eclipse WTP 1.0 > Reporter: Duncan Doyle > Fix For: 2.0.5 > > > While I was testing the features of Maven 2.0.1 and 2.0.2 I noticed the > following. > When specifying the correct version of my WAR project as a dependency in my > EAR pom.xml, the EAR file is generated correctly during a "mvn install" on my > SuperPom. However, when I specify a wrong WAR version number (a non-existing > one) in the dependency of my EAR Pom, the build still succeeds and an EAR > file is generated. I'm doing this just as a test. I would expect the build to > fail when the EAR project can't find the WAR file it depends on, but instead > it gives a message that it can't find the WAR file in the local repository > and remote repository and uses the generated WAR file (that is created before > the EAR file is created), which has the wrong version number, to create the > EAR package. > This my super pom.xml: > > 4.0.0 > Tour de France Service > nl.doyle.mccloud.TourDeFranceService > 0.0.1 > TourDeFranceService > pom > > ../TourDeFranceServiceEAR >../TourDeFranceServiceWeb > > > This my WAR pom.xml: > > 4.0.0 > Tour de France Service Web > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceWeb > war > 0.0.2 > > > junit > junit > 3.8.1 > test > > > > > >org.apache.maven.plugins >maven-war-plugin > > ../TourDeFranceServiceWeb/WebContent/WEB-INF/web.xml > > > >TourDeFranceServiceWeb > > > And this my EAR pom.xml with the wrong version number of the WAR project: > > 4.0.0 > Tour de France Service EAR > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceEAR > ear > 0.0.1 > > > nl.doyle.mccloud.TourDeFranceService > TourDeFranceServiceWeb > war > 1.0.2 > > > > TourDeFranceServiceEAR > > > This is part of the message that "mvn install" gives me: > Downloading: > http://repo1.maven.org/maven2/nl/doyle/mccloud/TourDeFranceService/TourDeFranceServiceWeb/1.0.2/TourDeFranceServiceWeb-1.0.2.pom > [WARNING] Unable to get resource from repository central > (http://repo1.maven.org/maven2) > [INFO] [ear:generate-application-xml] > [INFO] Generating application.xml > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [ear:ear] > [INFO] Copying > artifact[war:nl.doyle.mccloud.TourDeFranceService:TourDeFranceServiceWeb:1.0.2] > to[TourDeFranceServiceWeb.war] > How can it copy an artifact that doesn't exist??? The 1.0.2 version of my WAR > file doesn't exist in my local repository and the WAR file in my Enterprise > project has a different version number!!! -- 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: (MNG-2106) Add dependency-maven-plugin to plugins list (patch attached)
[ http://jira.codehaus.org/browse/MNG-2106?page=all ] John Casey updated MNG-2106: Fix Version: 2.0.5 > Add dependency-maven-plugin to plugins list (patch attached) > > > Key: MNG-2106 > URL: http://jira.codehaus.org/browse/MNG-2106 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.2 > Reporter: Brian Fox > Fix For: 2.0.5 > Attachments: plugins-add-dependency.patch > > > Added info about dependency plugin to plugins list in the mojo section -- 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: (MNG-1875) Cannot deploy artifact with classifier
[ http://jira.codehaus.org/browse/MNG-1875?page=all ] John Casey updated MNG-1875: Fix Version: 2.0.5 > Cannot deploy artifact with classifier > -- > > Key: MNG-1875 > URL: http://jira.codehaus.org/browse/MNG-1875 > Project: Maven 2 > Type: Bug > Reporter: Miguel Griffa > Assignee: Brett Porter > Fix For: 2.0.5 > > > Intro: > I have an artifact I want to deploy with different confs, I use profiles and > I want confs to be deployed, so I want somethings like > core-1.0.dev.jar > core-1.0.-test.jar > core-1.0.-prod.jar > profiles is the way to go. > The problem is how to set the name of the artifact with profiles. simple > overwriting finalName does not work, I was told to put the classifier in the > version, but this is incorrect, since all jars above should be in 1.0 dir. > putting the classifier in verison makes them appear in different version dirs. -- 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: (MNG-2056) Exception when starting new page with AbstractMavenMultiPageReport
[ http://jira.codehaus.org/browse/MNG-2056?page=all ] John Casey updated MNG-2056: Fix Version: 2.0.5 > Exception when starting new page with AbstractMavenMultiPageReport > -- > > Key: MNG-2056 > URL: http://jira.codehaus.org/browse/MNG-2056 > Project: Maven 2 > Type: Bug > Components: Sites & Reporting > Versions: 2.0.2 > Environment: OS X 10.3.4. running JDK 1.5 (1.5.0_06-93) > Reporter: Adam Winer > Fix For: 2.0.5 > > > Attempts to call AbstractMavenMultiPageReport.startPage() from a custom > report result in the following exception: > Caused by: java.io.EOFException: input contained no data > at > org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979) > at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022) > at > org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407) > at > org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392) > at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) > at > org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:172) > at > org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:83) > at > org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:48) > at > org.codehaus.doxia.module.xhtml.decoration.model.DecorationModelReader.createNavigation(DecorationModelReader.java:30) > at > org.codehaus.doxia.site.renderer.DefaultSiteRenderer.createSink(DefaultSiteRenderer.java:244) > at > org.apache.maven.reporting.sink.SinkFactory.getSink(SinkFactory.java:76) > at > org.apache.maven.reporting.AbstractMavenMultiPageReport.getSink(AbstractMavenMultiPageReport.java:79) > at > org.apache.maven.reporting.AbstractMavenMultiPageReport.startPage(AbstractMavenMultiPageReport.java:85) > FYI, I'm creating the SinkFactory for the multipage report using: > SinkFactory factory = new SinkFactory(); > factory.setSiteRenderer(getSiteRenderer()); > factory.setSiteDirectory(getOutputDirectory()); > setSinkFactory(factory); > Without this code, you just get a NullPointerException in > AbstractMavenMultiPageReport.getSink(). -- 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: (MNG-1928) ignores pluginRepository in settings.xml, honors in POM
[ http://jira.codehaus.org/browse/MNG-1928?page=all ] John Casey updated MNG-1928: Fix Version: 2.0.5 > ignores pluginRepository in settings.xml, honors in POM > --- > > Key: MNG-1928 > URL: http://jira.codehaus.org/browse/MNG-1928 > Project: Maven 2 > Type: Bug > Components: Plugins and Lifecycle > Versions: 2.0.1 > Environment: mvn 2.0.1, jvm 1.5.0_05, OSX 10.4.3 > Reporter: Ryan Marsh > Fix For: 2.0.5 > > > if specified in the POM as a plugin repo, maven can use the > team.andromda.org/maven2 repo for finding, downloading, and installing > plugins. > however, settings.xml ignores plugin repos and only checks central if the > plugin has never been downloaded before. > for instance. if settings.xml has a pluginRepository entry for > team.andromda.org/maven2 then: > mvn andromdapp:generate > should download the andromdapp plugin from our repo. but it doesn't. only > central is checked and it fails to find the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1995) filtering element in pom.xml ignore properties
[ http://jira.codehaus.org/browse/MNG-1995?page=all ]
John Casey updated MNG-1995:
Description:
you can mention it0091 as the test case
The following pom.xml does not end up filtering the resources:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.objectweb.celtix
test
jar
1.0
Test
true
src/main/resources
**
${filter.resources}
was:
you can mention it0091 as the test case
The following pom.xml does not end up filtering the resources:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.objectweb.celtix
test
jar
1.0
Test
true
src/main/resources
**
${filter.resources}
Fix Version: 2.0.5
> filtering element in pom.xml ignore properties
> --
>
> Key: MNG-1995
> URL: http://jira.codehaus.org/browse/MNG-1995
> Project: Maven 2
> Type: Bug
> Environment: Maven 2.0.1
> Reporter: Daniel Kulp
> Fix For: 2.0.5
>
>
> you can mention it0091 as the test case
> The following pom.xml does not end up filtering the resources:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> 4.0.0
> org.objectweb.celtix
> test
> jar
> 1.0
> Test
>
>
> true
>
>
>
>
>
> src/main/resources
>
> **
>
> ${filter.resources}
>
>
>
>
--
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: (MPECLIPSE-118) Attaching sourcepath in .classpath when file doesn't exist causes errors in Eclipse
Attaching sourcepath in .classpath when file doesn't exist causes errors in Eclipse --- Key: MPECLIPSE-118 URL: http://jira.codehaus.org/browse/MPECLIPSE-118 Project: maven-eclipse-plugin Type: Bug Versions: 1.11 Environment: Windows XP/Eclipse 3.2rc7 (eclipse.buildId=I20060602-1317) /maven 1.0.2 Reporter: Jon Christiansen Attachments: eclipseplugin.diff Plugin will put sourcepath attribute on classpathentry elements, regardless if file exists or not. Patch attached will only supply sourcepath attribute if the source archive exists. This will cause errors in eclipse when you dont have the source files available. For instance, if you have run a program and have a stack trace in your console and you click on a link to a file/line number in the stack trace of one of your source files, you will get something similar to this: An exception occurred while following link. Reason: Error logged from JDT Debug UI: Error logged from JDT Debug UI: Source lookup error Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\junit\java-sources\junit-3.8.1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-logging\java-sources\commons-logging-1.0.3-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-lang\java-sources\commons-lang-2.0-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-net\java-sources\commons-net-1.3.0-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\sshtools\java-sources\sshtools-maverick-all-1.2.7-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\jboss\java-sources\jboss-jmx-4.0.3SP1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-httpclient\java-sources\commons-httpclient-2.0.2-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-collections\java-sources\commons-collections-3.1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\jboss\java-sources\jboss-system-4.0.3SP1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\jboss\java-sources\jboss-common-4.0.3SP1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\servletapi\java-sources\servletapi-2.4-20040521-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-validator\java-sources\commons-validator-1.1.4-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-beanutils\java-sources\commons-beanutils-1.6-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\jboss\java-sources\jmx-adaptor-plugin-4.0.3SP1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\dom4j\java-sources\dom4j-1.6.1-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\jaxen\java-sources\jaxen-1.1-beta-4-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\commons-digester\java-sources\commons-digester-1.6-sources.jar Unable to access archive C:\Documents and Settings\jchristi\.maven\repository\oro\java-sources\oro-2.0.7-sources.jar Stack trace in Eclipse's error log shows: org.eclipse.core.runtime.CoreException: Source lookup error at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:104) at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:45) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupParticipant.findSourceElements(AbstractSourceLookupParticipant.java:67) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(AbstractSourceLookupDirector.java:136) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.findSourceElements(AbstractSourceLookupDirector.java:721) at org.eclipse.jdt.internal.debug.core.JavaDebugUtils.resolveSourceElement(JavaDebugUtils.java:262) at org.eclipse.jdt.internal.debug.ui.console.JavaStackTraceHyperlink.getSourceElement(JavaStackTraceHyperlink.java:130) at org.eclipse.jdt.internal.debug.ui.console.JavaStackTraceHyperlink.linkActivated(JavaStackTraceHyperlink.java:85) at org.eclipse.ui.console.TextConsoleViewer$2.handleEvent(TextConsoleViewer.java:103) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at
[jira] Updated: (MNG-1540) ability to categorise guides in the maven site
[ http://jira.codehaus.org/browse/MNG-1540?page=all ] John Casey updated MNG-1540: Fix Version: (was: documentation) 2.0.5 > ability to categorise guides in the maven site > -- > > Key: MNG-1540 > URL: http://jira.codehaus.org/browse/MNG-1540 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Reporter: Brett Porter > Priority: Critical > Fix For: 2.0.5 > > -- 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: (MNG-803) Document of Detailed Changes between M1/M2
[ http://jira.codehaus.org/browse/MNG-803?page=all ] John Casey updated MNG-803: --- Fix Version: (was: documentation) 2.1 > Document of Detailed Changes between M1/M2 > -- > > Key: MNG-803 > URL: http://jira.codehaus.org/browse/MNG-803 > Project: Maven 2 > Type: Task > Components: Documentation: General > Versions: 2.0-alpha-3 > Reporter: Natalie Burdick > Fix For: 2.1 > > > Parent Task will include sub-tasks for specific changes from M1 to M2 that > need to be documented -- 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: (MNG-1952) Give equal footing to all m2 plugins and add Cargo plugin to the list
[ http://jira.codehaus.org/browse/MNG-1952?page=all ] John Casey updated MNG-1952: Fix Version: (was: documentation) 2.1 > Give equal footing to all m2 plugins and add Cargo plugin to the list > - > > Key: MNG-1952 > URL: http://jira.codehaus.org/browse/MNG-1952 > Project: Maven 2 > Type: Improvement > Components: Documentation: General > Reporter: Vincent Massol > Fix For: 2.1 > Attachments: siteplugin2.patch > > > Right now there are several plugin lists (3) making it harder to find a given > plugin as this breaks the alphabetical order. In addition plugins that come > later on the page get less visibility. I am sending a patch that lists all > the plugins in the same table. If it's required we could create another > column mentioning where the plugin comes from but I don't think that's > required. > I have also added the Cargo m2 plugin which was missing from the list. -- 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: (MNG-808) Content ideas for Why Maven? type page
[ http://jira.codehaus.org/browse/MNG-808?page=all ] John Casey updated MNG-808: --- Fix Version: (was: documentation) 2.1 > Content ideas for Why Maven? type page > -- > > Key: MNG-808 > URL: http://jira.codehaus.org/browse/MNG-808 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Natalie Burdick > Fix For: 2.1 > > > Sample topics/themes (based on mailing lists): > 1) Why Choose/Use Maven: > - How does using Maven change my every day job? > - How does using Maven make my code better? > - I'm a developer that uses Maven, how do I get other developers to adopt > Maven when they say "I've got an IDE > that compile's my java code and don't need anything else." > - I'm a developer that uses Maven, how do I get my manager(s) to adopt Maven? > 2) Build Basics: > Why use a CI server? > How do I use CI with Maven: > --With Continuum > --with CruiseControl > --with Anthill > Why use a SCM? > How do I use my SCM and Maven: > --with CVS > --with subversion > --with (tbd) > Why Perform Unit Testing? > How do I perform unit testing in Maven: > --with Junit > --with Cactus > Why Apply Code Coverage? > *How to apply code coverage to Maven: > --with Clover > --with Jcoverage > --with Corbetura > 3) Maven-specifics: > When/Why should I use M1 > When/Why should I use M2 > When, Why should I set up a multi-project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1302) Write up a sync'ing partners guide
[ http://jira.codehaus.org/browse/MNG-1302?page=all ] John Casey updated MNG-1302: Fix Version: (was: documentation) 2.1 > Write up a sync'ing partners guide > -- > > Key: MNG-1302 > URL: http://jira.codehaus.org/browse/MNG-1302 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Reporter: Jason van Zyl > Assignee: Carlos Sanchez > Fix For: 2.1 > > > Make it easier for us to get new sync'ing partners. We need to document what > it takes to be a sync'ing partner and outline any tools that may help keep > the partner's repository sane for import into the canonical 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] Updated: (MNG-1871) CVS examples in guide to using release plugin
[ http://jira.codehaus.org/browse/MNG-1871?page=all ] John Casey updated MNG-1871: Fix Version: (was: documentation) 2.1 > CVS examples in guide to using release plugin > - > > Key: MNG-1871 > URL: http://jira.codehaus.org/browse/MNG-1871 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Reporter: Miguel Griffa > Fix For: 2.1 > > > Guide to using release plugin should include examples for CVS as well as SVN -- 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: (MNG-1583) Give pointers to integration tests in the docs
[ http://jira.codehaus.org/browse/MNG-1583?page=all ] John Casey updated MNG-1583: Fix Version: (was: documentation) 2.1 > Give pointers to integration tests in the docs > -- > > Key: MNG-1583 > URL: http://jira.codehaus.org/browse/MNG-1583 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Versions: 2.0 > Reporter: Carlos Sanchez > Fix For: 2.1 > > > Experimented developers like looking at code, so let's give them pointers > from the guides to the integration tests where the features are used as > example -- 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: (MNG-1541) generate index using a maven plugin
[ http://jira.codehaus.org/browse/MNG-1541?page=all ] John Casey updated MNG-1541: Fix Version: (was: documentation) 2.1 > generate index using a maven plugin > --- > > Key: MNG-1541 > URL: http://jira.codehaus.org/browse/MNG-1541 > Project: Maven 2 > Type: Improvement > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.1 > > > write our own site plugin, or make index generation a part of the site plugin. > need to be able to add metadata to APT, XDOC and FML files to be able to > specify the category, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1563) how to write integration tests
[ http://jira.codehaus.org/browse/MNG-1563?page=all ] John Casey updated MNG-1563: Fix Version: (was: documentation) 2.1 > how to write integration tests > -- > > Key: MNG-1563 > URL: http://jira.codehaus.org/browse/MNG-1563 > Project: Maven 2 > Type: Improvement > Components: Design, Patterns & Best Practices > Reporter: Matthew Pocock > Fix For: 2.1 > > > There doesn't seem to be a guide about either testing or integration testing. > It would be nice to see two guides: > plain vanilla junit tests: > how to write a simple one that will run in m2 > how to write one that uses the test suite API > integration testing: > test building e.g. plugin that does code generation > test resulting application e.g. command-line app or gui > test deployment e.g. to a test web service container > I have no idea what of this is currently implemented or even possible using > mvn, but then the documentation isn't giving my wishes any boundaries > either... -- 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: (MNG-1213) more info on the plugin summary
[ http://jira.codehaus.org/browse/MNG-1213?page=all ] John Casey updated MNG-1213: Fix Version: (was: documentation) 2.0.5 > more info on the plugin summary > --- > > Key: MNG-1213 > URL: http://jira.codehaus.org/browse/MNG-1213 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > > include: > - mojo.codehaus.org released plugins links > - versions/quality of release m2 plugins -- 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: (MNG-1887) Guide to transforming a maven.xml goal into a plugin
[ http://jira.codehaus.org/browse/MNG-1887?page=all ] John Casey updated MNG-1887: Fix Version: (was: documentation) 2.0.5 > Guide to transforming a maven.xml goal into a plugin > > > Key: MNG-1887 > URL: http://jira.codehaus.org/browse/MNG-1887 > Project: Maven 2 > Type: New Feature > Components: Documentation: Guides > Versions: 2.0.1 > Reporter: Geoffrey De Smet > Fix For: 2.0.5 > > > Many users coming from maven 1 have large maven.xml files and don't really > know how to start migrating those. > Usually these maven.xml do simple things like copy some files or run an ant > task. > 3 use cases should be shown: > 1) old custom assembly script can now be done by the assembly plugin > 2) some ant task can be done with the antrun plugin > 3) some custom script can be turned into a plugin > You probably don't like solution 2) and it's indeed not the best solution, > like use maven.xml in maven 1 was also not the best solution, > despite that people are doing it to do things quick & dirty or as proofs of > concepts, > so they should be guided (and also be told that 3) is better) > This could become a part of "Guide to Moving from Maven 1.x to Maven 2.x": > http://maven.apache.org/guides/mini/guide-m1-m2.html > But seeing the length of that one, some sort of index would be usefull (like > in FAQ's). -- 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: (MNG-1299) Document m1 xdocs compatibility with the m2 site plug-in
[ http://jira.codehaus.org/browse/MNG-1299?page=all ]
John Casey updated MNG-1299:
Fix Version: (was: documentation)
2.0.5
> Document m1 xdocs compatibility with the m2 site plug-in
>
>
> Key: MNG-1299
> URL: http://jira.codehaus.org/browse/MNG-1299
> Project: Maven 2
> Type: Improvement
> Reporter: Jason van Zyl
> Fix For: 2.0.5
>
>
> The m2 site plugin now supports the ${basedir}/xdocs directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1370) Guide to attached artifacts
[ http://jira.codehaus.org/browse/MNG-1370?page=all ] John Casey updated MNG-1370: Fix Version: (was: documentation) 2.0.5 > Guide to attached artifacts > --- > > Key: MNG-1370 > URL: http://jira.codehaus.org/browse/MNG-1370 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > Show how to use attached artifacts like source bundles and javadocs, and the > use the ejb plugin which creates the ejb-client attached artiact. -- 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: (MNG-1121) document standard location for plugin configuration files
[ http://jira.codehaus.org/browse/MNG-1121?page=all ] John Casey updated MNG-1121: Fix Version: (was: documentation) 2.0.5 > document standard location for plugin configuration files > - > > Key: MNG-1121 > URL: http://jira.codehaus.org/browse/MNG-1121 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > > discussion: > http://mail-archives.apache.org/mod_mbox/maven-users/200505.mbox/[EMAIL > PROTECTED] > things like checkstyle configuration files. > also see Vincent's recent discussion: > http://mail-archives.apache.org/mod_mbox/maven-dev/200510.mbox/[EMAIL > PROTECTED] -- 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: (MNG-1987) Set a minimal standard for plug-in documentation
[ http://jira.codehaus.org/browse/MNG-1987?page=all ] John Casey updated MNG-1987: Fix Version: (was: documentation) 2.0.5 > Set a minimal standard for plug-in documentation > > > Key: MNG-1987 > URL: http://jira.codehaus.org/browse/MNG-1987 > Project: Maven 2 > Type: Wish > Components: Documentation: General > Reporter: Bengt-Erik Fröberg > Fix For: 2.0.5 > > > There are many repositories and providers of Maven2 plugins. > However, layout and,above all, content vary in lenghth and information value. > A few providers had made efforts to document, and others tend to completely > skip this step > as if one could guess how to configure or use the plugin in the best way. > I had a very positive and inspiring experience with the > http://cargo.codehaus.org/Maven2+plugin plugin documentation, and from a > pedagogical and user-oriented point of view this makes the difference between > "yes" and "no way". > Compare this to the sparse deploy:deploy plugin docs. > I will try to pinpoint the reasons my immediate love with this documentation > style: > 1) From very basic to advanced (minimal, small-intermediate and full-fledged > configuration) - pedagogical > 2) Listing of different use-cases with appropriate descriptions. Note the > progressive approach - no guessing games needed and very pedagogical. > 3) Examples, examples and examples - show us how it's done, and we get > happy!!! > It does not matter that there are some "TODO"s in the page, you just love > the guys that wrote it. > I really would like a minimal set of criteria being fulfilled in terms of > documentation: At least three levels of config, > some common and some special use cases and a lot of example code. > In some other plugin docs there are examples, that's true, but I don't think > they interact very well with the written text. > One example is http://maven.apache.org/plugins/maven-antrun-plugin/usage.html > (at least this plugin has a "usage" section. > Slightly uninformative text aside the examples, and some references to things > you obviously should know... > I hope this could lead to a discussion about docs in general, but plugin ones > especially. > Regards, > /B-E Fröberg -- 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: (MNG-1367) Guide to creating report plugin
[ http://jira.codehaus.org/browse/MNG-1367?page=all ] John Casey updated MNG-1367: Fix Version: (was: documentation) 2.0.5 > Guide to creating report plugin > --- > > Key: MNG-1367 > URL: http://jira.codehaus.org/browse/MNG-1367 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Assignee: Allan Ramirez > Fix For: 2.0.5 > Attachments: maven-report-plugin.zip > > > Show people how to make reports. -- 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: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails
[ http://jira.codehaus.org/browse/MNG-1667?page=all ]
John Casey updated MNG-1667:
Fix Version: (was: documentation)
2.0.5
> M2_HOME is not used in the way described in README.txt and as such bootstrap
> build fails
>
>
> Key: MNG-1667
> URL: http://jira.codehaus.org/browse/MNG-1667
> Project: Maven 2
> Type: Bug
> Components: Bootstrap & Build
> Environment: Win32 (XP SP2)
> Reporter: John Allen
> Fix For: 2.0.5
>
>
> From README.txt
> Set the environment variable M2_HOME pointing to the dir where you want
> Maven2 installed.
> NOTE: presently, the directory {M2_HOME}/bin must be in your path:
> set PATH=%PATH%;%M2_HOME%\bin
> or
> export PATH=$PATH:$M2_HOME/bin
> MVN SNAPSHOT is actually installed into %M2_HOME$/../maven-2.0.1-SNAPSHOT
> and this is not the location on the PATH so integration tests fail.
--
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: (MNG-1500) document the running of a single test or group of tests using the -Dtest=FooTest option
[ http://jira.codehaus.org/browse/MNG-1500?page=all ] John Casey updated MNG-1500: Fix Version: (was: documentation) 2.0.5 > document the running of a single test or group of tests using the > -Dtest=FooTest option > --- > > Key: MNG-1500 > URL: http://jira.codehaus.org/browse/MNG-1500 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Reporter: Jason van Zyl > Assignee: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-1366) Guide to multi project setup
[ http://jira.codehaus.org/browse/MNG-1366?page=all ] John Casey updated MNG-1366: Fix Version: (was: documentation) 2.0.5 > Guide to multi project setup > > > Key: MNG-1366 > URL: http://jira.codehaus.org/browse/MNG-1366 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > Need to capture the best practices for setting up a multi-project build and > make a guide. -- 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: (MNG-1522) assembly guide enhancements
[ http://jira.codehaus.org/browse/MNG-1522?page=all ] John Casey updated MNG-1522: Fix Version: (was: documentation) 2.0.5 > assembly guide enhancements > --- > > Key: MNG-1522 > URL: http://jira.codehaus.org/browse/MNG-1522 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Brett Porter > Fix For: 2.0.5 > > > - describe dependency sets > - describe default descriptors (bin, src, jar-with-dependencies) > - link to generated descriptor reference > - link to actualy plugin reference -- 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: (MNG-1140) document how other common directory layouts could be used within/migrated to m2
[ http://jira.codehaus.org/browse/MNG-1140?page=all ] John Casey updated MNG-1140: Fix Version: (was: documentation) 2.0.5 > document how other common directory layouts could be used within/migrated to > m2 > --- > > Key: MNG-1140 > URL: http://jira.codehaus.org/browse/MNG-1140 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Priority: Minor > Fix For: 2.0.5 > > -- 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: (MNG-1593) Typo in settings doc
[ http://jira.codehaus.org/browse/MNG-1593?page=all ] John Casey updated MNG-1593: Fix Version: (was: documentation) 2.0.5 > Typo in settings doc > > > Key: MNG-1593 > URL: http://jira.codehaus.org/browse/MNG-1593 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0 > Reporter: Carlos Sanchez > Assignee: Maria Odea Ching > Priority: Minor > Fix For: 2.0.5 > > > http://maven.apache.org/maven-settings/settings.html > under and > should be > should be -- 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: (MNG-1818) update team list
[ http://jira.codehaus.org/browse/MNG-1818?page=all ] John Casey updated MNG-1818: Fix Version: (was: documentation) 2.0.5 > update team list > > > Key: MNG-1818 > URL: http://jira.codehaus.org/browse/MNG-1818 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > > 1) list all pmc members > 2) list all committers in > 3) seek out "Submitted by" in svn logs to populate -- 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: (MNG-1128) Create an archetype demonstrating the use of profiles targeting different environments
[ http://jira.codehaus.org/browse/MNG-1128?page=all ] John Casey updated MNG-1128: Fix Version: (was: documentation) 2.0.5 > Create an archetype demonstrating the use of profiles targeting different > environments > -- > > Key: MNG-1128 > URL: http://jira.codehaus.org/browse/MNG-1128 > Project: Maven 2 > Type: New Feature > Components: Documentation: General > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > Having an archetype which encapsulates how to use profiles to in order to do > things like filtering log4.properties files according to their target > environment would be useful. -- 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: (MNG-1560) Guide to accessing repository with https client authentication
[ http://jira.codehaus.org/browse/MNG-1560?page=all ] John Casey updated MNG-1560: Fix Version: (was: documentation) 2.0.5 > Guide to accessing repository with https client authentication > -- > > Key: MNG-1560 > URL: http://jira.codehaus.org/browse/MNG-1560 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Versions: 2.0 > Reporter: Arnaud Bailly > Priority: Minor > Fix For: 2.0.5 > Attachments: MavenRepoSSLAccess.apt, guide-repository-ssl.apt, > guide-repository-ssl.apt > > > The attachment describes a way (in APT format) to use a remote repository > through HTTPS with client-side certificate authentication. This may be useful > in corporate or private development settings. -- 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: (MNG-1459) guide for creating ejb and corresponding ejb client JAR
[ http://jira.codehaus.org/browse/MNG-1459?page=all ] John Casey updated MNG-1459: Fix Version: (was: documentation) 2.0.5 > guide for creating ejb and corresponding ejb client JAR > --- > > Key: MNG-1459 > URL: http://jira.codehaus.org/browse/MNG-1459 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-2026) Document how parent-child POM relationships, , and works
[ http://jira.codehaus.org/browse/MNG-2026?page=all ] John Casey updated MNG-2026: Fix Version: (was: documentation) 2.0.5 > Document how parent-child POM relationships, , and > works > -- > > Key: MNG-2026 > URL: http://jira.codehaus.org/browse/MNG-2026 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: John Casey > Fix For: 2.0.5 > > > Create a document that will describe how POMs can be related to one another > in a multimodule build. Specifically, document: > * The parent-child relationship - how is this manifest in the POMs > * How does the section work > * How does the element of the section work...and > what is required in the section? > * How to install ONLY the parent POM for a multimodule setup (mvn -N pom.xml > at the top level) > * How to build an entire multimodule setup from one command (tie all of this > together into a working example) > Related to this, but in another document, should be a list of things that are > inherited (could be a link to somewhere else, if this documentation exists in > other places). Also, the algorithm used to merge inherited and local POM > sections should be in this other 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
[jira] Updated: (MNG-1368) Guide to using version ranges
[ http://jira.codehaus.org/browse/MNG-1368?page=all ] John Casey updated MNG-1368: Fix Version: (was: documentation) 2.0.5 > Guide to using version ranges > - > > Key: MNG-1368 > URL: http://jira.codehaus.org/browse/MNG-1368 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-1494) Create comprehensive m2 feature list
[ http://jira.codehaus.org/browse/MNG-1494?page=all ] John Casey updated MNG-1494: Fix Version: (was: documentation) 2.0.5 > Create comprehensive m2 feature list > > > Key: MNG-1494 > URL: http://jira.codehaus.org/browse/MNG-1494 > Project: Maven 2 > Type: New Feature > Components: Documentation: General > Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-1212) apply new style to plugins sites
[ http://jira.codehaus.org/browse/MNG-1212?page=all ] John Casey updated MNG-1212: Fix Version: (was: documentation) 2.0.5 > apply new style to plugins sites > > > Key: MNG-1212 > URL: http://jira.codehaus.org/browse/MNG-1212 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > -- 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: (MNG-1961) Guide to Configuring Plug-ins
[ http://jira.codehaus.org/browse/MNG-1961?page=all ] John Casey updated MNG-1961: Fix Version: (was: documentation) 2.0.5 > Guide to Configuring Plug-ins > - > > Key: MNG-1961 > URL: http://jira.codehaus.org/browse/MNG-1961 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: 2.0.1 > Reporter: Napoleon Esmundo C. Ramirez > Priority: Minor > Fix For: 2.0.5 > > > The "Mapping maps" under "Mapping to Collections" section is blank. -- 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: (MNG-2143) Proposition of documentation
[ http://jira.codehaus.org/browse/MNG-2143?page=all ] John Casey updated MNG-2143: Fix Version: (was: documentation) 2.0.5 > Proposition of documentation > > > Key: MNG-2143 > URL: http://jira.codehaus.org/browse/MNG-2143 > Project: Maven 2 > Type: Improvement > Components: Documentation: General > Reporter: Raphaël Piéroni > Fix For: 2.0.5 > Attachments: AdvancedDocumentation.apt, Categories.txt, MainPage.apt > > > Here attached are 2 apt file that describe a first attempt to refactor the > maven documentation site. -- 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: (MNG-1582) Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide
[ http://jira.codehaus.org/browse/MNG-1582?page=all ] John Casey updated MNG-1582: Fix Version: (was: documentation) 2.0.5 > Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide > - > > Key: MNG-1582 > URL: http://jira.codehaus.org/browse/MNG-1582 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Versions: 2.0 > Reporter: Carlos Sanchez > Fix For: 2.0.5 > > > guide to convert pregoals and postgoals to lifecycle > give a pointer to the integration test that covers lifecycle as a example -- 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: (MNG-1141) document tag, and where we plan to go with USD and workspace definitions
[ http://jira.codehaus.org/browse/MNG-1141?page=all ] John Casey updated MNG-1141: Fix Version: (was: documentation) 2.0.5 > document tag, and where we plan to go with USD and workspace > definitions > - > > Key: MNG-1141 > URL: http://jira.codehaus.org/browse/MNG-1141 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > -- 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: (MNG-1305) Document Maven's own development process
[ http://jira.codehaus.org/browse/MNG-1305?page=all ] John Casey updated MNG-1305: Fix Version: (was: documentation) 2.0.5 > Document Maven's own development process > > > Key: MNG-1305 > URL: http://jira.codehaus.org/browse/MNG-1305 > Project: Maven 2 > Type: Task > Components: Design, Patterns & Best Practices > Reporter: Jason van Zyl > Assignee: Jason van Zyl > Fix For: 2.0.5 > > > There is a thread on the dev mailing list: dev process for 2.0.1/2.1 > and I would like to document the outcome of this discussion so we can > subsequently reference 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: (MNG-66) Create a matrix of possible exceptional conditions
[ http://jira.codehaus.org/browse/MNG-66?page=all ] John Casey updated MNG-66: -- Fix Version: (was: documentation) 2.0.5 > Create a matrix of possible exceptional conditions > -- > > Key: MNG-66 > URL: http://jira.codehaus.org/browse/MNG-66 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Jason van Zyl > Priority: Minor > Fix For: 2.0.5 > > > We need a little matrix of possible exception conditions, what causes them, > what resources we can point users to for help, and how we can format the > exception message as to make the most sense to users. -- 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: (MNG-1962) allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation.
[ http://jira.codehaus.org/browse/MNG-1962?page=all ] John Casey updated MNG-1962: Fix Version: (was: documentation) 2.0.5 > allow empty deprecation messages in plugin descriptor/annotation and document > usage of deprecation in descriptor/annotation. > > > Key: MNG-1962 > URL: http://jira.codehaus.org/browse/MNG-1962 > Project: Maven 2 > Type: Improvement > Components: Plugin Creation Tools, Documentation: General > Versions: 2.0.1 > Reporter: John Casey > Priority: Minor > Fix For: 2.0.5 > > > currently, the deprecation features for plugins (not the java deprecation > mechanism, necessarily) require a message for the deprecation warning to be > printed. This point is poorly documented. > Allow an empty deprecation message (make one up when the plugin descriptor is > read, if the element is present but empty), and then document > the usage of plugin deprecations at the class and parameter level. -- 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: (MNG-1371) How to deal with encoding and documentation
[ http://jira.codehaus.org/browse/MNG-1371?page=all ] John Casey updated MNG-1371: Fix Version: (was: documentation) 2.0.5 > How to deal with encoding and documentation > --- > > Key: MNG-1371 > URL: http://jira.codehaus.org/browse/MNG-1371 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > Show how people can use different encodings with APT. This can probably be > added to the guide-site.apt. -- 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: (MNG-1290) What is a Mojo?
[ http://jira.codehaus.org/browse/MNG-1290?page=all ] John Casey updated MNG-1290: Fix Version: (was: documentation) 2.0.5 > What is a Mojo? > --- > > Key: MNG-1290 > URL: http://jira.codehaus.org/browse/MNG-1290 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0 > Reporter: Binil Thomas > Fix For: 2.0.5 > > > On http://maven.apache.org/developers/mojo-api-specification.html page titled > "Mojo API", I see : > > Starting with Maven 2.0, plugins can be written in Java or any of a number of > scripting languages. Additionally, Maven tries to stay out of the way of the > programmer with its new Mojo API. This opens up the opportunity for many > Mojos to be reused outside of Maven, or bridged into Maven from external > systems like Ant. > > The first line states a fact - that Maven plugins can now be written in plain > Java. The second line doesnt suggest anything to me besides the irritating > name-dropping "Mojo API". The third line adds further confusion by the usage > "many Mojos" planting the supiscion that this things called "Mojo" might be > more than an API! > Two paragraph later, I see: > > As mentioned before, each Plugin - or packaged set of Mojos .. > > Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be > some API to write these. > It would have been much less intimidating had this fact be stated upfront. > A note here - the term "plugin" was did not need any introduction to me - > because it is a widely one used in the software scene. At this point I don't > even know what a Maven plugin can do - yet I have a vague notion that a > plugin might be something that enhances the out-of-the-box behaviour of Maven. > The same familiarity does not apply to the term "Mojo" - I am guessing here, > but I think the Maven team invented the term. If so, kindly desrcibe it fully > instead of confusing the reader. -- 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: (MNG-1304) Create a standard versioning document
[ http://jira.codehaus.org/browse/MNG-1304?page=all ] John Casey updated MNG-1304: Fix Version: (was: documentation) 2.0.5 > Create a standard versioning document > - > > Key: MNG-1304 > URL: http://jira.codehaus.org/browse/MNG-1304 > Project: Maven 2 > Type: Improvement > Components: Documentation: General > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > We need to document how SNAPSHOTs work and how we move from one version to > another. There are the starts of decent documents in the xstream project and > the commons project at Apache. -- 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: (MNG-2000) Create comprehensive profiles documentation
[ http://jira.codehaus.org/browse/MNG-2000?page=all ] John Casey updated MNG-2000: Fix Version: (was: documentation) 2.0.5 > Create comprehensive profiles documentation > --- > > Key: MNG-2000 > URL: http://jira.codehaus.org/browse/MNG-2000 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: John Casey > Assignee: John Casey > Priority: Critical > Fix For: 2.0.5 > > Original Estimate: 16 hours >Time Spent: 1 day > Remaining: 0 minutes > > This document should draw from the mailing list, FAQ wiki, MNGFAQ jira > project (on codehaus), existing site documentation, project source code, and > any IRC conversations necessary. > It should include: > * How can I tell which profiles are in effect during a build? > * What are the different types of profile? Where is each defined? > * Which areas of a POM can be customized by each type of profile? Why? > - settings-defined and profiles.xml-defined only modify properties, > repositories, and pluginRepositories. This is necessary to preserve the > portability of the pom as much as possible, since these two locations are not > installed/deployed to the repository system. > * How can a profile be triggered? How does this vary according to the type of > profile being used? > * Profiles are not inherited, but their effects are, because they are applied > to the POM before it's used for inheritance. This means a parent POM will > have its profiles triggered and applied before it is used to calculate the > inherited values for the current POM. Please include this in the > documentation as well. > There's probably more, but I can't think of it off the top of my head. We > need to make this another one of those definitive documents for POM > configuration. -- 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: (MNG-1059) update mojo API documentation
[ http://jira.codehaus.org/browse/MNG-1059?page=all ] John Casey updated MNG-1059: Fix Version: (was: documentation) 2.0.5 > update mojo API documentation > - > > Key: MNG-1059 > URL: http://jira.codehaus.org/browse/MNG-1059 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Brett Porter > Fix For: 2.0.5 > > -- 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: (MNG-2129) generated source repo page is misleading when added to the "general site".
[ http://jira.codehaus.org/browse/MNG-2129?page=all ] John Casey updated MNG-2129: Fix Version: (was: documentation) 2.0.5 > generated source repo page is misleading when added to the "general site". > -- > > Key: MNG-2129 > URL: http://jira.codehaus.org/browse/MNG-2129 > Project: Maven 2 > Type: Improvement > Components: Documentation: General, Design, Patterns & Best Practices > Reporter: Brett Porter > Fix For: 2.0.5 > Attachments: MNG-2129-maven-site.patch > > > it says: > $ svn checkout http://svn.apache.org/repos/asf/maven/components/trunk/ > maven-site > We really should set the SCM URL correctly in the site pom again (to point to > the site SCM), and the generated report should be excluded from the > navigation. It could still be generated and linked from another doc that > describes helping with the docs. -- 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: (MNG-1645) document clean and site lifecycles in the build lifecycle doc
[ http://jira.codehaus.org/browse/MNG-1645?page=all ] John Casey updated MNG-1645: Fix Version: (was: documentation) 2.0.5 > document clean and site lifecycles in the build lifecycle doc > - > > Key: MNG-1645 > URL: http://jira.codehaus.org/browse/MNG-1645 > Project: Maven 2 > Type: Bug > Components: Documentation: Introductions > Reporter: Brett Porter > Fix For: 2.0.5 > > -- 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: (MNG-1307) Document profile injection in conjunction with inheritance
[ http://jira.codehaus.org/browse/MNG-1307?page=all ] John Casey updated MNG-1307: Fix Version: (was: documentation) 2.0.5 > Document profile injection in conjunction with inheritance > -- > > Key: MNG-1307 > URL: http://jira.codehaus.org/browse/MNG-1307 > Project: Maven 2 > Type: Improvement > Components: Documentation: General > Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-1267) Complete the Introduction to the Standard Directory Layout
[ http://jira.codehaus.org/browse/MNG-1267?page=all ] John Casey updated MNG-1267: Fix Version: (was: documentation) 2.0.5 > Complete the Introduction to the Standard Directory Layout > -- > > Key: MNG-1267 > URL: http://jira.codehaus.org/browse/MNG-1267 > Project: Maven 2 > Type: Task > Components: Documentation: Introductions > Reporter: Srepfler Srgjan > Priority: Minor > Fix For: 2.0.5 > > > The document page is there but it's empty -- 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: (MNG-2027) Document POM inheritance
[ http://jira.codehaus.org/browse/MNG-2027?page=all ] John Casey updated MNG-2027: Fix Version: (was: documentation) 2.0.5 > Document POM inheritance > > > Key: MNG-2027 > URL: http://jira.codehaus.org/browse/MNG-2027 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: John Casey > Fix For: 2.0.5 > > > Document in detail how parent POMs are merged with local POM data. In > particular: > * how are lists of things merged > * how do local POMs override parent data > * how can one suppress inheritance of a plugin > * how can one control merge-vs-append in plugin configurations > * how does the affect the requirement for a locally > specified > How does managed information differ?? > Managed info (dependencyManagement, pluginManagement) sets the standard > configuration, version, etc for that information. This standard can be used > in opt-in fashion by child POMs, BUT WILL ONLY BE APPLIED WHERE IT IS > REFERENCED. > Document the way in which managed info is merged, and how it can be > referenced and overridden. -- 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: (MNG-1348) includes on resource tag not documented as being a list
[ http://jira.codehaus.org/browse/MNG-1348?page=all ] John Casey updated MNG-1348: Fix Version: (was: documentation) 2.0.5 > includes on resource tag not documented as being a list > --- > > Key: MNG-1348 > URL: http://jira.codehaus.org/browse/MNG-1348 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0 > Reporter: Ryan Sonnek > Fix For: 2.0.5 > > > according to the product documentation at > http://maven.apache.org/maven2/maven-model/maven.html each resource should be > able to specify includes. maven errors out unless the inclues is moved out > of "resource" and into the "resources" tag. > example model: > > > src/main/wsdd > *.wsdl > > > exception: > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Parse error reading POM > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error > re > ading POM > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1097) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1057) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi > le(DefaultMavenProjectBuilder.java:291) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave > nProjectBuilder.java:276) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:509) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:441) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:345) > ... 11 more > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected > ST > ART_TAG or END_TAG not TEXT (position: TEXT seen ...\r\n > ludes>*.wsdl at > org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1080 > ) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseResource(MavenXpp > 3Reader.java:3825) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Re > ader.java:621) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Re > ader.java:2131) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.j > ava:4255) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1093) -- 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: (MNG-1306) Document the use of https for transport in m2 (wagon)
[ http://jira.codehaus.org/browse/MNG-1306?page=all ] John Casey updated MNG-1306: Fix Version: (was: documentation) 2.0.5 > Document the use of https for transport in m2 (wagon) > - > > Key: MNG-1306 > URL: http://jira.codehaus.org/browse/MNG-1306 > Project: Maven 2 > Type: Task > Components: Documentation: General > Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- 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: (MNG-1281) Most of the links off the m2 ant task documentation page are broken
[ http://jira.codehaus.org/browse/MNG-1281?page=all ] John Casey updated MNG-1281: Fix Version: (was: documentation) 2.0.5 > Most of the links off the m2 ant task documentation page are broken > --- > > Key: MNG-1281 > URL: http://jira.codehaus.org/browse/MNG-1281 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0 > Environment: n/a > Reporter: Steve Loughran > Fix For: 2.0.5 > > > Most of the "for further information" links off the ant task docs refer to > pages that are either absent or the wrong page. please fix.. > http://maven.apache.org/maven-settings/settings.html //absent > http://maven.apache.org/dependencies.html //doesnt explain dependency mech > http://maven.apache.org/maven-model/maven.html //404 and not descriptor > reference > http://maven.apache.org/configuration.html //configuring maven is 404 -- 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: (MNG-1365) Document how to make a download link on your site
[ http://jira.codehaus.org/browse/MNG-1365?page=all ] John Casey updated MNG-1365: Fix Version: (was: documentation) 2.0.5 > Document how to make a download link on your site > - > > Key: MNG-1365 > URL: http://jira.codehaus.org/browse/MNG-1365 > Project: Maven 2 > Type: Improvement > Components: Documentation: Guides > Reporter: Jason van Zyl > Fix For: 2.0.5 > > > An addition to the guide-site.apt 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
[jira] Updated: (MNG-1879) Allow dependencies to be defined in external profiles.xml for inclusion at build time when a profile is activated (and allow reuse of profies.xml)
[ http://jira.codehaus.org/browse/MNG-1879?page=all ]
John Casey updated MNG-1879:
Fix Version: 2.1
> Allow dependencies to be defined in external profiles.xml for inclusion at
> build time when a profile is activated (and allow reuse of profies.xml)
> --
>
> Key: MNG-1879
> URL: http://jira.codehaus.org/browse/MNG-1879
> Project: Maven 2
> Type: Improvement
> Reporter: Rahul Thakur
> Fix For: 2.1
>
>
> Here's a use-case where I believe it would make sense to allow
> to be defined for profiles in profiles.xml.
> Lets says I have a web-project that sets up profiles.xml for target build
> environments that it can be deployed on. Target environments can each have
> different J2EE containers. Now this is what happens when I setup my project
> for builds/deploys.
> 1) Set up a build control project, a minimal pom.xml that has contains SCM
> connection to my web-project above.
> 2) checks out profiles.xml first so now the build control project has a
> minimal pom + profiles.xml.
> 3) checks out the web-project under ${basedir}/target
> 4) I can activate a particular profile, based on which some operations can be
> done by a custom Plugin before an embedded instance of maven is spawned
> and some goals (specific to that profile) are delegated down to the checked
> out project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1067) Replace the mock plugin data with real data
[ http://jira.codehaus.org/browse/MNG-1067?page=all ] John Casey updated MNG-1067: Fix Version: 2.1 > Replace the mock plugin data with real data > --- > > Key: MNG-1067 > URL: http://jira.codehaus.org/browse/MNG-1067 > Project: Maven 2 > Type: Task > Components: Embedding > Reporter: Jason van Zyl > Fix For: 2.1 > > > Initially we need to download the plugin metadata and use that to grab the > metadata from a plugin JAR. Eventually we can create an index. -- 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: (MNG-1086) Use the embedder in Maven's integration tests
[ http://jira.codehaus.org/browse/MNG-1086?page=all ] John Casey updated MNG-1086: Fix Version: 2.1 > Use the embedder in Maven's integration tests > - > > Key: MNG-1086 > URL: http://jira.codehaus.org/browse/MNG-1086 > Project: Maven 2 > Type: Task > Components: integration tests > Reporter: Jason van Zyl > Fix For: 2.1 > > -- 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: (MNG-2053) Implements a better toString method in the maven objects exemple in : o.a.m.p.MavenProject
[ http://jira.codehaus.org/browse/MNG-2053?page=all ] John Casey updated MNG-2053: Fix Version: 2.1 > Implements a better toString method in the maven objects exemple in : > o.a.m.p.MavenProject > -- > > Key: MNG-2053 > URL: http://jira.codehaus.org/browse/MNG-2053 > Project: Maven 2 > Type: Improvement > Versions: 2.0.2 > Environment: all > Reporter: Olivier Lamy > Fix For: 2.1 > > > In order to debug mojo, I use mvn -X. > Exemple with the eclipse plugin, I have something like this in the output : > [DEBUG] (f) reactorProjects = [EMAIL PROTECTED], > [EMAIL PROTECTED], org.apache.maven.project.MavenP > [EMAIL PROTECTED], [EMAIL PROTECTED], org.apache.maven. > [EMAIL PROTECTED], [EMAIL PROTECTED], o > [EMAIL PROTECTED], org.apache.maven.project.MavenPro > [EMAIL PROTECTED], [EMAIL PROTECTED] > Could we have a better toString() method with the minimum of information in > case of maven project groupId, artifactId and version ? > This could be done with a lot of core object Resource > Olivier -- 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: (MNG-1448) Easy way to tell if the plugin is for m2 or m1
[ http://jira.codehaus.org/browse/MNG-1448?page=all ] John Casey updated MNG-1448: Fix Version: 2.1 > Easy way to tell if the plugin is for m2 or m1 > -- > > Key: MNG-1448 > URL: http://jira.codehaus.org/browse/MNG-1448 > Project: Maven 2 > Type: Bug > Reporter: Alexandre Poitras > Fix For: 2.1 > > -- 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: (MNG-3) MavenProject / pom listener
[ http://jira.codehaus.org/browse/MNG-3?page=all ] John Casey updated MNG-3: - Fix Version: 2.1 > MavenProject / pom listener > --- > > Key: MNG-3 > URL: http://jira.codehaus.org/browse/MNG-3 > Project: Maven 2 > Type: Improvement > Components: Embedding, Inheritence and Interpolation > Reporter: gilles dodinet > Fix For: 2.1 > > > ide integration needs a listener mechanism so that when project/model is > changed interested parties are notified and can eventually reflect those > changes (f.i. refresh a view). we've implemented that in mevenide, please see > : > http://cvs.mevenide.codehaus.org/cvsweb.cgi/mevenide-core/src/java/org/mevenide/project/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-1636) option for a fast bootstrap
[ http://jira.codehaus.org/browse/MNG-1636?page=all ] John Casey updated MNG-1636: Fix Version: 2.1 > option for a fast bootstrap > --- > > Key: MNG-1636 > URL: http://jira.codehaus.org/browse/MNG-1636 > Project: Maven 2 > Type: Task > Components: Bootstrap & Build > Reporter: Brett Porter > Fix For: 2.1 > > > add an option to not rebuild the maven install and instead install the phase1 > install directly (since it is a complete install). -- 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: (MNG-1872) finalname not really final
[ http://jira.codehaus.org/browse/MNG-1872?page=all ] John Casey updated MNG-1872: Fix Version: 2.1 > finalname not really final > -- > > Key: MNG-1872 > URL: http://jira.codehaus.org/browse/MNG-1872 > Project: Maven 2 > Type: Bug > Reporter: Miguel Griffa > Fix For: 2.1 > > > when overwriting finalname in profiles, the... well, the final name > specified, is not really the final name, > this property is ignored both for snapshots and non-snapshots -- 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: (MNG-1053) Reactor mediates projects like dependencies
[ http://jira.codehaus.org/browse/MNG-1053?page=all ] John Casey updated MNG-1053: Fix Version: 2.1 > Reactor mediates projects like dependencies > --- > > Key: MNG-1053 > URL: http://jira.codehaus.org/browse/MNG-1053 > Project: Maven 2 > Type: Bug > Components: Reactor and workspace > Versions: 2.0-beta-3 > Environment: Windows XP, Cygwin > Reporter: Mark Hobson > Fix For: 2.1 > Attachments: test.zip > > > The attached zip contains the following projects: > test:a:1.0 > test:a:2.0 > Running m2 -r install in the project's parent directory results in only > test:a:2.0 being built. It appears that m2 mediates out projects in the > reactor in the same manner as dependencies. -- 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: (MNG-751) replace plexus-archiver with commons-compress
[ http://jira.codehaus.org/browse/MNG-751?page=all ] John Casey updated MNG-751: --- Fix Version: 2.1 > replace plexus-archiver with commons-compress > - > > Key: MNG-751 > URL: http://jira.codehaus.org/browse/MNG-751 > Project: Maven 2 > Type: Task > Reporter: Brett Porter > Fix For: 2.1 > > > commons-compress and plexus-archiver are both originally from Ant. Let's > consolidate the work and maintain one version. -- 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: (MNG-2133) plugin goal skipped if not bound to any phase and no default phase exists in the mojo.
[ http://jira.codehaus.org/browse/MNG-2133?page=all ] John Casey updated MNG-2133: Fix Version: 2.1 > plugin goal skipped if not bound to any phase and no default phase exists in > the mojo. > -- > > Key: MNG-2133 > URL: http://jira.codehaus.org/browse/MNG-2133 > Project: Maven 2 > Type: Bug > Components: Plugins and Lifecycle > Reporter: Prasad Kashyap > Fix For: 2.1 > > > In a pom, if no phase is specified for a plugin, then it is bound to the > default phase defined by the mojo. > However, if the mojo doesn't have a default phase, then it currently seems to > be skipped, which is a probably incorrect. -- 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: (MNG-1084) Review thread safety in maven to make the embedder safe to use
[ http://jira.codehaus.org/browse/MNG-1084?page=all ] John Casey updated MNG-1084: Fix Version: 2.1 > Review thread safety in maven to make the embedder safe to use > -- > > Key: MNG-1084 > URL: http://jira.codehaus.org/browse/MNG-1084 > Project: Maven 2 > Type: Task > Components: Embedding > Reporter: Jason van Zyl > Fix For: 2.1 > > > I've found several things so far so a general review needs to be done. -- 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: (MNG-1501) Provide more debug information in wagon (http request/response/headers)
[ http://jira.codehaus.org/browse/MNG-1501?page=all ] John Casey updated MNG-1501: Fix Version: 2.1 > Provide more debug information in wagon (http request/response/headers) > --- > > Key: MNG-1501 > URL: http://jira.codehaus.org/browse/MNG-1501 > Project: Maven 2 > Type: Improvement > Reporter: Olivier Lamy > Fix For: 2.1 > > > Is there any way to have more debug information concerning wagon with the > option -e -X ? > Like commons-httpclient does : > - http requests > - http response > - http headers > Thanks, > - Olivier -- 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: (MNG-1495) maven-exampletree-plugin
[ http://jira.codehaus.org/browse/MNG-1495?page=all ] John Casey updated MNG-1495: Fix Version: 2.1 > maven-exampletree-plugin > > > Key: MNG-1495 > URL: http://jira.codehaus.org/browse/MNG-1495 > Project: Maven 2 > Type: New Feature > Components: Plugin Requests > Reporter: Jason van Zyl > Fix For: 2.1 > > > A plugin which shows a tree of a project where descriptions can be attached > to nodes for explanatory purposes. > An example of this is here: http://codehaus.org/~jvanzyl/usd/mcm.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] Updated: (MNG-2086) Support writing all generated output to a different filesystem base to that of the project files (i.e. all non generated files)
[ http://jira.codehaus.org/browse/MNG-2086?page=all ] John Casey updated MNG-2086: Fix Version: 2.1 > Support writing all generated output to a different filesystem base to that > of the project files (i.e. all non generated files) > --- > > Key: MNG-2086 > URL: http://jira.codehaus.org/browse/MNG-2086 > Project: Maven 2 > Type: Improvement > Reporter: John Allen > Fix For: 2.1 > > > It is a useful and powerful feature for a build system to support using a > different base directory for all generated output. This enables the project > source (pom et al) to be accessed from read-only or networked location and > for all generated output to be written to a local filesystem location. > Currently maven will write all generated output locations relative to the > project and although this can be ovverriden via build-directory on a per > project basis (ignoring the outstanding JIRA re this not working) it would be > better if maven could be given a new output directory root for all generated > output and have it replicate the project structure as required... > E.g.: > \mnt\dev\projects\A > \mnt\dev\projects\A\src\... > \mnt\dev\projects\A\B > \mnt\dev\projects\A\B\src\... > maven.build-root = \home\developer\dev > Results in: > \home\developer\dev\projects\A > \home\developer\dev\projects\A\target\... > \home\developer\dev\projects\A\B > \home\developer\dev\projects\A\B\target\... -- 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
