Release #5312

Release #4316: gCube Release 4.1.0

Release #5056: org.gcube.data-publishing.3-9-0

document-store-lib-couchdb.1-1-0

Added by Maria Di Girolamo about 3 years ago. Updated about 3 years ago.

Status:ReleasedStart date:Oct 03, 2016
Priority:HighDue date:
Assignee:Luca Frosini
Category:data-publishing
Sprint:gCube Release 4.1.0
Wiki Updates: Version Control System:
Type: Building System:
Milestones:
Duration:

Description

document-store-lib-couchdb.1-0-1-1 fails for the Build#21.
Please, could you check the compilation error at http://eticsbuild2.research-infrastructures.eu/BuildReport/bdownload/AllBuilds/org.gcube.4-1-0/BUILD_21/reports/reportModuleDetail-document-store-lib-couchdb.html :
"
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/gbuilder/workspace/document-store-lib-couchdb/src/main/java/org/gcube/documentstore/persistence/PersistenceCouchDB.java:[9,28] package org.codehaus.jackson does not exist
[ERROR] /home/gbuilder/workspace/document-store-lib-couchdb/src/main/java/org/gcube/documentstore/persistence/PersistenceCouchDB.java:[10,32] package org.codehaus.jackson.map does not exist
[ERROR] /home/gbuilder/workspace/document-store-lib-couchdb/src/main/java/org/gcube/documentstore/persistence/PersistenceCouchDB.java:[55,35] cannot find symbol
symbol: class JsonNode
location: class org.gcube.documentstore.persistence.PersistenceCouchDB.....
"


Related issues

Related to BlueBRIDGE - Project Task #700: T10.3 Federated Resources Management [Months: 1-29] Closed Mar 07, 2016 Apr 30, 2016

History

#1 Updated by Luca Frosini about 3 years ago

  • Status changed from New to Available

#2 Updated by Luca Frosini about 3 years ago

  • Status changed from Available to Under Integration

#3 Updated by Roberto Cirillo about 3 years ago

@luca.frosini@isti.cnr.it Can it be dismissed?

#4 Updated by Luca Frosini about 3 years ago

  • Related to Project Task #700: T10.3 Federated Resources Management [Months: 1-29] added

#5 Updated by Maria Di Girolamo about 3 years ago

Dear luca.frosini@crn.isti.it the release#45 fails because has been setted gcube-release as maven-repository for deployment and artefact.

The difference with the previous build (where we use gcube-staging) is that gcube-releases doesn't allow redeploy.

Now, it happened that some components (the failed ones) generated some artifacts twice (e.g. the jar with sources) due to a misconfiguration in the pom.xml. So during the build they tried to deploy twice the same artifact and this caused the error because the second time the repository did not accept it.

This is not a big deal because the build is fine and also the deployment of the first copy of the artifact.

We do not think it will affact the upgrade the production.

In any case , is it possible to update the pom with the correct configuration ?
For example you can update the pom confguration as follows:

org.apache.maven.plugins
maven-assembly-plugin

            <executions>
                <execution>
                    <id>servicearchive</id>
                    <phase>install</phase>
                    <goals>
                        <goal>single</goal>
                    </goals>
                                             <configuration>
                <descriptors>
                    <descriptor>${distroDirectory}/descriptor.xml</descriptor>
                </descriptors>
            </configuration>
                </execution>

            </executions>
        </plugin>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-assembly-plugin</artifactId>

            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>single</goal>
                    </goals>
                                     <configuration>
                <descriptorRefs>
                    <descriptorRef>jar-with-dependencies</descriptorRef>
                </descriptorRefs>
            </configuration>
                </execution>
            </executions>
        </plugin>

or to have an unique configuration for maven plugin where to include the two execution:

org.apache.maven.plugins
maven-assembly-plugin

            <executions>
                <execution>
                    <id>servicearchive</id>
                    <phase>install</phase>
                    <goals>
                        <goal>single</goal>
                    </goals>
                                             <configuration>
                <descriptors>
                    <descriptor>${distroDirectory}/descriptor.xml</descriptor>
                </descriptors>
            </configuration>
                </execution>



                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>single</goal>
                    </goals>
                                     <configuration>
                <descriptorRefs>
                    <descriptorRef>jar-with-dependencies</descriptorRef>
                </descriptorRefs>
            </configuration>
                </execution>
            </executions>
        </plugin>

Thank you, Maria.

#6 Updated by Luca Frosini about 3 years ago

I'm going to fix it

#7 Updated by Luca Frosini about 3 years ago

I made the fix, upgraded the etics configuration (i.e. the revsion number) and launched a remote build.

#8 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Under Integration to Released

Also available in: Atom PDF