[jira] (MRESOURCES-199) Removed unused dependency to maven-monitor
Karl-Heinz Marbaise created MRESOURCES-199:
--
Summary: Removed unused dependency to maven-monitor
Key: MRESOURCES-199
URL: https://jira.codehaus.org/browse/MRESOURCES-199
Project: Maven Resources Plugin
Issue Type: Improvement
Affects Versions: 2.8
Reporter: Karl-Heinz Marbaise
Priority: Minor
Remove the dependency
{code:xml}
org.apache.maven
maven-monitor
${mavenVersion}
{code}
because it seemed to me it is not used.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-585) "repository cannot be null" on ScmManager.makeProviderScmRepository(String, File)
[
https://jira.codehaus.org/browse/SCM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358706#comment-358706
]
Jörg Hohwiller commented on SCM-585:
No feedback after 4 years now... Is maven-scm a dead project?
How does maven checkout from scratch? Is there a pattern and I am just not
seeing how to use the API properly?
> "repository cannot be null" on ScmManager.makeProviderScmRepository(String,
> File)
> -
>
> Key: SCM-585
> URL: https://jira.codehaus.org/browse/SCM-585
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.4
>Reporter: Jörg Hohwiller
>
> I want to update a subversion with maven-scm.
> Therefore I get the ScmManager via Plexus and then do this:
> {code}
> ScmManager.makeProviderScmRepository("svn", new File(path/to/checkout));
> {code}
> What I get is:
> {noformat}
> java.lang.NullPointerException: repository cannot be null
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:49)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.info(AbstractSvnScmProvider.java:377)
> at
> org.apache.maven.scm.provider.svn.svnexe.SvnExeScmProvider.getRepositoryURL(SvnExeScmProvider.java:150)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.makeProviderScmRepository(AbstractSvnScmProvider.java:119)
> at
> org.apache.maven.scm.manager.AbstractScmManager.makeProviderScmRepository(AbstractScmManager.java:267)
> {noformat}
> From what I understand the code tries to execute "svn info" to get the
> repository URL.
> However executing a command always checks that the repository is not {{null}}.
> In this case the svn command should be executed in order to be able to create
> the repository.
> It is not possible to create the repository before, because the URL is not
> known.
> My suggestion is to revisit this block in AbstractCommand:
> {code}
> if ( repository == null )
> {
> throw new NullPointerException( "repository cannot be null" );
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-585) "repository cannot be null" on ScmManager.makeProviderScmRepository(String, File)
[
https://jira.codehaus.org/browse/SCM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358706#comment-358706
]
Jörg Hohwiller edited comment on SCM-585 at 12/6/14 6:30 AM:
-
No feedback after 4 years now... Is maven-scm a dead project?
How does maven update an svn repo after it is checked out? Not at all? Is there
a pattern and I am just not seeing how to use the API properly?
was (Author: hohwille):
No feedback after 4 years now... Is maven-scm a dead project?
How does maven checkout from scratch? Is there a pattern and I am just not
seeing how to use the API properly?
> "repository cannot be null" on ScmManager.makeProviderScmRepository(String,
> File)
> -
>
> Key: SCM-585
> URL: https://jira.codehaus.org/browse/SCM-585
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.4
>Reporter: Jörg Hohwiller
>
> I want to update a subversion with maven-scm.
> Therefore I get the ScmManager via Plexus and then do this:
> {code}
> ScmManager.makeProviderScmRepository("svn", new File(path/to/checkout));
> {code}
> What I get is:
> {noformat}
> java.lang.NullPointerException: repository cannot be null
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:49)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.info(AbstractSvnScmProvider.java:377)
> at
> org.apache.maven.scm.provider.svn.svnexe.SvnExeScmProvider.getRepositoryURL(SvnExeScmProvider.java:150)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.makeProviderScmRepository(AbstractSvnScmProvider.java:119)
> at
> org.apache.maven.scm.manager.AbstractScmManager.makeProviderScmRepository(AbstractScmManager.java:267)
> {noformat}
> From what I understand the code tries to execute "svn info" to get the
> repository URL.
> However executing a command always checks that the repository is not {{null}}.
> In this case the svn command should be executed in order to be able to create
> the repository.
> It is not possible to create the repository before, because the URL is not
> known.
> My suggestion is to revisit this block in AbstractCommand:
> {code}
> if ( repository == null )
> {
> throw new NullPointerException( "repository cannot be null" );
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MWAR-309. Resolution: Won't Fix Assignee: Karl-Heinz Marbaise I will close the issue. If you have further informations/details don't hesitate to reopen the issue. > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Fix For: waiting-for-feedback > > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MWAR-309: - Fix Version/s: (was: waiting-for-feedback) > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358709#comment-358709 ] Kristian Rosenvold commented on MWAR-309: - I'm fairly sure recent versions of plexus-archiver fixes this > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358710#comment-358710 ] Karl-Heinz Marbaise commented on MWAR-309: -- maven-war-plugin use plexus-archiver 2.9 at the moment. > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358711#comment-358711 ] Kristian Rosenvold commented on MWAR-309: - Probable root cause > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358711#comment-358711 ] Kristian Rosenvold edited comment on MWAR-309 at 12/6/14 7:00 AM: -- Probable root cause is PLXCOMP-273 was (Author: krosenvold): Probable root cause > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Karl-Heinz Marbaise > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold reopened MWAR-309: - Assignee: Kristian Rosenvold (was: Karl-Heinz Marbaise) > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Kristian Rosenvold > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed MWAR-309. --- Resolution: Fixed Fix Version/s: 2.6 I think its safe to assume this as fixed > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Kristian Rosenvold > Fix For: 2.6 > > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-309) 'mvn package' duplicates WEB-INF/classes on linux only
[ https://jira.codehaus.org/browse/MWAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358710#comment-358710 ] Karl-Heinz Marbaise edited comment on MWAR-309 at 12/6/14 7:17 AM: --- maven-war-plugin uses plexus-archiver 2.9 at the moment. was (Author: khmarbaise): maven-war-plugin use plexus-archiver 2.9 at the moment. > 'mvn package' duplicates WEB-INF/classes on linux only > -- > > Key: MWAR-309 > URL: https://jira.codehaus.org/browse/MWAR-309 > Project: Maven WAR Plugin > Issue Type: Bug > Environment: OSX & windows seem to be in sync, ubuntu is not >Reporter: mike kozelsky >Assignee: Kristian Rosenvold > Fix For: 2.6 > > Attachments: build.centos_6.log, build.osx.log, build.ubuntu2.log, > build.ubuntu.log, build.windows.log, compare.png, pom.core.xml, pom.main.xml, > pom.rest-service.xml, pom.rest.xml > > > We have a multi-module n-tiered project. The endpoints (spring services) > rely on a core service project, which relies on a core logic project, which > relies on 2 others. So this is all set up using a main pom.xml file, listing > each module. I can then run 'mvn package' from the project root. > The issue is that running 'mvn package' on my windows workstation appears to > package things (what i would consider to be) correctly, and running the same > command on our server creates something slightly different. In essence, > there are class files from the core logic project which end up in the service > project's WEB-INF/classes output (as well as in the core's jar). Again, this > only happens on the ubuntu server. > In the attached screenshot, you can see on the left, the output of my > workstation, where there's two packages inside of WEB-INF/classes: > com.doolli.admin & com.doolli.rest. On the right side, you can see more > packages - additionally, you see com.doolli.database, com.doolli.main, > com.doolli.manager, com.doolli.object, as well as an org.sphx package - which > are defined further down in the dependency tree. > The duplicate definition is causing our server to throw runtime errors - > class and method not found exceptions. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1121) java.lang.NullPointerException org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
[
https://jira.codehaus.org/browse/SUREFIRE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358713#comment-358713
]
Tibor Digana commented on SUREFIRE-1121:
Whats'up Gary
Passing the tests?
> java.lang.NullPointerException
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> -
>
> Key: SUREFIRE-1121
> URL: https://jira.codehaus.org/browse/SUREFIRE-1121
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.18
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_71\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 2.19
>
> Attachments: effective.pom
>
>
> git clone http://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> Check out Log4j 2 commit {{d033a71eb0047ca35ec1582f0eab73abe3e04919}}. This
> is currently the latest.
> Run: {{mvn -e clean test}}
> I get:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 0.566
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 26.239
> s]
> [INFO] Apache Log4j Core .. SUCCESS [05:09
> min]
> [INFO] Apache Log4j 1.x Compatibility API . SUCCESS [ 9.233
> s]
> [INFO] Apache Log4j SLF4J Binding . SUCCESS [ 8.507
> s]
> [INFO] Apache Log4j to SLF4J Adapter .. FAILURE [ 5.781
> s]
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 06:02 min
> [INFO] Finished at: 2014-12-01T10:51:31-05:00
> [INFO] Final Memory: 34M/266M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed.
> NullPointerExc
> eption -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
> on project log4j-to-slf4j: Execution default-test of goal
> org.apache.maven.plugins:maven-
> surefire-plugin:2.18:test failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at
[jira] (MASSEMBLY-743) not correct
[
https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358714#comment-358714
]
Jean-Eric Cuendet commented on MASSEMBLY-743:
-
After analysis, the value set between the tag,
${min.includeBaseDirectory} is converted in Boolean while reading the assembly
descriptor. Since it's not a valid boolean value, it's transformed to the
default value : false
The resolution of variables into values is done after the assembly descriptor
reading. And at that moment the variable is lost.
To correct, there is 2 way:
1. In the Assembly class, have 2 values, one as String containing the variable,
another Boolean value containing the resolved value
2. Resolve the variables to values while reading the assembly descriptor.
Which one do you prefer?
I can try to correct that one and post a patche if you give some guidance.
> not correct
> --
>
> Key: MASSEMBLY-743
> URL: https://jira.codehaus.org/browse/MASSEMBLY-743
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jean-Eric Cuendet
>Assignee: Kristian Rosenvold
> Fix For: 2.5.3
>
> Attachments: maven-assembly-bug.tar.gz
>
>
> I use the assembly plugin, with the tag in the
> assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
> tag, it's not taken into account.
> But if I use true or false, that fine.
> I have created a small project that shows the problem. It's attached.
> To reproduce:
> - unzip the attachment
> - cd maven-assembly-bug/
> - mvn clean install assembly:single
> The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
> baseDir, while the variable used in the tag is set to
> true
> If you change the value in assembly.xml to true or false (instead of using
> the variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-388) create ITs to show how to implement reporting plugins and make test
[ https://jira.codehaus.org/browse/MSHARED-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-388: -- Fix Version/s: maven-reporting-impl 2.4 > create ITs to show how to implement reporting plugins and make test > --- > > Key: MSHARED-388 > URL: https://jira.codehaus.org/browse/MSHARED-388 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-reporting-impl >Affects Versions: maven-reporting-impl-2.3 >Reporter: Herve Boutemy > Fix For: maven-reporting-impl 2.4 > > > actual test report mojo only compile but don't really execute > creating an IT would not only compile but execute too -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-389) create an IT to show how to write a reporting mojo that uses external generator
Herve Boutemy created MSHARED-389: - Summary: create an IT to show how to write a reporting mojo that uses external generator Key: MSHARED-389 URL: https://jira.codehaus.org/browse/MSHARED-389 Project: Maven Shared Components Issue Type: Improvement Components: maven-reporting-impl Affects Versions: maven-reporting-impl-2.3 Reporter: Herve Boutemy latest questions on maven-dev and looking at m-javadoc-mojo, I think that a little demo would help -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-388) create ITs to show how to implement reporting plugins and make test
Herve Boutemy created MSHARED-388: - Summary: create ITs to show how to implement reporting plugins and make test Key: MSHARED-388 URL: https://jira.codehaus.org/browse/MSHARED-388 Project: Maven Shared Components Issue Type: Improvement Components: maven-reporting-impl Affects Versions: maven-reporting-impl-2.3 Reporter: Herve Boutemy actual test report mojo only compile but don't really execute creating an IT would not only compile but execute too -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-743) not correct
[
https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358717#comment-358717
]
Kristian Rosenvold commented on MASSEMBLY-743:
--
We are discussing this on the maven developers list right now. You might want
to look in on the discussion.
> not correct
> --
>
> Key: MASSEMBLY-743
> URL: https://jira.codehaus.org/browse/MASSEMBLY-743
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jean-Eric Cuendet
>Assignee: Kristian Rosenvold
> Fix For: 2.5.3
>
> Attachments: maven-assembly-bug.tar.gz
>
>
> I use the assembly plugin, with the tag in the
> assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
> tag, it's not taken into account.
> But if I use true or false, that fine.
> I have created a small project that shows the problem. It's attached.
> To reproduce:
> - unzip the attachment
> - cd maven-assembly-bug/
> - mvn clean install assembly:single
> The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
> baseDir, while the variable used in the tag is set to
> true
> If you change the value in assembly.xml to true or false (instead of using
> the variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-743) not correct
[
https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358717#comment-358717
]
Kristian Rosenvold edited comment on MASSEMBLY-743 at 12/6/14 12:50 PM:
We are discussing this on the maven developers list right now. You might want
to look in on the discussion.
http://www.mail-archive.com/dev@maven.apache.org/msg103433.html
was (Author: krosenvold):
We are discussing this on the maven developers list right now. You might want
to look in on the discussion.
> not correct
> --
>
> Key: MASSEMBLY-743
> URL: https://jira.codehaus.org/browse/MASSEMBLY-743
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jean-Eric Cuendet
>Assignee: Kristian Rosenvold
> Fix For: 2.5.3
>
> Attachments: maven-assembly-bug.tar.gz
>
>
> I use the assembly plugin, with the tag in the
> assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
> tag, it's not taken into account.
> But if I use true or false, that fine.
> I have created a small project that shows the problem. It's attached.
> To reproduce:
> - unzip the attachment
> - cd maven-assembly-bug/
> - mvn clean install assembly:single
> The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
> baseDir, while the variable used in the tag is set to
> true
> If you change the value in assembly.xml to true or false (instead of using
> the variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-648) lineEnding in fileSet corrupts jar files
[ https://jira.codehaus.org/browse/MASSEMBLY-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed MASSEMBLY-648. Resolution: Fixed Fix Version/s: (was: backlog) Assignee: Kristian Rosenvold Fixed in r1643597. Will now fail on linefeed filtering of zip/jar files > lineEnding in fileSet corrupts jar files > > > Key: MASSEMBLY-648 > URL: https://jira.codehaus.org/browse/MASSEMBLY-648 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Maven 3.0.5 on Mac Os 10.8.3 with Apple JDK 1.6.0_43 > Maven 3.0.5 on Windows XP with Oracle JDK 1.6.0_31 >Reporter: Anders Hammar >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5.3 > > Attachments: assembly-lineEnding.zip > > > I've found a difference in behavior between v2.3 and v2.4 of the plugin. If > lineEnding is set to, for example, unix for a fileSet which contains jar > files, the jar files are modified and corrupt with v2.4. This was not the > case with v2.3. See attached test project. > Not sure if this is an actual bug in the plugin, or rather a misconfiguation > in the project. But the behavioral change between the versions is a fact. :-) > If this is not a bug, maybe we could try to detect misconfiguration like this > and output a warning? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRESOURCES-199) Removed unused dependency to maven-monitor
[
https://jira.codehaus.org/browse/MRESOURCES-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MRESOURCES-199.
--
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1643598|http://svn.apache.org/r1643598]
> Removed unused dependency to maven-monitor
> --
>
> Key: MRESOURCES-199
> URL: https://jira.codehaus.org/browse/MRESOURCES-199
> Project: Maven Resources Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
>
> Remove the dependency
> {code:xml}
>
> org.apache.maven
> maven-monitor
>${mavenVersion}
>
> {code}
> because it seemed to me it is not used.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-195) Upgrade to PMD 5.2.2 as soon as it is available
[ https://jira.codehaus.org/browse/MPMD-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-195. --- Resolution: Fixed Fixed with [r1643601|http://svn.apache.org/r1643601]. > Upgrade to PMD 5.2.2 as soon as it is available > --- > > Key: MPMD-195 > URL: https://jira.codehaus.org/browse/MPMD-195 > Project: Maven PMD Plugin > Issue Type: Task >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-195) Upgrade to PMD 5.2.2 as soon as it is available
[ https://jira.codehaus.org/browse/MPMD-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-195: Fix Version/s: 3.4 > Upgrade to PMD 5.2.2 as soon as it is available > --- > > Key: MPMD-195 > URL: https://jira.codehaus.org/browse/MPMD-195 > Project: Maven PMD Plugin > Issue Type: Task >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 3.4 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-314) Upgrade to maven-plugins version 26 to 27
[ https://jira.codehaus.org/browse/MPIR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MPIR-314: - Fix Version/s: 2.8 > Upgrade to maven-plugins version 26 to 27 > - > > Key: MPIR-314 > URL: https://jira.codehaus.org/browse/MPIR-314 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.8 > > > Upgrade to maven-plugins version 26 to 27 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-314) Upgrade to maven-plugins version 26 to 27
Karl-Heinz Marbaise created MPIR-314: Summary: Upgrade to maven-plugins version 26 to 27 Key: MPIR-314 URL: https://jira.codehaus.org/browse/MPIR-314 Project: Maven Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.8 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade to maven-plugins version 26 to 27 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-314) Upgrade to maven-plugins version 26 to 27
[ https://jira.codehaus.org/browse/MPIR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MPIR-314. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1643603|http://svn.apache.org/r1643603] > Upgrade to maven-plugins version 26 to 27 > - > > Key: MPIR-314 > URL: https://jira.codehaus.org/browse/MPIR-314 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.8 > > > Upgrade to maven-plugins version 26 to 27 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-315) Replace org.apache.maven.shared:maven-doxia-tools with org.apache.maven.doxia:doxia-integration-tools
[
https://jira.codehaus.org/browse/MPIR-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MPIR-315:
-
Fix Version/s: 2.8
> Replace org.apache.maven.shared:maven-doxia-tools with
> org.apache.maven.doxia:doxia-integration-tools
> -
>
> Key: MPIR-315
> URL: https://jira.codehaus.org/browse/MPIR-315
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> {code:xml}
>
>org.apache.maven.shared
> maven-doxia-tools
> 1.4
>
> {codeâ
> Replace it with:
> {code:xml}
>
> org.apache.maven.doxia
> doxia-integration-tools
> 1.6
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-315) Replace org.apache.maven.shared:maven-doxia-tools with org.apache.maven.doxia:doxia-integration-tools
[
https://jira.codehaus.org/browse/MPIR-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MPIR-315:
Assignee: Karl-Heinz Marbaise
> Replace org.apache.maven.shared:maven-doxia-tools with
> org.apache.maven.doxia:doxia-integration-tools
> -
>
> Key: MPIR-315
> URL: https://jira.codehaus.org/browse/MPIR-315
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> {code:xml}
>
>org.apache.maven.shared
> maven-doxia-tools
> 1.4
>
> {codeâ
> Replace it with:
> {code:xml}
>
> org.apache.maven.doxia
> doxia-integration-tools
> 1.6
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-315) Replace org.apache.maven.shared:maven-doxia-tools with org.apache.maven.doxia:doxia-integration-tools
Karl-Heinz Marbaise created MPIR-315:
Summary: Replace org.apache.maven.shared:maven-doxia-tools with
org.apache.maven.doxia:doxia-integration-tools
Key: MPIR-315
URL: https://jira.codehaus.org/browse/MPIR-315
Project: Maven Project Info Reports Plugin
Issue Type: Improvement
Affects Versions: 2.8
Reporter: Karl-Heinz Marbaise
Priority: Minor
{code:xml}
org.apache.maven.shared
maven-doxia-tools
1.4
{codeâ
Replace it with:
{code:xml}
org.apache.maven.doxia
doxia-integration-tools
1.6
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-315) Replace org.apache.maven.shared:maven-doxia-tools with org.apache.maven.doxia:doxia-integration-tools
[
https://jira.codehaus.org/browse/MPIR-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MPIR-315.
Resolution: Fixed
Fixed in [r1643604|http://svn.apache.org/r1643604]
> Replace org.apache.maven.shared:maven-doxia-tools with
> org.apache.maven.doxia:doxia-integration-tools
> -
>
> Key: MPIR-315
> URL: https://jira.codehaus.org/browse/MPIR-315
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> {code:xml}
>
>org.apache.maven.shared
> maven-doxia-tools
> 1.4
>
> {codeâ
> Replace it with:
> {code:xml}
>
> org.apache.maven.doxia
> doxia-integration-tools
> 1.6
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-315) Replace org.apache.maven.shared:maven-doxia-tools with org.apache.maven.doxia:doxia-integration-tools
[
https://jira.codehaus.org/browse/MPIR-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MPIR-315:
-
Description:
{code:xml}
org.apache.maven.shared
maven-doxia-tools
1.4
{code}
Replace it with:
{code:xml}
org.apache.maven.doxia
doxia-integration-tools
1.6
{code}
was:
{code:xml}
org.apache.maven.shared
maven-doxia-tools
1.4
{codeâ
Replace it with:
{code:xml}
org.apache.maven.doxia
doxia-integration-tools
1.6
{code}
> Replace org.apache.maven.shared:maven-doxia-tools with
> org.apache.maven.doxia:doxia-integration-tools
> -
>
> Key: MPIR-315
> URL: https://jira.codehaus.org/browse/MPIR-315
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> {code:xml}
>
>org.apache.maven.shared
> maven-doxia-tools
> 1.4
>
> {code}
> Replace it with:
> {code:xml}
>
> org.apache.maven.doxia
> doxia-integration-tools
> 1.6
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-316) Removed dependency org.codehaus.plexus:plexus-container-default:1.0-alpha-9
[
https://jira.codehaus.org/browse/MPIR-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MPIR-316:
-
Fix Version/s: 2.8
> Removed dependency org.codehaus.plexus:plexus-container-default:1.0-alpha-9
> ---
>
> Key: MPIR-316
> URL: https://jira.codehaus.org/browse/MPIR-316
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> Removed dependency
> {code:xml}
>
> org.codehaus.plexus
> plexus-container-default
> 1.0-alpha-9
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-316) Removed dependency org.codehaus.plexus:plexus-container-default:1.0-alpha-9
[
https://jira.codehaus.org/browse/MPIR-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MPIR-316.
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1643605|http://svn.apache.org/r1643605].
> Removed dependency org.codehaus.plexus:plexus-container-default:1.0-alpha-9
> ---
>
> Key: MPIR-316
> URL: https://jira.codehaus.org/browse/MPIR-316
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 2.8
>
>
> Removed dependency
> {code:xml}
>
> org.codehaus.plexus
> plexus-container-default
> 1.0-alpha-9
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-316) Removed dependency org.codehaus.plexus:plexus-container-default:1.0-alpha-9
Karl-Heinz Marbaise created MPIR-316:
Summary: Removed dependency
org.codehaus.plexus:plexus-container-default:1.0-alpha-9
Key: MPIR-316
URL: https://jira.codehaus.org/browse/MPIR-316
Project: Maven Project Info Reports Plugin
Issue Type: Improvement
Affects Versions: 2.8
Reporter: Karl-Heinz Marbaise
Priority: Minor
Removed dependency
{code:xml}
org.codehaus.plexus
plexus-container-default
1.0-alpha-9
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-740) mismatched descriptors / descriptorRefs gives generic error
[ https://jira.codehaus.org/browse/MASSEMBLY-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated MASSEMBLY-740: - Fix Version/s: (was: 2.5.3) backlog > mismatched descriptors / descriptorRefs gives generic error > --- > > Key: MASSEMBLY-740 > URL: https://jira.codehaus.org/browse/MASSEMBLY-740 > Project: Maven Assembly Plugin > Issue Type: Bug >Reporter: Daniel Pocock >Priority: Minor > Fix For: backlog > > > Basically, if pom.xml is misconfigured: > > src/assembly/dist.xml > > instead of using the correct container : > > src/assembly/dist.xml > > then the assembly plugin fails with the rather generic error: > Error reading assemblies: Descriptor with ID 'src/assembly/dist.xml' not found > It had started off as a valid and working configuration like this: > > bin > > and then only the element was changed to to use > a custom dist.xml without realizing that descriptorRefs needs to be changed > too. > This is probably a very easy mistake for anybody to make the first time they > customize the assembly plugin so it would be nice to show a more explicit > error telling people not to mismatch with and > vice-versa. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-740) mismatched descriptors / descriptorRefs gives generic error
[ https://jira.codehaus.org/browse/MASSEMBLY-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358725#comment-358725 ] Kristian Rosenvold commented on MASSEMBLY-740: -- Unfortunately the descriptor parsing logic is generated code that actively stops us from detecting this condition. This is one of those cases where code generation makes a presumptively simple task extremely complex, causing all sorts of leaks/workarounds in other code. Unfortunately there is no easy workaround, so this is probably not going to be fixed any time soon. > mismatched descriptors / descriptorRefs gives generic error > --- > > Key: MASSEMBLY-740 > URL: https://jira.codehaus.org/browse/MASSEMBLY-740 > Project: Maven Assembly Plugin > Issue Type: Bug >Reporter: Daniel Pocock >Priority: Minor > Fix For: backlog > > > Basically, if pom.xml is misconfigured: > > src/assembly/dist.xml > > instead of using the correct container : > > src/assembly/dist.xml > > then the assembly plugin fails with the rather generic error: > Error reading assemblies: Descriptor with ID 'src/assembly/dist.xml' not found > It had started off as a valid and working configuration like this: > > bin > > and then only the element was changed to to use > a custom dist.xml without realizing that descriptorRefs needs to be changed > too. > This is probably a very easy mistake for anybody to make the first time they > customize the assembly plugin so it would be nice to show a more explicit > error telling people not to mismatch with and > vice-versa. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRRESOURCES-89) Removed deprecated attributes
[
https://jira.codehaus.org/browse/MRRESOURCES-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reassigned MRRESOURCES-89:
--
Assignee: Karl-Heinz Marbaise
> Removed deprecated attributes
> -
>
> Key: MRRESOURCES-89
> URL: https://jira.codehaus.org/browse/MRRESOURCES-89
> Project: Maven Remote Resources Plugin
> Issue Type: Improvement
>Affects Versions: 1.6
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.6
>
>
> Remove the @Deprecated marked attributes:
> {code:java}
> @Deprecated
> @Parameter( defaultValue = "true" )
> private boolean attached = true;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRRESOURCES-89) Removed deprecated attributes
[
https://jira.codehaus.org/browse/MRRESOURCES-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MRRESOURCES-89.
--
Resolution: Fixed
Fixed in [r1643610|http://svn.apache.org/r1643610].
> Removed deprecated attributes
> -
>
> Key: MRRESOURCES-89
> URL: https://jira.codehaus.org/browse/MRRESOURCES-89
> Project: Maven Remote Resources Plugin
> Issue Type: Improvement
>Affects Versions: 1.6
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.6
>
>
> Remove the @Deprecated marked attributes:
> {code:java}
> @Deprecated
> @Parameter( defaultValue = "true" )
> private boolean attached = true;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPMD-193) CPD's sourceEncoding not set since PMD 5.1.1 is used
[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-193. --- Resolution: Fixed Fix Version/s: 3.4 Fixed with [r1643612|http://svn.apache.org/r1643612]. Andreas, can you have a look and tell whether it is still necessary to set both encoding parameters? > CPD's sourceEncoding not set since PMD 5.1.1 is used > > > Key: MPMD-193 > URL: https://jira.codehaus.org/browse/MPMD-193 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.2, 3.3, 3.4 >Reporter: Tweea Tang >Assignee: Michael Osipov > Fix For: 3.4 > > Attachments: CpdReport.java.patch, > CpdReport.java(setSourceEncoding).patch > > > Since PMD 5.1.1, CPDConfiguration adds a method postContruct(). > This method is used to set the sourceEncoding property used to read source > files in PMD. > If the sourceEncoding not set, CPD will use the platform default encoding to > read the source files and maven-pmd-plugin's encoding has no effects. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-22) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MACR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MACR-22: Fix Version/s: 1.2 > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MACR-22 > URL: https://jira.codehaus.org/browse/MACR-22 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-22) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MACR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reassigned MACR-22: --- Assignee: Karl-Heinz Marbaise > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MACR-22 > URL: https://jira.codehaus.org/browse/MACR-22 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-22) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
Karl-Heinz Marbaise created MACR-22: --- Summary: Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api Key: MACR-22 URL: https://jira.codehaus.org/browse/MACR-22 Project: Maven ACR Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-22) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MACR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise resolved MACR-22. - Resolution: Fixed Fixed in [r1643614|http://svn.apache.org/r1643614] > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MACR-22 > URL: https://jira.codehaus.org/browse/MACR-22 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-22) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MACR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MACR-22. --- > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MACR-22 > URL: https://jira.codehaus.org/browse/MACR-22 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-80) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
Karl-Heinz Marbaise created MEJB-80: --- Summary: Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api Key: MEJB-80 URL: https://jira.codehaus.org/browse/MEJB-80 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-80) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MEJB-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-80. --- Resolution: Fixed Fix Version/s: 2.5 Assignee: Karl-Heinz Marbaise Fixed in [r1643615|http://svn.apache.org/r1643615] > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MEJB-80 > URL: https://jira.codehaus.org/browse/MEJB-80 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MACR-23) Upgrade maven-plugin-testing-harness to 1.3
Karl-Heinz Marbaise created MACR-23:
---
Summary: Upgrade maven-plugin-testing-harness to 1.3
Key: MACR-23
URL: https://jira.codehaus.org/browse/MACR-23
Project: Maven ACR Plugin
Issue Type: Improvement
Reporter: Karl-Heinz Marbaise
Upgrade from:
{code:xml}
org.apache.maven.shared
maven-plugin-testing-harness
1.1
test
{code}
to:
{code:xml}
org.apache.maven.plugin-testing
maven-plugin-testing-harness
1.3
test
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-217) Upgrade maven-plugin-testing-harness to 1.3
[
https://jira.codehaus.org/browse/MENFORCER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-217:
--
Fix Version/s: 1.4
> Upgrade maven-plugin-testing-harness to 1.3
> ---
>
> Key: MENFORCER-217
> URL: https://jira.codehaus.org/browse/MENFORCER-217
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> Upgrade from:
> {code:xml}
>
>org.apache.maven.shared
>maven-plugin-testing-harness
>1.1
>test
>
> {code}
> to:
> {code:xml}
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 1.3
>test
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-217) Upgrade maven-plugin-testing-harness to 1.3
[
https://jira.codehaus.org/browse/MENFORCER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MENFORCER-217:
--
Priority: Minor (was: Major)
> Upgrade maven-plugin-testing-harness to 1.3
> ---
>
> Key: MENFORCER-217
> URL: https://jira.codehaus.org/browse/MENFORCER-217
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> Upgrade from:
> {code:xml}
>
>org.apache.maven.shared
>maven-plugin-testing-harness
>1.1
>test
>
> {code}
> to:
> {code:xml}
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 1.3
>test
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-217) Upgrade maven-plugin-testing-harness to 1.3
[
https://jira.codehaus.org/browse/MENFORCER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise moved MACR-23 to MENFORCER-217:
---
Workflow: Maven New (was: classic default workflow)
Key: MENFORCER-217 (was: MACR-23)
Project: Maven Enforcer Plugin (was: Maven ACR Plugin)
> Upgrade maven-plugin-testing-harness to 1.3
> ---
>
> Key: MENFORCER-217
> URL: https://jira.codehaus.org/browse/MENFORCER-217
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Reporter: Karl-Heinz Marbaise
> Fix For: 1.4
>
>
> Upgrade from:
> {code:xml}
>
>org.apache.maven.shared
>maven-plugin-testing-harness
>1.1
>test
>
> {code}
> to:
> {code:xml}
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 1.3
>test
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MENFORCER-217) Upgrade maven-plugin-testing-harness to 1.3
[
https://jira.codehaus.org/browse/MENFORCER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MENFORCER-217.
-
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1643617|http://svn.apache.org/r1643617].
> Upgrade maven-plugin-testing-harness to 1.3
> ---
>
> Key: MENFORCER-217
> URL: https://jira.codehaus.org/browse/MENFORCER-217
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 1.4
>
>
> Upgrade from:
> {code:xml}
>
>org.apache.maven.shared
>maven-plugin-testing-harness
>1.1
>test
>
> {code}
> to:
> {code:xml}
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 1.3
>test
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-737) Generated WAR file does not contain the same default manifest entries as created by the Maven WAR Plugin
[
https://jira.codehaus.org/browse/MASSEMBLY-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358732#comment-358732
]
Michael Osipov commented on MASSEMBLY-737:
--
Why has the manifest to be the first in the file? I have always assumed that
all components use Maven Archiver throughout.
I am not particularily clinging to the same content of the manifest file but
indicating that there should be no difference between a Maven WAR Plugin and a
Maven Assembly Plugin generated WAR file.
> Generated WAR file does not contain the same default manifest entries as
> created by the Maven WAR Plugin
>
>
> Key: MASSEMBLY-737
> URL: https://jira.codehaus.org/browse/MASSEMBLY-737
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest, maven-archiver
>Affects Versions: 2.5.2
>Reporter: Michael Osipov
> Fix For: 2.5.3
>
> Attachments: massembly-737.zip
>
>
> I am repackaging a WAR file with some files exchanged. The original fiel
> contains following manifest entries:
> {noformat}
> Manifest-Version: 1.0
> Built-By: osipovmi
> Build-Jdk: 1.7.0_55
> Created-By: Apache Maven 3.2.2
> Archiver-Version: Plexus Archiver
> {noformat}
> The {{MANIFEST.MF}} generated by this plugin looks like:
> {noformat}
> Manifest-Version: 1.0
> Created-By: 24.55-b03 (Oracle Corporation)
> Archiver-Version: Plexus Archiver
> {noformat}
> while the descriptor looks very simple:
> {code}
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
> http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
> deployable
>
> war
>
> false
>
>
> true
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-280) Clarify that Web Access SCM link is not suitable for SCM checkout
[ https://jira.codehaus.org/browse/MPIR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-280: Fix Version/s: 2.8 > Clarify that Web Access SCM link is not suitable for SCM checkout > - > > Key: MPIR-280 > URL: https://jira.codehaus.org/browse/MPIR-280 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.7 >Reporter: SebbASF >Assignee: Michael Osipov > Fix For: 2.8 > > > The details for the viewvc section say (for example): > >>> > Web Access > The following is a link to the online source repository. > http://svn.apache.org/viewvc/commons/proper/lang/trunk > <<< > This has been taken by some readers to imply that the URL is suitable for SVN > client access, and there have been complaints on mailing lists when it does > not work. > It would be useful to clarify the text to reduce user frustration and > unnecessary mailing list traffic. > The text "The following is a link to the online source repository." applies > equally to a proper SVN link. It does not indicate that URL is intended for > Web Brower (HTTP) access only. > The section header "Web Access" does not really help either, as "Web" is > often used as a synonym for "Internet". > I can see how readers who don't know about ViewVC could easily not notice > that distinction. > I suggest that the default text is changed as follows: > report.scm.webaccess.title=Web Server (HTTP) Access > report.scm.webaccess.url= > The following is a link to a browsable version of the source repository. > Please use the "Anonymous Access" or "Developer Access" URL if you want to > check out the source using your SCM client. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[ https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358733#comment-358733 ] Michael Osipov commented on MNG-5568: - [~hboutemy], does your change implicitly fix MPIR-247? > ComparableVersion's breaks contract for Comparable, in some edgecases the > comparisons are not transitive > > > Key: MNG-5568 > URL: https://jira.codehaus.org/browse/MNG-5568 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.5 >Reporter: Milos Kleint >Assignee: Herve Boutemy >Priority: Critical > Fix For: 3.2.4 > > Attachments: ComparableVersion.patch > > > if ComparableVersion A > B and B > C, then it's required that A > C. In the > attached test patch, I'm demonstrating a case where it's failing. Please note > that the situation is not that rare, please see issues > https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and > https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and > https://jira.codehaus.org/browse/MPIR-247 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-280) Clarify that Web Access SCM link is not suitable for SCM checkout
[ https://jira.codehaus.org/browse/MPIR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-280. --- Resolution: Fixed Fixed with [r1643618|http://svn.apache.org/r1643618]. > Clarify that Web Access SCM link is not suitable for SCM checkout > - > > Key: MPIR-280 > URL: https://jira.codehaus.org/browse/MPIR-280 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.7 >Reporter: SebbASF >Assignee: Michael Osipov > Fix For: 2.8 > > > The details for the viewvc section say (for example): > >>> > Web Access > The following is a link to the online source repository. > http://svn.apache.org/viewvc/commons/proper/lang/trunk > <<< > This has been taken by some readers to imply that the URL is suitable for SVN > client access, and there have been complaints on mailing lists when it does > not work. > It would be useful to clarify the text to reduce user frustration and > unnecessary mailing list traffic. > The text "The following is a link to the online source repository." applies > equally to a proper SVN link. It does not indicate that URL is intended for > Web Brower (HTTP) access only. > The section header "Web Access" does not really help either, as "Web" is > often used as a synonym for "Internet". > I can see how readers who don't know about ViewVC could easily not notice > that distinction. > I suggest that the default text is changed as follows: > report.scm.webaccess.title=Web Server (HTTP) Access > report.scm.webaccess.url= > The following is a link to a browsable version of the source repository. > Please use the "Anonymous Access" or "Developer Access" URL if you want to > check out the source using your SCM client. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-737) Generated WAR file does not contain the same default manifest entries as created by the Maven WAR Plugin
[
https://jira.codehaus.org/browse/MASSEMBLY-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358736#comment-358736
]
Kristian Rosenvold commented on MASSEMBLY-737:
--
the jar specification requires that the manifest file be the first file in the
archive (the zip file). This is a royal PITA, since any items that have to go
into the manifest have to be known up-front. plexus-io/plexus-archiver is
generally as deferred as possible, meaning it lazily resolves anything you ask
it for. Currently the assembly plugin "solves" this by being 2-pass; it reads
all of the files specified in all the assembly descriptors. If any of them
contain "stuff" that is supposed to go into the descriptor it writes the
appropriate descriptor. It would be possible to add the scan for existing
manifests to this first pass of the archiver. I really don't like us being
2-pass over the source specifications in assembly and would really like to
reduce this to a single pass operation. In this case we'd have to re-write the
entire archive at the end if we discover things that are "worthy" of a manifest
entry. I'm not entirely ready to claim defeat on this yet, but it really means
that we need to be able to re-write the zip file with a new manifest entry (and
preferably without decompressing/recompressing) on the fly. So the moment I
give up on all these ambitions and accept the 2-pass strategy it all becomes
simple. But I'm not here for "simple"
> Generated WAR file does not contain the same default manifest entries as
> created by the Maven WAR Plugin
>
>
> Key: MASSEMBLY-737
> URL: https://jira.codehaus.org/browse/MASSEMBLY-737
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest, maven-archiver
>Affects Versions: 2.5.2
>Reporter: Michael Osipov
> Fix For: 2.5.3
>
> Attachments: massembly-737.zip
>
>
> I am repackaging a WAR file with some files exchanged. The original fiel
> contains following manifest entries:
> {noformat}
> Manifest-Version: 1.0
> Built-By: osipovmi
> Build-Jdk: 1.7.0_55
> Created-By: Apache Maven 3.2.2
> Archiver-Version: Plexus Archiver
> {noformat}
> The {{MANIFEST.MF}} generated by this plugin looks like:
> {noformat}
> Manifest-Version: 1.0
> Created-By: 24.55-b03 (Oracle Corporation)
> Archiver-Version: Plexus Archiver
> {noformat}
> while the descriptor looks very simple:
> {code}
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
> http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
> deployable
>
> war
>
> false
>
>
> true
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPIR-288) Add a skipEmptyReport option
[ https://jira.codehaus.org/browse/MPIR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-288: --- Assignee: Michael Osipov > Add a skipEmptyReport option > > > Key: MPIR-288 > URL: https://jira.codehaus.org/browse/MPIR-288 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.7 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 2.8 > > > Similar to MPMD-168, it should be possible to skip generation of empty > reports which do not contain any valuable information. > Some canditates are dependencies, cim, scm, issues, mailinglist, etc. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5568) ComparableVersion's breaks contract for Comparable, in some edgecases the comparisons are not transitive
[ https://jira.codehaus.org/browse/MNG-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358738#comment-358738 ] Herve Boutemy commented on MNG-5568: yes: MPIR-247 is just a consequence of MNG-5568 bug, and I don't see how to create a workaround in MPIR > ComparableVersion's breaks contract for Comparable, in some edgecases the > comparisons are not transitive > > > Key: MNG-5568 > URL: https://jira.codehaus.org/browse/MNG-5568 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.5 >Reporter: Milos Kleint >Assignee: Herve Boutemy >Priority: Critical > Fix For: 3.2.4 > > Attachments: ComparableVersion.patch > > > if ComparableVersion A > B and B > C, then it's required that A > C. In the > attached test patch, I'm demonstrating a case where it's failing. Please note > that the situation is not that rare, please see issues > https://netbeans.org/bugzilla/show_bug.cgi?id=226100 and > https://netbeans.org/bugzilla/show_bug.cgi?id=240845 at netbeans.org and > https://jira.codehaus.org/browse/MPIR-247 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MLINKCHECK-20) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MLINKCHECK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MLINKCHECK-20. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1643620|http://svn.apache.org/r1643620] > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MLINKCHECK-20 > URL: https://jira.codehaus.org/browse/MLINKCHECK-20 > Project: Maven Linkcheck Plugin > Issue Type: Improvement >Affects Versions: next-release >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MLINKCHECK-20) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
Karl-Heinz Marbaise created MLINKCHECK-20: - Summary: Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api Key: MLINKCHECK-20 URL: https://jira.codehaus.org/browse/MLINKCHECK-20 Project: Maven Linkcheck Plugin Issue Type: Improvement Affects Versions: next-release Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MLINKCHECK-20) Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api
[ https://jira.codehaus.org/browse/MLINKCHECK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MLINKCHECK-20: -- Fix Version/s: next-release > Remove unnecessary exclusions of org.codehaus.plexus:plexus-component-api > - > > Key: MLINKCHECK-20 > URL: https://jira.codehaus.org/browse/MLINKCHECK-20 > Project: Maven Linkcheck Plugin > Issue Type: Improvement >Affects Versions: next-release >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-465) Upgrade to maven-parent version 26
Karl-Heinz Marbaise created ARCHETYPE-465: - Summary: Upgrade to maven-parent version 26 Key: ARCHETYPE-465 URL: https://jira.codehaus.org/browse/ARCHETYPE-465 Project: Maven Archetype Issue Type: Improvement Affects Versions: 2.3 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade to maven-parent version 26 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-318) not correctly filtered
[
https://jira.codehaus.org/browse/ARCHETYPE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated ARCHETYPE-318:
--
Fix Version/s: (was: 2.x)
> not correctly filtered
>
>
> Key: ARCHETYPE-318
> URL: https://jira.codehaus.org/browse/ARCHETYPE-318
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 2.0-alpha-5
>Reporter: Jochen Ehret
>Priority: Minor
> Attachments: DefaultArchetypeGenerationConfigurator.patch
>
>
> In our archetype-metadata.xml we´ve defined a with a
> default value like this:
> {code:xml}
> ${artifactId}.itest1
> {code}
> When we call "archetype:generate" and enter the parameters in interactive
> mode everything works fine. But when we try to set the parameter
> "subArtifactId" on the command line (mvn archetype:generate
> -DsubArtifactId=xyz) or from an "archetype.properties" file, the value is
> ignored. In the generated pom.xml the variable ${subArtifactId} is always
> replaced with "${artifactId}.itest1".
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (ARCHETYPE-465) Upgrade to maven-parent version 26
[ https://jira.codehaus.org/browse/ARCHETYPE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated ARCHETYPE-465: -- Fix Version/s: 2.3 > Upgrade to maven-parent version 26 > -- > > Key: ARCHETYPE-465 > URL: https://jira.codehaus.org/browse/ARCHETYPE-465 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.3 > > > Upgrade to maven-parent version 26 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-465) Upgrade to maven-parent version 26
[ https://jira.codehaus.org/browse/ARCHETYPE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed ARCHETYPE-465. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1643621|http://svn.apache.org/r1643621] > Upgrade to maven-parent version 26 > -- > > Key: ARCHETYPE-465 > URL: https://jira.codehaus.org/browse/ARCHETYPE-465 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.3 > > > Upgrade to maven-parent version 26 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
