NanoContainer
  1. NanoContainer
  2. NANO-135

M2 compatibility

          Details

          • Type: Task Task
          • Status: Resolved Resolved
          • Priority: Minor Minor
          • Resolution: Fixed
          • Affects Version/s: 1.0-beta-4
          • Fix Version/s: None
          • Component/s: None
          • Labels:
            None
          • Number of attachments :
            0

            Description

            The distributes POMs are not self-contained and cannot be used for M2. We may have to fix the old onces and must think about the build process.

              Issue Links

              depends upon

              Improvement - An improvement or enhancement to an existing feature or task. MAVEN-1390 POM example <extends> doco is non-portable

              • Blocker - Blocks development and/or testing work, production could not run
              • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

              Task - A task that needs to be done. MEV-3 Broken dependencies for nanocontainer

              • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

                Activity

                Jörg Schaible made changes -
                Field Original Value New Value
                Link This issue depends upon MEV-3 [ MEV-3 ]
                Jörg Schaible made changes -
                Link This issue depends upon MAVEN-1390 [ MAVEN-1390 ]
                Hide
                Permalink
                Jörg Schaible added a comment -

                According to MPARTIFACT-40 we could give the artifact plugin 1.5 a try.

                Show
                Jörg Schaible added a comment - According to MPARTIFACT-40 we could give the artifact plugin 1.5 a try.
                Hide
                Permalink
                Mauro Talevi added a comment -

                Added maven-artifact-plugin-1.5 dependency.

                Other m1->m2 config changes to project.xml to facilitate m2 migration:

                • set scope as dependency properties, eg:

                <dependency>
                <id>junit</id>
                <version>3.7</version>
                <properties>
                <scope>test</scope>
                </properties>
                </dependency>

                Scopes detailed in
                http://maven.apache.org/maven2/dependency-mechanism.html#dependency_scope

                Show
                Mauro Talevi added a comment - Added maven-artifact-plugin-1.5 dependency. Other m1->m2 config changes to project.xml to facilitate m2 migration: set scope as dependency properties, eg: <dependency> <id>junit</id> <version>3.7</version> <properties> <scope>test</scope> </properties> </dependency> Scopes detailed in http://maven.apache.org/maven2/dependency-mechanism.html#dependency_scope
                Hide
                Permalink
                Jörg Schaible added a comment -

                Brett recommended latest version 1.5.2 though ...

                Show
                Jörg Schaible added a comment - Brett recommended latest version 1.5.2 though ...
                Hide
                Permalink
                Mauro Talevi added a comment -

                Updated all pico/nano/micro projects to use 1.6 (latest stable release).

                Show
                Mauro Talevi added a comment - Updated all pico/nano/micro projects to use 1.6 (latest stable release).
                Hide
                Permalink
                Jörg Schaible added a comment -

                Bad. 1.6 is M1.1 only. 1.5.2 is latest stable for M1.0.2 (according Brett). Stops me from building with Maven.

                BTW: Shouldn't beaver.directory point to /home/projects/(nano|pico)container/dist/ ?

                Show
                Jörg Schaible added a comment - Bad. 1.6 is M1.1 only. 1.5.2 is latest stable for M1.0.2 (according Brett). Stops me from building with Maven. BTW: Shouldn't beaver.directory point to /home/projects/(nano|pico)container/dist/ ?
                Hide
                Permalink
                Mauro Talevi added a comment -

                Oops They should state that in the release notes.
                Reverted to use 1.5.2.

                Note that /dist/xxxxcontainer -> /home/projects/xxxxcontainer/dist

                I'm not fussed as to which we use.

                Show
                Mauro Talevi added a comment - Oops They should state that in the release notes. Reverted to use 1.5.2. Note that /dist/xxxxcontainer -> /home/projects/xxxxcontainer/dist I'm not fussed as to which we use.
                Hide
                Permalink
                Jörg Schaible added a comment -

                maven-artifact-1.5.2 resolves poms now.

                Show
                Jörg Schaible added a comment - maven-artifact-1.5.2 resolves poms now.
                Jörg Schaible made changes -
                Status Open [ 1 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Jörg Schaible
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: