headers
Honnix Liang (JIRA | 1 Dec 2011 04:01

[jira] Created: (MVERSIONS-170) use-latest-snapshots does not respect -DallowIncrementalUpdates=false

use-latest-snapshots does not respect -DallowIncrementalUpdates=false
---------------------------------------------------------------------

                 Key: MVERSIONS-170
                 URL: https://jira.codehaus.org/browse/MVERSIONS-170
             Project: Maven 2.x Versions Plugin
          Issue Type: Bug
    Affects Versions: 1.2
         Environment: Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800)
Maven home: /usr/share/maven
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"

            Reporter: Honnix Liang

I have a few branches in my project A, and thus a few different versions of artifacts, say they're:

1.0.0
1.0.0-pc1-SNAPSHOT
1.0.0-pc2-SNAPSHOT
1.0.0-pc3-SNAPSHOT
1.0.1-SNAPSHOT

And another project B depends on A.

Consider following situation:

B depends on A:1.0.0, and now I need to make it depend on A:1.0.0-pc3-SNAPSHOT.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brett Porter (JIRA | 1 Dec 2011 09:09

[jira] Moved: (MOJO-1787) A mistake in wagon-maven-plugin user guide


     [
https://jira.codehaus.org/browse/MOJO-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved WAGON-360 to MOJO-1787:
------------------------------------------

           Complexity: Intermediate
          Component/s:     (was: Documentation)
                       wagon
    Affects Version/s:     (was: 1.0-beta-3)
                  Key: MOJO-1787  (was: WAGON-360)
              Project: Mojo  (was: Maven Wagon)

> A mistake in wagon-maven-plugin user guide
> ------------------------------------------
>
>                 Key: MOJO-1787
>                 URL: https://jira.codehaus.org/browse/MOJO-1787
>             Project: Mojo
>          Issue Type: Bug
>          Components: wagon
>            Reporter: devinhan
>            Priority: Critical
>
> Hi,
> Please see this link: http://mojo.codehaus.org/wagon-maven-plugin/usage.html
> in the "Configuration example to download." part
>  <artifactId>maven-wagon-plugin</artifactId>
> should be:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brett Porter (JIRA | 1 Dec 2011 09:13

[jira] Closed: (MOJO-1787) A mistake in wagon-maven-plugin user guide


     [
https://jira.codehaus.org/browse/MOJO-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MOJO-1787.
------------------------------

    Resolution: Duplicate
      Assignee: Brett Porter

> A mistake in wagon-maven-plugin user guide
> ------------------------------------------
>
>                 Key: MOJO-1787
>                 URL: https://jira.codehaus.org/browse/MOJO-1787
>             Project: Mojo
>          Issue Type: Bug
>          Components: wagon
>            Reporter: devinhan
>            Assignee: Brett Porter
>            Priority: Critical
>
> Hi,
> Please see this link: http://mojo.codehaus.org/wagon-maven-plugin/usage.html
> in the "Configuration example to download." part
>  <artifactId>maven-wagon-plugin</artifactId>
> should be:
>  <artifactId>wagon-maven-plugin</artifactId>
> Isn't it?
> Devin
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexis Li (JIRA | 1 Dec 2011 14:03

[jira] Commented: (MOJO-1785) lesscss-maven-plugin: provide m2e lifecycle-mapping


    [
https://jira.codehaus.org/browse/MOJO-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284681#comment-284681
] 

Alexis Li commented on MOJO-1785:
---------------------------------

Hi Chris, my apologies. I should have said that this is in anticipation of m2e 1.1.

I think that page is describing building an Eclipse plugin to act as an m2e extension. If you can figure out
how to do that and want to do it, that'd certainly help in the short term.

The only change I made to the pom.xml was to add a new dependency on
org.sonatype.plexus:plexus-build-api:0.0.7. I'll attach a new patch.

> lesscss-maven-plugin: provide m2e lifecycle-mapping
> ---------------------------------------------------
>
>                 Key: MOJO-1785
>                 URL: https://jira.codehaus.org/browse/MOJO-1785
>             Project: Mojo
>          Issue Type: New Feature
>          Components: _General
>         Environment: Eclipse
>            Reporter: Alexis Li
>         Attachments: lesscss-maven-plugin.zip, mojo1785-1.patch, mojo1785.patch
>
>
> I use m2e to use Maven within Eclipse. This requires a little special support from plugins so that
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexis Li (JIRA | 1 Dec 2011 14:03

[jira] Updated: (MOJO-1785) lesscss-maven-plugin: provide m2e lifecycle-mapping


     [
https://jira.codehaus.org/browse/MOJO-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexis Li updated MOJO-1785:
----------------------------

    Attachment: mojo1785-1.patch

> lesscss-maven-plugin: provide m2e lifecycle-mapping
> ---------------------------------------------------
>
>                 Key: MOJO-1785
>                 URL: https://jira.codehaus.org/browse/MOJO-1785
>             Project: Mojo
>          Issue Type: New Feature
>          Components: _General
>         Environment: Eclipse
>            Reporter: Alexis Li
>         Attachments: lesscss-maven-plugin.zip, mojo1785-1.patch, mojo1785.patch
>
>
> I use m2e to use Maven within Eclipse. This requires a little special support from plugins so that
incremental build works properly. I'd like the lesscss-maven-plugin to add this support.
> The necessary changes are best documented here: http://wiki.eclipse.org/M2E_compatible_maven_plugins
> In short, META-INF/m2e/lifecycle-mapping-metadata.xml needs to be added and the plexus-build-api
BuildContext used.
> I've attached some modifications which should get most of the way there, however I can't figure out how to
fix the Mockito or integration tests sorry. Eclipse complains that "when( buildContext.newScanner(
sourceDirectory ) ).thenReturn( ... )" is ambiguous and it's not clear how to fix it. I tried some of the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kent Soelvsten (JIRA | 1 Dec 2011 14:38

[jira] Created: (MOJO-1788) Upgrade chronos to use oarent pom version 29

Upgrade chronos to use oarent pom version 29
--------------------------------------------

                 Key: MOJO-1788
                 URL: https://jira.codehaus.org/browse/MOJO-1788
             Project: Mojo
          Issue Type: Improvement
          Components: chronos
    Affects Versions: chronos-modules-1.0-beta-1
            Reporter: Kent Soelvsten
            Assignee: Kent Soelvsten
            Priority: Minor

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 4 comments |
headers
Kent Soelvsten (JIRA | 1 Dec 2011 14:38

[jira] Updated: (MOJO-1788) Upgrade chronos to use parent pom version 29


     [
https://jira.codehaus.org/browse/MOJO-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kent Soelvsten updated MOJO-1788:
---------------------------------

    Summary: Upgrade chronos to use parent pom version 29  (was: Upgrade chronos to use oarent pom version 29)

> Upgrade chronos to use parent pom version 29
> --------------------------------------------
>
>                 Key: MOJO-1788
>                 URL: https://jira.codehaus.org/browse/MOJO-1788
>             Project: Mojo
>          Issue Type: Improvement
>          Components: chronos
>    Affects Versions: chronos-modules-1.0-beta-1
>            Reporter: Kent Soelvsten
>            Assignee: Kent Soelvsten
>            Priority: Minor
>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kent Soelvsten (JIRA | 1 Dec 2011 14:40

[jira] Closed: (MOJO-1788) Upgrade chronos to use parent pom version 29


     [
https://jira.codehaus.org/browse/MOJO-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kent Soelvsten closed MOJO-1788.
--------------------------------

       Resolution: Fixed
    Fix Version/s: chronos-modules-1.0-beta-3

> Upgrade chronos to use parent pom version 29
> --------------------------------------------
>
>                 Key: MOJO-1788
>                 URL: https://jira.codehaus.org/browse/MOJO-1788
>             Project: Mojo
>          Issue Type: Improvement
>          Components: chronos
>    Affects Versions: chronos-modules-1.0-beta-1
>            Reporter: Kent Soelvsten
>            Assignee: Kent Soelvsten
>            Priority: Minor
>             Fix For: chronos-modules-1.0-beta-3
>
>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kent Soelvsten (JIRA | 1 Dec 2011 14:42

[jira] Created: (MOJO-1789) Upgrade chronos to use jdom 1.1.2

Upgrade chronos to use jdom 1.1.2
---------------------------------

                 Key: MOJO-1789
                 URL: https://jira.codehaus.org/browse/MOJO-1789
             Project: Mojo
          Issue Type: Bug
          Components: chronos
    Affects Versions: chronos-modules-1.0-beta-1
            Reporter: Kent Soelvsten
            Assignee: Kent Soelvsten

chronos currently uses jdom-1.1.1. unfortunately this veriosn has been removed from central
repositories. Upgrade to use the newly released jdom -1.1.2.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 3 comments |
headers
Kent Soelvsten (JIRA | 1 Dec 2011 14:42

[jira] Closed: (MOJO-1789) Upgrade chronos to use jdom 1.1.2


     [
https://jira.codehaus.org/browse/MOJO-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kent Soelvsten closed MOJO-1789.
--------------------------------

       Resolution: Fixed
    Fix Version/s: chronos-modules-1.0-beta-3

> Upgrade chronos to use jdom 1.1.2
> ---------------------------------
>
>                 Key: MOJO-1789
>                 URL: https://jira.codehaus.org/browse/MOJO-1789
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>    Affects Versions: chronos-modules-1.0-beta-1
>            Reporter: Kent Soelvsten
>            Assignee: Kent Soelvsten
>             Fix For: chronos-modules-1.0-beta-3
>
>
> chronos currently uses jdom-1.1.1. unfortunately this veriosn has been removed from central
repositories. Upgrade to use the newly released jdom -1.1.2.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |

Gmane