You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Tracy Nelson (JIRA)" <ji...@apache.org> on 2011/02/05 02:49:30 UTC

[jira] Created: (SM-2053) pom and repos out of sync

pom and repos out of sync
-------------------------

                 Key: SM-2053
                 URL: https://issues.apache.org/jira/browse/SM-2053
             Project: ServiceMix
          Issue Type: Bug
          Components: tooling
    Affects Versions: 4.0
         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
            Reporter: Tracy Nelson
            Priority: Minor


When building from scratch, I get several errors when building with "mvn -Dmaven.test.skip=true -Pstep1 install".  In each case, Maven can't find artifacts because they are listed as version 2011-01-SNAPSHOT in the pom, but in the repo they are located under 2011-02-SNAPSHOT.  Changing the version in the pom fixes the problem.

The affected artifacts are:
servicemix-quartz
servicemix-eip
servicemix-jsr181
servicemix-http
servicemix-wsn2005
servicemix-jms

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

        

[jira] Commented: (SM-2053) pom and repos out of sync

Posted by "Tracy Nelson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SM-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990959#comment-12990959 ] 

Tracy Nelson commented on SM-2053:
----------------------------------

That's fine with me.  Thanks!

> pom and repos out of sync
> -------------------------
>
>                 Key: SM-2053
>                 URL: https://issues.apache.org/jira/browse/SM-2053
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
>            Reporter: Tracy Nelson
>            Priority: Minor
>         Attachments: pom.diff
>
>
> When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.
> The affected artifacts are:
> {{servicemix-quartz}}
> {{servicemix-eip}}
> {{servicemix-jsr181}}
> {{servicemix-http}}
> {{servicemix-wsn2005}}
> {{servicemix-jms}}
> {{servicemix-cxf-bc}}
> {{servicemix-saxon}}
> {{servicemix-mail}}
> {{servicemix-snmp}}
> {{servicemix-smpp}}
> {{servicemix-osworkflow}}
> {{servicemix-script}}
> {{servicemix-scripting}}
> {{servicemix-validation}}
> {{servicemix-file}}
> {{servicemix-ftp}}
> {{servicemix-xmpp}}
> {{servicemix-truezip}}

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

        

[jira] Commented: (SM-2053) pom and repos out of sync

Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SM-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990939#comment-12990939 ] 

Gert Vanthienen commented on SM-2053:
-------------------------------------

Sorry for the inconvenience - this is a temporary situation caused by releases being in progress!

We're currently in the process of releasing components 2011.01.  It looks like the latest snapshot for 2011.01-SNAPSHOT has expired from the snapshot repository and the new components trunk snapshot version is 2011.02-SNAPSHOT.  The vote has been running for 3 days now and, if there are no last minute -1 votes, it's bound to get promoted into central repo somewhere in the next few hours.  After that, we can upgrade the builds to use 2011.01 and move on the rest of the releases.

If that's OK for you, I'd rather close this issue as soon you verified that the build is fixed again with the release version instead of using 2011.02-SNAPSHOT?

> pom and repos out of sync
> -------------------------
>
>                 Key: SM-2053
>                 URL: https://issues.apache.org/jira/browse/SM-2053
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
>            Reporter: Tracy Nelson
>            Priority: Minor
>         Attachments: pom.diff
>
>
> When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.
> The affected artifacts are:
> {{servicemix-quartz}}
> {{servicemix-eip}}
> {{servicemix-jsr181}}
> {{servicemix-http}}
> {{servicemix-wsn2005}}
> {{servicemix-jms}}
> {{servicemix-cxf-bc}}
> {{servicemix-saxon}}
> {{servicemix-mail}}
> {{servicemix-snmp}}
> {{servicemix-smpp}}
> {{servicemix-osworkflow}}
> {{servicemix-script}}
> {{servicemix-scripting}}
> {{servicemix-validation}}
> {{servicemix-file}}
> {{servicemix-ftp}}
> {{servicemix-xmpp}}
> {{servicemix-truezip}}

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

        

[jira] Updated: (SM-2053) pom and repos out of sync

Posted by "Tracy Nelson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SM-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tracy Nelson updated SM-2053:
-----------------------------

    Description: 
When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.

The affected artifacts are:
{{servicemix-quartz}}
{{servicemix-eip}}
{{servicemix-jsr181}}
{{servicemix-http}}
{{servicemix-wsn2005}}
{{servicemix-jms}}
{{servicemix-cxf-bc}}
{{servicemix-saxon}}
{{servicemix-mail}}
{{servicemix-snmp}}
{{servicemix-smpp}}
{{servicemix-osworkflow}}
{{servicemix-script}}
{{servicemix-scripting}}
{{servicemix-validation}}
{{servicemix-file}}
{{servicemix-ftp}}
{{servicemix-xmpp}}
{{servicemix-truezip}}

  was:
