[jira] (MASSEMBLY-343) add symbolic links managment (java7+ only supported)
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355689#comment-355689 ] Daniel Seidewitz commented on MASSEMBLY-343: Is the patch really included in release 2.5? Because I just tried to create an assembly with in the descriptor and it doesn't recognize the element. Also I looked at the source for 2.5 and it seems the patch was not included. > add symbolic links managment (java7+ only supported) > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles >Assignee: Kristian Rosenvold > Fix For: 2.5 > > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-343) add symbolic links managment (java7+ only supported)
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355696#comment-355696 ] Kristian Rosenvold commented on MASSEMBLY-343: -- No, this patch was not included. But symlinks existing on the file system will be added to the archive as one would expect as parts of filesets or similar. > add symbolic links managment (java7+ only supported) > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles >Assignee: Kristian Rosenvold > Fix For: 2.5 > > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-343) add symbolic links managment (java7+ only supported)
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355698#comment-355698 ] Kristian Rosenvold commented on MASSEMBLY-343: -- I suppose it might be viable to add a "symlinkTarget" attribute to the "file" element to make a symlink in the descriptor > add symbolic links managment (java7+ only supported) > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles >Assignee: Kristian Rosenvold > Fix For: 2.5 > > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization header
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned WAGON-416:
--
Assignee: Olivier Lamy
> Lightweight HTTP Wagon doesn't set Proxy-Authorization header
> -
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>Assignee: Olivier Lamy
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization header
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated WAGON-416:
---
Fix Version/s: 2.8
> Lightweight HTTP Wagon doesn't set Proxy-Authorization header
> -
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>Assignee: Olivier Lamy
> Fix For: 2.8
>
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization header
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed WAGON-416.
--
Resolution: Fixed
pull request merged.
Thanks!
> Lightweight HTTP Wagon doesn't set Proxy-Authorization header
> -
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>Assignee: Olivier Lamy
> Fix For: 2.8
>
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-197) another NPE introduced by me :(
[ https://jira.codehaus.org/browse/WAGON-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-197. -- > another NPE introduced by me :( > --- > > Key: WAGON-197 > URL: https://jira.codehaus.org/browse/WAGON-197 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Reporter: Juan F. Codagnone >Assignee: Trygve Laugstøl > Fix For: 1.0-alpha-5 > > Attachments: WAGON-SSH-14.diff > > > In WAGONSSH-8 i introduced a NPE :(. > I know i saw it at that moment, but i think i did the patch from the wrong > tree. All the odd things happens on my first patch, always! -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-202) sftp: implement method getIfNewer()
[ https://jira.codehaus.org/browse/WAGON-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-202. -- > sftp: implement method getIfNewer() > --- > > Key: WAGON-202 > URL: https://jira.codehaus.org/browse/WAGON-202 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-ssh >Reporter: Juan F. Codagnone >Assignee: Trygve Laugstøl > Fix For: 1.0-alpha-5 > > Attachments: WAGON-SSH-11.diff > > > implement Wagon::getIfNewer to let the wagon-ssh can be used from maven-1. > (i will file the maven-1issue later) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-98) Use connection pooling in the http wagon
[ https://jira.codehaus.org/browse/WAGON-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-98. - > Use connection pooling in the http wagon > > > Key: WAGON-98 > URL: https://jira.codehaus.org/browse/WAGON-98 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http >Reporter: Don Brown > Attachments: connection-pooling.diff > > > The http wagon should take advantage of the connection pooling feature of > commons-httpclient. Currently, the multithreaded connection manager is used, > which is right, but instantiated per request, which defeats the purpose. It > needs to be created and stored statically, since multiple instances will be > created in Maven 2. The patch also updates the httpclient version to 3.1 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-122) An exception is throwed when the http response code is 201
[
https://jira.codehaus.org/browse/WAGON-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed WAGON-122.
--
> An exception is throwed when the http response code is 201
> --
>
> Key: WAGON-122
> URL: https://jira.codehaus.org/browse/WAGON-122
> Project: Maven Wagon
> Issue Type: Bug
>Reporter: Alexandre Poitras
>Assignee: Joakim Erdfelt
>Priority: Minor
>
> The put method of the LightweightHttpWagon class throw an exception whener
> the http response code is 201. The 201 code indicate the PUT method has
> completed successfully in a WebDav environment.
> The problem comes from here :
> if ( putConnection.getResponseCode() != HttpURLConnection.HTTP_OK
> )
> {
> throw new TransferFailedException(
> "Unable to transfer file. HttpURLConnection returned the
> response code: " +
> putConnection.getResponseCode() );
> }
>
> An exception is thrown whenever the Http code is different from 200 wich is
> not good.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-258) Update to post-5.0 checkstyle when the plugin is available
[ https://jira.codehaus.org/browse/MCHECKSTYLE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MCOBERTURA-186 to MCHECKSTYLE-258: Affects Version/s: (was: 2.5) (was: 2.4) 2.4 2.5 Key: MCHECKSTYLE-258 (was: MCOBERTURA-186) Project: Maven Checkstyle Plugin (was: Mojo's Cobertura Maven Plugin) > Update to post-5.0 checkstyle when the plugin is available > -- > > Key: MCHECKSTYLE-258 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-258 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 2.5, 2.4 >Reporter: Benson Margulies > > Once the maven-checkstyle-plugin releases a version with a newer checkstyle > that 5.0, use it and fix the rules to stop exploding on @goal. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-728) Assembly plugin >= 2.5 thinks my group ID is too big
[
https://jira.codehaus.org/browse/MASSEMBLY-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355747#comment-355747
]
Andrew Todd commented on MASSEMBLY-728:
---
Much appreciated, it does work when I change the mode. Thanks for continuing to
improve the assembly-plugin.
Off the top of your head, do you know if there are any disadvantages to
{{posix}} mode? I noticed that {{posix_warn}} is also listed in the docs. The
only documentation that I could find was in another codebase, which seems to
indicate it's not a problem:
https://github.com/sonatype/plexus-archiver/blob/master/src/main/java/org/codehaus/plexus/archiver/tar/TarArchiver.java#L93
Also, I assume that GNU tar can open POSIX tar archives -- again, my copy of
GNU tar seems to be fine with my new POSIX archive, just wanted to double-check.
> Assembly plugin >= 2.5 thinks my group ID is too big
>
>
> Key: MASSEMBLY-728
> URL: https://jira.codehaus.org/browse/MASSEMBLY-728
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrew Todd
>
> My OS X user's primary group ID is quite large, around 110075129.
> Up until assembly 2.4.1, I have had no troubles. However, in 2.5, I get this
> error when trying to create an assembly:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5:single
> (assemble-command-line) on project crypto-monster: Execution
> assemble-command-line of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5:single failed: group id
> '110075129' is too big ( > 2097151 ) -> [Help 1]
> I am using JDK 7 to build. Have not tested with 8.
> I have noticed that the error seems to be specific to assembly of a .tar.gz
> artifact. Assembling a .zip file does not cause this error.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-191) Update to PMD 5.2.1
[ https://jira.codehaus.org/browse/MPMD-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355749#comment-355749 ] Andreas Dangel commented on MPMD-191: - Thanks again! And sorry for not mentioning the PR earlier. Let me know, if I can help you with anything. > Update to PMD 5.2.1 > --- > > Key: MPMD-191 > URL: https://jira.codehaus.org/browse/MPMD-191 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Andreas Dangel >Assignee: Mirko Friedenhagen > Fix For: 3.3 > > > Changes in PMD: > * http://pmd.sourceforge.net/pmd-5.2.1/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.2.0/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.1.3/changelog.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-4667) Maven 2.2.1 XML parser fails to parse a UTF-8 POM that begins with a BOM
[
https://jira.codehaus.org/browse/MNG-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355750#comment-355750
]
Matthias Stevens commented on MNG-4667:
---
This still affects Maven 3.2.3. This can't be hard to fix I would think...
> Maven 2.2.1 XML parser fails to parse a UTF-8 POM that begins with a BOM
>
>
> Key: MNG-4667
> URL: https://jira.codehaus.org/browse/MNG-4667
> Project: Maven
> Issue Type: Bug
> Components: POM::Encoding
>Affects Versions: 2.2.1
>Reporter: Maria Catherine Tan
> Attachments: MNG-4667.patch, MNG-4667-updated.patch,
> MNG-4667-with-encoding.patch, pom.xml
>
>
> I've seen a lot of issues related to this that were closed because they're a
> duplicate of MNG-2254 but I think the fix for MNG-2254 doesn't fix this issue.
> I'm using maven 2.2.1 and the build failed when the UTF-8 POM begins with a
> BOM.
> Here's the log when running clean install
> {noformat}
> Reason: Parse error reading POM. Reason: only whitespace content allowed
> before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)
> for project unknown at /home/marica/quick/pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
> Reason: only whitespace content allowed before start tag and not \uef
> (position: START_DOCUMENT seen \uef... @1:1) for project unknown at
> /home/marica/quick/pom.xml
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error
> reading POM. Reason: only whitespace content allowed before start tag and not
> \uef (position: START_DOCUMENT seen \uef... @1:1) for project unknown at
> /home/marica/quick/pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1610)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
> ... 12 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: only
> whitespace content allowed before start tag and not \uef (position:
> START_DOCUMENT seen \uef... @1:1)
> at
> hidden.org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1528)
> at
> hidden.org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1407)
> at
> hidden.org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1105)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3911)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1606)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5721) Possible NullPointerException in org.apache.maven.repository. MetadataResolutionResult
Martin Schäf created MNG-5721:
-
Summary: Possible NullPointerException in
org.apache.maven.repository. MetadataResolutionResult
Key: MNG-5721
URL: https://jira.codehaus.org/browse/MNG-5721
Project: Maven
Issue Type: Bug
Components: General
Reporter: Martin Schäf
Priority: Minor
Attachments: MetadataResolutionResult.java
In line 235 of org.apache.maven.repository.MetadataResolutionResult
the function initList is used in the wrong way. Should be:
public MetadataResolutionResult addError( Exception e )
{
exceptions = initList( exceptions );
exceptions.add( e );
return this;
}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-191) Update to PMD 5.2.1
[ https://jira.codehaus.org/browse/MPMD-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen closed MPMD-191. --- Resolution: Fixed Included your changes, see http://svn.apache.org/viewvc?view=revision&revision=1637198 Thanks. > Update to PMD 5.2.1 > --- > > Key: MPMD-191 > URL: https://jira.codehaus.org/browse/MPMD-191 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Andreas Dangel >Assignee: Mirko Friedenhagen > Fix For: 3.3 > > > Changes in PMD: > * http://pmd.sourceforge.net/pmd-5.2.1/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.2.0/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.1.3/changelog.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-191) Update to PMD 5.2.1
[ https://jira.codehaus.org/browse/MPMD-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355767#comment-355767 ] Mirko Friedenhagen commented on MPMD-191: - Update documentation: http://svn.apache.org/viewvc?view=revision&revision=1637209 > Update to PMD 5.2.1 > --- > > Key: MPMD-191 > URL: https://jira.codehaus.org/browse/MPMD-191 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Andreas Dangel >Assignee: Mirko Friedenhagen > Fix For: 3.3 > > > Changes in PMD: > * http://pmd.sourceforge.net/pmd-5.2.1/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.2.0/overview/changelog.html > * http://pmd.sourceforge.net/pmd-5.1.3/changelog.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-893) Put the tag in a property in :prepare
Benson Margulies created MRELEASE-893: - Summary: Put the tag in a property in :prepare Key: MRELEASE-893 URL: https://jira.codehaus.org/browse/MRELEASE-893 Project: Maven Release Plugin Issue Type: New Feature Reporter: Benson Margulies Imagine another plugin that runs as part of the lifecycle after release:prepare and which needs to know the scm tag name. It could use maven-scm to try to guess what's most recent, but wouldn't it be easier if it :prepare just set a property to the tag name that a subsequent plugin execution could read? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-343) add symbolic links managment (java7+ only supported)
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355769#comment-355769 ] Kristian Rosenvold commented on MASSEMBLY-343: -- I've been thinking a little more about this, and there is definitely room for some way to create a symlink in the descriptor. I'll see if your patch is still fresh and try to find out what you've been thinking. > add symbolic links managment (java7+ only supported) > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles >Assignee: Kristian Rosenvold > Fix For: 2.5 > > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-728) Assembly plugin >= 2.5 thinks my group ID is too big
[ https://jira.codehaus.org/browse/MASSEMBLY-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355773#comment-355773 ] Kristian Rosenvold commented on MASSEMBLY-728: -- I dont really know any disatvantages of posix tar,but I suppose some old platforms may not support it. I'm sure google will tell us :) > Assembly plugin >= 2.5 thinks my group ID is too big > > > Key: MASSEMBLY-728 > URL: https://jira.codehaus.org/browse/MASSEMBLY-728 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Todd > > My OS X user's primary group ID is quite large, around 110075129. > Up until assembly 2.4.1, I have had no troubles. However, in 2.5, I get this > error when trying to create an assembly: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.5:single > (assemble-command-line) on project crypto-monster: Execution > assemble-command-line of goal > org.apache.maven.plugins:maven-assembly-plugin:2.5:single failed: group id > '110075129' is too big ( > 2097151 ) -> [Help 1] > I am using JDK 7 to build. Have not tested with 8. > I have noticed that the error seems to be specific to assembly of a .tar.gz > artifact. Assembling a .zip file does not cause this error. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error
[
https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355774#comment-355774
]
Tibor Digana commented on SUREFIRE-1112:
Hi Andreas,
I have found the commit which caused this issue
https://github.com/apache/maven-surefire/commit/fefaae7f0534a59f52c046a64c96987e8561dd48
> Remove uneccessary newlines in console output for test results with no error
>
>
> Key: SUREFIRE-1112
> URL: https://jira.codehaus.org/browse/SUREFIRE-1112
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Andreas Gudian
>Assignee: Andreas Gudian
>
> {code}
> Results :
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'm pretty sure it has something to do with the extended test result handling
> / printing for the flaky tests feature.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-729) lineEnding ignored when file is not filtered
Tony Jewell created MASSEMBLY-729:
-
Summary: lineEnding ignored when file is not filtered
Key: MASSEMBLY-729
URL: https://jira.codehaus.org/browse/MASSEMBLY-729
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Tony Jewell
Attachments:
maven-assembly-plugin-2.5-lineEnding-ignored-when-not-filtering.zip
lineEnding=unix is ignored when filtering is not enabled in FileSet.
See attached sample project.
unfiltered.properties - has original (DOS) line endings
filtered.properties - has unix file endings - original had DOS line endings
*NOTE* the pom.xml maven-assembly-plugin:2.5 with the following dependency
overrides:
{code}
org.codehaus.plexus
plexus-archiver
2.8.2
org.codehaus.plexus
plexus-io
2.3.3
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-729) lineEnding ignored when file is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Jewell updated MASSEMBLY-729:
--
Description:
lineEnding=unix is ignored when filtering is not enabled in FileSet.
See attached sample project.
unfiltered.properties - has original (DOS) line endings
filtered.properties - has unix file endings - original had DOS line endings
*NOTE* the pom.xml maven-assembly-plugin:2.5 with the following dependency
overrides:
{code}
org.codehaus.plexus
plexus-archiver
2.8.2
org.codehaus.plexus
plexus-io
2.3.3
{code}
was:
lineEnding=unix is ignored when filtering is not enabled in FileSet.
See attached sample project.
unfiltered.properties - has original (DOS) line endings
filtered.properties - has unix file endings - original had DOS line endings
*NOTE* the pom.xml maven-assembly-plugin:2.5 with the following dependency
overrides:
{code}
org.codehaus.plexus
plexus-archiver
2.8.2
org.codehaus.plexus
plexus-io
2.3.3
{code}
> lineEnding ignored when file is not filtered
>
>
> Key: MASSEMBLY-729
> URL: https://jira.codehaus.org/browse/MASSEMBLY-729
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Tony Jewell
> Attachments:
> maven-assembly-plugin-2.5-lineEnding-ignored-when-not-filtering.zip
>
>
> lineEnding=unix is ignored when filtering is not enabled in FileSet.
> See attached sample project.
> unfiltered.properties - has original (DOS) line endings
> filtered.properties - has unix file endings - original had DOS line endings
> *NOTE* the pom.xml maven-assembly-plugin:2.5 with the following dependency
> overrides:
> {code}
>
> org.codehaus.plexus
> plexus-archiver
> 2.8.2
>
>
> org.codehaus.plexus
> plexus-io
> 2.3.3
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-400) Wagon 1.0 Fail to build from source with Java7
[ https://jira.codehaus.org/browse/WAGON-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed WAGON-400. -- Resolution: Cannot Reproduce Assignee: Olivier Lamy Cannot reproduce with current version > Wagon 1.0 Fail to build from source with Java7 > -- > > Key: WAGON-400 > URL: https://jira.codehaus.org/browse/WAGON-400 > Project: Maven Wagon > Issue Type: Bug >Affects Versions: 1.0 > Environment: debian 7.0 >Reporter: Shuxiong Ye >Assignee: Olivier Lamy > Attachments: wagon-openjdk-7-log > > > I am build debian package of wagon 1.0, using Java7, but fail, for it can not > pass some tests. > Build log: > --- > T E S T S > --- > Running org.apache.maven.wagon.providers.http.HttpWagonTest > Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.926 sec > Running org.apache.maven.wagon.providers.http.HttpsWagonTest > Tests run: 42, Failures: 0, Errors: 19, Skipped: 0, Time elapsed: 4.984 sec > <<< FAILURE! > Running org.apache.maven.wagon.providers.http.HttpWagonTimeoutTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.867 sec > Results : > Tests in error: > testStreamingWagon(org.apache.maven.wagon.providers.http.HttpsWagonTest): > > testWagonGetIfNewerToStreamIsNewer(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonGetIfNewerToStreamIsOlder(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonGetIfNewerToStreamIsSame(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testFailedGetIfNewerToStream(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testFailedGetToStream(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > testWagon(org.apache.maven.wagon.providers.http.HttpsWagonTest): Address > already in use > > testWagonGetIfNewerIsNewer(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonGetIfNewerIsOlder(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonGetIfNewerIsSame(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonPutDirectory(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonPutDirectoryDeepDestination(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonPutDirectoryWhenDirectoryAlreadyExists(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonPutDirectoryForDot(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > testFailedGet(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > testFailedGetIfNewer(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonGetFileListWhenDirectoryDoesNotExist(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonResourceExists(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > > testWagonResourceNotExists(org.apache.maven.wagon.providers.http.HttpsWagonTest): > Address already in use > Tests run: 88, Failures: 0, Errors: 19, Skipped: 0 > Full version of build log is in the attachment. > More information is here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717280 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error
[
https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1112:
--
Assignee: Tibor Digana (was: Andreas Gudian)
> Remove uneccessary newlines in console output for test results with no error
>
>
> Key: SUREFIRE-1112
> URL: https://jira.codehaus.org/browse/SUREFIRE-1112
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Andreas Gudian
>Assignee: Tibor Digana
>
> {code}
> Results :
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'm pretty sure it has something to do with the extended test result handling
> / printing for the flaky tests feature.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error
[
https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355780#comment-355780
]
Tibor Digana commented on SUREFIRE-1112:
Hi Andreas, I have so spare time so I have fixed it already.
> Remove uneccessary newlines in console output for test results with no error
>
>
> Key: SUREFIRE-1112
> URL: https://jira.codehaus.org/browse/SUREFIRE-1112
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Andreas Gudian
>Assignee: Tibor Digana
>
> {code}
> Results :
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'm pretty sure it has something to do with the extended test result handling
> / printing for the flaky tests feature.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error
[
https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355781#comment-355781
]
Tibor Digana commented on SUREFIRE-1112:
Fixed in https://github.com/apache/maven-surefire/pull/66
> Remove uneccessary newlines in console output for test results with no error
>
>
> Key: SUREFIRE-1112
> URL: https://jira.codehaus.org/browse/SUREFIRE-1112
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Andreas Gudian
>Assignee: Tibor Digana
> Fix For: 2.19
>
>
> {code}
> Results :
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'm pretty sure it has something to do with the extended test result handling
> / printing for the flaky tests feature.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error
[
https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1112:
---
Fix Version/s: 2.19
> Remove uneccessary newlines in console output for test results with no error
>
>
> Key: SUREFIRE-1112
> URL: https://jira.codehaus.org/browse/SUREFIRE-1112
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Andreas Gudian
>Assignee: Tibor Digana
> Fix For: 2.19
>
>
> {code}
> Results :
> Tests run: 60, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'm pretty sure it has something to do with the extended test result handling
> / printing for the flaky tests feature.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
Guillaume Husta created MASSEMBLY-730:
-
Summary: jar-with-dependencies : a file in a dependency is
overridden by the same file in JDK / JRE
Key: MASSEMBLY-730
URL: https://jira.codehaus.org/browse/MASSEMBLY-730
Project: Maven Assembly Plugin
Issue Type: Bug
Components: predefined descriptors
Affects Versions: 2.5
Environment: JDK 6
Maven 3.0.4
Linux / Windows
Reporter: Guillaume Husta
Since version 2.5, when I try to make a "jar-with-dependencies" with the
"single" goal, I get a strange mistake.
A file in a dependency (a JDBC driver in my example) is overridden by a file
with the same path / name included in a dependency from the JDK / JRE (in my
example jre/lib/resources.jar).
In my example, I just add the dependency
_org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
Then I package to make a "jar-with-dependencies".
I can find the file _META-INF/services/java.sql.Driver_ in this jar.
But with the version 2.5 of plugin assembly, it contains
* {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
and with version 2.4.1 of the plugin, it contains
* {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
what I expect
In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-730) jar-with-dependencies : a file in a dependency is overridden by the same file in JDK / JRE
[
https://jira.codehaus.org/browse/MASSEMBLY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355783#comment-355783
]
Guillaume Husta commented on MASSEMBLY-730:
---
I made a test case on GitHub.
You can see it here : https://github.com/ghusta/test-issue-massembly-730
> jar-with-dependencies : a file in a dependency is overridden by the same file
> in JDK / JRE
> --
>
> Key: MASSEMBLY-730
> URL: https://jira.codehaus.org/browse/MASSEMBLY-730
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: predefined descriptors
>Affects Versions: 2.5
> Environment: JDK 6
> Maven 3.0.4
> Linux / Windows
>Reporter: Guillaume Husta
>
> Since version 2.5, when I try to make a "jar-with-dependencies" with the
> "single" goal, I get a strange mistake.
> A file in a dependency (a JDBC driver in my example) is overridden by a file
> with the same path / name included in a dependency from the JDK / JRE (in my
> example jre/lib/resources.jar).
> In my example, I just add the dependency
> _org.postgresql:postgresql:9.3-1102-jdbc4_ to my POM.
> Then I package to make a "jar-with-dependencies".
> I can find the file _META-INF/services/java.sql.Driver_ in this jar.
> But with the version 2.5 of plugin assembly, it contains
> * {{sun.jdbc.odbc.JdbcOdbcDriver}} (originated from JRE : resources.jar)
> and with version 2.4.1 of the plugin, it contains
> * {{org.postgresql.Driver}} (originated from postgresql-9.3-1102-jdbc4.jar),
> what I expect
> In the previous version (2.4.1) there was no problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
