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.

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

Issue with jar packaging #479

Closed
mevivs opened this issue Dec 18, 2013 · 2 comments
Closed

Issue with jar packaging #479

mevivs opened this issue Dec 18, 2013 · 2 comments
Assignees
Milestone

Comments

@mevivs
Copy link
Collaborator

mevivs commented Dec 18, 2013

Current released jar structure

com
|_impetus
|__
_ client
|_____ core
|_____ kundera-parent
|_____ kundera-tests
|_____ kundera

It seems bit out of order and confusing. With 2.10 release onwards, this needs to be modified as per proposed structure(see below):

com
|impetus
|
___
_ kundera
|_______ parent
|_______ core
|_______ client
|_______ test

@ghost ghost assigned kkmishra Dec 18, 2013
@ghost ghost assigned mevivs Dec 30, 2013
@mevivs
Copy link
Collaborator Author

mevivs commented Jan 9, 2014

Fixed on current trunk

@mevivs
Copy link
Collaborator Author

mevivs commented Jan 9, 2014

groupId for artifacts has been changed from <groupId>com.impetus.client</groupId> TO <groupId>com.impetus.kundera.client</groupId>. For example:

        <dependency>
            <groupId>com.impetus.client</groupId>
            <artifactId>kundera-cassandra</artifactId>
            <version>2.10-SNAPSHOT</version>
        </dependency>

TO

        <dependency>
            <groupId>com.impetus.kundera.client</groupId>
            <artifactId>kundera-cassandra</artifactId>
            <version>2.10-SNAPSHOT</version>
        </dependency>

@mevivs mevivs closed this as completed Jan 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants