[jira] (MNG-1378) Make dependencies of test-jars transitive
[ https://jira.codehaus.org/browse/MNG-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308388#comment-308388 ] Tomasz Szuba commented on MNG-1378: --- What is the status of this issue? Is it even considered to implement this feature? > Make dependencies of test-jars transitive > - > > Key: MNG-1378 > URL: https://jira.codehaus.org/browse/MNG-1378 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson > Fix For: Issues to be reviewed for 3.x > > Attachments: mng1378.tar.gz > > > test-jar transitive dependencies are calculated as per compile scope rather > than test scope. > The situation is demonstrated nicely in it0077: > * module sub1 has a test-scoped dependency of commons-lang > * module sub2 has a test-scoped dependency of sub1 test-jar > sub2 tests should inherit the commons-lang transitive dependency. For > example: > Index: > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > === > --- > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > (revision > 328307) > +++ > maven-core-it/it0077/sub2/src/test/java/org/apache/maven/it0077/PersonTwoTest.java > (working > copy) > @@ -1,6 +1,7 @@ > package org.apache.maven.it0077; > import junit.framework.TestCase; > +import org.apache.commons.lang.BooleanUtils; > public class PersonTwoTest > extends PersonTest > Results in: > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > c:\maven-components\maven-core-it\it0077\sub2\src\test\java\org\apache\maven\it0077\PersonTwoTest.java:[4,31] > package org.apache.commons.lang does not exist -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-1493) Support in multiproject environment modules with different named POMs
[ https://jira.codehaus.org/browse/MNG-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308389#comment-308389 ] Rollin Chen commented on MNG-1493: -- Here's an example for using alternative pom file in module child/pom-jdk14.xml > Support in multiproject environment modules with different named POMs > - > > Key: MNG-1493 > URL: https://jira.codehaus.org/browse/MNG-1493 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0 >Reporter: Joerg Schaible >Assignee: John Casey >Priority: Minor > Fix For: 2.0.9, 3.0-alpha-1 > > Attachments: DefaultMaven.diff > > > Command line version of Maven 2 supports POMs with a different name using the > -f option. Unfortunately such POMs cannot be used as modules, since the value > of the module tag is defined as a directory to another pom.xml instead of a > pathname to another POM. Only if the value is not already an existing file > the value should be treated as directory with a present pom.xml file. Similar > situation applies to the relativePath element of the parent tag. > This makes the generation of different artifacts from the same sources (with > some modifications) much more easy. Currently you will have to put the POMs > in separate directories and modify the sourec location into another module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-68) clean for in footer
Eric Barboni created MSKINS-68: -- Summary: clean for in footer Key: MSKINS-68 URL: https://jira.codehaus.org/browse/MSKINS-68 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.1 Environment: web Reporter: Eric Barboni Priority: Minor Attachments: footerxmlclean.patch There are some ugly shown in the generated page. Patch to make output nicer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-286) Support for Jira custom fields in jira-report columnNames
Peter Friberg created MCHANGES-286:
--
Summary: Support for Jira custom fields in jira-report columnNames
Key: MCHANGES-286
URL: https://jira.codehaus.org/browse/MCHANGES-286
Project: Maven 2.x Changes Plugin
Issue Type: Wish
Components: jira
Affects Versions: 2.7.1
Reporter: Peter Friberg
A lot of important info is often described in Jira custom fields. In my case,
the report will not fulfill the requirements because I can't output some
important customfields in the report.
I would be happy to see support for this. For example, be able specify:
{code:xml}Key,Type,Priority,Summary,customfield_10023,
customfield_10041{code}
The descriptive name of the customfield should be returned back to the report.
It would be a good start with the simple custom field types, such as text
fields and single select.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-61) Bump dependencies and fix POMs
Tamás Cservenák created MINDEXER-61: --- Summary: Bump dependencies and fix POMs Key: MINDEXER-61 URL: https://jira.codehaus.org/browse/MINDEXER-61 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák Bump dependencies and fix POMs: * plexus-component-anno is used but is not a dep (is transitive) * plexus-utils ditto * aether bump to 1.13.1 * sisu-inject-plexus bump to 2.2.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-62) Refactor the build and move out CLI tool
Tamás Cservenák created MINDEXER-62:
---
Summary: Refactor the build and move out CLI tool
Key: MINDEXER-62
URL: https://jira.codehaus.org/browse/MINDEXER-62
Project: Maven Indexer
Issue Type: Improvement
Reporter: Tamás Cservenák
Refactor the build and move out CLI tool. The fact that {{indexer-core}} makes
the library JAR but also produces a CLI tool (using shading, as subartifact)
just makes more problematic to properly scope deps and makes integrator's life
harder.
Just create a new module {{indexer-cli}} and make it dedicated to produce the
CLI tool, and make {{indexer-core}} have less burden to drag along.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-332) unpack-dependencies needs a skip parameter like unpack
[
https://jira.codehaus.org/browse/MDEP-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308405#comment-308405
]
Ivan commented on MDEP-332:
---
Any hope to have this in Maven ?
> unpack-dependencies needs a skip parameter like unpack
> --
>
> Key: MDEP-332
> URL: https://jira.codehaus.org/browse/MDEP-332
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: unpack-dependencies
>Affects Versions: 2.3
>Reporter: Laird Nelson
>Assignee: Brian Fox
> Attachments: [MDEP-332]
> Added_skip_option_copy-dependency-and_unpack_dependency.patch
>
>
> The {{unpack}} goal has a {{skip}} parameter that skips execution. The
> {{unpack-dependencies}} goal does not have such a parameter. It should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5255) Dependency with 'provided' scope has its transitive dependency included in final artifact
[ https://jira.codehaus.org/browse/MNG-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308416#comment-308416 ] Rakesh commented on MNG-5255: - @Andrey what version of Maven you are using ? Is this behavior only in the newer versions of Maven 3.x.x or its happening in Maven 2.x.x versions too .? > Dependency with 'provided' scope has its transitive dependency included in > final artifact > - > > Key: MNG-5255 > URL: https://jira.codehaus.org/browse/MNG-5255 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.4 > Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) > Maven home: D:\bin\apache-maven-3.0.4 > Java version: 1.6.0_27, vendor: Sun Microsystems Inc. > Java home: D:\bin\java\jdk1.6.0_27\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Bart Skondin > Attachments: provided-scope-not-working.zip > > > Expected: A dependency declared with a scope of 'provided', along with any > transitive dependencies, should not be included in the final artifact. > Actual: I have a dependency, jsp-api, declared with 'provided' scope. This > dependency has a dependency of its own, servlet-api. The servlet-api.jar is > being included in the web-inf/lib folder of the resultant war file. > Background: We recently upgraded from Maven 2.2.1 to Maven 3.0.4. The problem > was not witnessed until after the upgrade. > Steps to Reproduce: Run mvn install, then have a look at the web-inf/lib > folder. Notice that the servlet-api.jar has been included. > Additional Info: It seems that I can only reproduce this behavior when > declaring a specific dependency in my pom, spring-ldap. Here is the > dependency tree for the given pared-down project (attached): > --- maven-dependency-plugin:2.1:tree (default-cli) @ > provided-scope-not-working --- > com.bug.example:provided-scope-not-working:war:0.0.1-SNAPSHOT > +- javax.servlet:jsp-api:jar:2.0:provided > | \- javax.servlet:servlet-api:jar:2.4:provided > \- org.springframework.ldap:spring-ldap:jar:1.2.1:compile >+- commons-logging:commons-logging:jar:1.0.4:compile >+- commons-lang:commons-lang:jar:2.1:compile >+- org.springframework:spring-beans:jar:2.0.6:compile >| +- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) >| \- (org.springframework:spring-core:jar:2.0.6:compile - omitted for > duplicate) >\- org.springframework:spring-core:jar:2.0.6:compile > \- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5255) Dependency with 'provided' scope has its transitive dependency included in final artifact
[ https://jira.codehaus.org/browse/MNG-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308418#comment-308418 ] Andrey Saksonov commented on MNG-5255: -- @Rakesh same behavior on 3.0.3, 3.0.4 and 2.2.1 > Dependency with 'provided' scope has its transitive dependency included in > final artifact > - > > Key: MNG-5255 > URL: https://jira.codehaus.org/browse/MNG-5255 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.4 > Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) > Maven home: D:\bin\apache-maven-3.0.4 > Java version: 1.6.0_27, vendor: Sun Microsystems Inc. > Java home: D:\bin\java\jdk1.6.0_27\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Bart Skondin > Attachments: provided-scope-not-working.zip > > > Expected: A dependency declared with a scope of 'provided', along with any > transitive dependencies, should not be included in the final artifact. > Actual: I have a dependency, jsp-api, declared with 'provided' scope. This > dependency has a dependency of its own, servlet-api. The servlet-api.jar is > being included in the web-inf/lib folder of the resultant war file. > Background: We recently upgraded from Maven 2.2.1 to Maven 3.0.4. The problem > was not witnessed until after the upgrade. > Steps to Reproduce: Run mvn install, then have a look at the web-inf/lib > folder. Notice that the servlet-api.jar has been included. > Additional Info: It seems that I can only reproduce this behavior when > declaring a specific dependency in my pom, spring-ldap. Here is the > dependency tree for the given pared-down project (attached): > --- maven-dependency-plugin:2.1:tree (default-cli) @ > provided-scope-not-working --- > com.bug.example:provided-scope-not-working:war:0.0.1-SNAPSHOT > +- javax.servlet:jsp-api:jar:2.0:provided > | \- javax.servlet:servlet-api:jar:2.4:provided > \- org.springframework.ldap:spring-ldap:jar:1.2.1:compile >+- commons-logging:commons-logging:jar:1.0.4:compile >+- commons-lang:commons-lang:jar:2.1:compile >+- org.springframework:spring-beans:jar:2.0.6:compile >| +- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) >| \- (org.springframework:spring-core:jar:2.0.6:compile - omitted for > duplicate) >\- org.springframework:spring-core:jar:2.0.6:compile > \- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-131) Attaching of shaded jar does not happen
James Davis created MSHADE-131:
--
Summary: Attaching of shaded jar does not happen
Key: MSHADE-131
URL: https://jira.codehaus.org/browse/MSHADE-131
Project: Maven 2.x Shade Plugin
Issue Type: Bug
Affects Versions: 2.0, 1.5
Environment: Kubuntu 12.04, Oracle Java 1.6.0_26, Maven 3.0.3
Reporter: James Davis
With the following plugin configuration:
org.apache.maven.plugins
maven-shade-plugin
package
shade
${project.build.directory}/${project.build.finalName}-executable.jar
META-INF/spring.handlers
META-INF/spring.schemas
my.example.Main
true
shaded
If I use this, it builds the shaded artifact but it does not get included when
I run mvn install or mvn deploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-131) Attaching of shaded jar does not happen
[
https://jira.codehaus.org/browse/MSHADE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308424#comment-308424
]
James Davis commented on MSHADE-131:
After a little bit more experimentation, it turns out that what it does not
like is the setting of the output directory. After looking at the
documentation, I guess this is the "expected" behavior. However, I believe
this is not the correct behavior because this causes the shaded artifact to
clobber the original jar.
> Attaching of shaded jar does not happen
> ---
>
> Key: MSHADE-131
> URL: https://jira.codehaus.org/browse/MSHADE-131
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.5, 2.0
> Environment: Kubuntu 12.04, Oracle Java 1.6.0_26, Maven 3.0.3
>Reporter: James Davis
>
> With the following plugin configuration:
>
> org.apache.maven.plugins
> maven-shade-plugin
>
>
> package
>
> shade
>
>
>
> ${project.build.directory}/${project.build.finalName}-executable.jar
>
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> META-INF/spring.handlers
>
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> META-INF/spring.schemas
>
> implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
> my.example.Main
>
>
> true
> shaded
>
>
>
>
> If I use this, it builds the shaded artifact but it does not get included
> when I run mvn install or mvn deploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-131) Attaching of shaded jar does not happen
[
https://jira.codehaus.org/browse/MSHADE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Davis closed MSHADE-131.
--
Resolution: Not A Bug
Ok, after doing more playing around I discovered that not using outputFile and
leaving shadedArtifactAttached does behave as one might expect.
> Attaching of shaded jar does not happen
> ---
>
> Key: MSHADE-131
> URL: https://jira.codehaus.org/browse/MSHADE-131
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.5, 2.0
> Environment: Kubuntu 12.04, Oracle Java 1.6.0_26, Maven 3.0.3
>Reporter: James Davis
>
> With the following plugin configuration:
>
> org.apache.maven.plugins
> maven-shade-plugin
>
>
> package
>
> shade
>
>
>
> ${project.build.directory}/${project.build.finalName}-executable.jar
>
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> META-INF/spring.handlers
>
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> META-INF/spring.schemas
>
> implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
> my.example.Main
>
>
> true
> shaded
>
>
>
>
> If I use this, it builds the shaded artifact but it does not get included
> when I run mvn install or mvn deploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-68) clean for in footer
[ https://jira.codehaus.org/browse/MSKINS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MSKINS-68: -- Assignee: Olivier Lamy > clean for in footer > -- > > Key: MSKINS-68 > URL: https://jira.codehaus.org/browse/MSKINS-68 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.1 > Environment: web >Reporter: Eric Barboni >Assignee: Olivier Lamy >Priority: Minor > Attachments: footerxmlclean.patch > > > There are some ugly shown in the > generated page. > Patch to make output nicer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-68) clean for in footer
[ https://jira.codehaus.org/browse/MSKINS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSKINS-68. -- Resolution: Fixed Fix Version/s: fluido-1.3.1 applied. Thanks! > clean for in footer > -- > > Key: MSKINS-68 > URL: https://jira.codehaus.org/browse/MSKINS-68 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.1 > Environment: web >Reporter: Eric Barboni >Assignee: Olivier Lamy >Priority: Minor > Fix For: fluido-1.3.1 > > Attachments: footerxmlclean.patch > > > There are some ugly shown in the > generated page. > Patch to make output nicer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308442#comment-308442 ] Ahmed El-Madhoun commented on MASSEMBLY-343: Hi Zuhayr, I am running into a similar issue where I really need to support sym links as part of the assembly procedure. Do you know what version of the assembly plugin this patch is for? I would like to apply this patch and use it if possible. Thanks in advance. > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-179) Warnings
[ https://jira.codehaus.org/browse/MCOMPILER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MCOMPILER-179: -- The fix breaks the IT of MCOMPILER-120, downgrading to plexus-compiler-1.9.1 makes IT succeed again. > Warnings > - > > Key: MCOMPILER-179 > URL: https://jira.codehaus.org/browse/MCOMPILER-179 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.4, 2.5, 2.5.1 > Environment: Windows7, 64-bit > VMs, 1.6.0_32 and 1.7.0_04 both 64-bit >Reporter: Sascha Vogt >Assignee: Kristian Rosenvold > Fix For: 2.6 > > > If one error occurs, all warnings are shown as error as well. Up to 2.3.2 > this was not the case. Sample output 2.4 and higher: > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] bad path element "": no such file or directory > C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] > [unchecked] unchecked call to add(E) as a member of the raw type > java.util.List > [ERROR] > C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] > [unchecked] unchecked call to add(E) as a member of the raw type > java.util.List > [ERROR] > C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] > [unchecked] unchecked conversion > found : java.util.List > required: java.util.List > [ERROR] > C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] > getList() in de.maybebuggy.sample.Main cannot be applied to (int) > [INFO] 4 errors > Sample output 2.3.2: > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] > \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] > [unchecked] unchecked call to add(E) as a member of the raw type > java.util.List > [WARNING] > \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] > [unchecked] unchecked call to add(E) as a member of the raw type > java.util.List > [WARNING] > \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] > [unchecked] unchecked conversion > found : java.util.List > required: java.util.List > [INFO] 3 warnings > [INFO] - > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] > getList() in de.maybebuggy.sample.Main cannot be applied to (int) > [INFO] 1 error > [INFO] - > With the current behavior it is extremely hard to spot the error if there are > multiple warnings in a project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-179) Warnings
[
https://jira.codehaus.org/browse/MCOMPILER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCOMPILER-179:
-
Description:
If one error occurs, all warnings are shown as error as well. Up to {{2.3.2}}
this was not the case. Sample output {{2.4}} and higher:
{noformat}
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] bad path element "": no such file or directory
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found : java.util.List
required: java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 4 errors
{noformat}
Sample output {{2.3.2}}:
{noformat}
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found : java.util.List
required: java.util.List
[INFO] 3 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 1 error
[INFO] -
{noformat}
With the current behavior it is extremely hard to spot the error if there are
multiple warnings in a project.
was:
If one error occurs, all warnings are shown as error as well. Up to 2.3.2 this
was not the case. Sample output 2.4 and higher:
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] bad path element "": no such file or directory
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found : java.util.List
required: java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 4 errors
Sample output 2.3.2:
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found : java.util.List
required: java.util.List
[INFO] 3 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 1 error
[INFO] -
With the current behavior it is extremely hard to spot the error if there are
multiple warnings in a project.
> Warnings
> -
>
> Key: MCOMPILER-179
> URL: https://jira.codehaus.org/browse/MCOMPILER-179
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Af
[jira] (MJAVADOC-350) Allow include/exclude at the class level
[ https://jira.codehaus.org/browse/MJAVADOC-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MJAVADOC-350: - Assignee: Benson Margulies > Allow include/exclude at the class level > > > Key: MJAVADOC-350 > URL: https://jira.codehaus.org/browse/MJAVADOC-350 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.8.1 >Reporter: Benson Margulies >Assignee: Benson Margulies > > Javadoc itself (and the ant task, for purposes of comparison) allows > controlling the source files that are processed, one at a time. I suggest the > creation of a standard maven include/exclude setup to give class-at-a-time > control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-242) [shared-utils] improve shared utils featuers and introduce generics where possible
Mark Struberg created MSHARED-242: - Summary: [shared-utils] improve shared utils featuers and introduce generics where possible Key: MSHARED-242 URL: https://jira.codehaus.org/browse/MSHARED-242 Project: Maven Shared Components Issue Type: Bug Reporter: Mark Struberg Lots of the shared-utils stuff is still java-1.3 style. Should get some 1.5++ polishing and new features. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-350) Allow include/exclude at the class level
[ https://jira.codehaus.org/browse/MJAVADOC-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MJAVADOC-350. - Resolution: Fixed Fix Version/s: 2.9 1384611 > Allow include/exclude at the class level > > > Key: MJAVADOC-350 > URL: https://jira.codehaus.org/browse/MJAVADOC-350 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.8.1 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.9 > > > Javadoc itself (and the ant task, for purposes of comparison) allows > controlling the source files that are processed, one at a time. I suggest the > creation of a standard maven include/exclude setup to give class-at-a-time > control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-350) Allow include/exclude at the class level
[ https://jira.codehaus.org/browse/MJAVADOC-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MJAVADOC-350: -- Fix Version/s: (was: 2.9) 2.8.2 > Allow include/exclude at the class level > > > Key: MJAVADOC-350 > URL: https://jira.codehaus.org/browse/MJAVADOC-350 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.8.1 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.8.2 > > > Javadoc itself (and the ant task, for purposes of comparison) allows > controlling the source files that are processed, one at a time. I suggest the > creation of a standard maven include/exclude setup to give class-at-a-time > control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-350) Allow include/exclude at the class level
[ https://jira.codehaus.org/browse/MJAVADOC-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308472#comment-308472 ] fiwnmsf commented on MJAVADOC-350: -- ONLINE STORE : +++ http://l2y.eu/dddqh ++ Best online store Best quality, Best reputation , Best services --- NHL Jersey Woman $ 40 --- NFL Jersey $ 35 --- NBA Jersey $ 34 --- MLB Jersey $ 35 --- Jordan Six Ring_m $ 36 --- Air Yeezy_m $ 45 --- T-Shirt_m $ 25 --- Jacket_m $ 36 --- Hoody_m $ 50 --- Manicure Set $ 20 --- handbag $ 37 --- ugg boot $ 43 --- --- sunglass $ 16 --- bult $ 17 --- +++ http://l2y.eu/dddqh ++ > Allow include/exclude at the class level > > > Key: MJAVADOC-350 > URL: https://jira.codehaus.org/browse/MJAVADOC-350 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.8.1 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.9 > > > Javadoc itself (and the ant task, for purposes of comparison) allows > controlling the source files that are processed, one at a time. I suggest the > creation of a standard maven include/exclude setup to give class-at-a-time > control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-179) Warnings
[
https://jira.codehaus.org/browse/MCOMPILER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308479#comment-308479
]
Kristian Rosenvold commented on MCOMPILER-179:
--
Sorry, that's what I get for fixing a bug when a number of IT's were already
failing. I'll look into it.
> Warnings
> -
>
> Key: MCOMPILER-179
> URL: https://jira.codehaus.org/browse/MCOMPILER-179
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.4, 2.5, 2.5.1
> Environment: Windows7, 64-bit
> VMs, 1.6.0_32 and 1.7.0_04 both 64-bit
>Reporter: Sascha Vogt
>Assignee: Kristian Rosenvold
> Fix For: 2.6
>
>
> If one error occurs, all warnings are shown as error as well. Up to {{2.3.2}}
> this was not the case. Sample output {{2.4}} and higher:
> {noformat}
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] bad path element "": no such file or directory
> C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
> [unchecked] unchecked call to add(E) as a member of the raw type
> java.util.List
> [ERROR]
> C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
> [unchecked] unchecked call to add(E) as a member of the raw type
> java.util.List
> [ERROR]
> C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
> [unchecked] unchecked conversion
> found : java.util.List
> required: java.util.List
> [ERROR]
> C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
> getList() in de.maybebuggy.sample.Main cannot be applied to (int)
> [INFO] 4 errors
> {noformat}
> Sample output {{2.3.2}}:
> {noformat}
> [INFO] -
> [WARNING] COMPILATION WARNING :
> [INFO] -
> [WARNING]
> \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
> [unchecked] unchecked call to add(E) as a member of the raw type
> java.util.List
> [WARNING]
> \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
> [unchecked] unchecked call to add(E) as a member of the raw type
> java.util.List
> [WARNING]
> \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
> [unchecked] unchecked conversion
> found : java.util.List
> required: java.util.List
> [INFO] 3 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
> getList() in de.maybebuggy.sample.Main cannot be applied to (int)
> [INFO] 1 error
> [INFO] -
> {noformat}
> With the current behavior it is extremely hard to spot the error if there are
> multiple warnings in a project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308484#comment-308484 ] Zuhayr Khan commented on MASSEMBLY-343: --- Hi Ahmed, The version I had locally which I patched was maven-assembly-plugin:2.2.1 Hope that helps. BTW.. there's more comment and discussion on it's possibly inclusion on the PLXCOMP-117 issue. I'm more than happy to adjust/re-work these solutions so it can form part of the actual released plugin if there's sufficient interest. Zuhayr > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308484#comment-308484 ] Zuhayr Khan edited comment on MASSEMBLY-343 at 9/14/12 1:31 AM: Hi Ahmed, The version I had locally which I patched was maven-assembly-plugin:2.2.1 Hope that helps. BTW.. there's more comment and discussion on it's possible inclusion on the PLXCOMP-117 issue. I'm more than happy to adjust/re-work these solutions so it can form part of the actual released plugin if there's sufficient interest. Zuhayr was (Author: zuhayrkhan): Hi Ahmed, The version I had locally which I patched was maven-assembly-plugin:2.2.1 Hope that helps. BTW.. there's more comment and discussion on it's possibly inclusion on the PLXCOMP-117 issue. I'm more than happy to adjust/re-work these solutions so it can form part of the actual released plugin if there's sufficient interest. Zuhayr > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
