[Geoserver-devel] Publishing geocss jars to the local maven repo

Hi David,
I have a question about interactively testing changes I may be making to geocss.
Of course I do start with some kind of test, but eventually I’d like to see the new
jar also be used by GeoServer, and it seems that sbt out of the box can only
publish to the local Ivy repo.

Normally how do you make the GeoCSS jars available to a GeoServer running
either in the IDE or to a command line maven build?

Cheers
Andrea

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


On Tue, Aug 20, 2013 at 5:56 PM, Andrea Aime
<andrea.aime@anonymised.com>wrote:

Hi David,
I have a question about interactively testing changes I may be making to
geocss.
Of course I do start with some kind of test, but eventually I'd like to
see the new
jar also be used by GeoServer, and it seems that sbt out of the box can
only
publish to the local Ivy repo.

Normally how do you make the GeoCSS jars available to a GeoServer running
either in the IDE or to a command line maven build?

Ah, another weird detail: the sbt publish-local command builds a 0.8.1 jar,
and
yet geoserver css depends on version 0.8.2

However, I'm sure I have an up to date checkout...

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

I just alter the build file (project/Build.scala) and change the publishTo setting on line 15.

@@ -12,7 +12,7 @@ object GeoScript extends Build {
scalaVersion := “2.10.0”,
scalacOptions ++= Seq(“-feature”, “-deprecation”, “-Xlint”, “-unchecked”),
javacOptions ++= Seq(“-source”, “6”),

  • publishTo := Some(Resolver.file(“file”, file(“release”)))
  • publishTo := Some(Resolver.file(“file”, new File(Path.userHome.absolutePath+“/.m2/repository”)))
    )

val common =

With this modification in place I run the ‘sbt publish’ command and the jars and a generated pom are placed into the maven cache.

Sometimes rather than make changes I don’t want to commit, I instead run the ‘sbt publish’ command with the normal setting and rsync the results into the maven repo instead.

···

On Tue, Aug 20, 2013 at 11:56 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi David,
I have a question about interactively testing changes I may be making to geocss.
Of course I do start with some kind of test, but eventually I’d like to see the new
jar also be used by GeoServer, and it seems that sbt out of the box can only
publish to the local Ivy repo.

Normally how do you make the GeoCSS jars available to a GeoServer running
either in the IDE or to a command line maven build?

Cheers
Andrea

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it



Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

It appears I have some unpushed changes. I should be able to update the github repo later today. In the meantime, you can include any setting you like at the command line, like:

sbt ‘set version := “0.8.2”’ publish

···

On Tue, Aug 20, 2013 at 12:02 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, Aug 20, 2013 at 5:56 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:


Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Hi David,
I have a question about interactively testing changes I may be making to geocss.
Of course I do start with some kind of test, but eventually I’d like to see the new
jar also be used by GeoServer, and it seems that sbt out of the box can only
publish to the local Ivy repo.

Normally how do you make the GeoCSS jars available to a GeoServer running
either in the IDE or to a command line maven build?

Ah, another weird detail: the sbt publish-local command builds a 0.8.1 jar, and
yet geoserver css depends on version 0.8.2

However, I’m sure I have an up to date checkout…

Cheers

Andrea

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


On Tue, Aug 20, 2013 at 6:03 PM, David Winslow <dwinslow@anonymised.com> wrote:

I just alter the build file (project/Build.scala) and change the publishTo
setting on line 15.

@@ -12,7 +12,7 @@ object GeoScript extends Build {
       scalaVersion := "2.10.0",
       scalacOptions ++= Seq("-feature", "-deprecation", "-Xlint",
"-unchecked"),
       javacOptions ++= Seq("-source", "6"),
- publishTo := Some(Resolver.file("file", file("release")))
+ publishTo := Some(Resolver.file("file", new
File(Path.userHome.absolutePath+"/.m2/repository")))
     )

   val common =

With this modification in place I run the 'sbt publish' command and the
jars and a generated pom are placed into the maven cache.

Sometimes rather than make changes I don't want to commit, I instead run
the 'sbt publish' command with the normal setting and rsync the results
into the maven repo instead.

Wondering, any way to pass a variable from the sbt build command into that
scala file, so that we can publish to the local m2 repo without
altering the build files?
Something like sbt publish-local -Dtarget=m2_local

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------