When building from scratch, I get several errors when building with "mvn -Dmaven.test.skip=true -Pstep1 install".  In each case, Maven can't find artifacts because they are listed as version 2011-01-SNAPSHOT in the pom, but in the repo they are located under 2011-02-SNAPSHOT.  Changing the version in the pom fixes the problem.

The affected artifacts are:
servicemix-quartz
servicemix-eip
servicemix-jsr181
servicemix-http
servicemix-wsn2005
servicemix-jms

     Patch Info: [Patch Available]

Added additional artifacts & patch.

> pom and repos out of sync
> -------------------------
>
>                 Key: SM-2053
>                 URL: https://issues.apache.org/jira/browse/SM-2053
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
>            Reporter: Tracy Nelson
>            Priority: Minor
>         Attachments: pom.diff
>
>
> When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.
> The affected artifacts are:
> {{servicemix-quartz}}
> {{servicemix-eip}}
> {{servicemix-jsr181}}
> {{servicemix-http}}
> {{servicemix-wsn2005}}
> {{servicemix-jms}}
> {{servicemix-cxf-bc}}
> {{servicemix-saxon}}
> {{servicemix-mail}}
> {{servicemix-snmp}}
> {{servicemix-smpp}}
> {{servicemix-osworkflow}}
> {{servicemix-script}}
> {{servicemix-scripting}}
> {{servicemix-validation}}
> {{servicemix-file}}
> {{servicemix-ftp}}
> {{servicemix-xmpp}}
> {{servicemix-truezip}}

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

        

[jira] Updated: (SM-2053) pom and repos out of sync

Posted by "Tracy Nelson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SM-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tracy Nelson updated SM-2053:
-----------------------------

    Attachment: pom.diff

Diff of pom.xml

> pom and repos out of sync
> -------------------------
>
>                 Key: SM-2053
>                 URL: https://issues.apache.org/jira/browse/SM-2053
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
>            Reporter: Tracy Nelson
>            Priority: Minor
>         Attachments: pom.diff
>
>
> When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.
> The affected artifacts are:
> {{servicemix-quartz}}
> {{servicemix-eip}}
> {{servicemix-jsr181}}
> {{servicemix-http}}
> {{servicemix-wsn2005}}
> {{servicemix-jms}}
> {{servicemix-cxf-bc}}
> {{servicemix-saxon}}
> {{servicemix-mail}}
> {{servicemix-snmp}}
> {{servicemix-smpp}}
> {{servicemix-osworkflow}}
> {{servicemix-script}}
> {{servicemix-scripting}}
> {{servicemix-validation}}
> {{servicemix-file}}
> {{servicemix-ftp}}
> {{servicemix-xmpp}}
> {{servicemix-truezip}}

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

        

[jira] Resolved: (SM-2053) pom and repos out of sync

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SM-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-2053.
--------------------------------------

    Resolution: Not A Problem
      Assignee: Jean-Baptiste Onofré

The 2011.01 components release is out now, so the problem doesn't occur.

> pom and repos out of sync
> -------------------------
>
>                 Key: SM-2053
>                 URL: https://issues.apache.org/jira/browse/SM-2053
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Linux (Ubuntu 10.04), Sun JDK 1.6.0_21, Maven 2.2.1, trunk revision 1067373
>            Reporter: Tracy Nelson
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>         Attachments: pom.diff
>
>
> When building from scratch, I get several errors when building with {{mvn -Dmaven.test.skip=true -Pstep1 install}}.  In each case, Maven can't find artifacts because they are listed as version {{2011-01-SNAPSHOT}} in the pom, but in the repo they are located under {{2011-02-SNAPSHOT}}.  Changing the version in the pom fixes the problem.
> The affected artifacts are:
> {{servicemix-quartz}}
> {{servicemix-eip}}
> {{servicemix-jsr181}}
> {{servicemix-http}}
> {{servicemix-wsn2005}}
> {{servicemix-jms}}
> {{servicemix-cxf-bc}}
> {{servicemix-saxon}}
> {{servicemix-mail}}
> {{servicemix-snmp}}
> {{servicemix-smpp}}
> {{servicemix-osworkflow}}
> {{servicemix-script}}
> {{servicemix-scripting}}
> {{servicemix-validation}}
> {{servicemix-file}}
> {{servicemix-ftp}}
> {{servicemix-xmpp}}
> {{servicemix-truezip}}

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