Witek commented on ARIES-1549:

Hi [~gnt], thank you for closing my issue.

I still have some issues with building Aries from top-level folder:

a) {{<module>tx-control</module>}} should be removed from top-level pom
 b) *org.apache.aries.jmx.blueprint.api* ver 1.2.1 is [missing in maven 

I believe those are not blockers and are not required for Aries development.

But maybe it would be good to have some automatic build (something like travis) 
to test compilation of root-level module for every commit?


> Aries can't build from fresh sorce clone
> ----------------------------------------
>                 Key: ARIES-1549
>                 URL: https://issues.apache.org/jira/browse/ARIES-1549
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Witek
>            Assignee: Guillaume Nodet
>            Priority: Minor
>              Labels: easyfix, maven
> h4. Description
> Steps to reproduce
> 1. move aries artifacts outside local maven repository (into some _backup_ 
> location)
> 2. git clone source code from {{git://git.apache.org/aries.git}}
> 3. run {{mvn clean install -Dmaven.test.skip}} inside {{blueprint}} folder
> *actual:* build failure
> *expected:* successful installation
> h4. Proposed Fix:
> There is dependency in *org.apache.aries.blueprint* module 
> ({{.../aries/blueprint/blueprint-bundle/pom.xml}}):
> {code}
> <dependency>
>     <groupId>org.apache.aries.blueprint</groupId>
>     <artifactId>org.apache.aries.blueprint.core</artifactId>
>     <version>1.6.1-SNAPSHOT</version>
>     <scope>provided</scope>
> </dependency>
> {code}
> The version should be probably changed to 1.6.2 (last released) or 
> 1.6.3-SNAPSHOT (current)

This message was sent by Atlassian JIRA

Reply via email to