[jira] Commented: (MSKINS-14) Search searches only current site
[
https://jira.codehaus.org/browse/MSKINS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284850#comment-284850
]
Robert Scholte commented on MSKINS-14:
--
maybe we should change this a bit. Right now there's the option
{{enableSearch}}, but I think it should be something like:
{code:xml}
{code}
{code:xml}
struts.apache.org
{code}
> Search searches only current site
> -
>
> Key: MSKINS-14
> URL: https://jira.codehaus.org/browse/MSKINS-14
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Reporter: Christian Grobmeier
>Priority: Minor
>
> 1. Open page
> 2. click "go" on search form
> Search is done on the current webpage only, for example:
> https://www.google.com/search?sitesearch=struts.apache.org%2Findex.html&q=search...&Search=Go
> It should look like:
> https://www.google.com/search?sitesearch=struts.apache.org&q=search...&Search=Go
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-34) I cannot compile mixing modules and dependencies
[
https://issues.apache.org/jira/browse/MPOM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MPOM-34.
Resolution: Invalid
Sorry, this is the wrong project to file this under - it is for reporting
problems with the Apache parent POMs.
You can try asking this question on us...@maven.apache.org, or if you are sure
that it is a bug you can file it in http://jira.codehaus.org/browse/MNG.
Thanks!
> I cannot compile mixing modules and dependencies
>
>
> Key: MPOM-34
> URL: https://issues.apache.org/jira/browse/MPOM-34
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Environment: maven 3.0.3
>Reporter: Luca Stancapiano
> Attachments: exampletest.zip
>
>
> I have three two simple projects:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> ../pom.xml
>
> 4.0.0
> my-mioprogetto
> Mio progetto
>
>
>
> ${project.groupId}
> my-mioprogetto2
> ${project.version}
>
>
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> ../pom.xml
>
> 4.0.0
> my-mioprogetto2
> Mio progetto 2
>
> and one parent project:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> prova
> Mioframework
> 0.4.0-SNAPSHOT
> Mioframework
> pom
>
> mioprogetto
> mioprogetto2
>
>
> mioprogetto as mioprogetto2 as dependency. Mioframework has the two projects
> as modules.
> If I compile mioframework I have no problems.
> If I compile only mioprogetto2 I have no problems.
> If I compile only mioprogetto I have problems because the dependency is not
> matched. Here the error:
> [ERROR] Failed to execute goal on project my-mioprogetto: Could not resolve
> dependencies for project prova:my-mioprogetto:jar:0.4.0-SNAPSHOT: Could not
> find artifact prova:my-mioprogetto2:jar:0.4.0-SNAPSHOT in myrepo-xxx
> (http://repository.x) -> [Help 1]
> I attach the complete example test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-651) HgChangeLogCommand ignores ScmBranch
HgChangeLogCommand ignores ScmBranch Key: SCM-651 URL: https://jira.codehaus.org/browse/SCM-651 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.6 Reporter: Henning Schmiedehausen Attachments: hg-branch.patch Passing an ScmBranch object into the HgChangeLogCommand has no effect. It should select only the log messages for that branch. The attached patch fixes that behaviour. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (SUREFIRE-793) JUnit47 provider reports incorrect time in the XML report
[
https://jira.codehaus.org/browse/SUREFIRE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nkeywal reopened SUREFIRE-793:
--
I still have a wrong reported time in the xml file on 2.12-snapshot:
With JUnit47:
{noformat}
{noformat}
With JUnit4:
{noformat}
[skip properties]
{noformat}
> JUnit47 provider reports incorrect time in the XML report
> -
>
> Key: SUREFIRE-793
> URL: https://jira.codehaus.org/browse/SUREFIRE-793
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10, 2.11
> Environment: all
>Reporter: nkeywal
>Assignee: Kristian Rosenvold
>Priority: Critical
> Fix For: 2.11
>
> Attachments: surefire_793_trunk.v3.patch
>
>
> With this test:
> {noformat}
> public class Test0 {
> @Test
> public void testT0() throws Exception {
> Thread.sleep(2000);
> }
> }
> {noformat}
> The time presented in the XML report is wrong (close to zero), both for the
> total time and the time spent in the method. It's a side effect of the replay
> mechanism. I can't make it working without hacking the code quite a lot and
> probably breaking the other use cases, so a clean fix would be really
> appreciated. The complete test case would include before & after stuff, like
> this:
> {noformat}
> public class Test0 {
> @Test
> public void testT0() throws Exception {
> Thread.sleep(2000);
> }
> @Test
> public void testT1() throws Exception {
> Thread.sleep(2000);
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> Thread.sleep(2000);
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> Thread.sleep(2000);
> }
> @Before
> public void setUp() throws Exception {
> Thread.sleep(2000);
> }
> @After
> public void tearDown() throws Exception {
> Thread.sleep(2000);
> }
> }
> {noformat}
> The data are correct (at least individual method time) when using JUnit4
> provider.
> It's important, because the XML reports are used by Jenkins, and the test
> time is something we monitor very carefully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
