roikkuf / gwtsecurity

Automatically exported from code.google.com/p/gwtsecurity
0 stars 0 forks source link

Add GwtSecurity to the Maven Central Repository #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What do you think about having the project added to the Maven Central 
Repository?  I have had some experience in this and could refactor the project 
to make use of the Sonatype servers located at http://oss.sonatype.org.

Basically you deploy your project to the Sonatype servers and then they 
synchronize with the Central Repo.

This would require us to change the pom to reflect the hosting location.  
Something like this:

<groupId>com.google.code</groupId>
<artifactId>gwtsecurity</artifactId>
<version>1.1.0</version>

I would also probably recommend changing the package definitions to reflect the 
changes to the groupId and artifactId.

What do you think?

Original issue reported on code.google.com by steven.j...@gmail.com on 9 Jun 2011 at 7:12

GoogleCodeExporter commented 8 years ago
I would like to add this project to public maven server, but I have no 
experience  about this.
And GWT integrate Spring using gwt-sl & spring4gwt, both of them not provide 
maven pack.
That is why I put them all into private maven repository.

Original comment by kent.yeh...@gmail.com on 10 Jun 2011 at 12:51

GoogleCodeExporter commented 8 years ago
Only the gssDemo2 and gssDemo3 have these dependencies.  I would suggest not 
deploying the Gwt4ssDemo package at all, just leave it in the source as example 
code.

Since the gwtsecurity package doesn't depend on these it shouldn't be a problem 
deploying it to the main repo.

I will create a branch and give it a shot.  We'll see how it goes.

Original comment by steven.j...@gmail.com on 10 Jun 2011 at 1:25

GoogleCodeExporter commented 8 years ago
I have created a new branch called maven-central.  I branched only the 
gwtsecurity project.  I changed the pom.xml to work with the sonatype oss and 
opened a ticket for inclusion into their repository.

Once we get included we deploy to their repo and they sync with the central 
repo.

Please check out the changes in the branch and let me know what you think.

Original comment by steven.j...@gmail.com on 10 Jun 2011 at 7:20

GoogleCodeExporter commented 8 years ago
I have received notice of our inclusion into the sonatype repository.  Once we 
deploy and promote our 1st release in the sonatype repository they will 
synchronize with the maven central repository.

Please take a look at the pom.xml and let me know what you think.  I had to 
change a number of the spring dependencies in order to be able to remove the 
<repository> tags which are discouraged for maven central.

Original comment by steven.j...@gmail.com on 13 Jun 2011 at 7:57

GoogleCodeExporter commented 8 years ago
Hi Steven. I catch strange error on checking out branch prepared for the 
maven-central. It's seems broken svn configuration for exceptions dirictory. 
What do you think about?
Also please contact with me via skype if you can.

Error on branch update:

In directory 
'W:\prj\gwtsecurity\gwtsecurity-maven-central\gwtsecurity\src\main\java\com\gwt\
ss\client\exceptions'
Can't open file 
'W:\prj\gwtsecurity\gwtsecurity-maven-central\gwtsecurity\src\main\java\com\gwt\
ss\client\exceptions\.svn\tmp\text-base\GwtSessionAuthenticationException.java.s
vn-base':

Original comment by ivane...@gmail.com on 15 Jun 2011 at 4:37

GoogleCodeExporter commented 8 years ago
Complete in version 1.1.0.

Fix required code refactoring and new maven pom.xml dependency.

<dependency>
    <groupId>com.google.code</groupId>
    <artifactId>gwtsecurity</artifactId>
    <version>1.1.0</version>
</dependency>

Original comment by steven.j...@gmail.com on 15 Jun 2011 at 9:48