[jira] (MNGSITE-180) State more clearly that the maven-foo-plugin naming pattern is really reserved and can be a trademark infringement
[ https://jira.codehaus.org/browse/MNGSITE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Baptiste Mathus updated MNGSITE-180: Attachment: MNGSITE-180-followup.patch Followup of http://maven.40175.n5.nabble.com/Name-of-a-new-Apache-plugin-for-maven-tt5766852.html another small improvement proposal > State more clearly that the maven-foo-plugin naming pattern is really > reserved and can be a trademark infringement > -- > > Key: MNGSITE-180 > URL: https://jira.codehaus.org/browse/MNGSITE-180 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Baptiste Mathus >Assignee: Stephen Connolly > Attachments: MNGSITE-180-followup.patch, MNGSITE-180.patch > > > Hi, > As a followup to that thread of maven-users: > http://maven.40175.n5.nabble.com/Maven-plugin-trademarks-Re-Downloading-a-file-for-shipping-in-an-artifact-tt5759104.html > I'm attaching a possible patch to improve the current plugin documentation so > that people don't name their plugin maven-something-plugin without knowing > this is a very very bad idea. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-180) State more clearly that the maven-foo-plugin naming pattern is really reserved and can be a trademark infringement
[ https://jira.codehaus.org/browse/MNGSITE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reopened MNGSITE-180: --- Assignee: Anders Hammar (was: Stephen Connolly) > State more clearly that the maven-foo-plugin naming pattern is really > reserved and can be a trademark infringement > -- > > Key: MNGSITE-180 > URL: https://jira.codehaus.org/browse/MNGSITE-180 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Baptiste Mathus >Assignee: Anders Hammar > Attachments: MNGSITE-180-followup.patch, MNGSITE-180.patch > > > Hi, > As a followup to that thread of maven-users: > http://maven.40175.n5.nabble.com/Maven-plugin-trademarks-Re-Downloading-a-file-for-shipping-in-an-artifact-tt5759104.html > I'm attaching a possible patch to improve the current plugin documentation so > that people don't name their plugin maven-something-plugin without knowing > this is a very very bad idea. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-180) State more clearly that the maven-foo-plugin naming pattern is really reserved and can be a trademark infringement
[ https://jira.codehaus.org/browse/MNGSITE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MNGSITE-180. Resolution: Fixed r1510880 > State more clearly that the maven-foo-plugin naming pattern is really > reserved and can be a trademark infringement > -- > > Key: MNGSITE-180 > URL: https://jira.codehaus.org/browse/MNGSITE-180 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Baptiste Mathus >Assignee: Anders Hammar > Attachments: MNGSITE-180-followup.patch, MNGSITE-180.patch > > > Hi, > As a followup to that thread of maven-users: > http://maven.40175.n5.nabble.com/Maven-plugin-trademarks-Re-Downloading-a-file-for-shipping-in-an-artifact-tt5759104.html > I'm attaching a possible patch to improve the current plugin documentation so > that people don't name their plugin maven-something-plugin without knowing > this is a very very bad idea. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-242) org.codehaus.plexus.embed.Embedder no longer exists
[ https://jira.codehaus.org/browse/MANTTASKS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330139#comment-330139 ] Dennis Lundberg commented on MANTTASKS-242: --- Which version of Maven are you using when you are trying to build Maven Ant Tasks? > org.codehaus.plexus.embed.Embedder no longer exists > --- > > Key: MANTTASKS-242 > URL: https://jira.codehaus.org/browse/MANTTASKS-242 > Project: Maven Ant Tasks > Issue Type: Bug > Components: mvn task >Affects Versions: 2.1.3 >Reporter: Orion Poplawski > > Trying to build maven-ant-tasks for Fedora 20 fails because > org.codehaus.plexus.embed.Embedder has finally been dropped. Apparently this > has been deprecated since around 2007. Has any work been done to transition > to the new API? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330142#comment-330142
]
Dennis Lundberg commented on JXR-103:
-
Hi Michael,
I seem to recall that some plugin (can't remember which one though) uses
relative references to be able to validate the files when in offline mode. I
don't know if this applies to the JXR plugin or not. Could you try running all
tests in offline mode to see if they all still pass, just to make sure?
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-730) SVN branching fails with svn+ssh://username@host URL
Raúl Wegmann created SCM-730:
Summary: SVN branching fails with svn+ssh://username@host URL
Key: SCM-730
URL: https://jira.codehaus.org/browse/SCM-730
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-svn
Affects Versions: 1.8.1
Reporter: Raúl Wegmann
Similar to SCM-696, SVN branching (e.g. when executing {{mvn release:branch}})
is failing when using a svn+ssh://username@host style URL.
See
https://github.com/rwegmann/maven-scm/commit/f72d1461ddda3169beb24f7ae361c4fdf923406c
with the one-line patch.
There may be other instances where the URL might require "fixing", but I sadly
do not have time to look into it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330152#comment-330152
]
Kurt T Stam commented on MJARSIGNER-13:
---
Hi guys, is this project dead? Just wondering if we should spend time helping
to fix this or spend time working on a using ant instead.
> signing in multi-module project fails on windows
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-242) org.codehaus.plexus.embed.Embedder no longer exists
[ https://jira.codehaus.org/browse/MANTTASKS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330169#comment-330169 ] Orion Poplawski commented on MANTTASKS-242: --- 3.1.0 > org.codehaus.plexus.embed.Embedder no longer exists > --- > > Key: MANTTASKS-242 > URL: https://jira.codehaus.org/browse/MANTTASKS-242 > Project: Maven Ant Tasks > Issue Type: Bug > Components: mvn task >Affects Versions: 2.1.3 >Reporter: Orion Poplawski > > Trying to build maven-ant-tasks for Fedora 20 fails because > org.codehaus.plexus.embed.Embedder has finally been dropped. Apparently this > has been deprecated since around 2007. Has any work been done to transition > to the new API? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-186) Link to Maven 3 compatibility notes is broken
Santiago Mola created MNGSITE-186: - Summary: Link to Maven 3 compatibility notes is broken Key: MNGSITE-186 URL: https://jira.codehaus.org/browse/MNGSITE-186 Project: Maven Project Web Site Issue Type: Bug Reporter: Santiago Mola Priority: Trivial In the download page [1] there is a broken link to Maven 3 compatibility notes [2]. The correct link seems to be this: https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes [1] https://maven.apache.org/download.cgi [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated JXR-103:
---
Attachment: jxr-offline.log
Dennis,
I ran
{noformat}
D:\Projekte\jxr-trunk>mvn --offline clean install integration-test site
-Prun-its,reporting > jxr-offline.log
{noformat}
Output is attached.
Though I would recommend to set Javadoc plugin to quiet mode. It is very chatty.
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Attachments: jxr-offline.log
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330183#comment-330183
]
Dennis Lundberg commented on JXR-103:
-
Thanks Michael, that looks good.
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Attachments: jxr-offline.log
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-242) org.codehaus.plexus.embed.Embedder no longer exists
[ https://jira.codehaus.org/browse/MANTTASKS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MANTTASKS-242: -- Environment: Maven 3.1.0 Thanks for the info. > org.codehaus.plexus.embed.Embedder no longer exists > --- > > Key: MANTTASKS-242 > URL: https://jira.codehaus.org/browse/MANTTASKS-242 > Project: Maven Ant Tasks > Issue Type: Bug > Components: mvn task >Affects Versions: 2.1.3 > Environment: Maven 3.1.0 >Reporter: Orion Poplawski > > Trying to build maven-ant-tasks for Fedora 20 fails because > org.codehaus.plexus.embed.Embedder has finally been dropped. Apparently this > has been deprecated since around 2007. Has any work been done to transition > to the new API? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330185#comment-330185
]
Robert Scholte commented on JXR-103:
[~michael-o], please always use {{verify}} instead in {{integration-test}},
since only during this phase the results are checked. In other words: in an IT
had failed, it won't break the build yet. That'll happen during the {{verify}}
phase. (And verify is much easier to type ;) )
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Attachments: jxr-offline.log
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330186#comment-330186
]
Michael Osipov commented on JXR-103:
Robert, thanks. I will re-run the tests and upload an updated log file.
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Attachments: jxr-offline.log
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (JXR-103) All DTD XHTML 1.0 Transitional references are incorrect
[
https://jira.codehaus.org/browse/JXR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated JXR-103:
---
Attachment: jxr-offline.log
> All DTD XHTML 1.0 Transitional references are incorrect
> ---
>
> Key: JXR-103
> URL: https://jira.codehaus.org/browse/JXR-103
> Project: Maven JXR
> Issue Type: Bug
> Components: jxr
>Affects Versions: 2.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.4
>
> Attachments: jxr-offline.log, jxr-offline.log
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Velocity templates contain:
> {{ "DTD/xhtml1-transitional.dtd">}}
> whereas it should be:
> {{ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-186) Link to Maven 3 compatibility notes is broken
[ https://jira.codehaus.org/browse/MNGSITE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reassigned MNGSITE-186: - Assignee: Anders Hammar > Link to Maven 3 compatibility notes is broken > - > > Key: MNGSITE-186 > URL: https://jira.codehaus.org/browse/MNGSITE-186 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Santiago Mola >Assignee: Anders Hammar >Priority: Trivial > > In the download page [1] there is a broken link to Maven 3 compatibility > notes [2]. The correct link seems to be this: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes > [1] https://maven.apache.org/download.cgi > [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-186) Link to Maven 3 compatibility notes is broken
[ https://jira.codehaus.org/browse/MNGSITE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar closed MNGSITE-186. - Resolution: Fixed Thanks! > Link to Maven 3 compatibility notes is broken > - > > Key: MNGSITE-186 > URL: https://jira.codehaus.org/browse/MNGSITE-186 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Santiago Mola >Assignee: Anders Hammar >Priority: Trivial > > In the download page [1] there is a broken link to Maven 3 compatibility > notes [2]. The correct link seems to be this: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes > [1] https://maven.apache.org/download.cgi > [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
