[jira] Commented: (MNG-2980) Strange behavior with folder named null
[ http://jira.codehaus.org/browse/MNG-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95077 ] Francesco Tinti commented on MNG-2980: -- I'm afraid but according to the fact that jta war already in maven repository the problem is still here for two reasons: First because I add to pom this: javax.transaction jta 1.0.1B compile compiler continue to give Missing: -- 1) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta \ -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) net.sourceforge.openutils:openutils-usermanagement:jar:1.1.2-SNAPSHOT 2) javax.transaction:jta:jar:1.0.1B -- Second because if I remove the "null" folder -with or without the jta depedency in POM- I can build the jar without problems. > Strange behavior with folder named null > --- > > Key: MNG-2980 > URL: http://jira.codehaus.org/browse/MNG-2980 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows Vista 64bit - Sun JDK 1.6.0_01 64bit - Maven2 > based on svn trunk 534974 version >Reporter: Francesco Tinti >Priority: Critical > > To reproduce this issue follow these steps: > 1. create a multi-project POM with at least 1 module > 2. go to module folder > 3. create an empty folder named null > 4. launch mvn clean install from module folder as you want to build only that > module. > Maven will fail and the given reason is "Failed to resolve artifact" with a > list of missing artifacts. > And this is wrong because all artifacts are already in 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] Commented: (MJAVADOC-108) proxy support for plugin not complete enough
[
http://jira.codehaus.org/browse/MJAVADOC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95085
]
Vincent Siveton commented on MJAVADOC-108:
--
I guess that *-J-DproxyHost* is for *-J-Dhttp.proxyHost*
Since I have no proxy with auth, could you try with these parameters:
{noformat}
-J-Dhttp.proxyUserName=xxx -J-Dhttp.proxyPassword=xxx
{noformat}
> proxy support for plugin not complete enough
>
>
> Key: MJAVADOC-108
> URL: http://jira.codehaus.org/browse/MJAVADOC-108
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Barrie Treloar
>
> AbstractJavadocMojo.java supports
> * @parameter expression="${proxyHost}"
> default-value="${settings.activeProxy.host}"
> * @parameter expression="${proxyPort}"
> default-value="${settings.activeProxy.port}"
> but does not include the full capabilities of settings.xml
> This needs extending.
> line 981:
> {code:language=java}
> if ( StringUtils.isNotEmpty( proxyHost ) && proxyPort > 0 )
> {
> cmd.createArgument().setValue( "-J-DproxyHost=" + proxyHost );
> cmd.createArgument().setValue( "-J-DproxyPort=" + proxyPort );
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-121) Add a new parameter to handle additional -J options
Add a new parameter to handle additional -J options --- Key: MJAVADOC-121 URL: http://jira.codehaus.org/browse/MJAVADOC-121 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Vincent Siveton We need to add a new parameter (for example additionaljoptions) to handle java options: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#J Note: The parameter is for the javadoc not for the jvm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MJAVADOC-120) Better handling of Javadoc resources: overview.html, doc-files
[ http://jira.codehaus.org/browse/MJAVADOC-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-120. Resolution: Fixed Fix Version/s: 2.3 added in svn > Better handling of Javadoc resources: overview.html, doc-files > -- > > Key: MJAVADOC-120 > URL: http://jira.codehaus.org/browse/MJAVADOC-120 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.3 > > > The javadocDirectory parameter should be used for miscellaneous files > (doc-files in the spec, see > http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/javadoc.html#unprocessed) > Moreover, the overview.html should be autodetected in the javadocDirectory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MJAVADOC-121) Add a new parameter to handle additional -J options
[ http://jira.codehaus.org/browse/MJAVADOC-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-121. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.3 added additionalJOption parameter > Add a new parameter to handle additional -J options > --- > > Key: MJAVADOC-121 > URL: http://jira.codehaus.org/browse/MJAVADOC-121 > Project: Maven 2.x Javadoc Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.3 > > > We need to add a new parameter (for example additionaljoptions) to handle > java options: > http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#J > Note: The parameter is for the javadoc not for the jvm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MJAVADOC-87) doc-files ignored if they reside in the resources directory
[ http://jira.codehaus.org/browse/MJAVADOC-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-87. --- Resolution: Fixed Fix Version/s: (was: 2.1) 2.3 moreover see MJAVADOC-120 > doc-files ignored if they reside in the resources directory > --- > > Key: MJAVADOC-87 > URL: http://jira.codehaus.org/browse/MJAVADOC-87 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Matthew Beermann >Assignee: Vincent Siveton > Fix For: 2.3 > > Attachments: my-app.zip > > > It looks like MJAVADOC-76 was closed prematurely, or maybe it just had a bad > summary. The bug is this: if you have a "doc-files" folder in the > "src/main/resources" branch of your project, its contents will be omitted > from the Javadoc output. However, if you move the same folder over to > "src/main/java", it will be included in the output. This bug is present in > the released (2.0) version of the plugin. > The file "package.html", by comparison, will be included in the Javadoc > output no matter where it is. This is the expected behavior, AFAICT. More > information about the "doc-files" directory can be found here: > http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#unprocessed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MJAVADOC-114) Less output
[ http://jira.codehaus.org/browse/MJAVADOC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-114. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.3 added a FAQ entry > Less output > --- > > Key: MJAVADOC-114 > URL: http://jira.codehaus.org/browse/MJAVADOC-114 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Bernhard Mähr >Assignee: Vincent Siveton >Priority: Trivial > Fix For: 2.3 > > > Hello! > Javadoc creates to much unnesseary output. > Greetings > Bernhard Mähr -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MCLOVER-46) Coverage reports are incorrect for interface only modules.
[
http://jira.codehaus.org/browse/MCLOVER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol closed MCLOVER-46.
-
Resolution: Won't Fix
Closing as won't fix as suggsted
> Coverage reports are incorrect for interface only modules.
> ---
>
> Key: MCLOVER-46
> URL: http://jira.codehaus.org/browse/MCLOVER-46
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: ubuntu dapper drake. Maven 2.0, clover maven plugin 2.2
>Reporter: Meghan Claire Pike
>Assignee: Vincent Massol
>
> Our projects require a coverage of at least 1% in order to force everyone to
> at least think about testing. Unfortunately for interface only packages, (due
> to seperation of concerns) clover just goes into a small spasm and dies. It's
> output is like this:
> Clover Version 1.3.12, built on February 08 2006
> loaded from:
> .m2/repository/com/cenqua/clover/clover/1.3.12/clover-1.3.12.jar
> Academic License registered to EDINA. This license of Clover is provided to
> support coursework at EDINA only.
> You have 29 day(s) before your Academic License expires.
> Updating database at 'target/clover/clover.db'
> Processing files at 1.4 source level.
> Instrumented 12 source files.
> ...
> [INFO] [clover:instrument {execution: default}]
> [INFO] [clover:check {execution: default}]
> [INFO] Checking for coverage of [1%] for database [target/clover/clover.db]
> WARN: No coverage data found for '/target/clover/clover.db'.
> [ERROR] Total coverage of did not meet target of 1%
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Build failed to meet Clover coverage targets
> it doesn't even output 0% or anything like that, which seems to me to be a
> bug. I think clover should maybe understand a little better that testing
> api's doesn't make sense, and is quite difficult to do. I don't have any
> testing classes whatsoever in the project, so it could be from that. But
> clover should have some ability not to enforce coverage on interfaces. (Or
> understand that they can't be tested except indirectly.)
> Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-266) plugin applies java facet to ear project
plugin applies java facet to ear project Key: MECLIPSE-266 URL: http://jira.codehaus.org/browse/MECLIPSE-266 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: WTP support Affects Versions: 2.3 Environment: Windows XP Reporter: Srepfler Srgjan In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module I'm getting this: This is a wrong facet on a EAR module and I can't compile if I don't edit this file manually (I can't do it from the project properties - facets dialog) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MONE-8) The goal one:convert is not implemented in version 1.0 although it is documented and should work.
[ http://jira.codehaus.org/browse/MONE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MONE-8: --- Assignee: Dennis Lundberg Affects Version/s: 1.0 Fix Version/s: 1.1 Summary: The goal one:convert is not implemented in version 1.0 although it is documented and should work. (was: The goal one:convert is not implement in version 1.0 although it is documented and should work.) The page you are referring to says "Version: 1.1-SNAPSHOT" at the top left. It is sometimes unfortunate that we don't have separate docs for different versions of a plugin. Look out for version 1.1 within a couple of weeks. > The goal one:convert is not implemented in version 1.0 although it is > documented and should work. > - > > Key: MONE-8 > URL: http://jira.codehaus.org/browse/MONE-8 > Project: Maven 2.x M1 Plugin > Issue Type: Bug >Affects Versions: 1.0 > Environment: Win XP >Reporter: Eric Vanlaeken >Assignee: Dennis Lundberg > Fix For: 1.1 > > > The goal one:convert is not implement in version 1.0 although it is > documented and should work. > Could you give an estimation when this will work? > tnx > Eric -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MIDEA-86) [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules
[
http://jira.codehaus.org/browse/MIDEA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95103
]
Dennis Lundberg commented on MIDEA-86:
--
I'm reluctant to add features to this plugin for IDEA 7. IDEA 7 is still under
development and its features and configuration file format might change before
it's final release. So I prefer to not add this feature until IDEA 7 has been
released.
Setting the jdkLevel for the plugin is a good idea. But I think that I will do
it in the plugins pom instead, or perhaps even higher up in the pom hierarchy.
> [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules
> ---
>
> Key: MIDEA-86
> URL: http://jira.codehaus.org/browse/MIDEA-86
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
>Affects Versions: 2.0, 2.1
> Environment: IntelliJ IDEA 7.x (Selena)
>Reporter: Arik Kfir
> Attachments: idea-7-support.patch
>
>
> This patch prevents generation of an entry for the deployment descriptor if
> it does not exist, in accordance to JEE 5. This is only done if the actual
> IDEA version (set in the project's POM) is indeed 7. In IDEA 7, if a
> descriptor is specified in the IML file, but does not exist, it spits out an
> error on every compilation
> Also, *unrelated* to the plugin runtime, this patch adds this snippet to the
> pom.xml:
> {noformat}
>
>
> maven-idea-plugin
>
> 1.4
>
>
>
> {noformat}
> For those who use IDEA to work on the plugin, this makes sure that the
> project JDK level is 1.4 (which is the policy currently, to prevent IDEA's
> suggestions for JDK 5-level (e.g. "don't suggest using a "for-each" instead
> of "for(int i=...)")
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (WAGON-83) mvn deploy causes NPE in ChecksumObserver.transferStarted
mvn deploy causes NPE in ChecksumObserver.transferStarted -- Key: WAGON-83 URL: http://jira.codehaus.org/browse/WAGON-83 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Reporter: Eric Barroca Attachments: mvn-deploy-wagon-error.log When doing a mvn deploy to an archiva repository, I get a NPE in ChecksumObserver.transferStarted. I can reproduce it every time on this project. The strange thing is that I never get it on other projects. Full debug log attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MIDEA-86) [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules
[
http://jira.codehaus.org/browse/MIDEA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95168
]
Arik Kfir commented on MIDEA-86:
ok...
> [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules
> ---
>
> Key: MIDEA-86
> URL: http://jira.codehaus.org/browse/MIDEA-86
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
>Affects Versions: 2.0, 2.1
> Environment: IntelliJ IDEA 7.x (Selena)
>Reporter: Arik Kfir
> Attachments: idea-7-support.patch
>
>
> This patch prevents generation of an entry for the deployment descriptor if
> it does not exist, in accordance to JEE 5. This is only done if the actual
> IDEA version (set in the project's POM) is indeed 7. In IDEA 7, if a
> descriptor is specified in the IML file, but does not exist, it spits out an
> error on every compilation
> Also, *unrelated* to the plugin runtime, this patch adds this snippet to the
> pom.xml:
> {noformat}
>
>
> maven-idea-plugin
>
> 1.4
>
>
>
> {noformat}
> For those who use IDEA to work on the plugin, this makes sure that the
> project JDK level is 1.4 (which is the policy currently, to prevent IDEA's
> suggestions for JDK 5-level (e.g. "don't suggest using a "for-each" instead
> of "for(int i=...)")
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
