[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_67803 ] Brett Porter commented on MWAR-33: -- confirmed regression since beta-2 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.0.1 Original Estimate: 15 minutes Remaining: 15 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: (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_67810 ] Brett Porter commented on MWAR-33: -- ok, it took me a bit to realise this was because the war is being unpacked. You should use warExclude for now. This is a much bigger change that will require excluding WEB-INF/lib *and* pulling in the dependencies from the dependant WAR using the maven artifact mechanism. I don't think it's a good idea to exclude the WEB-INF/lib by default without that, though. 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] Updated: (MWAR-33) jars with differents versions can be in WEB-INF/lib with war as dependencies
[ http://jira.codehaus.org/browse/MWAR-33?page=all ] Brett Porter updated MWAR-33: - Fix Version: (was: 2.0.1) 2.1 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] Closed: (MNG-2397) update docck plugin rules to implement the plugin document standard
[ http://jira.codehaus.org/browse/MNG-2397?page=all ] Edwin Punzalan closed MNG-2397: --- Resolution: Fixed Fixed in SVN update docck plugin rules to implement the plugin document standard --- Key: MNG-2397 URL: http://jira.codehaus.org/browse/MNG-2397 Project: Maven 2 Type: New Feature Components: Sandbox Versions: documentation Reporter: Edwin Punzalan Assignee: Edwin Punzalan Original Estimate: 6 hours Remaining: 6 hours See: http://www.nabble.com/Plugin-documentation-standard-t1811662.html#a4938506 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=all ] Marvin King updated MWAR-48: Attachment: MWAR-48-maven-war-plugin[draft].patch review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Type: Task Versions: 2.0 Reporter: Marvin King Assignee: Marvin King Attachments: MWAR-48-maven-war-plugin[draft].patch Time Spent: 10 hours Remaining: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAVADOC-72) Aggregating javadocs doesn't work
[ http://jira.codehaus.org/browse/MJAVADOC-72?page=comments#action_67815 ] Andrea Aime commented on MJAVADOC-72: - I already updated to 2.0 final, yet the problem is still there... Aggregating javadocs doesn't work - Key: MJAVADOC-72 URL: http://jira.codehaus.org/browse/MJAVADOC-72 Project: Maven 2.x Javadoc Plugin Type: Bug Versions: 2.0 Environment: WinXP SP2 cygwin 1.5.19 maven 2.0.4 jdk 1.5.0_06 javadoc-plugin 2.0 final latest released plugins Reporter: Bugittaa Pahasti When I define aggregatetrue/aggregate to javadoc plugin configuration in parent pom, javadoc generation doesn't work from the parent (all other configuration options are default). If run under individual components, javadoc is generated without problems. It seems that the child dependencies aren't resolved: Embedded error: Exit code: 1 - c:/code/apps/project/common/src/main/java/com/company/AbstractLogEnabled.java:3: package org.apache.log4j does not exist import org.apache.log4j.Logger; c:/code/apps/component/common-test/src/main/java/com/company/unittest/AbstractDatasourceEnabledTestCase.java:11: package org.apache.commons.dbcp does not exist import org.apache.commons.dbcp.BasicDataSource; And lot more similar errors. Additionally, there are a huge number of ClassCastExceptions from javadoc. java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:804) at com.sun.tools.doclets.formats.html.TagletWriterImpl.deprecatedTagOutput(TagletWriterImpl.java:85) at com.sun.tools.doclets.internal.toolkit.taglets.DeprecatedTaglet.getTagletOutput(DeprecatedTaglet.java:40) at com.sun.tools.doclets.formats.html.MethodWriterImpl.writeDeprecated(MethodWriterImpl.java:166) at com.sun.tools.doclets.internal.toolkit.builders.MethodBuilder.buildDeprecationInfo(MethodBuilder.java:183) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.tools.doclets.internal.toolkit.builders.MethodBuilder.invokeMethod(MethodBuilder.java:109) at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90) at com.sun.tools.doclets.internal.toolkit.builders.AbstractMemberBuilder.build(AbstractMemberBuilder.java:56) at com.sun.tools.doclets.internal.toolkit.builders.MethodBuilder.buildMethodDoc(MethodBuilder.java:150) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.tools.doclets.internal.toolkit.builders.MethodBuilder.invokeMethod(MethodBuilder.java:109) at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90) at com.sun.tools.doclets.internal.toolkit.builders.AbstractMemberBuilder.build(AbstractMemberBuilder.java:56) at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildMethodDetails(ClassBuilder.java:322) at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101) at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90) at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildClassDoc(ClassBuilder.java:124) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101) at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90) at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.build(ClassBuilder.java:108) at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:155) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:177) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:161) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106) at
[jira] Updated: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=all ] Marvin King updated MWAR-48: Attachment: MWAR-48-maven-war-plugin[draft2].patch review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Type: Task Versions: 2.0 Reporter: Marvin King Assignee: Marvin King Attachments: MWAR-48-maven-war-plugin[draft2].patch, MWAR-48-maven-war-plugin[draft].patch Time Spent: 15 hours Remaining: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=all ] Marvin King updated MWAR-48: Attachment: (was: MWAR-48-maven-war-plugin[draft2].patch) review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Type: Task Versions: 2.0 Reporter: Marvin King Assignee: Marvin King Attachments: MWAR-48-maven-war-plugin[draft].patch Time Spent: 15 hours Remaining: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=all ] Marvin King updated MWAR-48: Attachment: MWAR-48-maven-war-plugin[draft2].patch review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Type: Task Versions: 2.0 Reporter: Marvin King Assignee: Marvin King Attachments: MWAR-48-maven-war-plugin[draft2].patch, MWAR-48-maven-war-plugin[draft].patch Time Spent: 15 hours Remaining: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-522) IRC support needed for IRC servers not supporting /privmsg
[ http://jira.codehaus.org/browse/CONTINUUM-522?page=comments#action_67816 ] Andrew Williams commented on CONTINUUM-522: --- I think this might be needed for freenode.net too, as I cannot get the bot to report to that network... IRC support needed for IRC servers not supporting /privmsg -- Key: CONTINUUM-522 URL: http://jira.codehaus.org/browse/CONTINUUM-522 Project: Continuum Type: Improvement Components: IRC Notifier Versions: 1.0.2 Environment: Linux Reporter: Daniel Kulp The IRC server we use in house does not support /privmsg for any non-operator user. The IS folks are refusing to add any other operators for use by the continuum builds. It would be nice if we could configure the IRC notifier to do a normal: /join #channel and then a normal text message is sent. -- 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: (MRAR-10) Excluding pom.xml and pom.properties files from the generated rar
[ http://jira.codehaus.org/browse/MRAR-10?page=comments#action_67818 ] Anita Kulshreshtha commented on MRAR-10: Thanks Brett! Excluding pom.xml and pom.properties files from the generated rar - Key: MRAR-10 URL: http://jira.codehaus.org/browse/MRAR-10 Project: Maven 2.x Rar Plugin Type: Wish Environment: All Reporter: Anita Kulshreshtha Assignee: Brett Porter It would be nice to be able to exclude pom.xml and pom.properties files from the generated rar. -- 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: (MDEPLOY-35) Review Plugin Documentation
[ http://jira.codehaus.org/browse/MDEPLOY-35?page=comments#action_67825 ] Allan Ramirez commented on MDEPLOY-35: -- hi, already committed the docs. btw, do i have to make configuration for the deploy goal.. the docs can already be found at the guides http://maven.apache.org/guides/mini/guide-deploy-ftp.html http://maven.apache.org/guides/mini/guide-deploy-ssh-external.html and also in the usage.html Review Plugin Documentation --- Key: MDEPLOY-35 URL: http://jira.codehaus.org/browse/MDEPLOY-35 Project: Maven 2.x Deploy Plugin Type: Task Versions: 2.2 Reporter: Allan Ramirez Assignee: Allan Ramirez Fix For: 2.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] Commented: (MWAR-50) Can't exclude more than one resource from war
[ http://jira.codehaus.org/browse/MWAR-50?page=comments#action_67829 ]
Stephane Nicoll commented on MWAR-50:
-
which version of the war plugin are you using?
Can't exclude more than one resource from war
-
Key: MWAR-50
URL: http://jira.codehaus.org/browse/MWAR-50
Project: Maven 2.x War Plugin
Type: Bug
Reporter: Hugo Palma
Fix For: 2.0.1
I'm trying to use the excludes configuration to exclude some resources from
the generated war. When i use only one exclude filter it works fine, but when
i add another filter none works, eg:
{code:xml}
plugin
artifactIdmaven-war-plugin/artifactId
configuration
excludesWEB-INF/lib/*,WEB-INF/temp/*/excludes
/configuration
/plugin
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (MWAR-50) Can't exclude more than one resource from war
[ http://jira.codehaus.org/browse/MWAR-50?page=all ]
Hugo Palma closed MWAR-50:
--
Resolution: Fixed
Fix Version: (was: 2.0.1)
2.0
Ok, i added version2.0/version to get the 2.0 version and the problem is
solved.
Thanks for the tip.
Can't exclude more than one resource from war
-
Key: MWAR-50
URL: http://jira.codehaus.org/browse/MWAR-50
Project: Maven 2.x War Plugin
Type: Bug
Reporter: Hugo Palma
Assignee: Stephane Nicoll
Fix For: 2.0
I'm trying to use the excludes configuration to exclude some resources from
the generated war. When i use only one exclude filter it works fine, but when
i add another filter none works, eg:
{code:xml}
plugin
artifactIdmaven-war-plugin/artifactId
configuration
excludesWEB-INF/lib/*,WEB-INF/temp/*/excludes
/configuration
/plugin
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-732) Add dependencies to the python code in continuum-core-it
[ http://jira.codehaus.org/browse/CONTINUUM-732?page=all ] Emmanuel Venisse updated CONTINUUM-732: --- Fix Version: (was: 1.0.3) 1.1 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 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] Created: (MSITE-151) Ability to change the site directory in the plugin configuration in the pom.xml file.
Ability to change the site directory in the plugin configuration in the pom.xml file. - Key: MSITE-151 URL: http://jira.codehaus.org/browse/MSITE-151 Project: Maven 2.x Site Plugin Type: Improvement Versions: 2.0-beta-5 Environment: All Reporter: Mark Soderquist Fix For: 2.0-beta-5 Attachments: AbstractSiteMojo.diff Added the ability to change the site directory via the plugin configuration in the pom.xml file. This completes an existing TODO in the code. Attached is the SVN diff file for the patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-949) Fluent API Plugin for JAXB RI 2.0.1 XJC
[ http://jira.codehaus.org/browse/MAVENUPLOAD-949?page=all ] Carlos Sanchez closed MAVENUPLOAD-949: -- Assign To: Carlos Sanchez Resolution: Fixed Fluent API Plugin for JAXB RI 2.0.1 XJC --- Key: MAVENUPLOAD-949 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-949 Project: maven-upload-requests Type: Task Reporter: Hanson Char Assignee: Carlos Sanchez Attachments: maven-jaxb-fluent-api-2.0.1.jar, maven-jaxb-fluent-api-2.0.1.jar, maven-jaxb-fluent-api-2.0.1.jar Causes JAXB RI 2.0.1 XJC to generate additional methods that allows method chaining. Method chaining is useful when building object tree in memory, allowing the code to be done in a concise way. The code that uses this plugin can still run with any JAXB2 implementation. -- 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: (MAVENUPLOAD-951) Bsh 2.0b4 jar for m1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-951?page=all ] Carlos Sanchez closed MAVENUPLOAD-951: -- Assign To: Carlos Sanchez Resolution: Won't Fix m1 repo redirects requests to m2 repo use org.beanshell as groupid Bsh 2.0b4 jar for m1 Key: MAVENUPLOAD-951 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-951 Project: maven-upload-requests Type: Task Reporter: Mauro Talevi Assignee: Carlos Sanchez Could the bsh-2.0b4.jar in m2 repo http://www.ibiblio.org/maven2/org/beanshell/bsh/2.0b4/ please be made available in the m1 repo http://www.ibiblio.org/maven/bsh ? Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-950) Upload new FindBugs 1.0.0 artifacts to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-950?page=all ] Carlos Sanchez closed MAVENUPLOAD-950: -- Assign To: Carlos Sanchez Resolution: Fixed Next time please add license info Upload new FindBugs 1.0.0 artifacts to ibiblio -- Key: MAVENUPLOAD-950 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-950 Project: maven-upload-requests Type: Improvement Reporter: Jeff Jensen Assignee: Carlos Sanchez Attachments: annotations-1.0.0-bundle.jar, coreplugin-1.0.0-bundle.jar, findbugs-1.0.0-bundle.jar, findbugs-ant-1.0.0-bundle.jar, findbugsGUI-1.0.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGECLIPSE-106) Dependency Resolver and PDE conflicts
[ http://jira.codehaus.org/browse/MNGECLIPSE-106?page=comments#action_67837 ] Scott Cytacki commented on MNGECLIPSE-106: -- I've found a way to have a maven project double as a eclipse plugin. I don't know if this solves your particular problem but it is mostly working for me. My main problem is that I have two types of dependencies: 1. Those that are available as both maven artifacts and plugins. 2. Those that are only available as maven artifacts. If a project has dependencies of type 1. Then it is easy, simply choose between the maven classpath container and the plugin classpath container. Remove one of them. Even if you remove the plugin classpath container, the plugin project can still be used by other plugin projects and it can still be used in a testing eclipse application. If a project has dependencies of type 2, then make a second plugin project that contains those maven dependencies. So lets say the project you are working with is called: MyPlugin. It has maven deps on jug and xstream. If you add jug and xtream to the MyPlugin plugin classpath you will get conflicts. So instead make a new plugin project called MyPluginDeps, and add jug and xstream to this project. Now change the MyPlugin manifest.mf so it depends on MyPluginDeps. Now the MyPlugin project will build with either the maven classpath container or the plugin classpath container. This isn't the perfect solution: 1. the dependencies need to be updated in two places. 2. if the dependencies are not the same you might have different jars at runtime than at compile time. The way I'm managing the dependencies right now is to use the maven assembly:assembly goal with the descriptorId set to jar-with-dependencies This creates a single jar that contains all dependencies combined into one jar. I then copy this jar into the MyPluginDeps project. Dependency Resolver and PDE conflicts - Key: MNGECLIPSE-106 URL: http://jira.codehaus.org/browse/MNGECLIPSE-106 Project: Maven 2.x Extension for Eclipse Type: Improvement Components: Dependency Resolver Environment: Eclipse PDE Reporter: Dimitry Voytenko Assignee: Eugene Kuleshov Attachments: sample-plugins.zip All tests have been done using the solution provided in the http://jira.codehaus.org/browse/MNGECLIPSE-59. This solution works very well, but there're specifics when using it in the PDE (Plugin Development) environment. Attached are sample plugins that demonstrate the issue (tested under Eclipse 3.1.2). Unpack sample-plugins.zip and import projects in the workspace. Patch from MNGECLIPSE-59 should be applied. Rebuild both projects. Build of com.example.plugins.main should fail with an error: Build path contains duplicate entry: 'com.example.plugins.component' for project com.example.plugins.main The problem occures b/c of conflict b/w PDE classpath container and Maven2 classpath container. They both contain com.example.plugins.component project. PDE's classpath container is defined in the org.eclipse.pde.core plugin as an org.eclipse.pde.core.requiredPlugins extension. It uses META-INF/MANIFEST.MF file as a source. MANIFEST.MF is basically an OSGI manifest that lists all dependent bundles in the form: Require-Bundle: org.eclipse.core.runtime, ... with optionally specified version and transiting information. Both manifest and PDE container are very essential for the PDE work. It's not clear if they can be properly extended to avoid conflicts. If such a way can be found, it is important to keep in mind the similarities and differences b/w Maven and PDE dependency management: a) PDE dependencies have flags optional and re-exported. By default dependencies are required and non-transient. The optional property can be modeled via Maven'2 optional dependency. The re-exported property basically makes the dependency transient. I'm not sure if all of these states can be modelled via Maven's scope. b) Version management is different. PDE allows to specify dependency on the latest found version of a plugin (if version parameters is specified then it should be greater or equal). In Eclipse 3.2 it's actually possible to specify both borders, i.e. version no earlier than 2.0.0 and no later than 3.0.0. c) MANIFEST.MF is a deployable file. It's used at runtime to build the classloader graph. If it's not possible to extend PDE to source it from the Maven's configuration a temporary solution could be to exclude a dependent project from the Maven container if it can be found elsewhere in the classpath. The possible issue here: if it's possible to get the access from Maven container to the content of the other containers. Cooperation with Eclipse team would probably help here as this would also benefit them in the long run. -- This message is
[jira] Created: (MNGECLIPSE-145) dependencyManagement in parent poms broken in eclipse on linux
dependencyManagement in parent poms broken in eclipse on linux
--
Key: MNGECLIPSE-145
URL: http://jira.codehaus.org/browse/MNGECLIPSE-145
Project: Maven 2.x Extension for Eclipse
Type: Bug
Components: Dependency Resolver
Versions: 0.0.9
Reporter: Scott Cytacki
Assigned to: Eugene Kuleshov
Attachments: pom.xml
This is a weird one. I don't know if it is a maven embedder bug or an eclipse
plugin bug. I attached a test pom.
This pom has a single dependency on org.codehaus.xfire:xfire-java5
From the command line I can run mvn compile and it downloads the correct xfire
artifacts. I tried it both with maven 2.0.2 and 2.0.4
When I enable maven on the project in eclipse using 0.0.9 maven plugin,
eclipse 3.2RC5, linux. It fails saying it cant find:
org.codehaus.xfire:xfire-core:jar:2.4.1
org.codehaus.xfire:xfire-aegis:jar:2.4.1
org.codehaus.xfire:xfire-annotations:jar:2.4.1
When I try the same thing on maven plugin 0.0.9, eclipse 3.2RC7, intel mac.
It works fine.
I looked into the xfire poms, and they are using a fancy dependency setup.
xfire-java5 dependends on xfire-core but it doesn't specifiy a version number.
The version is supposed to be pulled from the dependency management in the
parent pom: xfire-parent. Actually the dependency management section of the
xfire-parent doesn't have the version for each dependency instead it uses:
${version}. Which I assume pulles the version from xfire-parent itself. So
some how this double indirection of version number is confusing only linux. It
could also be the version of eclipse.
--
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-2399) file size check on pom.xml (or thing specified by --file opt) should only apply to regular files (patch attached)
[ http://jira.codehaus.org/browse/MNG-2399?page=all ]
Alan D. Salewski updated MNG-2399:
--
Attachment: MNG-2399-maven-core-2.0.4.patch
MNG-2399-maven-core-trunk.patch
file size check on pom.xml (or thing specified by --file opt) should only
apply to regular files (patch attached)
-
Key: MNG-2399
URL: http://jira.codehaus.org/browse/MNG-2399
Project: Maven 2
Type: Bug
Components: General, Command Line
Versions: 2.0.4
Reporter: Alan D. Salewski
Priority: Minor
Attachments: MNG-2399-maven-core-2.0.4.patch,
MNG-2399-maven-core-trunk.patch, mvn-get-plugin
The file size check in {{maven-core/.../org/apache/maven/DefaultMaven.java}}
is applied too aggressively. In particular, it should only be applied to
regular files; when reading from a unix named pipe (probably other
platform-specific devices, too) we may not be able to determine the file size
prior to reading the data.
The real-world motiviation from this is the attached '{{mvn-get-plugin}}'
{{bash}} script, which wants to pipe a dummy {{pom.xml}} file to {{mvn}} on
{{stdin}} (by specifying {{/dev/stdin}} as the argument to the {{mvn}}
{{\-\-file}} command line option).
Once I submit this issue and have the issue number, I'll attach two patches,
one against the maven svn trunk, and one against the {{maven-2.0.4}} tag.
--
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: (MDEPLOY-36) Custom ArtifactRepositoryLayouts confuse deploy-file
Custom ArtifactRepositoryLayouts confuse deploy-file Key: MDEPLOY-36 URL: http://jira.codehaus.org/browse/MDEPLOY-36 Project: Maven 2.x Deploy Plugin Type: Bug Versions: 2.2 Reporter: Matthew Beermann Fix For: 2.2.1 We've created some custom ArtifactRepositoryLayouts. They work just fine, but they seem to confuse the deploy-file goal. In particular, if the custom layout is present in maven-2.0.4\libs, then it will cause deploy-file to _always_ use the legacy layout, regardless of the value of -DrepositoryLayout. I'm pretty sure our custom ArtifactRepositoryLayout is written correctly, but just in case, here's the contents of components.xml: component-set components component roleorg.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout/role role-hinteclipse/role-hint implementationorg.apache.maven.artifact.repository.layout.EclipseRepositoryLayout/implementation /component /components /component-set -- 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-953) Custom dom4j for Maven 1
Custom dom4j for Maven 1 Key: MAVENUPLOAD-953 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-953 Project: maven-upload-requests Type: Task Reporter: Lukas Theussl This is a custom version of dom4j needed by m1, see MAVEN-1345. It is identified by namedom4j/name groupIdmaven/groupId artifactIddom4j/artifactId currentVersion1.7-20060614/currentVersion and was built from dom4j cvs trunk as of 2006-06-08 with the branch DOM4J_1_X_BRANCH merged in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-46) Don't set checkstyle.header.file property when using a custom checkstyle xml file
Don't set checkstyle.header.file property when using a custom checkstyle xml
file
-
Key: MCHECKSTYLE-46
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-46
Project: Maven 2.x Checkstyle Plugin
Type: Bug
Versions: 2.1
Reporter: Carlos Sanchez
Fix For: 2.2
I'd like to use this code in my xml, but maven will always set
checkstyle.header.file to LICENSE.txt, forcing me to set also headerLocation
{code}
module name=RegexpHeader
property name=headerFile value=${checkstyle.header.file}
default=config/maven-header.txt/
/module
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-47) Allow running checkstyle in test sources
Allow running checkstyle in test sources Key: MCHECKSTYLE-47 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-47 Project: Maven 2.x Checkstyle Plugin Type: New Feature Versions: 2.1 Reporter: Carlos Sanchez Fix For: 2.2 I think this is already implemented in maven 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-1015) Look at where to ideally attach a wagon TransferListener
[ http://jira.codehaus.org/browse/MNG-1015?page=all ] John Casey updated MNG-1015: Fix Version: 2.1 Look at where to ideally attach a wagon TransferListener Key: MNG-1015 URL: http://jira.codehaus.org/browse/MNG-1015 Project: Maven 2 Type: Task Components: Embedding, Artifacts and Repositories Reporter: Jason van Zyl Fix For: 2.1 I am adding the WagonManager to the MavenProjectBuilder so that I can attach a monitor to buildProjectWithDependencies but this might not be ideal. Right now with method is being employed in MavenCli but I hope to be able to use the embedder inside MavenCli so this should be revisited. Could probably attach the monitor via the artifact resolver. -- 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-1085) Use the embedder in MavenCLI
[ http://jira.codehaus.org/browse/MNG-1085?page=all ] John Casey updated MNG-1085: Fix Version: 2.1 Use the embedder in MavenCLI Key: MNG-1085 URL: http://jira.codehaus.org/browse/MNG-1085 Project: Maven 2 Type: Task Components: Command Line Reporter: Jason van Zyl Fix For: 2.1 The embedder should be the single point of entry for client code, including our own. -- 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-2108) archive element in assembly descriptor
[ http://jira.codehaus.org/browse/MNG-2108?page=all ] John Casey updated MNG-2108: Fix Version: 2.1 archive element in assembly descriptor -- Key: MNG-2108 URL: http://jira.codehaus.org/browse/MNG-2108 Project: Maven 2 Type: Improvement Components: Artifacts Versions: 2.0.2 Reporter: Greg Wilkins Fix For: 2.1 Currently it is not possible to have an archive element (and thus manipulate the manifest) in an assembly descriptor. This means that manifest entries must be set in the assembly plugin configuration and this makes it difficult to have different manifests for different assemblies. -- 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-1671) dependant plugins need to be built before any runMaven calls
[ http://jira.codehaus.org/browse/MNG-1671?page=all ] John Casey updated MNG-1671: Fix Version: 2.1 dependant plugins need to be built before any runMaven calls Key: MNG-1671 URL: http://jira.codehaus.org/browse/MNG-1671 Project: Maven 2 Type: Bug Components: Bootstrap Build Reporter: Brett Porter Fix For: 2.1 need to do interim builds of anything in the jar lifecycle before any runMaven() calls to avoid downloading in the instance that we are building the plugins from source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2110) ArtifactRepositoryLayout isn't extensible
[ http://jira.codehaus.org/browse/MNG-2110?page=all ] John Casey updated MNG-2110: Fix Version: 2.1 ArtifactRepositoryLayout isn't extensible - Key: MNG-2110 URL: http://jira.codehaus.org/browse/MNG-2110 Project: Maven 2 Type: Bug Components: Artifacts and Repositories Versions: 2.0.2 Reporter: Matthew Beermann Fix For: 2.1 I'm writing a plugin that (among other tasks) provides a new ArtifactRepositoryLayout suitable for Eclipse repositories. In my META-INF/plexus/components.xml, I have: component roleorg.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout/role role-hinteclipse/role-hint implementationorg.apache.maven.artifact.repository.layout.EclipseArtifactRepositoryLayout/implementation /component This plugin is listed in the POM with extensionstrue/extensions. I would expect that a repository/ with layouteclipse/eclipse would discover and load this layout provider. Instead, it simply results in an exception. Note that this same components.xml file also defines some lifecycle mappings, which work perfectly. [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find layout implementation corresponding to: 'eclipse' for remote repository with id: 'Eclipse Update Site'. at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayouteclipse. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) -- 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-2016) Document how to create a mirror of Ibiblio
[ http://jira.codehaus.org/browse/MNG-2016?page=all ] John Casey updated MNG-2016: Fix Version: 2.1 Document how to create a mirror of Ibiblio -- Key: MNG-2016 URL: http://jira.codehaus.org/browse/MNG-2016 Project: Maven 2 Type: Task Components: Documentation: General, Artifacts and Repositories Reporter: Trygve Laugstol Fix For: 2.1 Tips on what this document could include: o Find a pointer to the list of Ibiblio mirrors o Give an example command line for at least rsync, wget and curl where the two last ones will use ftp o Give an example cron expression and /etc/cron.d/ file that's useful for making a mirrors including setting the correct permissions o Give an example Apache configuration on how to configure Apache to serve the mirror This document should possibly be a part of http://maven.apache.org/guides/mini/guide-mirror-settings.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-1119) Allow to use custom pom resolution strategy
[ http://jira.codehaus.org/browse/MNG-1119?page=all ] John Casey updated MNG-1119: Fix Version: 2.1 Allow to use custom pom resolution strategy --- Key: MNG-1119 URL: http://jira.codehaus.org/browse/MNG-1119 Project: Maven 2 Type: Improvement Reporter: Eugene Kuleshov Fix For: 2.1 Currently all dependencies come from MavenEmbedder.readProjectWithDependencies() method that is using passed pom.xml to resolve dependencies from m2 repositories. It is possible that some of the dependencies could exist as other Eclipse projects in the same workspace. It would be interesting to hook up Eclipse-specific pom resolver, so it would implement IDE-specific logic to check if there are poms avaialble and if nothing is there use default resolution strategy. -- 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-1716) Need to be able to set the ResolutionListener
[ http://jira.codehaus.org/browse/MNG-1716?page=all ] John Casey updated MNG-1716: Fix Version: 2.1 Need to be able to set the ResolutionListener - Key: MNG-1716 URL: http://jira.codehaus.org/browse/MNG-1716 Project: Maven 2 Type: Improvement Components: Embedding Reporter: Jason van Zyl Fix For: 2.1 The ResolutionListeners appear to be hardwired and it needs to be configurable in some fashion. When new ResolutionListener components are added they must be picked up in addition to the code that we are using which programmatically sets the resolution listener. -- 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-1906) properties not being replaced before being passed to plugins (specificaly the surefire plugin)
[ http://jira.codehaus.org/browse/MNG-1906?page=all ]
John Casey updated MNG-1906:
Fix Version: 2.1
properties not being replaced before being passed to plugins (specificaly the
surefire plugin)
--
Key: MNG-1906
URL: http://jira.codehaus.org/browse/MNG-1906
Project: Maven 2
Type: Bug
Reporter: Bill Dudney
Fix For: 2.1
Attachments: foo-root.tar.gz, transcript.txt
in the attached foo-root proj run mvn package from foo-root and you will see
that ${project.build.directory} is not substituted but
${project.x.build.directory} is.
I spent a bit of time chatting with jdcasey on irc on Dec-07-2005 about this
issue if that helps.
--
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
[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-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-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-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-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-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-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-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-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-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-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-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: resources resource directorysrc/main/wsdd/directory includes*.wsdl/includes /resource /resources 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 .../directory\r\n inc ludes*.wsdl/... @71:27) 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-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 parentversion/ affect the requirement for a locally specified version/ 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-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-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-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-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-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-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-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-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 : snip 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. /snip 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: snip As mentioned before, each Plugin - or packaged set of Mojos .. /snip 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-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-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 deprecation/ 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-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-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-1141) document relativePath / 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 relativePath / 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-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-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-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-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-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-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-2026) Document how parent-child POM relationships, modules/, and parentrelativePath/ 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, modules/, and parentrelativePath/ 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 modules/ section work * How does the relativePath/ element of the parent/ section work...and what is required in the parent/ 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-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-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-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-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 developers 3) seek out Submitted by in svn logs to populate contributors -- 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 repository and pluginRepository release should be releases snapshot should be 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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] 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-1995) filtering element in pom.xml ignore properties
[ http://jira.codehaus.org/browse/MNG-1995?page=all ]
John Casey updated MNG-1995:
Description:
jvanzyl you can mention it0091 as the test case
The following pom.xml does not end up filtering the resources:
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdorg.objectweb.celtix/groupId
artifactIdtest/artifactId
packagingjar/packaging
version1.0/version
nameTest/name
properties
filter.resourcestrue/filter.resources
/properties
build
resources
resource
directorysrc/main/resources/directory
includes
include**/include
/includes
filtering${filter.resources}/filtering
/resource
/resources
/build
/project
was:
jvanzyl you can mention it0091 as the test case
The following pom.xml does not end up filtering the resources:
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdorg.objectweb.celtix/groupId
artifactIdtest/artifactId
packagingjar/packaging
version1.0/version
nameTest/name
properties
filter.resourcestrue/filter.resources
/properties
build
resources
resource
directorysrc/main/resources/directory
includes
include**/include
/includes
filtering${filter.resources}/filtering
/resource
/resources
/build
/project
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
jvanzyl you can mention it0091 as the test case
The following pom.xml does not end up filtering the resources:
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdorg.objectweb.celtix/groupId
artifactIdtest/artifactId
packagingjar/packaging
version1.0/version
nameTest/name
properties
filter.resourcestrue/filter.resources
/properties
build
resources
resource
directorysrc/main/resources/directory
includes
include**/include
/includes
filtering${filter.resources}/filtering
/resource
/resources
/build
/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-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-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-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-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: project modelVersion4.0.0/modelVersion nameTour de France Service/name groupIdnl.doyle.mccloud.TourDeFranceService/groupId version0.0.1/version artifactIdTourDeFranceService/artifactId packagingpom/packaging modules module../TourDeFranceServiceEAR/module module../TourDeFranceServiceWeb/module /modules /project This my WAR pom.xml: project modelVersion4.0.0/modelVersion nameTour de France Service Web/name groupIdnl.doyle.mccloud.TourDeFranceService/groupId artifactIdTourDeFranceServiceWeb/artifactId packagingwar/packaging version0.0.2/version dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration webXml../TourDeFranceServiceWeb/WebContent/WEB-INF/web.xml/webXml /configuration /plugin /plugins finalNameTourDeFranceServiceWeb/finalName /build /project And this my EAR pom.xml with the wrong version number of the WAR project: project modelVersion4.0.0/modelVersion nameTour de France Service EAR/name groupIdnl.doyle.mccloud.TourDeFranceService/groupId artifactIdTourDeFranceServiceEAR/artifactId packagingear/packaging version0.0.1/version dependencies dependency groupIdnl.doyle.mccloud.TourDeFranceService/groupId artifactIdTourDeFranceServiceWeb/artifactId typewar/type version1.0.2/version /dependency /dependencies build finalNameTourDeFranceServiceEAR/finalName /build /project 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] 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-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 execution/ + phase/ (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] 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] 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-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
