[jira] Commented: (MNG-2562) expose current time as a property for POM interpolation
[
http://jira.codehaus.org/browse/MNG-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138813#action_138813
]
Benjamin Bentmann commented on MNG-2562:
bq. I'm not sure of the best way to make the format of the time configurable
I like the idea proposed by Sharmarke Aden in MNG-1832:
${mvn.timestamp.DATE_FORMAT}, i.e. simply appending the desired format to the
propery base name. This allows users to easily choose the format for their
respective use case.
The only thing that might be missing is the locale. Could perhaps be integrated
like this: {{${mvn.tstamp-lang,country,variant.DATE_FORMAT}}} which should be
straightforward to parse.
> expose current time as a property for POM interpolation
> ---
>
> Key: MNG-2562
> URL: http://jira.codehaus.org/browse/MNG-2562
> Project: Maven 2
> Issue Type: New Feature
> Components: Inheritance and Interpolation
>Reporter: Brett Porter
>Assignee: John Casey
> Fix For: 2.0.10
>
>
> it is useful to have the current time, for example to write out a manifest
> entry for the build time or to filter into another file.
> I'm not sure of the best way to make the format of the time configurable -
> perhaps another POM element/property.
> See the related issue for a current example of how this can be done, but it
> would be nice to have a built-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: (ARCHETYPE-184) Fail to create multimodule archetype from project : modules created later as "__rootArtifactId__-modulename"
Fail to create multimodule archetype from project : modules created later as "__rootArtifactId__-modulename" Key: ARCHETYPE-184 URL: http://jira.codehaus.org/browse/ARCHETYPE-184 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.0-alpha-3 Environment: creating multimodule archetype from project http://platina.svn.sourceforge.net/svnroot/platina/platina-archetype/trunk/ using the archetype.properties in SVN root Reporter: nicolas de loof Create archetype from project -> OK install -> OK generate -> NOK : __rootArtifactId__-application __rootArtifactId__-business __rootArtifactId__-domain __rootArtifactId__-infrastructure __rootArtifactId__-persistence __rootArtifactId__-remoting __rootArtifactId__-webapp __rootArtifactId__-webservices pom.xml All other elements are fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2093) RabbitMQ Java Client For AMQP
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138831#action_138831 ] Ben Hood commented on MAVENUPLOAD-2093: --- groupId: com.rabbitmq Error: Host key verification failed. rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9] Error synchronizing metadata. Exit code: 255 Here is our host key (as a dsa and rsa) for you to add to your rsync client, if that helps. ssh-dss B3NzaC1kc3MAAACBALMhX8T5i4Y4u32cIC+f7MxGDkRQW0nlbcI8aPI/bFZWfFsjg/VVwkX1SFxvfd+GwF3cp8nmxmaokGRkxBraH5ZkYE6YGcOUh9U4KVqeZohqr/+vXFZK7wRoySq8HsYq6KLa2jKaF7YqmANxwsesTPYPw0B1O3UaP+Pd7ePKTokfFQDhyLSeZuAIn+ao7TnoXjGaA8yUgwAAAIBT9TLaKtL1bE0Rx5uNO6dCNkqiit0vLEVWhEa4EwxDQm0yIHD/VSlfZGk9GubbLzliMinE40jcRU3O+KlqeW46a4DEiuBgBjQGHxKZw3TWt2vIIFfb4AcM3fwEyHHssS0t45ENtlTLDpJM9x3Wf82QhZ2H09Eex+DhFDYzk5obbgAAAIEAnmlLU5xwv2+rjNl1FvCEsVHEnSjZsjawbpqHlt6FHzVGDrAKLO9mZzdtfNV4yOxqXGUgCJS1ce7rmZHMp3wsgE/UjPff9v6ipovtXn4fpWHhVkvGLiprwsfGVycQ4cvE0FxVM+Csj+TDHJZ15liLcwQzLzxtk4PGFFLGLFRlaYk= [EMAIL PROTECTED] ssh-rsa B3NzaC1yc2EBIwAAAQEAzn9oOddHu35nmHBdpCsV/HUeFJVj/ANQKC0day6dZwsHmHvcAD4LfNMIPYUuHV/Bdp/7gbtWUJRlc+evFTViCAhA2EoAmyq3i115dZasonpMA/q8cz2cIOyBfb2Uq8+IJat4QBVO0XS4QaTcyfbEfW9Lb7O5Tk+8dMXTl2uZYaeIWL/mNIWAywpcqkjtTvSzn0/6FpoBosBVodIfwEtEbIz8a256b2UQTrvQueNxyjJCsQNAy94VY7NOChTvw8UKhPw4zkBIxKHcEKXfwQXDyV2aIOaW/RgxQ4IyYR4LGQvsZiHOLjbnJpvVxK3xxK0FfFsC7nQOu3t6KwuC/CRtIw== [EMAIL PROTECTED] > RabbitMQ Java Client For AMQP > - > > Key: MAVENUPLOAD-2093 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2093 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Ben Hood >Assignee: Carlos Sanchez > > "com.rabbitmq","[EMAIL > PROTECTED]:/home/maven/rabbitmq-java-client/","rsync_ssh","Ben Hood","[EMAIL > PROTECTED]" > I am a developer at LShift who is the company that maintains RabbitMQ > (http://www.rabbitmq.com/), which you can see on the site. > Please note that we do not have any links to the development team on the > site, but you can see from whois that our infrastructure manager Stuart > Mottram is the domain owner > (http://www.whois.net/whois_new.cgi?d=rabbitmq&tld=com). > I have set up the rsync server with your public key. > Please let me know if you need any further identification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2106) xradar upload
xradar upload - Key: MAVENUPLOAD-2106 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2106 Project: Maven Upload Requests Issue Type: Wish Reporter: Nicolas Dordet "net.sf.xradar","[EMAIL PROTECTED]:/home/groups/x/xr/xradar/htdocs/m2repo","rsync_ssh","Nicolas Dordet","[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] Created: (MAVENUPLOAD-2107) upload ckjm
upload ckjm --- Key: MAVENUPLOAD-2107 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2107 Project: Maven Upload Requests Issue Type: Wish Reporter: Nicolas Dordet "gr.spinellis","[EMAIL PROTECTED]:/home/groups/c/ck/ckjm/htdocs/m2repo","rsync_ssh","Nicolas Dordet","[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] Created: (MSKINS-4) maven-application-skin does not work in IE7
maven-application-skin does not work in IE7
---
Key: MSKINS-4
URL: http://jira.codehaus.org/browse/MSKINS-4
Project: Maven Skins
Issue Type: Bug
Components: Application Skin
Reporter: Paul Spencer
Revision 440343 of maven-theme.css in maven-application-skin undid revision
430364 - "fix the CSS so that it renders correctly in IE7 and Opera."
Basically the height for #navcolumn li.expanded should be auto.
#navcolumn li.expanded {
background-image: url( ../images/super.gif );
height: auto;
}
Note: The Archiva and Continuum projects may use this skin.
[1]http://svn.apache.org/viewvc/maven/skins/trunk/maven-application-skin/src/main/resources/css/maven-theme.css?r1=430364&r2=440343&diff_format=h
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MSKINS-4) maven-application-skin does not work in IE7
[
http://jira.codehaus.org/browse/MSKINS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSKINS-4.
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: application-1.0
Fixed in r668675.
New SNAPSHOT deployed.
> maven-application-skin does not work in IE7
> ---
>
> Key: MSKINS-4
> URL: http://jira.codehaus.org/browse/MSKINS-4
> Project: Maven Skins
> Issue Type: Bug
> Components: Application Skin
>Reporter: Paul Spencer
>Assignee: Dennis Lundberg
> Fix For: application-1.0
>
>
> Revision 440343 of maven-theme.css in maven-application-skin undid revision
> 430364 - "fix the CSS so that it renders correctly in IE7 and Opera."
> Basically the height for #navcolumn li.expanded should be auto.
> #navcolumn li.expanded {
> background-image: url( ../images/super.gif );
> height: auto;
> }
> Note: The Archiva and Continuum projects may use this skin.
> [1]http://svn.apache.org/viewvc/maven/skins/trunk/maven-application-skin/src/main/resources/css/maven-theme.css?r1=430364&r2=440343&diff_format=h
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MREPOSITORY-5) Plugin website needs to be completed
[ http://jira.codehaus.org/browse/MREPOSITORY-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MREPOSITORY-5. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1 Usage and FAQ are now in place, along with a standard index page. No examples yet, though. I've deployed the site, even though the plugin is still at 2.1-SNAPSHOT. But the site had already been deployed for 2.1-SNAPSHOT, so I figured it would be better to have a site with proper content and no broken links in it. > Plugin website needs to be completed > > > Key: MREPOSITORY-5 > URL: http://jira.codehaus.org/browse/MREPOSITORY-5 > Project: Maven 2.x Repository Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Wendy Smoak >Assignee: Dennis Lundberg > Fix For: 2.1 > > > The Repository plugin site is missing the usage and faq pages, among other > things. Run 'mvn docck:check' for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MREPOSITORY-12) any and all attempts to use locate and download maven-clean-plugin fail
[ http://jira.codehaus.org/browse/MREPOSITORY-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MREPOSITORY-12. -- Resolution: Incomplete This has nothing to do with maven-repository-plugin. > any and all attempts to use locate and download maven-clean-plugin fail > --- > > Key: MREPOSITORY-12 > URL: http://jira.codehaus.org/browse/MREPOSITORY-12 > Project: Maven 2.x Repository Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: mvn 2.0.8 >Reporter: Martin Gainty > > any all attempts to find/locate/use/download maven-clean-plugin fail > [INFO] The plugin 'org.apache.maven.plugins:clean' does not exist or no valid > ve > rsion could be found > [INFO] > > the clean plugin is not available anywhere -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MREPOSITORY-8) improve the error message that tells the user how to install missing jars locally
[
http://jira.codehaus.org/browse/MREPOSITORY-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138849#action_138849
]
Dennis Lundberg commented on MREPOSITORY-8:
---
What command do you type to get this error message?
How is this related to maven-repository-plugin?
> improve the error message that tells the user how to install missing jars
> locally
> -
>
> Key: MREPOSITORY-8
> URL: http://jira.codehaus.org/browse/MREPOSITORY-8
> Project: Maven 2.x Repository Plugin
> Issue Type: Improvement
> Environment: Maven 2.0.4, all platforms
>Reporter: S.
>Priority: Minor
>
> When a missing dependency is detected, maven reports to the user how to
> install that dependency locally ('mvn install:install-file...').
> However, the instructions are missing the '-DgeneratePom=true' directive.
> Without it, maven keeps looking for the dependencies in the repo, causing
> unnecessary delays in the build.
> I suggest to add '-DgeneratePom=true' to the error message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MREPOSITORY-7) When given blank repositories cannot attain goal
[ http://jira.codehaus.org/browse/MREPOSITORY-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138850#action_138850 ] Dennis Lundberg commented on MREPOSITORY-7: --- What command do you type to get this error message? How is this related to maven-repository-plugin? > When given blank repositories cannot attain goal > > > Key: MREPOSITORY-7 > URL: http://jira.codehaus.org/browse/MREPOSITORY-7 > Project: Maven 2.x Repository Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Matthew Purland > > With the example in the pom.xml > > > > > > > > > > > Maven fails with the following: > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at org.apache.maven.wagon.PathUtils.protocol(PathUtils.java:206) > at > org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:119) > at > org.apache.maven.wagon.repository.Repository.(Repository.java:72) > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.(DefaultArtifactRepository.java:84) > at > org.apache.maven.artifact.repository.DefaultArtifactRepositoryFactory.createArtifactRepository(DefaultArtifactRepositoryFactory.java:82) > at > org.apache.maven.project.ProjectUtils.buildArtifactRepository(ProjectUtils.java:102) > at > org.apache.maven.project.ProjectUtils.buildArtifactRepositories(ProjectUtils.java:53) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildArtifactRepositories(DefaultMavenProjectBuilder.java:811) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:958) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:674) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (ARCHETYPE-185) unable to create a project with local repository.
[
http://jira.codehaus.org/browse/ARCHETYPE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MREPOSITORY-9 to ARCHETYPE-185:
-
Affects Version/s: (was: 2.0)
Key: ARCHETYPE-185 (was: MREPOSITORY-9)
Project: Maven Archetype (was: Maven 2.x Repository Plugin)
> unable to create a project with local repository.
> --
>
> Key: ARCHETYPE-185
> URL: http://jira.codehaus.org/browse/ARCHETYPE-185
> Project: Maven Archetype
> Issue Type: Bug
> Environment: Windows XP professional SP2. LAN connected PC with NO
> Internet access.
>Reporter: Alan Lewis
>
> When using maven 2.0.4 for the first time on a PC with no internet access,
> but that has a local copy of the ibiblio maven2 repository, the
> archetype:create fails. The "system" settings.xml [ in {maven2_home}/conf ]
> has been updated to include the section below:
> ...previous text removed for clarity, from default (2.0.4) settings.xml
>
> jdk-1.5
>
> 1.5
>
>
>
> jdk15
> Local Repository for JDK 1.5 builds
> http://localhost/maven2
> default
>
>
>
>
>
> maven2-plugins
> Local Repository for maven2 plugins
> http://localhost/maven2
> default
>
>
>
> ...remainder ignored, from default settings.xml
> This url is accessible from a browser. The local Apache installation is
> 2.0.55
> The command used is:
> C:\sandbox\maven_projects\sapphire\review-tool>mvn -e archetype:create
> -DgroupId=com.fujitsu.sapphire -DartifactId=review-tool
> -DarchetypeArtifactId=maven-archetype-webapp
> -DremoteRepositories=http://localhost/maven2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MREPOSITORY-11) Javadoc not included in the bundle
[ http://jira.codehaus.org/browse/MREPOSITORY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MREPOSITORY-11. -- Assignee: Carlos Sanchez Resolution: Fixed Fix Version/s: 2.1 Fixed in r378353. > Javadoc not included in the bundle > -- > > Key: MREPOSITORY-11 > URL: http://jira.codehaus.org/browse/MREPOSITORY-11 > Project: Maven 2.x Repository Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Maven version: 2.0.7 > Java version: 1.4.2_13 > OS name: "windows xp" version: "5.1" arch: "x86" >Reporter: Julien HENRY >Assignee: Carlos Sanchez > Fix For: 2.1 > > > On a simple project, I run: > mvn clean source:jar javadoc:jar repository:bundle-create > As a result in target I get: > artifact-version.jar > artifact-version-bundle.jar > artifact-version-javadoc.jar > artifact-version-sources.jar > But in artifact-version-bundle.jar there are only: > META-INF > pom.xml > LICENSE.txt > artifact-version.jar > artifact-version-sources.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: (MREPOSITORY-3) Please add support for multi-module projects in repository:bundle-create mojo
[ http://jira.codehaus.org/browse/MREPOSITORY-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138854#action_138854 ] Dennis Lundberg commented on MREPOSITORY-3: --- The following message is printed if the packaging of the project is pom: bq. Packaging cannot be 'pom' when creating an upload bundle. I don't understand why we shouldn't allow pom packaging. Even if we don't implement multi module support it would easy the pain for people who needs to create an upload bundle for their (parent) POM project. > Please add support for multi-module projects in repository:bundle-create mojo > - > > Key: MREPOSITORY-3 > URL: http://jira.codehaus.org/browse/MREPOSITORY-3 > Project: Maven 2.x Repository Plugin > Issue Type: New Feature > Environment: Java 1.5, WinXP >Reporter: John R Fallows > > Currently the repository:bundle-create mojo only supports single module > upload bundles, so multi-module bundles must be created manually, once for > each sub-module, and each individual bundle file must be uploaded to a public > site individually. > In addition, the "pom" packaging (which is often used by the parent pom of a > multi-module project) is not supported repository:bundle-create, so upload > bundles for projects with "pom" packaging must be created manually, before > uploading to a public site. > Please support multi-module repository:bundle-create mojo such that: > $ mvn repository:bundle-create > in the top level of a multi-module project produces a single archive that can > be used to upload the multi-module project artifacts to ibiblio. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MREPOSITORY-10) add XML encoding support for POM reading/writing
[ http://jira.codehaus.org/browse/MREPOSITORY-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MREPOSITORY-10: --- Attachment: MREPOSITORY-10.patch Does this patch seem correct to you Herve? If so I can apply it. I just want confirmation from the expert :-) > add XML encoding support for POM reading/writing > > > Key: MREPOSITORY-10 > URL: http://jira.codehaus.org/browse/MREPOSITORY-10 > Project: Maven 2.x Repository Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.1 > > Attachments: MREPOSITORY-10.patch > > > With MNG-2254 being fixed in Maven 2.0.8, same XML encoding support is > necessary in this plugin to avoid data corruption when reading and writing > POM files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2108) Uploading antenna 1.0.2 to The Central Repository
Uploading antenna 1.0.2 to The Central Repository - Key: MAVENUPLOAD-2108 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2108 Project: Maven Upload Requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 0.9.14 The antenna project provides a set of Ant tasks for developing J2ME/MIDP applications based on the J2ME Wireless Toolkit. Maven plugin exists (j2me-maven-plugin) to use this library in maven build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MREPOSITORY-3) Please add support for multi-module projects in repository:bundle-create mojo
[ http://jira.codehaus.org/browse/MREPOSITORY-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138854#action_138854 ] dennislundberg edited comment on MREPOSITORY-3 at 6/17/08 12:12 PM: - The following message is printed if the packaging of the project is 'pom': bq. Packaging cannot be 'pom' when creating an upload bundle. I don't understand why we shouldn't allow pom packaging. Even if we don't implement multi module support it would ease the pain for people who needs to create an upload bundle for their (parent) POM project. was (Author: dennislundberg): The following message is printed if the packaging of the project is pom: bq. Packaging cannot be 'pom' when creating an upload bundle. I don't understand why we shouldn't allow pom packaging. Even if we don't implement multi module support it would easy the pain for people who needs to create an upload bundle for their (parent) POM project. > Please add support for multi-module projects in repository:bundle-create mojo > - > > Key: MREPOSITORY-3 > URL: http://jira.codehaus.org/browse/MREPOSITORY-3 > Project: Maven 2.x Repository Plugin > Issue Type: New Feature > Environment: Java 1.5, WinXP >Reporter: John R Fallows > > Currently the repository:bundle-create mojo only supports single module > upload bundles, so multi-module bundles must be created manually, once for > each sub-module, and each individual bundle file must be uploaded to a public > site individually. > In addition, the "pom" packaging (which is often used by the parent pom of a > multi-module project) is not supported repository:bundle-create, so upload > bundles for projects with "pom" packaging must be created manually, before > uploading to a public site. > Please support multi-module repository:bundle-create mojo such that: > $ mvn repository:bundle-create > in the top level of a multi-module project produces a single archive that can > be used to upload the multi-module project artifacts to ibiblio. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3314) offline build not running, when having SNAPSHOT dependencies
[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138858#action_138858 ] Marc Harris commented on MNG-3314: -- I too see this issue. It happens for me when attempting to depend on a snapshot version of a module downloaded from a repository. If the snapshot version of the module is built and installed locally, the problem goes away. I will attach two projects (in a tar file) that have minimal external dependencies, and the debug output of trying to build. Here are the steps to reproduce: Environment: Maven 2.0.8 Linux 2.6.18 Artifactory 1.2.5 (rev. 1154) Preliminary steps: 1) Modify the pom files to refer to your repository instead of http://localhost:8081/artifactory/jumptap-snapshots 2) Build maven-test-project1 3) Upload the pom and jar for maven-test-project1 to your repository. Steps that cause the error to happen: 1) Delete maven-test-project1 from the local repository. 2) Build maven-test-project2 without the offline flag (mvn install). This build is successful (and downloads maven-test-project1 to the local repository). 3) Build maven-test-project2 with the offline flag (mvn -o install). This build fails, unable to resolve the maven-test-project1 artifact. Steps that cause the error not to happen 1) Build maven-test-project1 locally. This build is successful. 2) Build maven-test-project2 without the offline flag (mvn install). This build is successful. 3) Build maven-test-project2 with the offline flag (mvn -o install). This build is successful. > offline build not running, when having SNAPSHOT dependencies > > > Key: MNG-3314 > URL: http://jira.codehaus.org/browse/MNG-3314 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.7 >Reporter: Matthias Weßendorf >Assignee: John Casey >Priority: Critical > Fix For: 2.0.10 > > > am having troubles with > mvn ... -o > (with maven 2.0.7) > says not able to download (but, really, the file is in my local repo) > The dependency is a -SNAPSHOT (for what's worth) > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > A change to use 2.0.4 works fine. > So, is this an already know bug in 2.0.7 ? > To my understanding it is a bug, since offline just shouldn't try to get a > newer > SNAPSHOT, perhaps I am wrong. > I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect > just not checking for new stuff. > and... for some reasons, sometimes, > it just downloads a new SNAPSHOT. > That is a pain, when you are "maintaining" the same snapshot on your > box, but the build just goes ahead and actually downloads a 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-3314) offline build not running, when having SNAPSHOT dependencies
[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Harris updated MNG-3314: - Attachment: maven-offline-snapshot-problem.tar Contains two projects, maven-test-project1 and maven-test-project2. maven-test-project2 depends on maven-test-project1. maven-test-project2 offline unless maven-test-project1 has been built locally. > offline build not running, when having SNAPSHOT dependencies > > > Key: MNG-3314 > URL: http://jira.codehaus.org/browse/MNG-3314 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.7 >Reporter: Matthias Weßendorf >Assignee: John Casey >Priority: Critical > Fix For: 2.0.10 > > Attachments: maven-offline-snapshot-problem.tar > > > am having troubles with > mvn ... -o > (with maven 2.0.7) > says not able to download (but, really, the file is in my local repo) > The dependency is a -SNAPSHOT (for what's worth) > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > A change to use 2.0.4 works fine. > So, is this an already know bug in 2.0.7 ? > To my understanding it is a bug, since offline just shouldn't try to get a > newer > SNAPSHOT, perhaps I am wrong. > I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect > just not checking for new stuff. > and... for some reasons, sometimes, > it just downloads a new SNAPSHOT. > That is a pain, when you are "maintaining" the same snapshot on your > box, but the build just goes ahead and actually downloads a 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-3314) offline build not running, when having SNAPSHOT dependencies
[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Harris updated MNG-3314: - Attachment: maven-offline-snapshot-failure.log The debug log produced when trying to build maven-test-project2 offline when maven-test-project1 has not been built locally, but when maven-test-project1 has been previously downloaded due to an online build > offline build not running, when having SNAPSHOT dependencies > > > Key: MNG-3314 > URL: http://jira.codehaus.org/browse/MNG-3314 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.7 >Reporter: Matthias Weßendorf >Assignee: John Casey >Priority: Critical > Fix For: 2.0.10 > > Attachments: maven-offline-snapshot-failure.log, > maven-offline-snapshot-problem.tar > > > am having troubles with > mvn ... -o > (with maven 2.0.7) > says not able to download (but, really, the file is in my local repo) > The dependency is a -SNAPSHOT (for what's worth) > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > A change to use 2.0.4 works fine. > So, is this an already know bug in 2.0.7 ? > To my understanding it is a bug, since offline just shouldn't try to get a > newer > SNAPSHOT, perhaps I am wrong. > I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect > just not checking for new stuff. > and... for some reasons, sometimes, > it just downloads a new SNAPSHOT. > That is a pain, when you are "maintaining" the same snapshot on your > box, but the build just goes ahead and actually downloads a 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] Commented: (MNG-3314) offline build not running, when having SNAPSHOT dependencies
[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138861#action_138861 ] Marc Harris commented on MNG-3314: -- Sorry about those two previous comments. I thought they were comments about the attachments, not comments about the bug. The first comment refers to maven-offline-snapshot-problem.tar and the second comment refers to maven-offline-snapshot-failure.log > offline build not running, when having SNAPSHOT dependencies > > > Key: MNG-3314 > URL: http://jira.codehaus.org/browse/MNG-3314 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.7 >Reporter: Matthias Weßendorf >Assignee: John Casey >Priority: Critical > Fix For: 2.0.10 > > Attachments: maven-offline-snapshot-failure.log, > maven-offline-snapshot-problem.tar > > > am having troubles with > mvn ... -o > (with maven 2.0.7) > says not able to download (but, really, the file is in my local repo) > The dependency is a -SNAPSHOT (for what's worth) > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > A change to use 2.0.4 works fine. > So, is this an already know bug in 2.0.7 ? > To my understanding it is a bug, since offline just shouldn't try to get a > newer > SNAPSHOT, perhaps I am wrong. > I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect > just not checking for new stuff. > and... for some reasons, sometimes, > it just downloads a new SNAPSHOT. > That is a pain, when you are "maintaining" the same snapshot on your > box, but the build just goes ahead and actually downloads a 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] Commented: (ARCHETYPE-184) Fail to create multimodule archetype from project : modules created later as "__rootArtifactId__-modulename"
[
http://jira.codehaus.org/browse/ARCHETYPE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138862#action_138862
]
Raphaël Piéroni commented on ARCHETYPE-184:
---
I works fine here :
{noformat}
[EMAIL PROTECTED]:~/projects/platina/platina-archetype/target$ mvn -v
Maven version: 2.0.9
Java version: 1.6.0_10-beta
OS name: "linux" version: "2.6.24-18-generic" arch: "amd64" Family: "unix"
{noformat}
{noformat}
[EMAIL PROTECTED]:~/projects/platina/platina-archetype$ mvn clean
archetype:create-from-project -Darchetype.properties=archetype.properties
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] archetype
[INFO] archetype :: business domain model
[INFO] archetype :: business services
[INFO] archetype :: persistence layer
[INFO] archetype :: infrastructure
[INFO] archetype :: remoting
[INFO] archetype :: web services
[INFO] archetype :: web application
[INFO] archetype :: entreprise application
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] triemax: checking for updates from snapshot
[INFO] triemax: checking for updates from apache.snapshots
[INFO] triemax: checking for updates from codehaus.snapshots
[INFO] org.apache.maven.plugins: checking for updates from snapshot
[INFO] org.apache.maven.plugins: checking for updates from apache.snapshots
[EMAIL PROTECTED]:~/projects/platina/platina-archetype$ mvn clean
archetype:create-from-project -Darchetype.properties=archetype.properties
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] archetype
[INFO] archetype :: business domain model
[INFO] archetype :: business services
[INFO] archetype :: persistence layer
[INFO] archetype :: infrastructure
[INFO] archetype :: remoting
[INFO] archetype :: web services
[INFO] archetype :: web application
[INFO] archetype :: entreprise application
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] org.apache.maven.plugins: checking for updates from apache.snapshots
[INFO] org.apache.maven.plugins: checking for updates from codehaus.snapshots
[INFO] org.codehaus.mojo: checking for updates from snapshot
[INFO] org.codehaus.mojo: checking for updates from apache.snapshots
[INFO] org.codehaus.mojo: checking for updates from codehaus.snapshots
Downloading:
http://localhost:8081/nexus/content/repositories/snapshots/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom
Downloading:
http://localhost:8081/nexus/content/groups/all/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom
4K downloaded
Downloading:
http://localhost:8081/nexus/content/repositories/snapshots/org/apache/maven/archetype/maven-archetype/2.0-alpha-3/maven-archetype-2.0-alpha-3.pom
Downloading:
http://localhost:8081/nexus/content/groups/all/org/apache/maven/archetype/maven-archetype/2.0-alpha-3/maven-archetype-2.0-alpha-3.pom
13K downloaded
Downloading:
http://localhost:8081/nexus/content/repositories/snapshots/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar
Downloading:
http://localhost:8081/nexus/content/groups/all/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar
71K downloaded
[SNIP]
[INFO] [archetype:create-from-project]
[INFO] Archetype created in target/generated-sources/archetype
[INFO]
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] archetype . SUCCESS [25.989s]
[INFO] archetype :: business domain model SUCCESS [0.934s]
[INFO] archetype :: business services SUCCESS [0.829s]
[INFO] archetype :: persistence layer SUCCESS [1.175s]
[INFO] archetype :: infrastructure ... SUCCESS [0.888s]
[INFO] archetype :: remoting . SUCCESS [0.856s]
[INFO] archetype :: web services . SUCCESS [1.307s]
[INFO] archetype :: web application .. SUCCESS [1.132s]
[INFO] archetype :: entreprise application ... SUCCESS [1.108s]
[INFO]
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 42 seconds
[INFO] Finished at: Tue Jun 17 18:14:57 GMT 2008
[INFO] Final Memory: 38M/81M
[INFO]
{noformat}
{noformat}
[EMAIL
PROTECTED]:~/projects/platina/platina-archetype/target/generated-sources/archetype$
tree
.
|-- pom.x
[jira] Commented: (ARCHETYPE-185) unable to create a project with local repository.
[
http://jira.codehaus.org/browse/ARCHETYPE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138863#action_138863
]
Raphaël Piéroni commented on ARCHETYPE-185:
---
What is the result (full trace) of the command. maybe using -X option also.
Are you sure you use maven 2.0.4 and not maven 2.0.9?
> unable to create a project with local repository.
> --
>
> Key: ARCHETYPE-185
> URL: http://jira.codehaus.org/browse/ARCHETYPE-185
> Project: Maven Archetype
> Issue Type: Bug
> Environment: Windows XP professional SP2. LAN connected PC with NO
> Internet access.
>Reporter: Alan Lewis
>
> When using maven 2.0.4 for the first time on a PC with no internet access,
> but that has a local copy of the ibiblio maven2 repository, the
> archetype:create fails. The "system" settings.xml [ in {maven2_home}/conf ]
> has been updated to include the section below:
> ...previous text removed for clarity, from default (2.0.4) settings.xml
>
> jdk-1.5
>
> 1.5
>
>
>
> jdk15
> Local Repository for JDK 1.5 builds
> http://localhost/maven2
> default
>
>
>
>
>
> maven2-plugins
> Local Repository for maven2 plugins
> http://localhost/maven2
> default
>
>
>
> ...remainder ignored, from default settings.xml
> This url is accessible from a browser. The local Apache installation is
> 2.0.55
> The command used is:
> C:\sandbox\maven_projects\sapphire\review-tool>mvn -e archetype:create
> -DgroupId=com.fujitsu.sapphire -DartifactId=review-tool
> -DarchetypeArtifactId=maven-archetype-webapp
> -DremoteRepositories=http://localhost/maven2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3070) ${x} properties no longer expanded in tag after 2.0.3
[
http://jira.codehaus.org/browse/MNG-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3070.
---
Assignee: John Casey
Resolution: Incomplete
The zip you reference in this description no longer exists, and there isn't
enough information in this bug report to reproduce the problem. If you have a
failing test case that you can attach, please don't hesitate to reopen this
issue.
> ${x} properties no longer expanded in tag after 2.0.3
>
>
> Key: MNG-3070
> URL: http://jira.codehaus.org/browse/MNG-3070
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.7
>Reporter: Gabriele Garuglieri
>Assignee: John Casey
> Fix For: 2.0.10
>
>
> I was experimenting with maven using killer-app sample
> (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book
> (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
> Maven 2.0.3 is able to build the sample out of the box, but any later version
> up to 2.0.7 chokes telling that it's not able to find the parent project:
> C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> GroupId: com.training.killerapp
> ArtifactId: killerapp
> Version: 1.0-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> com.training.killerapp:killerapp for project: null:killerapp-model:jar:null
> for project null:killerapp-model:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> All the problems looks to be caused by the fact that the root POM has the
> following construct (that should be perfectly legal) in it:
> ${killerappVersion}
>
> 1.0-SNAPSHOT
>
> If i substitute the version tag in the root POM with the following everything
> works with all versions.
> 1.0-SNAPSHOT
> I was not able to find anywhere in the doc that ${x} substitution is no
> longer legal in tag, so i think this is a regression from 2.0.3.
> Btw, all the test were done with clean local repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANT-42) Update to p-u 1.5.4
Update to p-u 1.5.4 --- Key: MANT-42 URL: http://jira.codehaus.org/browse/MANT-42 Project: Maven 2.x Ant Plugin Issue Type: Task Affects Versions: 2.1 Reporter: Vincent Siveton -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MREPOSITORY-10) add XML encoding support for POM reading/writing
[ http://jira.codehaus.org/browse/MREPOSITORY-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138866#action_138866 ] Herve Boutemy commented on MREPOSITORY-10: -- ok for the code but for the plexus-utils dependency, please use 1.5.1 because of PLXUTILS-60 > add XML encoding support for POM reading/writing > > > Key: MREPOSITORY-10 > URL: http://jira.codehaus.org/browse/MREPOSITORY-10 > Project: Maven 2.x Repository Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.1 > > Attachments: MREPOSITORY-10.patch > > > With MNG-2254 being fixed in Maven 2.0.8, same XML encoding support is > necessary in this plugin to avoid data corruption when reading and writing > POM files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MANT-42) Update to p-u 1.5.4
[ http://jira.codehaus.org/browse/MANT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138867#action_138867 ] Vincent Siveton commented on MANT-42: - done in r668794, snapshot deployed. Close it when the p-u release will be done > Update to p-u 1.5.4 > --- > > Key: MANT-42 > URL: http://jira.codehaus.org/browse/MANT-42 > Project: Maven 2.x Ant Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1.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: (MANT-42) Update to p-u 1.5.4
[ http://jira.codehaus.org/browse/MANT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MANT-42: Fix Version/s: 2.1.1 > Update to p-u 1.5.4 > --- > > Key: MANT-42 > URL: http://jira.codehaus.org/browse/MANT-42 > Project: Maven 2.x Ant Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1.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] Closed: (MREPOSITORY-10) add XML encoding support for POM reading/writing
[ http://jira.codehaus.org/browse/MREPOSITORY-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MREPOSITORY-10. -- Assignee: Dennis Lundberg (was: Herve Boutemy) Resolution: Fixed Fixed in r668802. New 2.1-SNAPSHOT deployed. > add XML encoding support for POM reading/writing > > > Key: MREPOSITORY-10 > URL: http://jira.codehaus.org/browse/MREPOSITORY-10 > Project: Maven 2.x Repository Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Herve Boutemy >Assignee: Dennis Lundberg > Fix For: 2.1 > > Attachments: MREPOSITORY-10.patch > > > With MNG-2254 being fixed in Maven 2.0.8, same XML encoding support is > necessary in this plugin to avoid data corruption when reading and writing > POM files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPPMD-33) Support PMD 4.2 and support "mimimumPriority" property (patch attached)
Support PMD 4.2 and support "mimimumPriority" property (patch attached) --- Key: MPPMD-33 URL: http://jira.codehaus.org/browse/MPPMD-33 Project: Maven 1.x PMD Plugin Issue Type: Improvement Affects Versions: 1.10 Reporter: Charlie Collins Attachments: maven-pmd-plugin.patch Attached patch upgrades deps to PMD 4.2.2 (and jaxen 1.1.1,asm 3.1, and backport-util-concurrent 3.1). Also includes support for the PMD Ant-Task "mimimumPriority" setting with the maven.pmd.minimumpriority property. (Allows you to set the priority at which violations are triggered to fail the build - rather than just any violation.) And, if interested, I would be willing to join the project to test and commit this sort of stuff on various Maven 1.x plugins (I work for a company that still heavily uses Maven 1.x, though we also use 2.x in some places - a lot of our 1.x plugins are updated where the current released versions are not). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
