[jira] (MSKINS-31) If you have no body you get error on rendering
Conny Kreyssel created MSKINS-31: Summary: If you have no body you get error on rendering Key: MSKINS-31 URL: https://jira.codehaus.org/browse/MSKINS-31 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Reporter: Conny Kreyssel If you have a single project and you doesnt define a body element in site.xml you get the following error: [ERROR] Left side ($decoration.body.links.size()) of '' operation has null value. Operation not possible. META-INF/maven/site.vm [line 842, column 67] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-32) Use ${project.name} as default for bannerLeft
Conny Kreyssel created MSKINS-32:
Summary: Use ${project.name} as default for bannerLeft
Key: MSKINS-32
URL: https://jira.codehaus.org/browse/MSKINS-32
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Reporter: Conny Kreyssel
If you doesnt define a bannerLeft you get no title on top.
If you do this with the default-skin, its renders the ${project.name} instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-829) junit | Support inheritance while running test cases belonging to a particular category/group
[ https://jira.codehaus.org/browse/SUREFIRE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayathri Muralidharan updated SUREFIRE-829: --- Attachment: SUREFIRE-829-common-junit48.patch Attaching the patch. Changes have been made on 2.13-SNAPSHOT (trunk version). Modified an existing test case to test the new change as well Thanks, Gayathri junit | Support inheritance while running test cases belonging to a particular category/group - Key: SUREFIRE-829 URL: https://jira.codehaus.org/browse/SUREFIRE-829 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Reporter: Gayathri Muralidharan Attachments: SUREFIRE-829-common-junit48.patch We have a parent class which is extended by all the unit test cases (multi module maven based project) It would be great if surefire plugin config looks for the category in parent class as well. This will avoid redundant @Category(UnitTestCategory.class) annotations, as we expect all unit test cases to extend the corresponding base class and the base class will alone be annotated with @Category(UnitTestCategory.class) Please let me know if this can be achieved by any other config. Thanks, Gayathri -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-31) If you have no body you get error on rendering
[ https://jira.codehaus.org/browse/MSKINS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294302#comment-294302 ] Simone Tripodi commented on MSKINS-31: -- good, that means that the skins assumes $decoration.body exists, which is a wrong assumption. I have to add a check! Thanks for reporting! If you have no body you get error on rendering Key: MSKINS-31 URL: https://jira.codehaus.org/browse/MSKINS-31 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Reporter: Conny Kreyssel Assignee: Simone Tripodi If you have a single project and you doesnt define a body element in site.xml you get the following error: [ERROR] Left side ($decoration.body.links.size()) of '' operation has null value. Operation not possible. META-INF/maven/site.vm [line 842, column 67] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-32) Use ${project.name} as default for bannerLeft
[
https://jira.codehaus.org/browse/MSKINS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294301#comment-294301
]
Simone Tripodi commented on MSKINS-32:
--
good catch! I always wondered why fluido rendered sites looked with less
elements! :D
I'm going to fix it ASAP!
Use ${project.name} as default for bannerLeft
-
Key: MSKINS-32
URL: https://jira.codehaus.org/browse/MSKINS-32
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Reporter: Conny Kreyssel
Assignee: Simone Tripodi
If you doesnt define a bannerLeft you get no title on top.
If you do this with the default-skin, its renders the ${project.name} instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGELOG-125) Support regexp capturing group in issueIDRegexPattern configuration property
[
https://jira.codehaus.org/browse/MCHANGELOG-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294309#comment-294309
]
Markus Spann commented on MCHANGELOG-125:
-
I'm totally with Eric on this issue. A single capturing group as described
would be most helpful.
Our tickets are incrementing integers. The regex \d{2,} is really too fuzzy.
Support regexp capturing group in issueIDRegexPattern configuration property
Key: MCHANGELOG-125
URL: https://jira.codehaus.org/browse/MCHANGELOG-125
Project: Maven 2.x Changelog Plugin
Issue Type: Improvement
Affects Versions: 2.3
Environment: Any
Reporter: Eric Blanchard
In order to support more complex issue id detection in changelog comments, I
propose to support regexp capturing group in issueIDRegexPattern /
configuration property.
For example, with a Trac Issues Management System, I use
issueIDRegexPattern#(\d+)/issueIDRegexPattern
issueLinkUrlhttp://trac.host/path/to/trac/project/ticket/%ISSUE%/issueLinkUrl
and the %ISSUE% keyword will be replaced by the issue number (without the
prefixing '#')
I have successfully tested a simple modification of ChangeLogReport.java /
sinkIssueLink() / line: 1319
replace:
String match = matcher.group();
by:
String match;
if(matcher.groupCount() == 1) {
match = matcher.group(1);
} else {
match = matcher.group();
}
Hope this little modification can be adopted and put in 2.3 release.
Best regards.
--
Eric
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-586) Using -Declipse.projectNameTemplate is broken on multi module projects
[
https://jira.codehaus.org/browse/MECLIPSE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294314#comment-294314
]
Max Bowsher commented on MECLIPSE-586:
--
This regression was introduced in r727620.
To fix, just delete the code which does the wrong thing from EclipsePlugin.java:
MavenProject reactorProject = getReactorProject( artifact );
if ( reactorProject != null )
{
return IdeUtils.getProjectName(
getProjectNameTemplateForMavenProject( reactorProject ), artifact );
}
Using -Declipse.projectNameTemplate is broken on multi module projects
--
Key: MECLIPSE-586
URL: https://jira.codehaus.org/browse/MECLIPSE-586
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : .project, Core : Dependencies resolution and
build path (.classpath), Core : Multi-projects
Affects Versions: 2.6, 2.7
Environment: Maven version: 2.0.9
Java version: 1.6.0_10-rc
OS name: linux version: 2.6.27-14-generic arch: amd64 Family: unix
Reporter: Baard Johansen
In version 2.5.1 when specifying projectNameTemplate on the commandline, the
.project file and references are generated correcly. In 2.6 and 2.7 the
project has the correct name, but referenced projects is not using the
specified pattern. This renderes the .project-file and .classpath useless.
Example (using mvn eclipse:eclipse
-Declipse.projectNameTemplate=trunk-[artifactId]) where moduleA depends on
moduleB:
moduleA/.project
projectDescription
nametrunk-moduleA/name
projects
projectmoduleB/project
/projects
[..]
/projectDescription
moduleA/.classpath
classpath
[..]
classpathentry kind=src path=/moduleB/
/classpath
moduleB/.project
projectDescription
nametrunk-moduleB/name
[..]
/projectDescription
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-28) Make it possible to center powered by logos in sidebar
[ https://jira.codehaus.org/browse/MSKINS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294318#comment-294318 ] Andreas Sewe commented on MSKINS-28: Thanks, Bruno. That solves the problem for one project. It gets tedious, however, if you have dozens of them, as a custom site.css is not inherited. (At least, I don't know a way to inherit a resource from parent to child project.) Make it possible to center powered by logos in sidebar Key: MSKINS-28 URL: https://jira.codehaus.org/browse/MSKINS-28 Project: Maven Skins Issue Type: Wish Components: Fluido Skin Affects Versions: fluido-1.1 Reporter: Andreas Sewe Priority: Minor Left alignment may look OK for badge-like logos like http://maven.apache.org/skins/maven-fluido-skin/images/logos/maven-feather.png, but is quite ugly for other types of logo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-851) Error with a JUnit test using surefire plugin
Martin Simons created SUREFIRE-851: -- Summary: Error with a JUnit test using surefire plugin Key: SUREFIRE-851 URL: https://jira.codehaus.org/browse/SUREFIRE-851 Project: Maven Surefire Issue Type: Bug Components: classloading, Junit 4.x support, Maven Surefire Plugin Affects Versions: 2.12 Environment: Ubuntu 10.04 64 bit Reporter: Martin Simons Attachments: output I am attempting to run a junit test against a JAX-WS service method using a simple client class and compiled generated sources from ws-import. When the test is run through surefire while doing either test or install I get the error java.lang.NoSuchMethodError: com.sun.xml.ws.api.model.SEIModel.getJAXBContext()Lcom/sun/xml/bind/api/JAXBRIContext; but when I inspect the xml in the surefire reports directory and use java and junit directly on the command line using the classpath and bootclasspath outlined in the xml file (and, of course, the same version of junit and the same version of java) the test is successful. What is (or could be) the problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MAVENUPLOAD-2819) Upload request for new version of jcifs: 1.3.17
[ https://jira.codehaus.org/browse/MAVENUPLOAD-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294329#comment-294329 ] Joel Orlina commented on MAVENUPLOAD-2819: -- This project is no longer in use for Maven Upload Requests. If you are trying to deploy your own project to the Central Repository, consider using OSSRH: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide If you need a 3rd-party artifact on which your project depends, see: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central Upload request for new version of jcifs: 1.3.17 --- Key: MAVENUPLOAD-2819 URL: https://jira.codehaus.org/browse/MAVENUPLOAD-2819 Project: Maven Upload Requests Issue Type: Wish Reporter: Pontus Ullgren Attachments: jcifs-1.3.17-bundle.jar http://jcifs.samba.org/ JCIFS is an Open Source client library that implements the CIFS/SMB networking protocol in 100% Java. CIFS is the standard file sharing protocol on the Microsoft Windows platform (e.g. Map Network Drive ...). This client is used extensively in production on large Intranets. The bundle jar with a classes jar, sources jar and java-doc jar, is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-32) Use ${project.name} as default for bannerLeft
[
https://jira.codehaus.org/browse/MSKINS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294363#comment-294363
]
Simone Tripodi commented on MSKINS-32:
--
Hi Conny,
I am a little confused - I copied the banner behavior from the default doxia
[site
renderer|https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site.vm]
and if I am reading right, if no image is defined, the skin tries to render
{{$banner.name}} that is defined in {{site.xml}}.
Am I missing something? Can you point me please to an OSS projects where I can
see the described behavior with the default skin?
Many thanks in advance!
Use ${project.name} as default for bannerLeft
-
Key: MSKINS-32
URL: https://jira.codehaus.org/browse/MSKINS-32
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Reporter: Conny Kreyssel
Assignee: Simone Tripodi
If you doesnt define a bannerLeft you get no title on top.
If you do this with the default-skin, its renders the ${project.name} instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-851) Error with a JUnit test using surefire plugin
[ https://jira.codehaus.org/browse/SUREFIRE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294367#comment-294367 ] Kristian Rosenvold commented on SUREFIRE-851: - Which forkmode did you try? Error with a JUnit test using surefire plugin - Key: SUREFIRE-851 URL: https://jira.codehaus.org/browse/SUREFIRE-851 Project: Maven Surefire Issue Type: Bug Components: classloading, Junit 4.x support, Maven Surefire Plugin Affects Versions: 2.12 Environment: Ubuntu 10.04 64 bit Reporter: Martin Simons Attachments: output I am attempting to run a junit test against a JAX-WS service method using a simple client class and compiled generated sources from ws-import. When the test is run through surefire while doing either test or install I get the error java.lang.NoSuchMethodError: com.sun.xml.ws.api.model.SEIModel.getJAXBContext()Lcom/sun/xml/bind/api/JAXBRIContext; but when I inspect the xml in the surefire reports directory and use java and junit directly on the command line using the classpath and bootclasspath outlined in the xml file (and, of course, the same version of junit and the same version of java) the test is successful. What is (or could be) the problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-483) PrepareReleaseMojo always increments development version
[ https://jira.codehaus.org/browse/MRELEASE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-483. --- Resolution: Cannot Reproduce This one seem already to be fixed in the past. I've added a test in [rev. 1301781|http://svn.apache.org/viewvc?rev=1301781view=rev] to prevent regression. PrepareReleaseMojo always increments development version Key: MRELEASE-483 URL: https://jira.codehaus.org/browse/MRELEASE-483 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Environment: Mac Reporter: Noah Vihinen Assignee: Robert Scholte PrepareReleaseMojo always increments development version For example, if the latest development version is 1.3-SNAPSHOT. mvn --batch-mode -Dtag=yflex_library-1.0.1237 -DreleaseVersion=1.0.1237 -DdevelopmentVersion=1.0-SNAPSHOT release:prepare mvn --batch-mode -Dtag=yflex_library-1.0.1237 -DreleaseVersion=1.0.1237 -Dproject.dev.yahoo.yinst.yflex_library:yflex_library=1.0-SNAPSHOT release:prepare results in this line in the generated release.properties project.dev.yahoo.yinst.yflex_library\:yflex_library=1.4-SNAPSHOT even though I specified the development version to be 1.0-SNAPSHOT. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-303) Resolved SNAPSHOT versions are overwritten
[
https://jira.codehaus.org/browse/MRELEASE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-303.
---
Resolution: Duplicate
Assignee: Robert Scholte
Duplicate of MRELEASE-589, already fixed in version 2.1
Resolved SNAPSHOT versions are overwritten
--
Key: MRELEASE-303
URL: https://jira.codehaus.org/browse/MRELEASE-303
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0-beta-8
Reporter: Jean-Philippe Steck
Assignee: Robert Scholte
When running release:prepare on a parent-child projet, I'm asked to resolved
the SNAPSHOT version but some of my answers are ignored.
Cause is :
In this method : CheckDependencySnapshotsPhase.resolveSnapshots
Lig 367 : releaseDescriptor.setResolvedSnapshotDependencies(
resolvedSnapshots );
This line overwrite the map of resolved snapshot of the releaseDescriptor :
The newly resolved informations should be added to the existing map.
It should be smthg like :
for (resolvedSnapshots ) {
if (! eleaseDescriptor.getResolvedSnapshotDependencies().contains(key))
releaseDescriptor.getResolvedSnapshotDependencies().put(resolvedSnapshots.key,
resolvedSnapshots .value)
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-97) make release:perform upload progress overwrite the previous xxK/yyK uploaded line
[ https://jira.codehaus.org/browse/MRELEASE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-97. -- Resolution: Fixed Fix Version/s: 2.3 Assignee: Robert Scholte I don't see this kind of lines anymore. This is probably due to MRELEASE-744. make release:perform upload progress overwrite the previous xxK/yyK uploaded line - Key: MRELEASE-97 URL: https://jira.codehaus.org/browse/MRELEASE-97 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: prepare Affects Versions: 2.0-beta-4 Environment: maven 2.0.4, head versions of all plugins, win xp, sun jdk 1.5.0_06 Reporter: Marcel Schutte Assignee: Robert Scholte Fix For: 2.3 Attachments: maven-release-plugin.diff, plexus-utils.diff, ReleaseTestWEB.zip The current CommandLineUtils.executeCommandLine() in plexus-utils uses the StreamPumper class to copy the output of the 'mvn deploy' call. Because this class is line based, it cannot distinguish between a standard newline and a '\r'. Because of this the upload progress doesn't overwrite itself as the download progress usually does, but writes each step on a new line (see MRELEASE-55). I've created 2 patches, one for the release-plugin itself and one for plexus-utils. I'm submitting the plexus-utils patch here as well, because of the direct relation with this report. To test, replace the plexus-utils-1.1.jar in m2_home/core with the newly built plexus-utils-1.2-SNAPSHOT.jar. After this, import the web project in ReleaseTestWEB.zip into CVS and update the scm url in the pom. Perform a release:prepare and release:perform and verify that the upload counter stays on the same line. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-120) Username is completely ignored
[ https://jira.codehaus.org/browse/MRELEASE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-120: Component/s: documentation Username is completely ignored -- Key: MRELEASE-120 URL: https://jira.codehaus.org/browse/MRELEASE-120 Project: Maven 2.x Release Plugin Issue Type: Bug Components: documentation, scm Affects Versions: 2.0-beta-4 Reporter: Matthew Beermann Priority: Critical Labels: scrub-review-started When I run something like mvn release:prepare -DdryRun=true -Dusername=mb011000, the resulting contents of release.properties suggest that the username is being completely ignored when forming the scm.url: scm.username=mb011000 scm.url=scm\:cvs\:pserver\:anonymous\:@prdwebdev17\:/projects\:system-core Note that the anonymous has stuck around for some reason. This may be related to MRELEASE-83 and/or MRELEASE-107, but I don't think it's a duplicate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-139) -X and -e command line parameters are not passed to sublevel buil
[ https://jira.codehaus.org/browse/MRELEASE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-139. --- Resolution: Not A Bug Assignee: Robert Scholte Close it based on the comment of Patrick -X and -e command line parameters are not passed to sublevel buil - Key: MRELEASE-139 URL: https://jira.codehaus.org/browse/MRELEASE-139 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: perform Affects Versions: 2.0-beta-4 Reporter: Gilles Scokart Assignee: Robert Scholte When I launch mvn release:perform, I have the error and the tracing for the top level build, but not for the sub build After the trace : [INFO] Executing: mvn deploy --no-plugin-updates -DperformRelease=true I only have normal output until the execution return to the top level. If the subbuild fails, it is hard to investigate why (I know, it should not, but in my case, it does... :-( ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
