Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LCOM #6

Closed
yegor256 opened this issue Oct 18, 2017 · 8 comments
Closed

LCOM #6

yegor256 opened this issue Oct 18, 2017 · 8 comments

Comments

@yegor256
Copy link
Member

yegor256 commented Oct 18, 2017 •
edited
Loading

Let's implement LCOM cohesion metric.

S. R. Chidamber and C. F. Kemerer, A metrics suite for object oriented design. IEEE Transactions on Software Engineering, vol.20, no.6, 1994.

http://www.pitt.edu/~ckemerer/CK%20research%20papers/MetricForOOD_ChidamberKemerer94.pdf

Shyam R. Chidamber, Chris F. Kemerer. A Metrics suite for Object Oriented design. M.I.T. Sloan School of Management E53-315. 1993. http://uweb.txstate.edu/~mg43/CS5391/Papers/Metrics/OOMetrics.pdf

Victor Basili, Lionel Briand and Walcelio Melo. A Validation of Object-Oriented Design Metrics as Quality Indicators. IEEE Transactions on Software Engineering. Vol. 22, No. 10, October 1996. http://www.cs.umd.edu/users/basili/publications/journals/J60.pdf

Bindu S. Gupta: A Critique of Cohesion Measures in the Object-Oriented Paradigm. Master of Science Thesis. Michigan Technological University, Department of Computer Science. 1997.
@yegor256 yegor256 changed the title LCOM1 LCOM Oct 18, 2017
yegor256 added a commit that referenced this issue Oct 18, 2017
@yegor256
#6 JavassistClasses
a69f581
yegor256 added a commit that referenced this issue Oct 18, 2017
@yegor256
#6 LCOM works
84aa766
yegor256 added a commit that referenced this issue Oct 18, 2017
@yegor256
#6 LCOM in App
8d3cb92
@yegor256
Copy link
Member Author

@rultor release, tag is 0.2

@rultor
Copy link
Collaborator

rultor commented Oct 18, 2017

@rultor release, tag is 0.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Oct 18, 2017

@rultor release, tag is 0.2

@yegor256 Oops, I failed. You can see the full log here (spent 11min)

Uploading: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-javadoc.jar.asc
473/473 B   
            
Uploaded: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-javadoc.jar.asc (473 B at 3.7 KB/sec)
Uploading: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-javadoc.jar
2/73 KB     
4/73 KB   
6/73 KB   
8/73 KB   
10/73 KB   
12/73 KB   
14/73 KB   
16/73 KB   
18/73 KB   
20/73 KB   
22/73 KB   
24/73 KB   
26/73 KB   
28/73 KB   
30/73 KB   
32/73 KB   
34/73 KB   
36/73 KB   
38/73 KB   
40/73 KB   
42/73 KB   
44/73 KB   
46/73 KB   
48/73 KB   
50/73 KB   
52/73 KB   
54/73 KB   
56/73 KB   
58/73 KB   
60/73 KB   
62/73 KB   
64/73 KB   
66/73 KB   
68/73 KB   
70/73 KB   
72/73 KB   
73/73 KB   
           
Uploaded: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-javadoc.jar (73 KB at 188.7 KB/sec)
Uploading: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-sources.jar
2/21 KB    
4/21 KB   
6/21 KB   
8/21 KB   
10/21 KB   
12/21 KB   
14/21 KB   
16/21 KB   
18/21 KB   
20/21 KB   
21/21 KB   
           
