[jira] Commented: (MPIR-138) Complet Polish translation
[ http://jira.codehaus.org/browse/MPIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169050#action_169050 ] Bartlomiej Kuczynski commented on MPIR-138: --- Ok. I know where is mistake. It should be \u015B\u0107 Complet Polish translation -- Key: MPIR-138 URL: http://jira.codehaus.org/browse/MPIR-138 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Environment: ALL Reporter: Bartlomiej Kuczynski Assignee: Vincent Siveton Priority: Trivial Fix For: 2.2 Attachments: project-info-report_pl.properties I make complete Polish translation of project-info-report.properties, but when I compile and install plug-in I local repository and I try to use it with Polish locales I got only English communicates and messages on sides. Could someone check this file (in attachment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPIR-138) Complet Polish translation
[ http://jira.codehaus.org/browse/MPIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartlomiej Kuczynski updated MPIR-138: -- Attachment: project-info-report_pl.properties Fixed file. Complet Polish translation -- Key: MPIR-138 URL: http://jira.codehaus.org/browse/MPIR-138 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Environment: ALL Reporter: Bartlomiej Kuczynski Assignee: Vincent Siveton Priority: Trivial Fix For: 2.2 Attachments: project-info-report_pl.properties, project-info-report_pl.properties I make complete Polish translation of project-info-report.properties, but when I compile and install plug-in I local repository and I try to use it with Polish locales I got only English communicates and messages on sides. Could someone check this file (in attachment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPIR-138) Complet Polish translation
[ http://jira.codehaus.org/browse/MPIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169050#action_169050 ] Bartlomiej Kuczynski edited comment on MPIR-138 at 3/12/09 5:52 AM: Ok. I know where is mistake. It should be \u015B\u0107 I attach new file was (Author: koziolek): Ok. I know where is mistake. It should be \u015B\u0107 Complet Polish translation -- Key: MPIR-138 URL: http://jira.codehaus.org/browse/MPIR-138 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Environment: ALL Reporter: Bartlomiej Kuczynski Assignee: Vincent Siveton Priority: Trivial Fix For: 2.2 Attachments: project-info-report_pl.properties I make complete Polish translation of project-info-report.properties, but when I compile and install plug-in I local repository and I try to use it with Polish locales I got only English communicates and messages on sides. Could someone check this file (in attachment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3472) configuration possibilities to limit size of local repository
[ http://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169056#action_169056 ] Kariem Hussein commented on MNG-3472: - I have to agree with Andrus and David. The question is not how to configure maven to point to a local repository, but to configure maven to manage the space used by the local repository. The repository is maven's responsibility and should not be handled by external tools. As can be seen from the linked issue CONTINUUM-1693 (referring to CONTINUUM-782), projects relying on maven have to build workarounds to handle this. What can be done to raise awareness and reopen this ticket? What is needed to include something like this? configuration possibilities to limit size of local repository - Key: MNG-3472 URL: http://jira.codehaus.org/browse/MNG-3472 Project: Maven 2 Issue Type: Improvement Components: Settings Affects Versions: 2.0.8 Reporter: manuel aldana it would be great to make repository-size configurable, for instance by setting the maximum number of downloads of a snapshot-version to be kept. thus the explosion of local repository size can be reduced. especially when you are working with many in-house multi-module projects which are marked as snapshots before released , can increase repository size significantly. see mailing-list discussion: http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-100) War overlay with merged web.xml
[ http://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169057#action_169057 ] Gabriele Columbro commented on MWAR-100: An Xpatch kind of thing is not applicable? http://cocoon.apache.org/2.2/maven-plugins/maven-plugin/1.0/1360_1_1.html War overlay with merged web.xml --- Key: MWAR-100 URL: http://jira.codehaus.org/browse/MWAR-100 Project: Maven 2.x War Plugin Issue Type: Wish Affects Versions: 2.0 Reporter: Anders Romin I'm looking for a way to use the war overlay feature and have the web.xml merged with the content of both the parent war and the child war. For example, we have two wars A and B, and B is depending on A using the overlay feature. Now, I'd like all filters, servlets etc that are configured in A to be available in the resulting war, as well as all filters, servlets etc from B. If the id attributes clash, then the objects from B should be used. Any ideas how this could be accomplished? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2388) Jacex Project
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169062#action_169062 ] Alexey Noskov commented on MAVENUPLOAD-2388: Link to WHOIS database for jacex.org http://www.pir.org/index.php?mode=whoisdb=content%2FWebsitetbl=Registrantsid=3whois_query_field=jacexSubmit=Search Jacex Project - Key: MAVENUPLOAD-2388 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2388 Project: Maven Upload Requests Issue Type: Wish Reporter: Alexey Noskov org.jacex,mavens...@web.sourceforge.net:/home/groups/j/ja/jacex/htdocs/maven,rsync_ssh,Alexey Noskov,alexey.nos...@gmail.com,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRELEASE-423) Wrong goal specified to generate a release pom
Wrong goal specified to generate a release pom -- Key: MRELEASE-423 URL: http://jira.codehaus.org/browse/MRELEASE-423 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: documentation Affects Versions: 2.0-beta-8 Environment: On documentation page : http://maven.apache.org/plugins/maven-release-plugin/examples/generate-release-poms.html Reporter: Jérome Da Costa Priority: Minor On the documentation page to explain how to generate a release pom there is an error for the goal : it works on the release:prepare but not on the release:perform goal. According to the documentation of the release:perform goal there is no generateReleasePom option. 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] Commented: (DOXIA-226) Make XML based parsers better handle whitespace
[
http://jira.codehaus.org/browse/DOXIA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169064#action_169064
]
Lukas Theussl commented on DOXIA-226:
-
In addition, whitespace is never ignorable/collapsible/trimmable within
verbatim blocks, ie within source/source or pre/pre in xdocs.
Make XML based parsers better handle whitespace
---
Key: DOXIA-226
URL: http://jira.codehaus.org/browse/DOXIA-226
Project: Maven Doxia
Issue Type: Improvement
Reporter: Benjamin Bentmann
Fix For: 1.2
Regarding whitespace in XML documents, one needs to consider the following
aspects:
- ignorable whitespace, i.e. view {{tr td/ /tr}} and
{{trtd//tr}} as equivalent
- collapsible whitespace, i.e. view {{Text nbsp; Text}} and {{Text
Text}} as equivalent
- trimmable whitespace, i.e. view {{p Text /p}} and {{pText/p}}
as equivalent
Those distinctions require a DTD/XSD in combination with a validating parser
and/or application-specific knowledge. For robustness, doxia parsers for
XML-based formats should not depend on the existence of a schema definition
such that they reliably deliver events into the sinks. Hence I suggest to
hard-code the required logic for proper whitespace handling into each parser.
Currently, whitespace handling is rather static, e.g. {{XhtmlBaseParser}}
pushes all input whitespace into the sink. This might cause troubles with
sinks that are not expected to receive ignorable whitespace. To address this
issue, it seems helpful if {{AbstractXmlParser}} provided a default
implementation of {{handleText()}} that subclasses can simply control via
state flags instead of implementing {{handleText()}} from scratch in each
parser. CopyPaste - which caused DOXIA-225 - needs to be avoided.
More precisely, I image the following changes:
- Have {{AbstractXmlParser}} maintain a stack of tuples (ignorable,
collapsible, trimmable) where each tuple describes the whitespace handling
for the currently parsed element
- Have {{AbstractXmlParser}} push/pop a tuple from this stack before/after
calling {{handleStartTag()}}/{{handleEndTag()}}
- Have {{AbstractXmlParser}} provide setters to allow subclasses to control
the desired whitespace handling in their {{handleStartTag()}} implementation
- Have {{AbstractXmlParser}} implement {{handleText()}} where it evalutes the
top-most tuple from the stack
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-4079) Duplicate error messages
[ http://jira.codehaus.org/browse/MNG-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169083#action_169083 ] Julien HENRY commented on MNG-4079: --- Hi John, Is it supposed to be fixed in RC2? I see no change with my test: mvn -v Apache Maven 2.1.0-RC2 (r752688; 2009-03-12 00:26:25+0100) Java version: 1.4.2_17 Java home: C:\j2sdk1.4.2_17\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Duplicate error messages Key: MNG-4079 URL: http://jira.codehaus.org/browse/MNG-4079 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.0 Environment: Apache Maven 2.1.0 (r751709; 2009-03-09 16:35:14+0100) Java version: 1.4.2_17 Java home: C:\j2sdk1.4.2_17\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Julien HENRY Assignee: John Casey Priority: Minor Fix For: 2.1.0 Attachments: output.txt Very often with Maven the error messages are duplicated. For example deprecation warnings and compilation issues. I've attached an example with -e option. In my case I'm trying to build a project that requires JDK 1.5+ with JDK 1.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSITE-390) Parent menu not visible in child modules
[ http://jira.codehaus.org/browse/MSITE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169085#action_169085 ] Cyril Landriot commented on MSITE-390: -- Yes I used menu ref=parent/ (and it works with site:stage). I can't find a repo with the 2.0 version of the plugin (perhap's could you help me for that ?) I have attached a sample project with same problem. In this sample, the parent menu is not displayed in the pmd-rules module site if generated with mvn site. but it appears with mvn site:stage. Parent menu not visible in child modules Key: MSITE-390 URL: http://jira.codehaus.org/browse/MSITE-390 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-6, 2.0-beta-7 Environment: Tested on Windows XP SP2 3, with maven 2.0.9 2.0.10 Reporter: Cyril Landriot Priority: Minor Attachments: top.zip Hello My problem is that I can't manage to display the parent menu in children modules. This problem appear only when deploying the site, not when staging it (site:stage is OK, site site-deploy are KO). Thank you for your help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSITE-390) Parent menu not visible in child modules
[ http://jira.codehaus.org/browse/MSITE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyril Landriot updated MSITE-390: - Attachment: top.zip Sample project Parent menu not visible in child modules Key: MSITE-390 URL: http://jira.codehaus.org/browse/MSITE-390 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-6, 2.0-beta-7 Environment: Tested on Windows XP SP2 3, with maven 2.0.9 2.0.10 Reporter: Cyril Landriot Priority: Minor Attachments: top.zip Hello My problem is that I can't manage to display the parent menu in children modules. This problem appear only when deploying the site, not when staging it (site:stage is OK, site site-deploy are KO). Thank you for your help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSITE-390) Parent menu not visible in child modules
[ http://jira.codehaus.org/browse/MSITE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169085#action_169085 ] Cyril Landriot edited comment on MSITE-390 at 3/12/09 9:25 AM: --- Yes I used menu ref=parent/ (and it works with site:stage). I can't find a repo with the 2.0 version of the plugin (perhap's could you help me for that ?) I have attached a sample project with same problem (top.zip). In this sample, the parent menu is not displayed in the pmd-rules module site if generated with mvn site. but it appears with mvn site:stage. was (Author: clandriot): Yes I used menu ref=parent/ (and it works with site:stage). I can't find a repo with the 2.0 version of the plugin (perhap's could you help me for that ?) I have attached a sample project with same problem. In this sample, the parent menu is not displayed in the pmd-rules module site if generated with mvn site. but it appears with mvn site:stage. Parent menu not visible in child modules Key: MSITE-390 URL: http://jira.codehaus.org/browse/MSITE-390 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0-beta-6, 2.0-beta-7 Environment: Tested on Windows XP SP2 3, with maven 2.0.9 2.0.10 Reporter: Cyril Landriot Priority: Minor Attachments: top.zip Hello My problem is that I can't manage to display the parent menu in children modules. This problem appear only when deploying the site, not when staging it (site:stage is OK, site site-deploy are KO). Thank you for your help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-482) Surefire tries to run JUnit4 tests that contain no @Test annotations
[ http://jira.codehaus.org/browse/SUREFIRE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169092#action_169092 ] Rik Smith commented on SUREFIRE-482: In my current project, support classes for testing can also be named like *Test. I don't see why this is so strange, and why surefire cannot silently ignore this. The class doesn't extend testcase (which is by my knowledge required by JUnit 3) and it does not have any annotations (Isn't this also required for JUnit 4?) This generates a lot of false failed tests. Surefire tries to run JUnit4 tests that contain no @Test annotations Key: SUREFIRE-482 URL: http://jira.codehaus.org/browse/SUREFIRE-482 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.4.2 Reporter: Mark Hobson Attachments: test.zip Similar to SUREFIRE-346 but for JUnit4, Surefire tries to run classes that contain no @Test annotations as tests, resulting in the exception: java.lang.Exception: No runnable methods at org.junit.internal.runners.MethodValidator.validateInstanceMethods(MethodValidator.java:32) at org.junit.internal.runners.MethodValidator.validateMethodsForDefaultRunner(MethodValidator.java:43) at org.junit.internal.runners.JUnit4ClassRunner.validate(JUnit4ClassRunner.java:36) at org.junit.internal.runners.JUnit4ClassRunner.init(JUnit4ClassRunner.java:27) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.junit.internal.requests.ClassRequest.buildRunner(ClassRequest.java:33) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:28) at org.apache.maven.surefire.junit4.JUnit4TestSet.init(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Such classes should be ignored by Surefire. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3078) artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository
[
http://jira.codehaus.org/browse/MNG-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169097#action_169097
]
Jeremie BOUSQUET commented on MNG-3078:
---
Having exactly this problem with Maven 2.0.10, trying to use
org.apache.maven:apache-maven, classifier:bin, version:2.0.10 and packaging
tar.gz or tar.bz2. Maven used to download it last week, but can't anymore after
deleting from my local repository. I checked in repository central existence of
these different packages.
I'm using archiva as repository manager, proxifying maven central. All other
dependencies download well.
Changing packaging to zip unblocks the situation ...
Dependency declared in my pom in dependencies :
{noformat}
dependency
groupIdorg.apache.maven/groupId
artifactIdapache-maven/artifactId
version2.0.10/version
typetar.gz/type
classifierbin/classifier
scopecompile/scope
/dependency
{noformat}
... And used in my assembly in dependencySets :
{noformat}
dependencySet
unpacktrue/unpack
unpackOptions
excludes
exclude**/settings.xml/exclude
/excludes
/unpackOptions
includes
includeorg.apache.maven:apache-maven/include
/includes
useProjectArtifactfalse/useProjectArtifact
/dependencySet
{noformat}
I tried to bypass archiva and directly connect to central, but the same error
occurs.
artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but
not saved to local repository
-
Key: MNG-3078
URL: http://jira.codehaus.org/browse/MNG-3078
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories, Dependencies
Affects Versions: 2.0.6, 2.0.7
Reporter: Peter Lynch
Priority: Critical
Fix For: 2.0.x
Using mvn deploy:deploy-file you can successfully upload a 'tar.gz' artifact
to a repository.
Example without classifier:
mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=apache-tomcat
-Dversion=6.0.13 -Dpackaging=tar.gz -DrepositoryId=repo-central
-Durl=dav:http://repo.example.com:4000/maven-repos/repo-central/
-Dfile=apache-tomcat-6.0.13.tar.gz
Example with classifier
mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=apache-tomcat
-Dversion=6.0.13 -Dpackaging=tar.gz -Dclassifier=bin
-DrepositoryId=repo-central
-Durl=dav:http://repo.example.com:4000/maven-repos/repo-central/
-Dfile=apache-tomcat-6.0.13.tar.gz
Once uploaded define a dependency in your pom to it.
Example without classifier
project
packagingpom/packaging
...
dependencies
...
dependency
groupIdorg.apache.tomcat/groupId
artifactIdapache-tomcat/artifactId
version6.0.13/version
typetar.gz/type
optionaltrue/optional
/dependency
...
/dependencies
...
/project
Example with classifier
project
packagingpom/packaging
...
dependencies
...
dependency
groupIdorg.apache.tomcat/groupId
artifactIdapache-tomcat/artifactId
version6.0.13/version
typetar.gz/type
classifierbin/classifier
optionaltrue/optional
/dependency
...
/dependencies
...
/project
Now to reproduce the problem you could either do
mvn dependency:resolve
or
mvn assembly:assembly
(if the maven assembly plugin is configured with a dependency set that
unpacks this dependency for example)
The reason I think this is a core bug and not an maven assembly plugin or
maven-dependency-plugin bug is because the problem happens in both of these
independent plugins.
When you run 'mvn dependency:resolve' you'll see that the dependency appears
downloaded but then the build fails with :
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.tomcat:apache-tomcat:tar.gz:bin:6.0.13
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tomcat
-DartifactId=apache-tomcat \
-Dversion=6.0.13 -Dclassifier=bin -Dpackaging=tar.gz
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn
[jira] Commented: (MCHECKSTYLE-105) Update to Checkstyle 5.0-beta01
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169100#action_169100 ] Travis Schneeberger commented on MCHECKSTYLE-105: - Does anyone know the status of the patch? For those now using Java 5 and above CheckStyle 5 fixes a lot of bugs. This is an important patch for those building with Maven and using CheckStyle. Update to Checkstyle 5.0-beta01 --- Key: MCHECKSTYLE-105 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Felix Röthenbacher Fix For: 2.3 Attachments: patch.diff Checkstyle 5.0-beta01 adds support for generics, etc. See http://checkstyle.sourceforge.net/5.x/releasenotes.html for a list of new features. Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is available from a public Maven repository. Patch updates plugin to changed API / implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2390) JETM 1.2.3 bundles
JETM 1.2.3 bundles --- Key: MAVENUPLOAD-2390 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2390 Project: Maven Upload Requests Issue Type: Wish Reporter: Juergen Englisch Please upload jetm 1.2.3 to central maven2 repository. Thanks, Jürgen http://jetm.void.fm/maven2/jetm-1.2.3/jetm-1.2.3-bundle.jar http://jetm.void.fm/maven2/jetm-1.2.3/jetm-optional-1.2.3-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-2390) JETM 1.2.3 bundles
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169126#action_169126 ] Juergen Englisch commented on MAVENUPLOAD-2390: --- https://sourceforge.net/projects/jetm/ http://sourceforge.net/users/jenglisch/ JETM 1.2.3 bundles --- Key: MAVENUPLOAD-2390 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2390 Project: Maven Upload Requests Issue Type: Wish Reporter: Juergen Englisch Please upload jetm 1.2.3 to central maven2 repository. Thanks, Jürgen http://jetm.void.fm/maven2/jetm-1.2.3/jetm-1.2.3-bundle.jar http://jetm.void.fm/maven2/jetm-1.2.3/jetm-optional-1.2.3-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: (MJAR-24) don't sign already signed jars (also allow for in-place jar signing)
[ http://jira.codehaus.org/browse/MJAR-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169144#action_169144 ] Andrew Hart commented on MJAR-24: - I know this is an old issue, but why is it this way? For example, suppose I have an already signed jar and I want to add another signer to the jar. This is currently causing me a little bit of grief. To elaborate: my understanding is that if I have a secure applet, all of the jars need to be signed by the same signer. This applet uses several jar files, including one from the Nasa WorldWind project which is signed by Nasa. My applet is signed by me, but I also want to sign the nasa jar so that all of the jars used by the applet are signed by the same signer. A jar file may have multiple signers. In looking at the docs for this plugin, I don't see any way to force the plugin to sign (add another signer) to an already signed jar. Thanks. don't sign already signed jars (also allow for in-place jar signing) Key: MJAR-24 URL: http://jira.codehaus.org/browse/MJAR-24 Project: Maven 2.x Jar Plugin Issue Type: Improvement Reporter: Jerome Lacoste Assignee: Kenney Westerhof Priority: Critical Fix For: 2.1 Attachments: jarsign-skipsignedjars.diff, MJAR-24-v2.diff Patch by Richard Allen richard.al...@gtri.gatech.edu Documentation by Jerome Lacoste (jer...@coffeebreaks.org) - allows for in-place signing of the jar. - avoid signing the jar twice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-103) Maven bootstrap fails on some local repos
[ http://jira.codehaus.org/browse/MERCURY-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169148#action_169148 ] Oleg Gusakov commented on MERCURY-103: -- solved the last piece of the puzzle: cache was checking condition ts1 ts2, while for always it should have been ts1 = ts2 as diff was zero. Added explicit check for policy always in order to save some nannos .. Case closed! Maven bootstrap fails on some local repos - Key: MERCURY-103 URL: http://jira.codehaus.org/browse/MERCURY-103 Project: Mercury Issue Type: Bug Components: Ant tasks, Dependency Builder, Repository Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov Fix For: 1.0-alpha-6 Attachments: bad-mercury-repo.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-103) Maven bootstrap fails on some local repos
[ http://jira.codehaus.org/browse/MERCURY-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-103. Resolution: Fixed figured out all the use cases, changed the code to make the best effort to address them. Maven bootstrap fails on some local repos - Key: MERCURY-103 URL: http://jira.codehaus.org/browse/MERCURY-103 Project: Mercury Issue Type: Bug Components: Ant tasks, Dependency Builder, Repository Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov Fix For: 1.0-alpha-6 Attachments: bad-mercury-repo.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-541) Add objectFactory support
Add objectFactory support - Key: SUREFIRE-541 URL: http://jira.codehaus.org/browse/SUREFIRE-541 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Reporter: Marvin Froeder Attachments: objectFactory.patch TestNG does have an option called objectFactory. That is currently not supported by surefire. The following patch includes it. VELO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-541) Add objectFactory support
[ http://jira.codehaus.org/browse/SUREFIRE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed SUREFIRE-541. - Resolution: Fixed Add objectFactory support - Key: SUREFIRE-541 URL: http://jira.codehaus.org/browse/SUREFIRE-541 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Reporter: Marvin Froeder Attachments: objectFactory.patch TestNG does have an option called objectFactory. That is currently not supported by surefire. The following patch includes it. VELO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSITE-391) site:state creates wrong links for menu items
[
http://jira.codehaus.org/browse/MSITE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169166#action_169166
]
Dennis Lundberg commented on MSITE-391:
---
Your test case works just fine for me. I'm on Windows XP using Maven 2.0.10.
What's your environment?
You have an invalid site URL specified in the POM. That might be the reason for
your problems.
{noformat}
/site
{noformat}
is not a valid URL.
site:state creates wrong links for menu items
-
Key: MSITE-391
URL: http://jira.codehaus.org/browse/MSITE-391
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Hugo Palma
Attachments: test-case.zip
I'm attaching a test case where if you run the site:stage goal it will
generate wrong links on the left menu. The links will actually point to the
root site directory when they should point the the pages i provided in the
href attribute in my site.xml descriptor file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-4084) Unnecessary Warning for an activate profile in child project
Unnecessary Warning for an activate profile in child project Key: MNG-4084 URL: http://jira.codehaus.org/browse/MNG-4084 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.0 Environment: windows Reporter: Dan Tran Attachments: testpoms.zip When a profile defined in parent but activate from command line in child project, an incorrect warning display on the screen Reference to this discussion is at http://www.nabble.com/-PLEASE-TEST--Maven-2.1.0-RC2-td22467128.html see the attached poms to reproduce the propblem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-4084) Unnecessary Warning for an activate profile in child project
[ http://jira.codehaus.org/browse/MNG-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4084: Assignee: John Casey Fix Version/s: 2.1.0 Unnecessary Warning for an activate profile in child project Key: MNG-4084 URL: http://jira.codehaus.org/browse/MNG-4084 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.0 Environment: windows Reporter: Dan Tran Assignee: John Casey Fix For: 2.1.0 Attachments: testpoms.zip When a profile defined in parent but activate from command line in child project, an incorrect warning display on the screen Reference to this discussion is at http://www.nabble.com/-PLEASE-TEST--Maven-2.1.0-RC2-td22467128.html see the attached poms to reproduce the propblem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-4084) Unnecessary Warning for an activate profile in child project
[ http://jira.codehaus.org/browse/MNG-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-4084. - Assignee: Brett Porter (was: John Casey) Resolution: Fixed Unnecessary Warning for an activate profile in child project Key: MNG-4084 URL: http://jira.codehaus.org/browse/MNG-4084 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.0 Environment: windows Reporter: Dan Tran Assignee: Brett Porter Fix For: 2.1.0 Attachments: testpoms.zip When a profile defined in parent but activate from command line in child project, an incorrect warning display on the screen Reference to this discussion is at http://www.nabble.com/-PLEASE-TEST--Maven-2.1.0-RC2-td22467128.html see the attached poms to reproduce the propblem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-4084) Unnecessary Warning for an activate profile in child project
[ http://jira.codehaus.org/browse/MNG-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4084: -- Fix Version/s: 2.0.11 Unnecessary Warning for an activate profile in child project Key: MNG-4084 URL: http://jira.codehaus.org/browse/MNG-4084 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1.0 Environment: windows Reporter: Dan Tran Assignee: Brett Porter Fix For: 2.0.11, 2.1.0 Attachments: testpoms.zip When a profile defined in parent but activate from command line in child project, an incorrect warning display on the screen Reference to this discussion is at http://www.nabble.com/-PLEASE-TEST--Maven-2.1.0-RC2-td22467128.html see the attached poms to reproduce the propblem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2391) Prevayler 2.3 bundle to upload
Prevayler 2.3 bundle to upload -- Key: MAVENUPLOAD-2391 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2391 Project: Maven Upload Requests Issue Type: Wish Reporter: Justin Sampson Attachments: prevayler-2.3-bundle.jar http://prevayler.sourceforge.net/maven/prevayler-2.3-bundle.jar I'm the current project lead: http://sourceforge.net/projects/prevayler/ Our next release will be built using Maven natively, so I'll set up the proper automatic repository sync (and we'll have more complete POMs). I'd like to get this previous release uploaded to the central repository manually, though. 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
