Re: [sunxacml-devl] public maven repository containing sunxacml-2.0-M1

[Kaleb P. <kal...@gm...>]

Lennart,

That looks quite good to me an it eliminates the need for anybody to choose a specific mirror. I think it is a good move. Thank you for your work on this.

Is the desired goal to set up the deploy so that you can deploy to both the file shares as well as the maven repository at the same time?

--Kaleb


On Saturday, August 07, 2010 03:36:11 am Lennart Jütte wrote:
> I tried to publish (by calling mvn deploy) some artifacts to sf.net web hosting. It's as easy as setting up a directory in the htdocs directory (called maven) and fixing two lines is the pom (see attached  ).
> 
> I compiled a project with the following repository and dependency secions successfully:
> 
> <repository>
> 	<id>sunxacml-snapshots</id>
> 	<name>sunxacml Repository</name>
> 	<url>http://sunxacml.sourceforge.net/maven/snapshots/</url>
> 	<layout>default</layout>
> 	<snapshots>
> 		<enabled>true</enabled>
> 	</snapshots>
> </repository>
> 
> ...
> 
> <dependency>
> 	<groupId>net.sf.sunxacml</groupId>
> 	<artifactId>sunxacml</artifactId>
> 	<version>2.0-M2-SNAPSHOT</version>
> </dependency>
> 
> For setting up an assembly (read: zip or tar.gz) for sourceforge the maven assembly plugin may come in handy. The maven deploy-single Mojo is a way to publish everything to sf.net.
> But i don't have time to continue the work on this right now. I have to work on my thesis.
> 
> Cheers,
> Lennart
> 
> P.S.: I did not delete the files i published on the sf.net servers. Someone should delete /home/groups/s/su/sunxacml/htdocs/maven/ if we don't switch to this directory anytime soon.
> 
> Am 07.08.2010 um 09:53 schrieb Lennart Jütte:
> 
> > 
> > Am 06.08.2010 um 22:23 schrieb Farrukh Najmi:
> > 
> >> On 08/06/2010 04:09 PM, Lennart Jütte wrote:
> >>> Am 06.08.2010 um 22:04 schrieb Kaleb Pederson:
> >>> 
> >>> 
> >>>> On Friday, August 06, 2010 12:15:59 pm Farrukh Najmi wrote:
> >>>> 
> >>>>> On 08/06/2010 03:07 PM, Kaleb Pederson wrote:
> >>>>> 
> >>>>>> On Friday, July 30, 2010 11:47:31 am Lennart Jütte wrote:
> >>>>>> 
> >>>>>> 
> >>>>>>>> The big change was on how to reference the m2 repo in other projects as
> >>>>>>>> you posted below. Thanks very much!
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>> But Kaleb is right: a project shouldn't reference a mirror directly. Maybe there's a better solution?
> >>>>>>> 
> >>>>>>> 
> >>>>>> Just a couple of days ago I stumbled across a project that was using svn to host their maven repository. They just created a "mavenrepo" directory along side branches and trunk.  Although it seems a bit strange, it is functional.
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>> That would be much worse than referencing a mirror IMHO.
> >>>>> 
> >>>> I don't think it's a good solution either, I just referenced it as an additional option since I hadn't seen anybody reference my original suggestion of using SF's web hosting.
> >>>> 
> >>> Oh, i didn't even see this suggestion or forgot about it just after reading.
> >>> 
> >>> +1!
> >>> 
> >>> 
> >>>> 
> >>>>> I think we
> >>>>> could simply use a variable with a default value referencing one mirror
> >>>>> and anyone can override it to use as a different mirror.
> >>>>> 
> >>>> I'm coming from the point of view of typical developer who only needs a binary.  That developer likely already has a pom to which he just needs to add a dependency (and maybe a repository). In that case, providing a pom with a variable doesn't really help
> >>>> 
> >>>> Is there a reason not to use SF's web hosting to host the maven repository? Using their web hosting you can manage all the uploads with ssh/scp using ssh keys and it acts as a standard web server, which is all that maven needs.
> >>>> 
> >>>> 
> >> 
> >> There is no reason not to use the SF's web hosting to host the maven 
> >> repository. The reason why I did it the current way was to have the 
> >> single mvn:deploy take care of the maven repo deployment as well as 
> >> publishing to the Files area in a single action. Seemed like less 
> >> headache to me.
> >> 
> > 
> > I'll try to find out if it's possible to deploy to two targets at the same time.
> > 
> > Maybe you have read what i've been thinking about:
> > 1) deploy jars, etc to web hosting
> > 2) deploy prepackaged zip (with docs) to file hosting. But this should only happen when a new non-SNAPSHOT release is coming out.
> > 
> >> If you guys would prefer to use the web hosting than I can support that 
> >> position. Thanks.
> >> 
> > 
> > 
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by 
> > 
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev 
> > _______________________________________________
> > sunxacml-devl mailing list
> > sun...@li...
> > https://lists.sourceforge.net/lists/listinfo/sunxacml-devl
> 
>