Uploaded: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgjpeek-1001/org/jpeek/jpeek/0.2/jpeek-0.2-sources.jar (21 KB at 51.8 KB/sec)
[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "orgjpeek-1001".

Waiting for operation to complete...
........

[INFO] Remote staged 1 repositories, finished with success.
[INFO] 
[INFO] --- nexus-staging-maven-plugin:1.6.7:release (jcabi-deploy-to-sonatype) @ jpeek ---
[INFO]  + Using server credentials "oss.sonatype.org" from Maven settings.
[INFO]  * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.14.5-02 and edition "Professional"
[INFO] Releasing staging repository with IDs=[orgjpeek-1001]

Waiting for operation to complete...
........

[INFO] Released
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:56 min
[INFO] Finished at: 2017-10-18T22:09:32+00:00
[INFO] Final Memory: 96M/537M
[INFO] ------------------------------------------------------------------------
+ mv /home/r/repo .
++ whoami
+ chown -R root repo
+ '[' -n '' ']'
++ whoami
+ sudo chown -R rultor repo
+ cd repo
+ git checkout __rultor
Already on '__rultor'
+ git tag 0.2 -m '0.2: tagged by rultor.com'
+ git reset --hard
HEAD is now at 0733693 0.2
+ git clean -fd
+ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
+ git branch -D __rultor
Deleted branch __rultor (was 0733693).
+ git push --all origin
To git@github.com:yegor256/jpeek.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'git@github.com:yegor256/jpeek.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
container 0f59b4c3bd84cd77aba68500ba2b6252cc3f14b69a13aa41052d15b6a6aa90d9 is dead
Thu Oct 19 00:10:05 CEST 2017

@yegor256
Copy link
Member Author

@rultor release, tag is 0.2

@rultor
Copy link
Collaborator

rultor commented Oct 18, 2017

@rultor release, tag is 0.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Oct 18, 2017

@rultor release, tag is 0.2

@yegor256 Oops, I failed. You can see the full log here (spent 10min)

[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.2/jpeek-0.2-jar-with-dependencies.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.2/jpeek-0.2-sources.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.2/jpeek-0.2.pom'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.2/jpeek-0.2-javadoc.jar'
[ERROR] 
[ERROR] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:14 min
[INFO] Finished at: 2017-10-18T22:23:29+00:00
[INFO] Final Memory: 89M/537M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:release (jcabi-deploy-to-sonatype) on project jpeek: Could not perform action: there are failing staging rules! Staging rules failure! -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:release (jcabi-deploy-to-sonatype) on project jpeek: Could not perform action: there are failing staging rules!
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not perform action: there are failing staging rules!
	at org.sonatype.nexus.maven.staging.workflow.AbstractStagingActionMojo.execute(AbstractStagingActionMojo.java:65)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 20 more
Caused by: com.sonatype.nexus.staging.client.StagingRuleFailuresException: Staging rules failure!
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV3ServiceImpl.monitorRepositoryTransition(StagingWorkflowV3ServiceImpl.java:272)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl.monitorRepositoryTransition(StagingWorkflowV2ServiceImpl.java:407)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl$10.perform(StagingWorkflowV2ServiceImpl.java:281)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl$10.perform(StagingWorkflowV2ServiceImpl.java:276)
	at com.sonatype.nexus.staging.client.internal.ExceptionConverter.runAndReturn(ExceptionConverter.java:38)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl.releaseStagingRepositories(StagingWorkflowV2ServiceImpl.java:275)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV3ServiceImpl.releaseStagingRepositories(StagingWorkflowV3ServiceImpl.java:91)
	at org.sonatype.nexus.maven.staging.workflow.ReleaseStageRepositoryMojo.doExecute(ReleaseStageRepositoryMojo.java:55)
	at org.sonatype.nexus.maven.staging.workflow.AbstractStagingActionMojo.execute(AbstractStagingActionMojo.java:55)
	... 22 more
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
container c483f95af2d549375ac49c10a014d572b9e05efdc68b891a55816f897148908f is dead
Thu Oct 19 00:23:59 CEST 2017

@0crat
Copy link
Collaborator

0crat commented Oct 18, 2017

Oops! There is no order for job gh:yegor256/jpeek#6.

@0crat
Copy link
Collaborator

0crat commented Oct 18, 2017

Oops! Job gh:yegor256/jpeek#6 was not in scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yegor256 @rultor @0crat