[jira] (MNG-5323) Add ability to interrupt a build with SUCCESS status from maven plugins.
[ https://jira.codehaus.org/browse/MNG-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Tyurikov reopened MNG-5323: - > Add ability to interrupt a build with SUCCESS status from maven plugins. > > > Key: MNG-5323 > URL: https://jira.codehaus.org/browse/MNG-5323 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: General, Plugin API >Affects Versions: 3.1.x > Environment: any >Reporter: Stanislav Tyurikov >Priority: Critical > Attachments: build_succeed_exception.patch > > > Add ability to successfully finish a build from maven plugin. It can help to > create maven plugins for build optimization. Currently we can interrupt a > build only to fail it (by throwing an exception from the execute method of a > mojo). > This functionality can be easily implemented by adding BuildSuccessException > to the maven core and modifying LifecycleModuleBuilder and > DefaultBuildPluginManager to process this exception and finish the build as > succeed. Any custom maven plugin can throw BuildSuccessException to indicate > the build is OK and no further steps are needed to be executed. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344718#comment-344718
]
Mirko Friedenhagen edited comment on MNG-5604 at 4/11/14 2:27 AM:
--
[~kenneyw], so your approach would be:
* Given two projects A and B where B depends on A.
* Create an enforcer-rule "markAsDeprecated" which only states that the current
project (A) is deprecated and is to be replaced by A2 (I would suggest a
message here). This rule should be included in project A itself, right?
* Create another enforcer-rule "banDeprecated" to be included in project B
which checks the for the existence of the "markAsDeprecated" rule in all it's
dependencies and warns or fails with a message when it finds any such
dependencies.
This could work, however it would violate the spirit of the enforcer-plugin IMO.
was (Author: mfriedenhagen):
[~kenney], so your approach would be:
* Given two projects A and B where B depends on A.
* Create an enforcer-rule "markAsDeprecated" which only states that the current
project (A) is deprecated and is to be replaced by A2 (I would suggest a
message here). This rule should be included in project A itself, right?
* Create another enforcer-rule "banDeprecated" to be included in project B
which checks the for the existence of the "markAsDeprecated" rule in all it's
dependencies and warns or fails with a message when it finds any such
dependencies.
This could work, however it would violate the spirit of the enforcer-plugin IMO.
> make it possible to mark a maven module as deprected
>
>
> Key: MNG-5604
> URL: https://jira.codehaus.org/browse/MNG-5604
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Artifacts and Repositories
>Affects Versions: 3.2.1
>Reporter: Klaus Claszen
>Priority: Minor
> Labels: build, pom.xml
>
> It would be great if it would be possible to mark a maven module as
> 'deprecated'. It would help to document that a module is outdated. The
> information could be used during build processes to show warnings and guide
> the user to a better alternative.
> Maybe it could be a pom enhancement linke this
> {code:xml}
>
> not maintained anymore
>
> foo
> bar
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344718#comment-344718
]
Mirko Friedenhagen commented on MNG-5604:
-
[~kenney], so your approach would be:
* Given two projects A and B where B depends on A.
* Create an enforcer-rule "markAsDeprecated" which only states that the current
project (A) is deprecated and is to be replaced by A2 (I would suggest a
message here). This rule should be included in project A itself, right?
* Create another enforcer-rule "banDeprecated" to be included in project B
which checks the for the existence of the "markAsDeprecated" rule in all it's
dependencies and warns or fails with a message when it finds any such
dependencies.
This could work, however it would violate the spirit of the enforcer-plugin IMO.
> make it possible to mark a maven module as deprected
>
>
> Key: MNG-5604
> URL: https://jira.codehaus.org/browse/MNG-5604
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Artifacts and Repositories
>Affects Versions: 3.2.1
>Reporter: Klaus Claszen
>Priority: Minor
> Labels: build, pom.xml
>
> It would be great if it would be possible to mark a maven module as
> 'deprecated'. It would help to document that a module is outdated. The
> information could be used during build processes to show warnings and guide
> the user to a better alternative.
> Maybe it could be a pom enhancement linke this
> {code:xml}
>
> not maintained anymore
>
> foo
> bar
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-543) japanese filenames cannot be correctly assembled by maven-assembly-plugin
[ https://jira.codehaus.org/browse/MASSEMBLY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344720#comment-344720 ] Markus KARG commented on MASSEMBLY-543: --- Since today the project lead has changed, I'd like to ask the new project lead(s) to discuss this issue and post an answer on the following questions here: * Is some particular person known already planning a solution for this issue? * Is some particular problem known which prevents a solution to this issue? * Is it wanted for third party people to contribute a solution or do you want to provide a solution on your own? Depending on the answers I'd maybe chime in and start working on a solution. But not if another person already is working on this, and not if the problem is already known to be unsolveable. > japanese filenames cannot be correctly assembled by maven-assembly-plugin > - > > Key: MASSEMBLY-543 > URL: https://jira.codehaus.org/browse/MASSEMBLY-543 > Project: Maven Assembly Plugin > Issue Type: Bug > Environment: Windows XP SP3 Japanese, Eclipse Ganymede 3.4.2 >Reporter: Eros Sy > Attachments: 新規テキスト > ドキュメント.xml > > > I am successfully created the distribution zip file but when I add a file > which is in Japanese character file name, it is include in the zip file but > the file name was garbled. > How to reproduce: add a file to be included in the distribution which file > name is in Japanese character. i will provide a sample file. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344721#comment-344721 ] john ten Den commented on MRELEASE-875: --- First the requested debug logging m-release-p-2.5 + Git 1.9.0 1) pom.xml in Git root : (working fine) == [INFO] [INFO] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] [INFO] [INFO] Total time: 0.540 s [INFO] [INFO] Finished at: 2014-04-11T09:24:09+01:00 [INFO] [INFO] Final Memory: 5M/123M [INFO] [INFO] [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add -- pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] M pom.xml [DEBUG] ?? pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup [DEBUG] ?? release.properties [WARNING] Ignoring unrecognized line: ?? release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw900gn/T/maven-scm-1011576472.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push g...@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Tagging release with the label johntest-0.0.2... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier; files = [] [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw900gn/T/maven-scm-1340971298.commit johntest-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push g...@git.trivento.nl:john/bier.git refs/tags/johntest-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git ls-files [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] indirectory/pom.xml [DEBUG] pom.xml [INFO] Transforming 'johntest'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add -- pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] M pom.xml [DEBUG] ?? pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup [DEBUG] ?? release.properties [WARNING] Ignoring unrecognized line: ?? release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw900gn/T/maven-scm-364960822.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push g...@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Release preparation complete. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 13.402 s [INFO] Finished at: 2014-04-11T09:24:13+01:00 [INFO] Final Memory: 11M/222M [INFO] 2) pom.xml not in Git root (but in directory indirectory:) (added >>> comment where i expected other behaviour) =
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344724#comment-344724 ] john ten Den commented on MRELEASE-875: --- I retested m-release-p2.4.2 with git 1.7.0 and its working well. Added trace of the indirectory/pom.xml below. I see that the git status 1.7.0 is returning the filelist relatieve to the path running from in this test case "indirectory") [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] # On branch master [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits. [DEBUG] # [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD ..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add ..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties where the 1.9.0 is returning the filefiles relative to the git root: [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] M indirectory/pom.xml [DEBUG] ?? indirectory/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup [DEBUG] ?? indirectory/release.properties [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties trace : m-release-p2.4.2 with git 1.7.0 == [INFO] [INFO] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] [INFO] [INFO] Total time: 0.534 s [INFO] [INFO] Finished at: 2014-04-11T09:42:37+01:00 [INFO] [INFO] Final Memory: 6M/156M [INFO] [INFO] [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add -- pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] # On branch master [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits. [DEBUG] # [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD ..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add ..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw900gn/T/maven-scm-1159491710.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push g...@git.trivento.nl:john/bier.git master:master [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Tagging release with the label johntest2-0.0.3... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier/indirectory; files = [] [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw900gn/T/maven-scm-1210701058.commit johntest2-0.0.3 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push g...@git.trivento.nl:john/bier.git johntest2-0.0.3 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git ls-files [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] pom.xml [INFO] Transforming 'johntest'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add -- pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin
[jira] (MASSEMBLY-543) japanese filenames cannot be correctly assembled by maven-assembly-plugin
[
https://jira.codehaus.org/browse/MASSEMBLY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344725#comment-344725
]
Dmitry Pelevin commented on MASSEMBLY-543:
--
Markus, please try to specify encoding for assembly plugin in the following way
(also do not forget about "-Dfile.encoding=UTF-8"):
{code:xml}
maven-assembly-plugin
2.4
make-assembly
package
single
src/main/assembly/package-sources.xml
src/main/assembly/package.xml
CP866
org.codehaus.plexus
plexus-archiver
2.4.4
org.codehaus.plexus
plexus-component-api
{code}
Let me explain why this is required. ZIP is old enought format and initialli it
did not know anything about Unicode encodings. Later ZIP specification was
extended and support for Unicode and LEF flag was added. The problem is that
not all software understand LEF flag. I can surprise you Windows exlorer still
do not understand LEF flag. As I know - there is no problems with LEF at linux
and MacOS. Windows is still read ZIP assuming that it contain file names
encoded with non-Unicode encoding, using MSDOS encoding corresponding to user
locale. So if I want to be able to see cyrilyc file names in ZIP files at
Windows I need to pack ZIP using
[CP866|https://en.wikipedia.org/wiki/Code_page_866] encoding. Not sure exactly,
but I think you need to use [CP850|https://en.wikipedia.org/wiki/Code_page_850]
encoding to be able to see file names with symbols from german abc.
In the case if you set only "-Dfile.encoding=UTF-8" flag without specifying
encoding as in my example - you will be able to see "German umlauts" using
archiver which understand LEF flag [7-Zip|http://7-zip.org/] is one of such
archivers.
I think this will solve all your problems with encoding as it did for me.
> japanese filenames cannot be correctly assembled by maven-assembly-plugin
> -
>
> Key: MASSEMBLY-543
> URL: https://jira.codehaus.org/browse/MASSEMBLY-543
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Environment: Windows XP SP3 Japanese, Eclipse Ganymede 3.4.2
>Reporter: Eros Sy
> Attachments: 新規テキスト
> ドキュメント.xml
>
>
> I am successfully created the distribution zip file but when I add a file
> which is in Japanese character file name, it is include in the zip file but
> the file name was garbled.
> How to reproduce: add a file to be included in the distribution which file
> name is in Japanese character. i will provide a sample file.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-674) escapeString using \ does not work correctly
[
https://jira.codehaus.org/browse/MASSEMBLY-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-674:
--
Description:
Using \ does not correctly when dealing with
case where previous text is also a \.
attached pom,test and assembly.xml show what happens. The follwoing scenario is
currently fail: (varible=Hello)
{code}
C:\path\\${variable}
{code}
converted to
{code}
C:\path\\Hello
{code}
I would of expected:
{code}
C:\path\${variable}
{code}
The following does work but is not exactly as required as it means you get get
two \'s
{code}
C:\path\\\${variable}
{code}
converted to
{code}
C:\path\\${variable}
{code}
was:
Using \ does not correctly when dealing with
case where previous text is also a \.
attached pom,test and assembly.xml show what happens. The follwoing scenario is
currently fail: (varible=Hello)
C:\path\\${variable} converted to C:\path\\Hello
I would of expected: C:\path\${variable}
The following does work but is not exactly as required as it means you get get
two \'s
C:\path\\\${variable} converted to C:\path\\${variable}
I think we need to add another option for filtering, like this one:
http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#escapeWindowsPaths
> escapeString using \ does not work correctly
>
>
> Key: MASSEMBLY-674
> URL: https://jira.codehaus.org/browse/MASSEMBLY-674
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Components: filtering
>Affects Versions: 2.4
>Reporter: Iain Coulter
>Priority: Minor
> Fix For: 2.5
>
> Attachments: escapeStringBug.zip
>
>
> Using \ does not correctly when dealing with
> case where previous text is also a \.
> attached pom,test and assembly.xml show what happens. The follwoing scenario
> is currently fail: (varible=Hello)
> {code}
> C:\path\\${variable}
> {code}
> converted to
> {code}
> C:\path\\Hello
> {code}
> I would of expected:
> {code}
> C:\path\${variable}
> {code}
> The following does work but is not exactly as required as it means you get
> get two \'s
> {code}
> C:\path\\\${variable}
> {code}
> converted to
> {code}
> C:\path\\${variable}
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344763#comment-344763
]
Kenney Westerhof commented on MNG-5604:
---
Hi Mirko,
That's pretty much it, although I would not declare A as deprecated using a
rule, since it is not applicable as a rule to project A. I'd make a split in
the to distinguish rules from declarations, for example:
A's pom.xml:
{code:xml}
maven-enforcer-plugin
maven-enforcer-plugin
make it possible to mark a maven module as deprected
>
>
> Key: MNG-5604
> URL: https://jira.codehaus.org/browse/MNG-5604
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Artifacts and Repositories
>Affects Versions: 3.2.1
>Reporter: Klaus Claszen
>Priority: Minor
> Labels: build, pom.xml
>
> It would be great if it would be possible to mark a maven module as
> 'deprecated'. It would help to document that a module is outdated. The
> information could be used during build processes to show warnings and guide
> the user to a better alternative.
> Maybe it could be a pom enhancement linke this
> {code:xml}
>
> not maintained anymore
>
> foo
> bar
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5616) when multithreading is activated, log level FINE is wrongly printed
mohamed chenouili created MNG-5616: -- Summary: when multithreading is activated, log level FINE is wrongly printed Key: MNG-5616 URL: https://jira.codehaus.org/browse/MNG-5616 Project: Maven 2 & 3 Issue Type: Bug Components: Logging Affects Versions: 3.1.1 Environment: Unix, RedHat Reporter: mohamed chenouili Hello, In maven 3, I encountered that there are some additionnal log, when a multi-module project is builded with multi-thread. Maven keeps printing the http header of all of the download request for dependencies. I did not alter the configuration log in simplelogger.properties and I use a log4j in many of my projects. Could you tell me if there is another way to overwrite the log level of MAVEN ? Regards, -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5617) unreadable log in multi thread compilation
mohamed chenouili created MNG-5617: -- Summary: unreadable log in multi thread compilation Key: MNG-5617 URL: https://jira.codehaus.org/browse/MNG-5617 Project: Maven 2 & 3 Issue Type: Bug Components: Logging Affects Versions: 3.1.1 Environment: Unix, RedHat Reporter: mohamed chenouili Priority: Critical when I try to compile multi-module project (-T 8), the log of each project is not printed sequentially, all logs of the compilation is being printed as soon as it is thrown by the compiler. This makes logs unreadble. Am I the only one in this case ? I have seen that a solution was implemented but not used in Maven source code (ThreadOutputMuxer.java). Is there a solution for this issue ? I should not be the only one. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
Kenney Westerhof created MASSEMBLY-696:
--
Summary: Internal Regexp Error with Windows Paths
Key: MASSEMBLY-696
URL: https://jira.codehaus.org/browse/MASSEMBLY-696
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5
Environment: Windows 7
maven-assembly-plugin trunk@e785abb
Reporter: Kenney Westerhof
On windows the Assembly plugin shows this error:
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
(default-cli) on project myproject: Execution default-cli of goal
org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
Unexpected internal error near index 1
\
^
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
near index 1
\
^
at java.util.regex.Pattern.error(Pattern.java:1924)
at java.util.regex.Pattern.compile(Pattern.java:1671)
at java.util.regex.Pattern.(Pattern.java:1337)
at java.util.regex.Pattern.compile(Pattern.java:1022)
at java.lang.String.split(String.java:2313)
at java.lang.String.split(String.java:2355)
at
org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-696:
---
Patch Submitted: Yes
Attachment: MASSEMBLY-696.patch
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-696.patch
>
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-696:
---
Attachment: MASSEMBLY-696.patch
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-696.patch, MASSEMBLY-696.patch
>
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-696:
---
Attachment: (was: MASSEMBLY-696.patch)
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-696.patch
>
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-696:
---
Attachment: (was: MASSEMBLY-696.patch)
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-696) Internal Regexp Error with Windows Paths
[
https://jira.codehaus.org/browse/MASSEMBLY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-696:
---
Attachment: MASSEMBLY-696.patch
> Internal Regexp Error with Windows Paths
>
>
> Key: MASSEMBLY-696
> URL: https://jira.codehaus.org/browse/MASSEMBLY-696
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
> maven-assembly-plugin trunk@e785abb
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-696.patch
>
>
> On windows the Assembly plugin shows this error:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single
> (default-cli) on project myproject: Execution default-cli of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5-SNAPSHOT:single failed:
> Unexpected internal error near index 1
> \
> ^
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>
> Caused by: java.util.regex.PatternSyntaxException: Unexpected internal error
> near index 1
> \
> ^
> at java.util.regex.Pattern.error(Pattern.java:1924)
> at java.util.regex.Pattern.compile(Pattern.java:1671)
> at java.util.regex.Pattern.(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at java.lang.String.split(String.java:2313)
> at java.lang.String.split(String.java:2355)
> at
> org.apache.maven.plugin.assembly.utils.AssemblyFormatUtils.fixRelativeRefs(AssemblyFormatUtils.java:509)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-697) Repository assembly does not include project jar
Kenney Westerhof created MASSEMBLY-697: -- Summary: Repository assembly does not include project jar Key: MASSEMBLY-697 URL: https://jira.codehaus.org/browse/MASSEMBLY-697 Project: Maven Assembly Plugin Issue Type: Bug Affects Versions: 2.4, 2.5 Environment: Windows / Any Maven 3.2.1 Reporter: Kenney Westerhof The example on http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html does not produce the advertised results, as it copies the pom into the repository archive, but omits the project .jar. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-697) Repository assembly does not include project jar
[
https://jira.codehaus.org/browse/MASSEMBLY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenney Westerhof updated MASSEMBLY-697:
---
Attachment: MASSEMBLY-697.tar.gz
The attachment contains a simple project (pom, assembly descriptor and a
placeholder Java class) that illustrates the bug. Run:
{code}
mvn package
unzip -l target/artifactId-1-SNAPSHOT-repository.jar
{code}
to see that the project .jar is missing.
> Repository assembly does not include project jar
>
>
> Key: MASSEMBLY-697
> URL: https://jira.codehaus.org/browse/MASSEMBLY-697
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.4, 2.5
> Environment: Windows / Any
> Maven 3.2.1
>Reporter: Kenney Westerhof
> Attachments: MASSEMBLY-697.tar.gz
>
>
> The example on
> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html
> does not produce the advertised results, as it copies the pom into the
> repository archive, but omits the project .jar.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344773#comment-344773
]
Robert Scholte commented on MRELEASE-875:
-
please surround the output with \{noformat\} tags to make it easier to read.
Maybe I'm a bad reader, but I only see succeeding builds...
> release:prepare does not commit pom.xml if not in the git root
> --
>
> Key: MRELEASE-875
> URL: https://jira.codehaus.org/browse/MRELEASE-875
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.5
> Environment: git 1.9.0
>Reporter: john ten Den
>
> When the project pom.xml is not in the Git project root (f.e. in the "src"
> directory) the pom.xml not committed and pushed (before tagging)
> Commit of the pom.xml during release:prepare works fine if it is in the /
> (root) of the git repository
> Using the pom.xml in a subdirectory worked well with version 2.4.2 using git
> 1.7.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344780#comment-344780
]
Paul Benedict commented on MNG-5604:
Perhaps it is better to open up a new ticket at
http://jira.codehaus.org/browse/MENFORCER and keep this open in case Maven core
gets its own solution.
> make it possible to mark a maven module as deprected
>
>
> Key: MNG-5604
> URL: https://jira.codehaus.org/browse/MNG-5604
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Artifacts and Repositories
>Affects Versions: 3.2.1
>Reporter: Klaus Claszen
>Priority: Minor
> Labels: build, pom.xml
>
> It would be great if it would be possible to mark a maven module as
> 'deprecated'. It would help to document that a module is outdated. The
> information could be used during build processes to show warnings and guide
> the user to a better alternative.
> Maybe it could be a pom enhancement linke this
> {code:xml}
>
> not maintained anymore
>
> foo
> bar
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEP-439) maven-dependency-plugin not compatible with Java 8
[
https://jira.codehaus.org/browse/MDEP-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344782#comment-344782
]
Steven Schlansker commented on MDEP-439:
Heads up, you also need a patch like this, otherwise you get exceptions like:
Caused by: java.lang.IllegalArgumentException: INVOKESPECIAL/STATIC on
interfaces require ASM 5
at org.objectweb.asm.MethodVisitor.visitMethodInsn(Unknown Source)
at org.objectweb.asm.ClassReader.a(Unknown Source)
at org.objectweb.asm.ClassReader.b(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass(DependencyClassFileVisitor.java:70)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass(ClassFileVisitorUtils.java:154)
Index:
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultAnnotationVisitor.java
===
---
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultAnnotationVisitor.java
(revision 1586727)
+++
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultAnnotationVisitor.java
(working copy)
@@ -36,7 +36,7 @@
public DefaultAnnotationVisitor(ResultCollector resultCollector)
{
-super(Opcodes.ASM4);
+super(Opcodes.ASM5);
this.resultCollector = resultCollector;
}
Index:
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultClassVisitor.java
===
---
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultClassVisitor.java
(revision 1586727)
+++
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultClassVisitor.java
(working copy)
@@ -49,7 +49,7 @@
public DefaultClassVisitor(SignatureVisitor signatureVisitor,
AnnotationVisitor annotationVisitor, FieldVisitor fieldVisitor, MethodVisitor
methodVisitor, ResultCollector resultCollector)
{
-super(Opcodes.ASM4);
+super(Opcodes.ASM5);
this.signatureVisitor = signatureVisitor;
this.annotationVisitor = annotationVisitor;
this.fieldVisitor = fieldVisitor;
Index:
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultFieldVisitor.java
===
---
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultFieldVisitor.java
(revision 1586727)
+++
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultFieldVisitor.java
(working copy)
@@ -37,7 +37,7 @@
public DefaultFieldVisitor(AnnotationVisitor annotationVisitor,
ResultCollector resultCollector)
{
-super(Opcodes.ASM4);
+super(Opcodes.ASM5);
this.annotationVisitor = annotationVisitor;
this.resultCollector = resultCollector;
}
Index:
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultMethodVisitor.java
===
---
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultMethodVisitor.java
(revision 1586727)
+++
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultMethodVisitor.java
(working copy)
@@ -39,7 +39,7 @@
public DefaultMethodVisitor(AnnotationVisitor annotationVisitor,
SignatureVisitor signatureVisitor, ResultCollector resultCollector)
{
-super(Opcodes.ASM4);
+super(Opcodes.ASM5);
this.annotationVisitor = annotationVisitor;
this.signatureVisitor = signatureVisitor;
this.resultCollector = resultCollector;
Index:
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultSignatureVisitor.java
===
---
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultSignatureVisitor.java
(revision 1586727)
+++
src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultSignatureVisitor.java
(working copy)
@@ -38,7 +38,7 @@
public DefaultSignatureVisitor(ResultCollector resultCollector)
{
-super(Opcodes.ASM4);
+super(Opcodes.ASM5);
this.resultCollector = resultCollector;
}
> maven-dependency-plugin not compatible with Java 8
> --
>
> Key: MDEP-439
> URL: https://jira.codehaus.org/browse/MDEP-439
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.8
> Environment: Java 8
>Reporter: Steven Schlansker
>Assignee: Mirko Friedenhagen
>Priority: Critical
>
> m
[jira] (MSHARED-327) maven-dependency-analyzer not compatible with Java 8
[ https://jira.codehaus.org/browse/MSHARED-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen reopened MSHARED-327: jar still uses ASM4, which is not able to handle JDK 8 constructs, see linked MDEP-439 > maven-dependency-analyzer not compatible with Java 8 > > > Key: MSHARED-327 > URL: https://jira.codehaus.org/browse/MSHARED-327 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-dependency-analyzer >Affects Versions: maven-dependency-analyzer-1.4 >Reporter: Mirko Friedenhagen >Assignee: Mirko Friedenhagen > Fix For: maven-dependency-analyzer-1.5 > > > Java 8 needs a newer version of ASM as stated in MDEP-439. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
