[jira] Commented: (MANTRUN-86) Cannot handle multiple tasks elements
[
http://jira.codehaus.org/browse/MANTRUN-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131538#action_131538
]
Thomas Diesler commented on MANTRUN-86:
---
Ok, in that case we might want to rename the issue to "Improve configuration
error reporting"
> Cannot handle multiple tasks elements
> -
>
> Key: MANTRUN-86
> URL: http://jira.codehaus.org/browse/MANTRUN-86
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Thomas Diesler
>
> {code:xml}
>
> maven-antrun-plugin
>
>
> install
>
> run
>
>
>
>
>value="${jboss.local.repository}"/>
>
>
>
>
>
>
>
>
>
> {code}
> Always executes the last tasks element although 'jboss.local.repository' is
> set
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [echo] Cannot install to
> jboss.local.repository=/home/tdiesler/svn/jboss.local.repository
> [INFO] Executed tasks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MINSTALL-50) provide property filtering on .pom files placed in local repo
[
http://jira.codehaus.org/browse/MINSTALL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131539#action_131539
]
Stefan Armbruster commented on MINSTALL-50:
---
No, filtering type "pom" was not necessary for my use case. That's why I missed
this one. Feel free to change it.
> provide property filtering on .pom files placed in local repo
> -
>
> Key: MINSTALL-50
> URL: http://jira.codehaus.org/browse/MINSTALL-50
> Project: Maven 2.x Install Plugin
> Issue Type: New Feature
>Affects Versions: 2.3
> Environment: independent
>Reporter: Stefan Armbruster
> Attachments: MNG-maven-install.patch
>
>
> When maven installs an artifact, it's pom is also copied into the artifact's
> directory. Unfortunately, if the pom contains a property reference (e.g.
> ${myprop}), this will not be replaced upon copying the pom file.
> I've created a patch for the install plugin that switches on property
> filtering by setting a mojo parameter "filteringEnabled". Since this defaults
> to "false", backward compatibility is kept 100%.
> Some implementation notes:
> * the dirty work is done in FilteredProjectArtifactMetadata.java, the
> property resolution code has been inspired by ResourcesMojo.
> * I've added a unit test, that replaces ${basedir} with the value of a system
> property.
> * since "svn diff" does not handle binary files,
> src/test/resources/unit/basic-install-test-with-filtering/target/maven-install-test-1.0-SNAPSHOT.jar
> is not included in the patch. This file is the same as
> src/test/resources/unit/basic-install-test/target/maven-install-test-1.0-SNAPSHOT.jar
> Since my knowledge of Maven API is more than limited, there might be a more
> elegant way to provide this feature ... but it works! I'd be happy to see
> this in a future release of maven.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-154) documentation for overlay is incorrect
[ http://jira.codehaus.org/browse/MWAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131548#action_131548 ] Olaf Kittelmann commented on MWAR-154: -- I am sorry - the pom snippet is with the version element is on http://maven.apache.org/plugins/maven-war-plugin/usage.html > documentation for overlay is incorrect > -- > > Key: MWAR-154 > URL: http://jira.codehaus.org/browse/MWAR-154 > Project: Maven 2.x War Plugin > Issue Type: Task >Reporter: Olaf Kittelmann >Assignee: Stephane Nicoll > > The documentation on > http://maven.apache.org/plugins/maven-war-plugin/overlays.html describes a > feature that only works with > version 2.1-alpha-1 of the plugin. > yet the pom snippets on the documentation page always point to version 2.0. > [...] > > > org.apache.maven.plugins > maven-war-plugin > 2.0 > > > **/IncludeME,**/images > > > > > [...] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MCHANGES-107) Add http output format for mail annoucement
Add http output format for mail annoucement --- Key: MCHANGES-107 URL: http://jira.codehaus.org/browse/MCHANGES-107 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Reporter: Christophe Lallement We want to use a custom annoucement template wich is a HTML template to get a better look into our mail. No pb to do this except the output format is hardcoded into PLAINTEXT into plugin. Can you add an option into the plugin configuration (after tag for example) to specify the output type (HTMP or PLAINTEXT). The default should be "text/plain". The Hardcoded feature is in file ProjectJavamailMailSender.java (svn rev 553871) line 181. Thx Christophe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2027) Please add Jyntax to the central repository for syncing
Please add Jyntax to the central repository for syncing --- Key: MAVENUPLOAD-2027 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2027 Project: maven-upload-requests Issue Type: New Feature Reporter: Clemens D. Renner The project is hosted at SourceForge, here is the CSV entry for the syncing database "net.sf.jyntax","[EMAIL PROTECTED]:/home/groups/j/jy/jyntax/htdocs/m2repo","rsync_ssh","Clemens Renner","[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: (MSHADE-31) When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom
When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom -- Key: MSHADE-31 URL: http://jira.codehaus.org/browse/MSHADE-31 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.0.1 Environment: Maven 2.0.9, Linux. Reporter: Max Bowsher When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSHADE-31) When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom
[ http://jira.codehaus.org/browse/MSHADE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Bowsher updated MSHADE-31: -- Attachment: pom.xml Here is a pom.xml that demonstrates the problem. In this project, commons-httpclient is depended upon and shaded into the jar, whilst independently, hibernate-annotations is depended upon with an exclusion of hibernate itself. Run "mvn package", then inspect target/dependency-reduced-pom.xml - the have been stripped out, resulting in unwanted addition of hibernate to the effective resolved dependency set. If promoteTransitiveDependencies is turned off, this bug does not occur. > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom > -- > > Key: MSHADE-31 > URL: http://jira.codehaus.org/browse/MSHADE-31 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.0.1 > Environment: Maven 2.0.9, Linux. >Reporter: Max Bowsher > Attachments: pom.xml > > > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSHADE-31) When promoteTransitiveDependencies=true, all are stripped from the dependency-reduced-pom
[ http://jira.codehaus.org/browse/MSHADE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131574#action_131574 ] Max Bowsher commented on MSHADE-31: --- Oops, I managed to upload the pom.xml with false, change that to true to reproduce the problem. > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom > -- > > Key: MSHADE-31 > URL: http://jira.codehaus.org/browse/MSHADE-31 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.0.1 > Environment: Maven 2.0.9, Linux. >Reporter: Max Bowsher > Attachments: pom.xml > > > When promoteTransitiveDependencies=true, all are stripped from > the dependency-reduced-pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-92) A "" is missing
A "" is missing - Key: MCHECKSTYLE-92 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-92 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Cyril Martin Priority: Trivial w3c HTML validator show me one error in the page generated by checkstyle plugin. (http://opensource.fastconnect.org/projects/wan-gateway/checkstyle.html) After a check, I see a "div" ending tag is missing. Maybe the end of the Or maybe the end of the Checkstyle Results We use a custom skin, but checkstyle-report page is the only one with this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-104) Add the ability to specify source exclusions
[ http://jira.codehaus.org/browse/MECLIPSE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-104: - Assignee: Arnaud Heritier Fix Version/s: 2.5.2 > Add the ability to specify source exclusions > > > Key: MECLIPSE-104 > URL: http://jira.codehaus.org/browse/MECLIPSE-104 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: James Mitchell >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 2.5.2 > > Attachments: fix-eclipse-classpaths.sh, MECLIPSE-104.patch, > srcExclusions-patch.zip > > > When source files contain scm information (**/.svn/** or **/CVS/**), which is > pretty much a given, there's currently no way to specify that those > directories be excluded except through the GUI. This isn't so much of a > problem except that the next time a change is needed and this plugin is ran, > it will overwrite this exclusion and will force me to exclude it, by hand, > again. > The above case is the driving reason why I decided to get involved and help > out. So, I have written everything (I think) that is needed for this > enhancement including, adding to the javadoc, creating a new test that > verifies this enhancement, and fully testing this with my own projects (many > of them @ Struts). If there is anything else I need to do as far as site > documentation, please tell me where it is and I'll add it. > This is my first patch to Maven. If this sucks, please don't ignore it, just > say 'it sucks, no thanks" and I'll go about working on something else. > Thanks so much for your attention. > -- > James Mitchell -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-104) Add the ability to specify source exclusions
[ http://jira.codehaus.org/browse/MECLIPSE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van der Hoff updated MECLIPSE-104: -- Attachment: MECLIPSE-104.patch An updated version of the patch. It's pretty trivial, so it would be nice if it could be applied before it bitrots this time! :) > Add the ability to specify source exclusions > > > Key: MECLIPSE-104 > URL: http://jira.codehaus.org/browse/MECLIPSE-104 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: James Mitchell >Priority: Minor > Attachments: fix-eclipse-classpaths.sh, MECLIPSE-104.patch, > srcExclusions-patch.zip > > > When source files contain scm information (**/.svn/** or **/CVS/**), which is > pretty much a given, there's currently no way to specify that those > directories be excluded except through the GUI. This isn't so much of a > problem except that the next time a change is needed and this plugin is ran, > it will overwrite this exclusion and will force me to exclude it, by hand, > again. > The above case is the driving reason why I decided to get involved and help > out. So, I have written everything (I think) that is needed for this > enhancement including, adding to the javadoc, creating a new test that > verifies this enhancement, and fully testing this with my own projects (many > of them @ Struts). If there is anything else I need to do as far as site > documentation, please tell me where it is and I'll add it. > This is my first patch to Maven. If this sucks, please don't ignore it, just > say 'it sucks, no thanks" and I'll go about working on something else. > Thanks so much for your attention. > -- > James Mitchell -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-438) manifest location hard coded to src/main/webapp in 2.5.1
[
http://jira.codehaus.org/browse/MECLIPSE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131598#action_131598
]
Mohan K commented on MECLIPSE-438:
--
Arnaud,
Thanks for the reply. Then the instruction for setting up a multi-module
projects here is it wrong?
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html
Where at the end the configuration is given as:
org.apache.maven.plugins
maven-eclipse-plugin
[artifactId]-[version]
true
true
2.0
${basedir}/src/main/resources/META-INF/MANIFEST.MF
Is that a doc bug? Thanks!! (confused)
> manifest location hard coded to src/main/webapp in 2.5.1
>
>
> Key: MECLIPSE-438
> URL: http://jira.codehaus.org/browse/MECLIPSE-438
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.5.1
> Environment: Maven 2.0.8
>Reporter: Mohan K
>
> In 2.5.1:
> ANY_LOCATION
> is ignored. It *always* generates in src/main/webapp/META-INF/MANIFST.MF
> It works fine in 2.5. For now, reverting to 2.5 from 2.5.1 as a workaround.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MPIR-98) Team list does not contain anchors on user ids
Team list does not contain anchors on user ids
--
Key: MPIR-98
URL: http://jira.codehaus.org/browse/MPIR-98
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Michael Osipov
Priority: Minor
I ran recently W3C link checker and noticed:
{code}
Processing
http://page.mi.fu-berlin.de/ossipov/fckeditor-java/changes-report.html
List of broken links
Fragments listed are broken. See the table below to know what action to take.
CodeOccurrences What to do
200 1 There are broken fragments which must be fixed.
http://page.mi.fu-berlin.de/ossipov/fckeditor-java/team-list.html
What to do: There are broken fragments which must be fixed.
Response status code: 200
Response message: OK
Lines: 142, 261
Broken fragments and their line numbers: They need to be fixed!
mosipov: 261
th-schwarz: 261
{code}
Basically this means that the Chages Report refers to user id anchors which are
never created.
These anchors should be created as invisible anchors right before the user id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MECLIPSE-438) manifest location hard coded to src/main/webapp in 2.5.1
[ http://jira.codehaus.org/browse/MECLIPSE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131603#action_131603 ] Arnaud Heritier commented on MECLIPSE-438: -- Yes I think. I have to review the code to be sure. > manifest location hard coded to src/main/webapp in 2.5.1 > > > Key: MECLIPSE-438 > URL: http://jira.codehaus.org/browse/MECLIPSE-438 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5.1 > Environment: Maven 2.0.8 >Reporter: Mohan K > > In 2.5.1: > ANY_LOCATION > is ignored. It *always* generates in src/main/webapp/META-INF/MANIFST.MF > It works fine in 2.5. For now, reverting to 2.5 from 2.5.1 as a workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPIR-98) Team list does not contain anchors on user ids
[
http://jira.codehaus.org/browse/MPIR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-98.
--
Resolution: Duplicate
Fix Version/s: 2.1
> Team list does not contain anchors on user ids
> --
>
> Key: MPIR-98
> URL: http://jira.codehaus.org/browse/MPIR-98
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 2.0.1
>Reporter: Michael Osipov
>Priority: Minor
> Fix For: 2.1
>
>
> I ran recently W3C link checker and noticed:
> {code}
> Processing
> http://page.mi.fu-berlin.de/ossipov/fckeditor-java/changes-report.html
> List of broken links
> Fragments listed are broken. See the table below to know what action to take.
> Code Occurrences What to do
> 200 1 There are broken fragments which must be fixed.
> http://page.mi.fu-berlin.de/ossipov/fckeditor-java/team-list.html
> What to do: There are broken fragments which must be fixed.
> Response status code: 200
> Response message: OK
> Lines: 142, 261
> Broken fragments and their line numbers: They need to be fixed!
> mosipov: 261
> th-schwarz: 261
> {code}
> Basically this means that the Chages Report refers to user id anchors which
> are never created.
> These anchors should be created as invisible anchors right before the user id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3475) Some directories are not basedir aligned
[
http://jira.codehaus.org/browse/MNG-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3475:
---
Fix Version/s: 2.0.10
> Some directories are not basedir aligned
>
>
> Key: MNG-3475
> URL: http://jira.codehaus.org/browse/MNG-3475
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
> Fix For: 2.0.10
>
> Attachments: base-directory-alignment.patch,
> base-directory-alignment.patch
>
>
> The output from
> {code:xml}
> ${project.build.sourceDirectory}
> ${project.build.testSourceDirectory}
> ${project.build.scriptSourceDirectory}
> ${project.build.directory}
> ${project.build.outputDirectory}
> ${project.build.testOutputDirectory}
> ${project.reporting.outputDirectory}
> {code}
> delivers something like
> {noformat}
> [echo] M:\maven\z\antrun\src\main\java
> [echo] M:\maven\z\antrun\src\test\java
> [echo] src/main/scripts
> [echo] M:\maven\z\antrun\target
> [echo] M:\maven\z\antrun\target\classes
> [echo] M:\maven\z\antrun\target\test-classes
> [echo] target/site
> {noformat}
> revealing that neither the script source directory nor the reporting output
> directory are basedir aligned.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MECLIPSE-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-437. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.5.2 added IdeDependency.isJavaApi() based on java.* / javax.* groupIds changed EclipseClassPathWriter to write javaApi dependency prior to classpath container. TODO : maybe some better discovery mecanism could also include "geronimo-specs-*" and equivalent jars by opening the dependency .jar and looking for java.*/javax.* packages, but this would slow the plugin. > Ordering of .classpath entries when using a newer version of JARs already > included in the JDK. > -- > > Key: MECLIPSE-437 > URL: http://jira.codehaus.org/browse/MECLIPSE-437 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: WinXP, Maven 2.0.7 >Reporter: Patrick Zeising >Assignee: nicolas de loof > Fix For: 2.5.2 > > > While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the > one supplied with JDK6 the generated .classpath file in my project directory > contains all relevant entries headed by the entry for the JRE container. > ---CODE--- > > > > >path="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar" > sourcepath="M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar"/> > >path="M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar"/> > >path="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar" > sourcepath="M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar"/> > > ---/CODE--- > As long as the JRE_CONTAINER is mentioned and loaded first my project will > not compile in Eclipse since I am using operations unique to the newer > version of JaxWS. When I set the order of the classpath entries in Eclipse > manually (Properties - Java Build Path - Order and Export, setting the entry > for JRE_CONTAINER to the 'bottom') my project will compile of course. > Nicolas de Loof suggested the following in my post to the maven users mailing > list > (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): > ---CITE--- > Maybe the eclipse plugin could detect java* and javax* groupIds and force > them as toplevel ? > This would require : > - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove > those deps from getDepsOrdered > - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE > container. > ---/CITE--- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-326) m2eclipse goal does not respect additionalBuildcommands and additionalProjectnatures defined in pom
[ http://jira.codehaus.org/browse/MECLIPSE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-326: - Fix Version/s: 2.5.2 > m2eclipse goal does not respect additionalBuildcommands and > additionalProjectnatures defined in pom > --- > > Key: MECLIPSE-326 > URL: http://jira.codehaus.org/browse/MECLIPSE-326 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: M2Eclipse support >Affects Versions: 2.4 > Environment: win xp, jre/jdk 1.6, maven 2.0.7, maven-eclipse-plugin > 2.4 >Reporter: Tom Pasierb >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: m2eclipseMojoPatch.patch, > m2eclipseMojoPatchWithUnitTest.patch > > > I have defined additional buildCommand and projectNature in my pom.xml > After running eclipse:m2eclipse on my project, the produced eclipse project > descriptors contain neither of the above. > From what I saw in the source code the m2eclipseMojo uses the > setAdditionalBuildcommands and setAdditionalProjectnatures methods not > considering that the collections may already contain some entries. > I'm attaching a patch that solves this issue, however I have no experience in > developing mojos so I'm not sure if I'm doing it the right way. Should it be > acceptable please apply 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] Updated: (MECLIPSE-326) m2eclipse goal does not respect additionalBuildcommands and additionalProjectnatures defined in pom
[ http://jira.codehaus.org/browse/MECLIPSE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-326: - Testcase included: yes > m2eclipse goal does not respect additionalBuildcommands and > additionalProjectnatures defined in pom > --- > > Key: MECLIPSE-326 > URL: http://jira.codehaus.org/browse/MECLIPSE-326 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: M2Eclipse support >Affects Versions: 2.4 > Environment: win xp, jre/jdk 1.6, maven 2.0.7, maven-eclipse-plugin > 2.4 >Reporter: Tom Pasierb >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: m2eclipseMojoPatch.patch, > m2eclipseMojoPatchWithUnitTest.patch > > > I have defined additional buildCommand and projectNature in my pom.xml > After running eclipse:m2eclipse on my project, the produced eclipse project > descriptors contain neither of the above. > From what I saw in the source code the m2eclipseMojo uses the > setAdditionalBuildcommands and setAdditionalProjectnatures methods not > considering that the collections may already contain some entries. > I'm attaching a patch that solves this issue, however I have no experience in > developing mojos so I'm not sure if I'm doing it the right way. Should it be > acceptable please apply 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] Updated: (MNG-3424) Respect ordering of elements as given in POM
[
http://jira.codehaus.org/browse/MNG-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3424:
---
Fix Version/s: 2.0.10
> Respect ordering of elements as given in POM
>
>
> Key: MNG-3424
> URL: http://jira.codehaus.org/browse/MNG-3424
> Project: Maven 2
> Issue Type: Improvement
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
>Priority: Trivial
> Fix For: 2.0.10
>
> Attachments: retain-collection-order.patch
>
>
> "Better safe than sorry" suggests to keep the ordering of collections when
> converting them into maps. It's hard to know when ordering is really
> irrelevant and the penalty of using {{java.util.Linked*}} is usually
> neglectable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MCHANGES-107) Add http output format for mail annoucement
[ http://jira.codehaus.org/browse/MCHANGES-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Lallement updated MCHANGES-107: -- Attachment: custom-mail-content-type.patch This is a patch from tag "maven-changes-plugin-2.0" Patch made from root project (where pom.xml is located) Compilation is ok, no test provided. > Add http output format for mail annoucement > --- > > Key: MCHANGES-107 > URL: http://jira.codehaus.org/browse/MCHANGES-107 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Reporter: Christophe Lallement > Attachments: custom-mail-content-type.patch > > > We want to use a custom annoucement template wich is a HTML template to get a > better look into our mail. > No pb to do this except the output format is hardcoded into PLAINTEXT into > plugin. > Can you add an option into the plugin configuration (after > tag for example) to specify the output type (HTMP or > PLAINTEXT). > The default should be "text/plain". > The Hardcoded feature is in file ProjectJavamailMailSender.java (svn rev > 553871) line 181. > Thx > Christophe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MCHANGES-107) Add http output format for mail annoucement
[ http://jira.codehaus.org/browse/MCHANGES-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131610#action_131610 ] Christophe Lallement commented on MCHANGES-107: --- To udpate my request title, understand HTML in place of Http. > Add http output format for mail annoucement > --- > > Key: MCHANGES-107 > URL: http://jira.codehaus.org/browse/MCHANGES-107 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Reporter: Christophe Lallement > Attachments: custom-mail-content-type.patch > > > We want to use a custom annoucement template wich is a HTML template to get a > better look into our mail. > No pb to do this except the output format is hardcoded into PLAINTEXT into > plugin. > Can you add an option into the plugin configuration (after > tag for example) to specify the output type (HTMP or > PLAINTEXT). > The default should be "text/plain". > The Hardcoded feature is in file ProjectJavamailMailSender.java (svn rev > 553871) line 181. > Thx > Christophe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2028) Sync Compass maven repository with the central maven repository
Sync Compass maven repository with the central maven repository --- Key: MAVENUPLOAD-2028 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2028 Project: maven-upload-requests Issue Type: Task Reporter: Shay Banon "org.compass-project","rsync://repo.compass-project.org","rsync","Shay Banon","[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: (MNGSITE-49) Remove redundant section about Maven Code Style
Remove redundant section about Maven Code Style --- Key: MNGSITE-49 URL: http://jira.codehaus.org/browse/MNGSITE-49 Project: Maven 2 Project Web Site Issue Type: Improvement Reporter: Benjamin Bentmann Priority: Minor See [Guide to Developing Maven|http://maven.apache.org/guides/development/guide-m2-development.html#Maven_Code_Style] and [Committer Environment|http://maven.apache.org/developers/committer-environment.html#Maven_Code_Style]. Déjà-vu? The same goes for the Subversion config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MNG-3537) "Nested imports" doesn't work on Maven 2.0.9
"Nested imports" doesn't work on Maven 2.0.9 Key: MNG-3537 URL: http://jira.codehaus.org/browse/MNG-3537 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.9 Reporter: Yan Huang Attachments: sample.zip The "nested imports" doesn't work on Maven 2.0.9. When trying to resolve "nested imports", Maven 2.0.9 kind of "forget" about the repositories that are defined in settings.xml and only tries to look up some of artifacts in "central" repository. Here attaches the sample. The steps to produce this bug under Maven 2.0.9: 1. unzip this zip and it'll create a folder called "sample". There are 5 POM files under there. 2. deploy all sample*.xml to a Maven 2 repository by using "deploy:deploy-file". 3. run "mvn help:effective-pom" and it will fail. The sample/pom.xml imports "sample-1.0.0.0" POM which in turn imports all other sample-pom-[1-3] artifacts. The error messages are as belows. It's trying to look up artifacts ONLY in central repository. >mvn help:effective-pom [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/test-nested-import/sample-pom-1/1.0.0.0/sample-pom-1-1.0.0.0.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: test-nested-import ArtifactId: sample-pom-1 Version: 1.0.0.0 Reason: Unable to download the artifact from any repository test-nested-import:sample-pom-1:pom:1.0.0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: POM 'test-nested-import:sample-pom-1' not found in repository: Unable to download the artifact from any repository test-nested-import:sample-pom-1:pom:1.0.0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project test-nested-import:sample-pom-1 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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) Caused by: org.apache.maven.project.ProjectBuildingException: POM 'test-nested-import:sample-pom-1' not found in reposit ory: Unable to download the artifact from any repository test-nested-import:sample-pom-1:pom:1.0.0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project test-nested-import:sample-pom-1 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:6 03) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:249) at org.apache.maven.project.DefaultMavenProjectBuilder.mergeManagedDependencies(DefaultMavenProjectBuilder.java: 1438) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1030) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253) at org.apache.maven.project.DefaultMavenProjectBuilder.mergeManagedDependencies(DefaultMavenProjectBuilder.java: 1438) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1030) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.ja va:506) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.
[jira] Commented: (MPIR-80) Add Java requirements to the Dependency Report
[ http://jira.codehaus.org/browse/MPIR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131616#action_131616 ] Dennis Lundberg commented on MPIR-80: - I'd like to see the commit reverted. We had a lengthy discussion about this path over on the commons dev list. My main objection is that the site is not necessarily built with the same JDK as the artifact itself, or at the same time. This can lead to false information on the site. > Add Java requirements to the Dependency Report > -- > > Key: MPIR-80 > URL: http://jira.codehaus.org/browse/MPIR-80 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Niall Pemberton >Assignee: Herve Boutemy > Fix For: 2.1 > > Attachments: maven-projectinfo-dependency-java-v2.patch, > maven-projectinfo-dependency-java-v3.patch, > maven-projectinfo-dependency-java.patch, maven-projectinfo-summary-java.patch > > > It would be nice to add a section to the dependency report showing the java > version requirements. > Attaching a patch which discovers the java version and compiler options from > the java-compiler-plugin configuration and outputs a "Java Version" section. > Has an option to configure whether or not this section is shown (default to > false). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MCHANGES-107) Add html output format for mail annoucement
[ http://jira.codehaus.org/browse/MCHANGES-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-107: - Affects Version/s: 2.0 Patch Submitted: [Yes] Summary: Add html output format for mail annoucement (was: Add http output format for mail annoucement) > Add html output format for mail annoucement > --- > > Key: MCHANGES-107 > URL: http://jira.codehaus.org/browse/MCHANGES-107 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Christophe Lallement > Attachments: custom-mail-content-type.patch > > > We want to use a custom annoucement template wich is a HTML template to get a > better look into our mail. > No pb to do this except the output format is hardcoded into PLAINTEXT into > plugin. > Can you add an option into the plugin configuration (after > tag for example) to specify the output type (HTMP or > PLAINTEXT). > The default should be "text/plain". > The Hardcoded feature is in file ProjectJavamailMailSender.java (svn rev > 553871) line 181. > Thx > Christophe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3536) REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore
[
http://jira.codehaus.org/browse/MNG-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-3536:
---
Fix Version/s: 2.0.10
Summary: REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it
doesn't work anymore (was: pom.build.sourceDirectory in Maven 2.0.9: it
doesn't work anymore)
> REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore
> -
>
> Key: MNG-3536
> URL: http://jira.codehaus.org/browse/MNG-3536
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: MacOSX, Java 6, Maven 2.0.9
>Reporter: Sébastien Arbogast
>Priority: Critical
> Fix For: 2.0.10
>
> Attachments: test.zip
>
>
> On one of my projects, I have the following property:
>
> file:${project.build.sourceDirectory}/myapp.xmi
>
> Knowing that in the same POM, sourceDirectory is configured that way:
>
> ${project.basedir}/src/main/uml
>
> With Maven 2.0.8, model.uri was correctly mapped to
> /Users/sarbogast/dev/myapp/src/main/uml/myapp.xmi
> But with Maven 2.0.9, now it's mapped to
> /Users/sarbogast/dev/myapp/Users/sarbogast/dev/myapp/src/main/uml/myapp.xmi,
> which is not good at all.
>
> I have attached a test project that builds with Maven 2.0.8 but not with
> Maven 2.0.9.
> It's not the simplest project ever but it's a real AndroMDA skeleton project.
> All the configuration is in mda/pom.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-439) Support filesets for clean goal
Support filesets for clean goal --- Key: MECLIPSE-439 URL: http://jira.codehaus.org/browse/MECLIPSE-439 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.5.1 Reporter: Michael Johns It would be great if filesets with includes/excludes were supported for the clean goal. We have a situation where we have to commit our .settings directory due to the presence of some items that are not generated by the plugin, and the clean plugin simply deletes that whole directory. I'm envisioning something like the maven-clean-plugin, which lets us control exactly what we want to clean. I realize that the plugin can generate custom configuration via the tag, which would allow us to regenerate the cleaned file, but if the additional config files are large, the XML in pom.xml can get unwieldy very fast. It would be easier to just commit the file and tell the plugin to not clean 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] Commented: (MECLIPSE-439) Support filesets for clean goal
[ http://jira.codehaus.org/browse/MECLIPSE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131625#action_131625 ] Michael Johns commented on MECLIPSE-439: I just dug into the source a little more, and I realized the plugin is smart enough to not delete custom files that I put in .settings. I saw it wiping out the entire directory earlier, and I figured it would just take my file with it, but it didn't. So that's good. But even with this new understanding of how it works, I actually stand by my original improvement request. I still think it would be nice to have a finer control over just what gets cleaned. > Support filesets for clean goal > --- > > Key: MECLIPSE-439 > URL: http://jira.codehaus.org/browse/MECLIPSE-439 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.5.1 >Reporter: Michael Johns > > It would be great if filesets with includes/excludes were supported for the > clean goal. We have a situation where we have to commit our .settings > directory due to the presence of some items that are not generated by the > plugin, and the clean plugin simply deletes that whole directory. I'm > envisioning something like the maven-clean-plugin, which lets us control > exactly what we want to clean. > I realize that the plugin can generate custom configuration via the > tag, which would allow us to regenerate the cleaned file, > but if the additional config files are large, the XML in pom.xml can get > unwieldy very fast. It would be easier to just commit the file and tell the > plugin to not clean 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] Reopened: (MPIR-80) Add Java requirements to the Dependency Report
[ http://jira.codehaus.org/browse/MPIR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy reopened MPIR-80: --- Assignee: (was: Herve Boutemy) reverted the commit > Add Java requirements to the Dependency Report > -- > > Key: MPIR-80 > URL: http://jira.codehaus.org/browse/MPIR-80 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Niall Pemberton > Fix For: 2.1 > > Attachments: maven-projectinfo-dependency-java-v2.patch, > maven-projectinfo-dependency-java-v3.patch, > maven-projectinfo-dependency-java.patch, maven-projectinfo-summary-java.patch > > > It would be nice to add a section to the dependency report showing the java > version requirements. > Attaching a patch which discovers the java version and compiler options from > the java-compiler-plugin configuration and outputs a "Java Version" section. > Has an option to configure whether or not this section is shown (default to > false). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1980) Upload couchdb4j jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1980. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload couchdb4j jars > - > > Key: MAVENUPLOAD-1980 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1980 > Project: maven-upload-requests > Issue Type: Task >Reporter: Dan Diephouse >Assignee: Carlos Sanchez > > Please upload couchdb4j to the repo :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2005) Hessian Flex 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2005. --- Assignee: Carlos Sanchez Resolution: Fixed > Hessian Flex 3.1.5 > -- > > Key: MAVENUPLOAD-2005 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2005 > Project: maven-upload-requests > Issue Type: Task >Reporter: evgeny >Assignee: Carlos Sanchez > Attachments: hessian-flex-3.1.5-bundle.jar, > hessian-flex-3.1.5-bundle.jar > > > The Hessian binary web service protocol makes web services usable without > requiring a large framework, and without learning yet another alphabet soup > of protocols. Because it is a binary protocol, it is well-suited to sending > binary data without any need to extend the protocol with attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2012) TestNG 5.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2012. --- Assignee: Carlos Sanchez Resolution: Fixed > TestNG 5.8 > -- > > Key: MAVENUPLOAD-2012 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2012 > Project: maven-upload-requests > Issue Type: Task >Reporter: Dan Fabulich >Assignee: Carlos Sanchez > Attachments: testng-5.8-bundle.jar > > > TestNG 5.8. I'm not a developer, but I'll happily lend a hand. Created > using TestNG's new dist-maven-bundle ant task, but against the 5.8 tag which > doesn't include this source. That makes this bundle a one-off, so there may > be errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2016) Please synchronize with http://m2repo.apithefire.org/ repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2016. --- Assignee: Carlos Sanchez Resolution: Fixed > Please synchronize with http://m2repo.apithefire.org/ repository > > > Key: MAVENUPLOAD-2016 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2016 > Project: maven-upload-requests > Issue Type: Task >Reporter: Chew Boon Aik >Assignee: Carlos Sanchez > > "org.apithefire","[EMAIL > PROTECTED]:/var/www/apithefire.org/m2repo","rsync_ssh","Chew Boon > Aik","[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] Closed: (MAVENUPLOAD-2017) Upload Ashwood 2.0 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2017. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Ashwood 2.0 bundle > - > > Key: MAVENUPLOAD-2017 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2017 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrus Adamchik >Assignee: Carlos Sanchez > > An update to the Ashwood lib uploaded per MAVENUPLOAD-765. > > http://objectstyle.org/downloads/cayenne/maven-bundles/ashwood-2.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: (MAVENUPLOAD-2015) Maven1 Clover 2 Plugin 2.2.1 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131667#action_131667 ] James William Dumay commented on MAVENUPLOAD-2015: -- Carlos, are we able to get some more traction on this please? > Maven1 Clover 2 Plugin 2.2.1 release > > > Key: MAVENUPLOAD-2015 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2015 > Project: maven-upload-requests > Issue Type: Task >Reporter: James William Dumay > > Clover is a code coverage tool for Java > Please upload :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MONE-25) maven.repo.local is not interpolated
maven.repo.local is not interpolated
Key: MONE-25
URL: http://jira.codehaus.org/browse/MONE-25
Project: Maven 2.x One Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows
Reporter: Piotr Kania
Priority: Minor
Plugin reads Maven 1 build.properties and get value for 'maven.repo.local'
property.
If this property is interpolated (i.e.
maven.repo.local=${maven.home.local}/repository) then plugin uses this direct
value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MECLIPSE-440) unit tests depends on local configuration and artifacts in local repository
unit tests depends on local configuration and artifacts in local repository --- Key: MECLIPSE-440 URL: http://jira.codehaus.org/browse/MECLIPSE-440 Project: Maven 2.x Eclipse Plugin Issue Type: Task Components: Core : Workspace settings Affects Versions: 2.5.2 Reporter: nicolas de loof My local repository contans -sources.jar for junit and servlet-api. I then have failing tests : testProject13(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject22(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject28(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject29(org.apache.maven.plugin.eclipse.EclipsePluginTest) testProject30(org.apache.maven.plugin.eclipse.EclipsePluginTest) ... All of them fail beacuse the .classpath contains link to the sources archive : Checking .classpath, line #3 expected:<...servlet-api-2.3.jar"[]/>> but was:<...servlet-api-2.3.jar"[ sourcepath="M2_REPO/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar"]/>> An option would be to package with the plugin test resource a repository containing fake (0byte) artifacts, and use it as local repo with offline mode set, so that the available artifacts are fully under control. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
